# Invoice acceptance matrix

Worked example companion. Fictional scenario; no measured results.

The reviewer needs the original field and the failed check, not just a confidence score.

## How to use this sheet

Replace the example rules with your own. Keep each acceptance decision linked to its owner and evidence. Use the blank CSV to record your actual process; the example CSV contains teaching material.

| Check | Example failure | Required action |
| --- | --- | --- |
| Supplier identity | Name matches several vendor records | AP resolves the vendor |
| Invoice total | Lines and tax do not explain the total | Reviewer checks source document |
| Currency | Missing or conflicting currency | Hold draft creation |
| Duplicate candidate | Same supplier and invoice number | Compare original, revision and credit context |
| Bank-detail change | Document contains new instructions | Use separate verification process |
| Unreadable page | Required total is absent | Request a replacement document |

## Workflow

1. **Register document** (AP intake): Keep original, document ID and file hash.
2. **Extract proposals** (Extraction service): Retain field values and source locations.
3. **Validate and review** (AP reviewer): Check totals, vendor identity and duplicates.
4. **Create draft** (AP system): Write accepted fields with a stable reference.

Exception: Unreadable files request replacement. Conflicting totals or probable duplicates stay in review. Bank-detail changes use a separate verified process.

## Measurement

Measure field-level correctness and correction time on a defined, permissioned evaluation set. Report document families, sample size and failure categories. Processing volume alone does not establish extraction quality.

## Limitations

- Model choice, data permissions and review thresholds require evaluation on the actual documents.
- This example creates a reviewed draft, not an automatic payment.

Source page: https://www.opsautomators.com/work/invoice-extraction-human-review
Prepared September 7, 2026.