Finance operations
Invoice review
Research pilot — simulated example, not a live deployment
Compare invoices with purchase orders and delivery records. Prepare mismatches and supporting evidence for finance to review.
See an input and its handoff
Compare the expected behavior in a routine case and an exception.
Agreed rule
Invoiced quantities must not exceed recorded receipt. Prices must match the purchase order.
Matching records
The three supplied records agree; finance still approves the next step.
Example input
- Purchase order PO-DEMO-208
- 100 desk lamps at USD 40.00 each.
- Delivery record GR-DEMO-84
- 100 desk lamps received against PO-DEMO-208.
- Invoice INV-DEMO-1042
- 100 desk lamps at USD 40.00 each · USD 4,000.00 before tax.
Illustrative output
- Quantity check
- 100 ordered · 100 received · 100 invoiced
- Price check
- USD 40.00 per unit matches the purchase order; line total is USD 4,000.00.
- Assessment
- Records match · ready for finance review
The human handoff
Finance reviews the matched references and structured fields before approving import or payment. A match is not payment authorization.
Partial delivery
Twenty invoiced units have no matching receipt in the supplied records.
Example input
- Purchase order PO-DEMO-208
- 100 desk lamps at USD 40.00 each.
- Delivery record GR-DEMO-84
- 80 desk lamps received. No further receipt supplied.
- Invoice INV-DEMO-1042
- 100 desk lamps at USD 40.00 each · USD 4,000.00 before tax.
Illustrative output
- Quantity check
- 100 invoiced − 80 recorded as received = 20 units to reconcile.
- Amount to reconcile
- 20 × USD 40.00 = USD 800.00 before tax; receipt evidence is missing.
- Assessment
- Quantity mismatch · hold for review
The human handoff
Purchasing confirms whether another delivery record exists or the invoice needs correction. Finance holds the invoice until the discrepancy is resolved.
How this agent would work
Match the documents
Extract references and line items from the supplied invoice, purchase order and delivery record. Keep missing or unreadable fields flagged.
Reconcile against the rules
Compare quantities, currency and unit prices using explicit checks. Identify each mismatch and its source documents.
Prepare the exception brief
Return structured fields, the comparison and unresolved evidence for finance or purchasing to review.
Where human judgment stays
- A missing receipt is missing evidence, not proof that the goods were never delivered.
- Document matching and arithmetic follow the agreed rules. Unreadable references stay empty rather than being guessed.
- Finance approves the result before import or payment. This example neither pays invoices nor posts accounting entries.
When you build your version
A backend you can inspect and own
- Approved spec
- Define required invoice, purchase-order and receipt fields; document matching; quantity and price checks; treatment of missing evidence; and approval before import or payment.
- Backend/API
- A generated FastAPI backend, packaged as a versioned artifact. Review its configuration, integrations and deployment requirements for your environment.
- Source code
- Download the project code to inspect, change and run in your own environment.
- Validation results
- Evidence tied to the artifact version and the checks actually run. Include partial deliveries, missing receipts, duplicate references, price or currency mismatches, unreadable fields and inconsistent totals in the test plan.
No validation report is provided for this pilot. The scenarios above illustrate expected behavior, not passed tests.
Read what Axtra validates