Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
Use audit policies to check expense reports, vendor invoices, and purchase orders. Make sure they follow the policy rules you create. The system runs all the rules for an audit policy in batch mode, following the schedule you set. Each policy rule belongs to a policy rule type. For each policy rule type, only one policy rule can be active at a time.
Queries and query types
When you create an audit policy rule, you first select a policy rule type. The policy rule type specifies the Application Object Tree (AOT) query to use as the starting point for creating the policy rule. It also specifies the query type to use for the policy rule. The query determines the source document that the policy rule evaluates. It also specifies the fields in the source document that identify both the legal entity and the date to use when documents are selected for audit. The query type controls the default fields in the query page and in the Audit policy rule page. The following table shows the query types that are available for audit policy rules.
| Query type | Purpose | More information |
|---|---|---|
| Conditional | Evaluate source document attributes against specified values. | |
| Aggregate | Evaluate multiple source documents or source document lines against a policy rule by aggregating numeric values. | |
| Sampling | Randomly select a specified percentage of the source documents to evaluate for policy violations. | When you select this option, use the Audit policy rule page to specify the percentage of documents to randomly select for audit. |
| Duplicate | Evaluate source documents to determine whether they contain duplicate entries in specified fields. | When you select this option, use the Audit policy rule page to specify the number of days to add to the start of the document selection date range when evaluating documents for duplicate entries. |
| List search | Evaluate source documents for specific entities. | The root document of the query defines the document that's being audited. The query must be a list query that includes a reference to the dirpartytable table. You can use this option only with the following AOT queries:
|
| Keyword search | Evaluate source documents to determine whether they contain certain words. | When you select this option, enter the words to look for in the Audit policy rule page. The Audit policy rule page also includes options that you can use to specify the tables and fields to evaluate for the words you entered. |
Common parameters
All policy rules for a particular audit policy share the same batch parameters and the same document selection date range. Specify these parameters for the policy in the Additional options page.
Additional resources
Audit policy violations and cases Define audit policies for source documents