> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gocromo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review invoice exceptions

> Structure invoice data, identify exceptions, and prepare a controlled accounts-payable review.

This example helps an accounts-payable team identify invoices that need attention while keeping payment decisions under explicit human control.

## Outcome

The team wants to find:

* invoices missing required fields;
* possible duplicates;
* invoices without a purchase-order match;
* overdue invoices;
* amounts that exceed review thresholds;
* the next action and responsible owner.

## Add the business context

Create an **Accounts Payable** Project and add:

* invoice review and payment policies as Sources;
* reviewed Knowledge pages for required evidence, thresholds, and exceptions;
* an **Invoices** table;
* a **Suppliers** table when supplier details need structured tracking.

Useful invoice fields include supplier, invoice number, purchase order, invoice date, due date, currency, subtotal, tax, total, status, exception type, owner, and next action.

## Import and inspect data

Upload a representative CSV to chat or add records to the Invoices table. Before automating, ask Cromo to inspect the field mapping and report rejected or ambiguous rows.

## Prompt to try

```text theme={null}
Review the open invoices in the Invoices table using our invoice review policy.

For each exception:
- identify the invoice and supplier;
- classify the exception;
- explain the rule with a policy citation;
- show the relevant amount and dates;
- recommend an owner and next action;
- distinguish confirmed duplicates from possible duplicates.

Return a review table. Do not change payment status and do not initiate payment.
```

## Verify the review

Manually check a sample from every exception category. Pay particular attention to:

* invoice numbers with different punctuation;
* credit notes and corrected invoices;
* currency and tax treatment;
* duplicate amounts from the same supplier;
* threshold boundaries;
* invoices already resolved outside Cromo.

## Capture the routine

Create a Process Skill named **Review an invoice exception**.

Then create a Workflow:

```text theme={null}
Create a workflow named Weekly invoice exception review.

Every Monday:
1. read open invoices;
2. identify incomplete, overdue, unmatched, high-value, and possible duplicate invoices;
3. apply the Review an invoice exception process;
4. write exception type, owner, and next action to the Invoices table;
5. save a dated review file grouped by owner.

Never change approval or payment status and never initiate a payment.
```

Run the Workflow manually against known records before activating its schedule.

## Dashboard example

Publish a Dashboard with:

* open exception count and value;
* overdue value by age;
* possible duplicates;
* unmatched invoices by supplier;
* exceptions without an owner;
* a table grouped by next action.

## Expected result

| Asset         | Purpose                                     |
| ------------- | ------------------------------------------- |
| Sources       | Invoice and payment policies                |
| Knowledge     | Required evidence and exception rules       |
| Data          | Invoices and Suppliers tables               |
| Process Skill | Review an invoice exception                 |
| Workflow      | Weekly invoice exception review             |
| Dashboard     | Exception volume, value, age, and ownership |

## Safety checks

* Never treat similarity alone as proof of a duplicate.
* Preserve original invoice evidence and review history.
* Keep approval and payment actions outside the review Workflow.
* Test currencies, taxes, credit notes, and corrected invoices.