BeyondERP.Newsletter
Menu

Setup step on the Dynamics 365 for Project Service Automation integration journal page · Project management and accounting

Retire the Project Service Automation integration journal

Move actuals to the supported integration.

Business process
Manage project delivery
Menu item
ProjAdvancedJournal
Main table
ProjAdvancedJournal
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 isThe legacy integration journal for Dynamics 365 Project Service Automation: it holds the time, expense and fee actuals imported from Project Service Automation so they can be posted in Finance.
What you do hereUse it only where the old Project Service Automation integration still runs, to post the imported actuals; Project Service Automation reached end of support on 31 March 2025 and was replaced by Project Operations, whose actuals post through the Project Operations integration journal.
ExampleFor example, a company still finishing its move from Project Service Automation imports 312.00 hours of December actuals from the staging table into journal PSA-000045, checks the lines and posts it before switching to Project Operations.
Dynamics 365 for Project Service Automation integration journal 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

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.

Setup steps on this page

Retire the Project Service Automation integration journal

Move actuals to the supported integration.

Steps from Microsoft

  1. Go to Project management and accounting > Journals > Dynamics 365 for Project Service Automation integration journal.
  2. Run Periodic > Project Service Automation > Import from staging table first, so the synchronized actuals become journal lines.
  3. In the Show field, choose Draft and select the journal.
  4. Select Lines and check the project, category, quantity and amounts.
  5. Post the journal, or run Post all unposted Dynamics 365 for Project Service Automation integration journals in batch.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
StatusWhether the journal is still draft or posted.Checked in Dynamics 365Draft
Period start dateThe start of the period the journal groups actuals for.Checked in Dynamics 36501/12/2026
Original journalThe journal the lines came from when a journal was split or reposted.Checked in Dynamics 365PSA-000044
ShowChooses which journals to list, for example Draft.Checked in Dynamics 365Draft

Common errors and fixes

MessageWhat to do
No new journal lines appear after Project Service Automation synchronized actuals.Run Import from staging table; it moves the synchronized actuals from the staging table into this journal. Microsoft Learn

Test checklist

  1. Run Import from staging table after a synchronization.
  2. Open the journal filtered on Draft.
  3. Post it.
  4. Check the number of Draft journals drops and the lines show on Posted project transactions.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Retire the Project Service Automation integration journalPost all open journals here and move to Project Operations integrated with ERP, whose actuals post through the Project Operations integration journal.Project Service Automation is no longer supported in commercial cloud since 31 March 2025.Which integration journal posts external project actuals?Setting up this journal for a new implementation: new implementations use Project Operations and its integration journal.Test: Post the remaining PSA journals

Feature management and licence

Licence or add-inOn the live system, Project manager, Project accountant, Project assistant and Field Service Integration User use this page. Project Service Automation is a legacy application, no longer supported in commercial cloud since 31 March 2025.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer company: each legal entity has its own records. Microsoft data model
Can it be undoneHard to reverse: Posted actuals are corrected through adjustments.
If you change it laterPosting applies the accounting with the default financial dimensions and posting setup. For Project Operations integrated with ERP, actuals go to the Project Operations integration journal instead. Microsoft Learn
Technical architect

6Technical

Menu itemProjAdvancedJournal Checked in Dynamics 365
FormProjAdvancedJournal Checked in Dynamics 365
TableProjAdvancedJournalShown as “Project advanced journal” in Record infoChecked in Dynamics 365
Roles to set it up and use itTo set it up or change itProject manager ProjProjectManagerProject accountant ProjProjectAccountantProject assistant ProjProjectClerkField Service Integration User FieldServiceIntegrationUserMachine operator JmgMachineOperatorTo use itProject supervisor ProjProjectSupervisorChief executive officer CompanyChiefExecutiveOfficerGive people one of these roles. On this system, 8 roles can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=ProjAdvancedJournal
Data migrationLoad order: The Dynamics 365 for Project Service Automation integration journal has no data entity in Data management. Its lines come from the staging table through Import from staging table. Post the open journals before you switch to Project Operations; nothing is loaded into it.Checked in Dynamics 365
Table definitionProjAdvancedJournal columns and relations Microsoft data model
Everyone

8Sources