Setup step on the Audit policies page · Audit workbench
Set up Audit policies
Use this page to create audit policies, add policy rules to them, test the rules, and run the policy in batch for a document date range so that violations become audit cases.
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 setup page where you define audit policies: the organizations each policy applies to and the policy rules it checks completed expense reports, purchase orders, and vendor invoices against.
What you do here
Use this page to create audit policies, add policy rules to them, test the rules, and run the policy in batch for a document date range so that violations become audit cases.
Example
For example, a policy can flag employees whose hotel expenses on expense reports total more than 2,000.
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.
Setup steps on this page
Set up Audit policies
Use this page to create audit policies, add policy rules to them, test the rules, and run the policy in batch for a document date range so that violations become audit cases.
Steps from Microsoft
Go to Audit workbench > Setup > Audit policies.
Select New and enter a name.
In the Policy organizations section, select each organization and select Add.
In the Policy rules section, select a policy rule and select Create policy rule.
Enter the effective date, set the filter criteria, and select OK.
Select Test, enter the document selection dates, and select Run test.
Select Additional options, enter the starting and ending dates, and run the policy in batch.
Run each policy in batch on back-to-back document selection date ranges, with no gaps and no overlaps, after testing each rule with TestBatches expect no gap with earlier batches: a gap leaves documents unchecked and an overlap double-counts them. The system warns when you change batch dates but doesn't correct them.
Hard to reverse: Rules are effective-dated and can be changed, but cases already generated by a run stay and must be handled through case management.
If you change it later
A run uses the version of each policy rule, and the organizations linked to the policy, that are effective on the last day of the document selection date range. Batch date ranges that overlap count documents twice, and gaps leave documents unchecked. Microsoft Learn
Technical architect
6Technical
Menu item
AuditPolicyDetailsChecked in Dynamics 365
Form
SysPolicyListPageChecked in Dynamics 365
Table
SysPolicyShown as “POLICY” in Record infoKey field: NameChecked in Dynamics 365
To set it up or change itAuditor AuditPolicyManagerTo use itFinancial controller LedgerFinancialControllerGive people one of these roles. On this system, 2 roles can open this page.Checked in Dynamics 365
Actions on the page
(Action Pane without tabs): Edit, Retire policy, Parameters, Additional optionsChecked in Dynamics 365