Testing Prerequisites
Before testing begins, verify the following activities have been completed.
Configuration Readiness
Verify:
- Payables Agent is activated.
- Document Recognition and Processing Options are configured.
- Invoice submission channels are operational.
- Business Unit derivation is configured.
- Routing rules are configured.
- Invoice Completion policies are configured, if applicable.
- Anomaly controls are configured and activated, if applicable.
Security Readiness
Verify:
- User access is provisioned.
- Business Unit security is configured.
- Permission group policies have been processed.
- Users who manage or review Compliance & Control have the required privileges.
Synchronization Readiness
Verify:
- Supplier synchronization has completed.
- Purchase order synchronization has completed.
Oracle recommends waiting at least 24 hours after activation before beginning invoice testing.
Test Invoice Readiness
Collect representative invoices from major suppliers.
Recommended minimum:
- 20 invoices from each major supplier
- Top 10–20 suppliers
- Multiple invoice layouts where available
Include:
- Matched invoices
- Unmatched invoices
- Service invoices
- Utility invoices
- multipage invoices
- Regional invoice variants
- Invoices that meet Invoice Completion policy conditions
- Invoices that don't meet Invoice Completion policy conditions
- Invoices that trigger each configured anomaly control
- Invoices that shouldn't trigger configured anomaly controls
- Multiple incomplete invoices with the same fingerprint for bulk-reprocessing validation
Invoice Completion rules should be tested in a controlled environment before wider rollout. Policies populate a target attribute only when the field is blank and apply during invoice import.