Verify incoming invoice

Upload an invoice, match it with the ERP accrual and review the decision

Local processing Files stay in this browser

Try a sample case

Add source files

Invoice is required. ERP data is preloaded for the demo

Supplier invoice

Bundled invoice text loaded

Choose invoice

ERP accrual

Loading bundled ERP dataset

Load ERP JSON

Review extracted invoice

Extracted invoice text

PDF, DOCX and text files are supported. Scanned PDFs use browser OCR

Review ERP data and controls

Approved vendor Shipment ID Currency Original accrual Approved adjustments Accrual status Expected cost lines (JSON)

Control results

Supporting documents Duplicate check Supplier status Bank details

Decision

Not processed

Ready to verify

Add an invoice and run the check

Invoice-

Accrual-

Variance-

What happens next

Validation evidence

Check	Result	Evidence

Structured outputJSON

Invoice history

Decisions and human actions saved in this browser

Time	Invoice	Shipment	Decision	Status	Evidence

No invoices processed yet

How the decision works

AI extracts data. Versioned rules determine the action

1
Read invoice
Extract fields from PDF, DOCX or text
2
Match ERP accrual
Use shipment ID first, then invoice number as a fallback
3
Run controls
Check supplier, currency, charges, documents and duplicates
4
Route decision
Approve, review or reject with reason codes
5
Authorize payment
A human still controls final payment release

Auto-approve

Variance at or below 3% and all controls passed

Review

Variance from 3% to 10% or a non-critical mismatch

Reject or escalate

Critical missing data, compliance issue or variance above 10%

Prototype scope: invoice parsing and policy decisions run locally in the browser. Production AI, ERP, email and payment integrations are represented but not connected. Final payment release remains human-controlled.