Operational Governance

Define clear ownership for Payables Agent configuration, security, training, monitoring, policies, controls, and continuous improvement.

Area	Recommended owner	Responsibility
Configuration	Payables Administrator	Maintain Payables Agent setup, invoice-submission channels, routing rules, and configuration changes.
Security	Security Administrator	Maintain privileges, roles, permission groups, and Business Unit data access.
Training	Accounts Payable Operations Team	Manage layout onboarding, training review, learning validation, and training quality control.
Recognition monitoring	Accounts Payable Supervisor	Review recognition metrics, exception trends, supplier performance, and correction volumes.
Reporting	Accounts Payable Operations Team	Run and review recognition-tracking and recognition-rate reports.
Invoice Completion policies	Authorized Payables Administrator or Business Process Owner	Define, test, approve, maintain, and retire Invoice Completion policies. Ensure each policy has a clear business purpose and supported source-and-target attributes.
Anomaly controls	Authorized Control Owner or Business Process Owner	Select anomaly patterns, define criteria, review false positives, approve changes, and periodically reassess thresholds and historical periods.
Bulk learning review	Accounts Payable Operations Team	Confirm that propagated corrections affect only applicable invoices and investigate invoices that still require manual correction.
Continuous improvement	Process Owner	Prioritize improvement actions and coordinate supplier, master-data, training, policy, control, and process changes.

Compliance & Control supports Invoice Completion and anomaly detection through natural-language policy configuration and should be governed through restricted access and controlled change procedures.

Compliance and Control Policy Governance

Use the following practices when governing Compliance and Control policies:

• Upload clear, current, and approved policy documents.
• State business conditions, exceptions, and required outcomes explicitly in the policy document.
• Include the specific values required for Policy Details, such as account combinations, tax determinants, project attributes, or control thresholds.
• Review generated Policies and Policy Details before activating them.
• Keep policy documents aligned with current business processes and regulatory requirements.
• Use Invoice Completion policies to derive missing invoice attributes.
• Use Control policies to identify anomalies and validate invoices against purchase orders or receipts.
• Define clear ownership for reviewing invoices marked by Control policies.
• Update or replace policies when business rules, organizational structures, or compliance requirements change.

Avoid the following practices:

• Don't upload draft, outdated, conflicting, or unapproved policy documents.
• Don't rely on implied business knowledge. Document the intended condition and outcome explicitly.
• Don't use ambiguous terms such as “high value,” “appropriate account,” or “when necessary” without defining the applicable criteria or values.
• Don't activate generated rules without confirming that the generated logic reflects the intended policy.
• Don't introduce rules that conflict with existing accounting, tax, procurement, or approval requirements.
• Don't assume a policy applies only to selected invoices unless its conditions explicitly limit the scope.
• Don't ignore invoices marked by Control policies. Investigate and resolve exceptions according to the organization’s review process.
• Don't leave inactive, duplicate, or superseded policies in place without appropriate governance.