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 payments for a pay run are issued, so the payroll team can review the payment data and sign off on the run.
How often
Every pay period.
What the output shows
The payments made to workers from pay statements in the pay cycle and range of periods, per worker. A payment missing or doubled usually means a pay statement was reversed, submitted twice, or belongs to another payment run type.
The first and last pay period in the range the report covers.Microsoft Learn
Print social security number
Whether workers' Social Security Numbers are printed on the report; Microsoft advises against it where possible.Microsoft Learn
Payment run type
Limits the report to payments from pay statements of the selected payment run types.Microsoft Learn
Batch number
Limits the report to payments from the selected pay statement generation runs.Microsoft Learn
Payment date
Limits the report to payments from pay statements with the selected payment dates.Microsoft Learn
Solution architect
4Design impact
Can it be undone
Nothing to undo: The worker payment register only reads payment data; it changes nothing. Microsoft Learn
Technical architect
5Technical
Menu item
PayrollWorkerPaymentRegisterChecked in Dynamics 365
Form
SysOperationTemplateFormChecked in Dynamics 365
Roles to set it up and use it
To use itPayroll administrator HcmPayrollAdministratorPayroll manager HcmPayrollManagerGive people one of these roles. On this system, 2 roles can run this page.Checked in Dynamics 365