SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone
1What it is and why
What it is
A periodic job that updates the payment information on expense reports after the employee has been paid through accounts payable.
What you do here
Use this job, usually as a recurring batch after payment runs, so expense reports show that they are paid.
Example
For example, after the Friday vendor payment run pays 45 employees, the job runs at night and the next morning the 45 expense reports show their payment details.
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 vendor payments that reimburse employees are posted.
How often
After each payment run, usually as a recurring batch.
Batch settings
Schedule it as a recurring batch that runs after the payment runs.
What the output shows
Updated payment information on expense reports. A paid report that still shows as unpaid usually means the job hasn't run since the payment was posted.
Schedule it as a recurring batch shortly after each payment run.Without it, employees can't see from the report that they were paid and ask accounts payable instead.
In this system Employee and Contractor enter their own expenses, and Expense administrator sets up the module and processes documents. The expense mobile app needs the Employee role, a company on the user account and a link to an employee with active employment. The expense administrator schedules this job. No Feature management feature is needed.
Per company: the job updates the expense reports of the legal entity it runs in. Checked in Dynamics 365
Can it be undone
Reversible: The job only refreshes payment information; run it again if payments change.
If you change it later
Posting an expense report creates the amount owed to the employee; the payment itself is made in accounts payable, and this job brings the payment details back to the report. Microsoft Learn
Technical architect
6Technical
Menu item
action:TrvExpPaymentDetailsBatchChecked in Dynamics 365
Form
DialogChecked in Dynamics 365
Data entities
TrvExpPaymentDetailsEntityExpense payment details (the payment details this job writes; the job itself has no entity) Microsoft data model
Roles to set it up and use it
To use itExpense administrator ExpenseAdministratorGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365
Load order: The job has no data entity in Data management, so it can't be loaded from a file or a configuration template. It processes data that is already in the system and keeps only its batch settings; set up and schedule it again in each environment.Microsoft Learn
Checked in a working Dynamics 365 system, version 10.0.49: the menu item, form, table and security, the page.
To cite this step: EM-JOB-050, Bring payment status back to expense reports. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/EM-JOB-050