Configure Compliance and Control Policies

Compliance & Control policies are uploaded from the Compliance and Control page and then reviewed, validated, and activated.

To configure policy details:

1. Open Payables > Configuration > Compliance and Control.
2. Open Policy Details.
3. Download the Policy Details to Excel.
4. Update the spreadsheet with the required target values for the applicable supported criteria.
5. Upload the completed spreadsheet.
6. Repeat validation until all errors are resolved.
7. Activate the configuration after all policy-detail validation errors are resolved.

Activation promotes the draft Policy and Policy Details to the active version. Only active policies are applied during invoice processing. Draft policies are retained for configuration review and the next activation cycle.

Policy Validation and Activation Behavior

Policy-level validation errors can occur when:

• A Policy Detail refers to an unavailable or inactive value.
• A Policy Detail omits a required supporting attribute. For example, Primary Ledger is required to derive an account combination.

Correct policy-level errors in the source policy document, upload the revised document to AI Studio, publish it, and repeat the policy review.

Policy-detail validation errors can occur when:

• A Policy Detail refers to a value that is unavailable or inactive.
• A Policy Detail omits a required supporting attribute. For example, Primary Ledger is required to derive an account combination.

Correct Policy Detail errors by downloading the Policy Details to Excel, updating the missing or invalid information, and uploading the corrected spreadsheet. Repeat validation until all errors are resolved.

When the configuration is activated, the draft Policy and Policy Details become the active version. The newly activated set replaces the previously active Policy and Policy Details configuration. Active policies are used during invoice processing and runtime evaluation. Draft versions are used to prepare the next configuration iteration and don't affect active invoice processing.

Invoice Completion Behavior

Invoice Completion policies can derive supported attributes in the following categories:

• Accounting
• Tax
• Project
• Asset
• Payment
• Localization

Create a separate policy for each target attribute. A policy populates the target attribute only when the field doesn't already contain a value. It doesn't override an existing value.

Some target attributes require specific source attributes:

• Distribution Set requires Business Unit.
• Project-related targets require Business Unit or Project, depending on the target.
• Distribution Account targets require Ledger.

Invoice Completion policies are applied during invoice import. They aren't applied to manually created invoices or invoices inserted directly into Payables base tables.

Anomaly Control Behavior

Available anomaly patterns include:

• Invoice Currency
• Remittance Bank Account
• High Invoice Amount
• Fraudulent Invoice
• Duplicate Invoice

For each applicable anomaly pattern, define the required historical period, variation threshold, or comparison attributes. A pattern isn't enforced until it is explicitly enabled.

Enable only the patterns required by the organization’s policies. Test and tune the criteria before broader deployment to reduce false positives and unnecessary review activity.

Runtime Sequence

Invoice Completion policies are evaluated first to populate supported missing invoice attributes. Control policies are then evaluated to identify anomalies and other policy deviations.

Invoice Completion policies run during invoice import. Anomaly policies run during import for imported invoices and during validation for invoices created through other supported channels.

Control Policy Evaluation

Compliance and Control policies are evaluated automatically during invoice processing. Individual users don't need to trigger policy evaluation for each invoice.

Invoice Completion policies are evaluated first to populate supported internal attributes that are missing. Control policies are then evaluated to identify anomalies and other policy deviations. Control policies can also validate invoice information against related purchase orders or receipts. Transactions that deviate from the active policy criteria are marked and isolated for review.

This evaluation applies the same active business rules consistently to the applicable invoice population rather than relying on one-time or sampled checks.