Test Matrix
Use this matrix to validate Payables Agent configuration before pilot or production rollout.
Test with representative supplier invoices, including matched invoices, unmatched invoices, service invoices, utility invoices, multipage invoices, and regional invoice variants.
| Test area | Objective | Test activities | Expected result |
|---|---|---|---|
| Invoice submission | Verify invoices are received and ingested. | Submit invoices through the configured submission channel. Verify email forwarding and review the documents in Invoice Document Streams. | Documents appear in Streams, file names display correctly, stream classification is correct, and processing begins successfully. |
| Invoice recognition | Validate extraction of invoice attributes. | Review header attributes such as supplier, supplier site, invoice number, invoice date, invoice amount, currency, Business Unit, payment terms, and requester. Review line attributes such as description, quantity, unit price, line amount, purchase order number, and ship-to location. | Required attributes are populated, suppliers are identified correctly, invoice totals are accurate, and purchase orders are identified correctly. |
| Business Unit derivation | Validate Business Unit assignment logic. | Submit invoices for each configured derivation method, such as purchase-order-based derivation, supplier-site derivation, sender email derivation, recipient email derivation, or routing-attribute derivation. | Business Units are assigned correctly, routing acts as expected, and no manual Business Unit correction is required. |
| Invoice creation | Validate invoice creation behavior. | Process complete invoices, incomplete invoices, matched invoices, unmatched invoices, service invoices, and utility invoices. | Invoice status is correct, invoice lines are created correctly, and tax and freight handling behave as configured. |
| Exception handling | Validate invoice exception management. | Create scenarios with missing supplier information, missing invoice numbers, invalid purchase orders, missing required attributes, Business Unit derivation issues, and policy violations. | Exceptions and policy violations are visible, routing occurs correctly, users can access assigned invoices, and corrective actions can be performed. |
| Invoice correction | Validate correction workflows. | Correct invoice numbers, suppliers, purchase orders, dates, invoice amounts, and line information. | Corrections are saved, invoice status updates correctly, and processing continues successfully. |
| Adaptive learning | Validate learning behavior. | Process an invoice with recognition errors, correct the invoice, save the correction, and submit another invoice with the same layout. | Corrections are retained, recognition improves, and manual intervention decreases for future invoices with the same layout. |
| Bulk learning and reprocessing | Validate propagation of applicable learning. | Prepare multiple incomplete invoices with the same fingerprint. Correct one invoice in Invoice Document Training or the Edit Invoice page and review the remaining invoices. | The correction is stored against the fingerprint and applied only to other incomplete invoices where the application determines that it is applicable. Unrelated invoices aren’t changed. |
| Invoice Document Training | Validate onboarding of new invoice layouts. | Upload representative invoice samples, review extracted attributes, correct recognition issues, and save training results. | Training completes successfully, fingerprints are generated, and future invoices benefit from training. |
| Invoice Completion | Validate policy-based attribute defaulting. | Import invoices that meet and don’t meet each policy condition. Test invoices where the target field is blank and where it already contains a value. | The target attribute is populated only when the policy condition is met and the target is blank. Existing values aren’t overridden. |
| Invoice Completion prerequisites | Validate required source-and-target dependencies. | Test policies for Distribution Set, Project, Expenditure Type, Project Organization, Distribution Account, and Global Descriptive Flexfields using the required source attributes. | Policies execute only when required source attributes are available and generate valid target values. |
| Anomaly controls | Validate anomaly identification. | Submit invoices that trigger configured currency, remittance-bank-account, high-amount, fraudulent-invoice, or duplicate-invoice criteria. Also submit invoices that fall within normal criteria. | Invoices meeting configured criteria are marked for review. Invoices outside the criteria continue without being marked as an anomaly. |
| Invoice Document Streams | Validate operational visibility. | Search documents, filter results, review processing status, and verify statuses such as Processing, Pending Review, Pending Approval, Completed, and Invalid File. | Users can monitor inbound documents, identify processing status, and locate documents requiring attention. |
| Invoice List | Validate exception-management functionality. | Search and filter invoices, review invoice details, policy violations, anomalies, and rejected invoices. | Users can manage invoice exceptions from Invoice List and see only invoices for authorized Business Units. |
| Routing rules | Validate incomplete-invoice routing. | Generate invoices that require manual review and confirm workflow behavior. | Workflow notifications are generated, the correct users receive assignments, and assigned users can access the invoices. |
| Reporting | Validate tracking and recognition reporting. | Run the Invoice Documents Recognition Tracking Report and the Invoice Documents Recognition Rate Report. | Submitted invoices appear in reporting, processing status is accurate, import status is correct, and recognition rates can be reviewed. |
| Home page | Validate Home page inquiry and prompt behavior. | Submit a free-form question and each predefined prompt with complete and partial parameters. | The Agent returns the appropriate invoice population and opens the related chat-and-canvas context. |
| Top Insights | Validate Top Insights navigation. | Open an insight from the Home page and select View All. | The user reaches the insight detail or full Insights experience permitted by security. |
| Insight lifecycle | Validate insight lifecycle actions. | Mark an insight reviewed, dismiss it, and reopen it. | Status and comments are retained, and the enabled action is reflected in the Insights page. |
| Monitoring prompts | Validate monitoring prompt management. | Review, enable, disable, and clone a predefined prompt using an authorized user. | Only supported execution settings are editable; predefined conditions remain read-only. |
| Instruction documents | Validate instruction-document extraction and review. | Upload a Word, text, or PDF instruction document. | Instructions are extracted for review and can be edited before application. |
| Annotation learning | Validate annotation-based learning. | Correct a PDF or image invoice through annotation. | The corrected value is saved and reused for an applicable document fingerprint. |
| Invoice List query | Validate natural-language invoice queries. | Enter a natural-language invoice request. | The canvas displays authorized records that match the request. |
| Invoice actions | Validate invoice and exception actions. | Validate or cancel a test invoice and override a test anomaly or release a test hold. | The action follows security and state rules and is recorded in the audit trail. |
| Capture endpoints | Validate endpoint visibility and stream actions. | Open Document Receiving Endpoints and review the required supplier-invoice and payment-request endpoints. Open the Invoice Image Documents stream and review the available stream actions. | Required supplier-invoice and payment-request endpoints and stream-specific actions are available. |
Bulk learning stores corrections against the document fingerprint and propagates them only to applicable invoices with the same fingerprint, including incomplete Payables invoices. Invoice Completion policies apply during import, don't override populated fields, and require defined source-target dependencies for specific attributes.