BeyondERP.Newsletter
Menu

Setup step on the Post all unposted Dynamics 365 for Project Service Automation integration journals page · Project management and accounting

Schedule posting of integration journals

Post imported actuals without opening each journal.

Business process
Manage project delivery
Menu item
action:ProjAdvancedJournalAutoPostBatch
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA legacy periodic job that posts every unposted integration journal in one run. It belongs to the Dynamics 365 Project Service Automation integration; Project Service Automation is a legacy application, and the current process posts the Project Operations integration journal.
What you do hereUse it only where project actuals still arrive through the integration journal: it posts all unposted journals, so the project subledger and the general ledger are updated without opening each journal.
ExampleAt BEAT, the import creates 12 integration journals for October 2026 with 1,846 lines of time and expense actuals. A nightly run of this job posts all 12, and the project accountant only opens the 1 journal that stays unposted because of a closed ledger period.
Post all unposted Dynamics 365 for Project Service Automation integration journals page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processManage project delivery
Menu pathProject management and accounting › Periodic › Journals › Post all unposted Dynamics 365 for Project Service Automation integration journals
Set up firstImport from staging table Microsoft Learn
Used next byProject invoice proposals Microsoft Learn
Related pagesIntegration journal Microsoft Learn Integration parameters Microsoft Learn
In this process Delete old posted project journals · Remind workers about missing timesheets
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itAfter each import of actuals into the integration journals.
How oftenDaily, as a recurring batch job that follows the import.
Batch settingsLearn notes that journals with more than 100 lines are always posted in batch.
What the output showsPosted integration journals, with project transactions in the subledger and vouchers in the general ledger. Journals with errors stay unposted.

Source: Microsoft Learn

Setup steps on this page

Schedule posting of integration journals

Post imported actuals without opening each journal.

Steps from Microsoft

  1. Go to Project management and accounting > Periodic > Journals > Post all unposted Dynamics 365 for Project Service Automation integration journals.
  2. Make sure Import from staging table has run first, so the latest actuals are in integration journals.
  3. Set the job up as a recurring batch job after the import, because it posts every unposted journal and has no selection fields.
  4. After each run, open Journals > Dynamics 365 for Project Service Automation integration journal and filter on unposted journals to find any that failed.
  5. Fix the cause in the failed journal, for example a closed period, and let the next run post it.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Run in the backgroundThe only tab on the dialog: the job has no selection fields and posts every unposted integration journal; set it up here as a recurring batch job.Checked in Dynamics 365Recurring every night at 02:00

Common errors and fixes

MessageWhat to do
A journal stays unposted after every run.A line fails validation, for example the accounting date is in a closed period or a financial dimension isn't valid. Correct the line or the setup; the next run posts it. Microsoft Learn

Test checklist

  1. Count the unposted integration journals before the run (for example 12).
  2. Run the job.
  3. Filter the integration journal list on unposted: only journals with errors remain (for example 1).
  4. Open Posted project transactions and find the lines of a posted journal.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Schedule posting of integration journalsRun it as a recurring batch job right after Import from staging table, and review unposted journals each morning.The job has no filters and posts everything that is valid, so timing it after the import keeps the ledger current.How are integration journals posted?Assuming every journal posted; journals with errors stay unposted and need a fix.Test: Post all unposted integration journals

Feature management and licence

Licence or add-inOn the live system, Project manager, Project accountant, Project assistant, Field Service Integration User and Shop supervisor use this page.

Checked in Dynamics 365

Solution architect

5Design impact

Shared or per companyPer company: the job posts the integration journals of the legal entity you run it in. Microsoft Learn
Can it be undoneIrreversible: Posted journals can only be corrected with adjustments.
If you change it laterPosting creates project subledger transactions and general ledger vouchers, which feed invoicing, revenue recognition and financial reports. Project Service Automation is legacy (no longer supported since March 31, 2025); new setups use the Project Operations integration journal. Microsoft Learn
Technical architect

6Technical

Menu itemaction:ProjAdvancedJournalAutoPostBatch Checked in Dynamics 365
FormDialog Checked in Dynamics 365
Roles to set it up and use itTo use itProject manager ProjProjectManagerProject accountant ProjProjectAccountantProject assistant ProjProjectClerkField Service Integration User FieldServiceIntegrationUserShop supervisor JmgShopSupervisorGive people one of these roles. On this system, 6 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:ProjAdvancedJournalAutoPostBatch
Data migrationLoad order: Post all unposted integration journals has no data entity in Data management: it is a periodic job and keeps no records of its own. Don't migrate unposted integration journals; post them in the old system or import the actuals again in the new one.Microsoft Learn
Everyone

8Sources

To cite this step: PM-JOB-020, Schedule posting of integration journals. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/PM-JOB-020