Use the NLP-Based Chat-Assisted Invoice List

The Invoice List is a multipane workspace with a NLP-based chat assistant on one side and an interactive data canvas on the other.

Users describe the invoice population they need in natural language, and the Agent displays the matching records on the canvas.

A query is required to populate the canvas. Users can start a new search by entering a new independent request rather than clearing traditional filters.

Once results are displayed, users can select the invoice number to open the Edit Invoice or View Invoice page according to their security access. When they return to the Invoice List, the original query context remains available on the canvas.

Invoice-level actions

Supported invoice-level actions include:

• Validate Invoice: Run invoice validation and related compliance checks.
• Cancel Invoice: Stop processing an invoice confirmed to be invalid, fraudulent, or a duplicate.

Exception-level actions

An invoice can have more than one anomaly or hold. Open the panel drawer and use the Anomalies and Holds tabs to review and resolve each exception individually.

• Override Anomaly: Release a specific anomaly when the reviewer determines that it shouldn't block processing.
• Release Hold: Release a user-releasable hold so the invoice can continue processing.

To resolve an exception:

1. Open the invoice panel drawer.
2. Select the Anomalies or Holds tab.
3. Select the individual exception.
4. Enter a reason or comment when required.
5. Confirm the action.

Manual overrides and hold releases are recorded in the invoice audit trail with the user identity.

Correct rejected invoices

1. Ask the Agent to display the required rejected invoices.
2. Select Open Correction Spreadsheet from the populated canvas.
3. Review the records in the VBAF workbook.
4. Correct the Header and Line worksheets.
5. Upload the changes.
6. Run the Payables Invoice Import process to reprocess the corrected invoices.

Oracle Visual Builder Excel Add-in must be installed to use the workbook.

Don't use the conversational Agent to clear exceptions in bulk. Review and resolve anomalies and holds individually.

Invoice List Scope and Action Behavior

When users drill down from Invoice Document Streams, the Invoice List canvas initially displays the invoices related to the selected document. Users can then ask the Agent to expand or refine the population, such as displaying successfully processed invoices or invoices that require manual intervention.

The Invoice List displays active invoices and invoices formally rejected by the Invoice Import process. Interface invoices that are waiting for the Invoice Import process to run aren’t displayed.

Invoice-level actions have the following behavior:

• Validate Invoice: Runs invoice validation, policy verification, and applicable compliance checks. When anomalies are identified, the invoice is marked. When validation completes without issues, the invoice status is updated according to the completed processing outcome.
• Cancel Invoice: Permanently stops processing for an invoice confirmed to be invalid, fraudulent, or a duplicate. The invoice status changes to Cancelled, and the invoice doesn’t continue through recording or payment processing.

Exception-level actions have the following behavior:

• Override Anomaly: Releases a selected application-generated anomaly, such as a confirmed false positive. The invoice can resume processing after all other blocking exceptions are resolved.
• Release Hold: Clears a selected user-releasable hold so the invoice can continue through the standard processing flow.

The Open Correction Spreadsheet action is context-dependent. It is available when the canvas displays invoices rejected by Invoice Import and isn’t intended for active invoices. When opened, the VBAF workbook downloads the selected rejected invoices based on the active dataset displayed on the canvas.

Users with read-only access can open invoice-number links and review invoice details but can’t perform overrides, cancellations, hold releases, or other update actions. Users performing these actions require the applicable edit or management access.

Traditional saved filters and static custom views aren’t required in the conversational workspace. To begin a separate search, enter a new independent request in the Agent pane.