A report that lists the general ledger updates that credit the payroll allocation account for posted project hours, per project for a ledger date range.
Project management and accountingInquiries and reportsGeneral ledger reconciliation reports
output:ProjListLedgerUpdatesPayroll
Business process
Manage project financials
Menu item
output:ProjListLedgerUpdatesPayroll
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone
1What it is and why
What it is
A report that lists the general ledger updates that credit the payroll allocation account for posted project hours, per project for a ledger date range.
What you do here
Use it to see the vouchers behind the payroll allocation account before you reconcile it.
Example
For October 2026 BEAT's project accountant sees 1,531.00 hours with 61,240.00 credited to payroll allocation account 515900, of which PRJ-0042 carries 1,240.00.
The page in Dynamics 365. page title tab to open what to set or check
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 it
After hour transactions for the period are posted, to review the payroll allocation entries they made in the ledger.
How often
On demand, at period close.
What the output shows
Every hour posted with Post costs - hour set to Balance or Profit and loss credits the payroll allocation account; hours under No ledger or Never ledger make no update here. The report changes nothing; it only lists amounts.
First ledger date of the postings to include.Checked in Dynamics 365
2026-10-01
To date
Last ledger date of the postings to include.Checked in Dynamics 365
2026-10-31
Project view
Groups the rows of the report, for example by project.Checked in Dynamics 365
Project
Project level
How many levels of subprojects are shown; 0 shows the project level as grouped.Checked in Dynamics 365
0
Skip zero
Leave out rows whose amounts are zero.Checked in Dynamics 365
Yes
Common errors and fixes
Message
What to do
A posted transaction has no payroll allocation ledger update.
Check its ledger date against the range and the cost and revenue profile of the project: with No ledger the cost is posted later by Post costs, with Never ledger never. Microsoft Learn
Use the ledger date range of the period and group by Project so that each voucher can be traced to one project.The report lists the ledger updates of payroll allocation postings; grouping by project lets you match them with the project reports of the same family.
On the live system, Project manager, Project supervisor, Chief executive officer and Chief financial officer can run this page.
Checked in Dynamics 365
Solution architect
5Design impact
Shared or per company
Per legal entity: the report reads only the project data of the company you are signed in to, so run it in each company you close. Checked in Dynamics 365
Can it be undone
Reversible: the report changes no data: The payroll allocation ledger updates report only reads data; it changes nothing. Microsoft Learn
If you change it later
Every hour posted with Post costs - hour set to Balance or Profit and loss credits the payroll allocation account; hours under No ledger or Never ledger make no update here. Microsoft Learn
Technical architect
6Technical
Menu item
output:ProjListLedgerUpdatesPayrollChecked in Dynamics 365
Form
SysOperationTemplateFormChecked in Dynamics 365
Roles to set it up and use it
To use itProject manager ProjProjectManagerProject supervisor ProjProjectSupervisorChief executive officer CompanyChiefExecutiveOfficerChief financial officer CompanyChiefFinancialOfficerGive people one of these roles. On this system, 4 roles can run this page.Checked in Dynamics 365
Load order: Ledger updates - payroll allocation has no data entity in Data management: the menu item ProjListLedgerUpdatesPayroll opens a report that only reads posted project data. There is nothing to migrate for the report itself; load the project data it reads, for example opening balances through Journals > Beginning balance, then run the report in the new system and compare its totals with the old one.Checked in Dynamics 365