Run Test Scenario
Watch the agent execute against a sample invoice before certifying its logic.
Expert Review
Visual DAG
Testing
New Invoice Review
Business Configuration
Connectors
Invoice Activity
Graph Agent
Observability
Enhancements
Sample scenarios
Runs are fully simulated against the mock vendor/PO/receipt data — nothing is written anywhere.
Clean three-way match
PO, vendor, amount and quantity all agree and nothing is flagged — routes to the tiered approver.
Auto-approve under threshold
Clean match at $347.20 — under the $500 auto-approve threshold, so no human is involved.
Amount off, but within tolerance
Invoice is $27.65 over the $3,412.35 PO — inside the 2% / $50 allowance, so it still passes (the negative control for amount mismatch).
PO not found
No such purchase order. The graph skips anomaly review and approval entirely and goes straight to blocked.
Amount exceeds PO beyond tolerance
Invoice is $3,050.00 against a $2,820.00 PO — $230 over, past the allowance.
Vendor name differs (exact match mode)
Invoice says "Pinnacle Manufacturing Inc", PO says "Pinnacle Manufacturing". Exact matching rejects it.
Same vendor name, fuzzy matching on
The identical invoice, but Business Config uses fuzzy vendor matching (ignores Inc/LLC/Corp) — it now passes.
Only 70% of the goods received
98 of 140 units received, below the 90% quantity threshold. Quantity failures always hard-block.
Same 70% shortfall, 40% tolerance
The identical invoice with the quantity tolerance raised to 40% — 70% received now passes.
No delivery receipt (all three required)
Needs PO-2026-7108 to have no delivery receipt (delete GR-2026-6108). With all three documents required, it blocks.
No delivery receipt (two-way allowed)
Same PO and invoice, but Business Config allows two-way matching without a receipt — quantity is simply not verified. Only exercises that path while GR-2026-6108 is absent.
Vendor not on the approved list
Ironclad Fabrication (VND-2106) was deliberately never added to Vendors, so the approved-vendor check fails.
Unapproved vendor, handled as reviewable
The identical invoice, but vendor mismatches are set to flag-for-override instead of block — it goes to a human instead.
Duplicate invoice
This invoice number and vendor were already processed (seeded before the run), so the duplicate check blocks it.
Round-number amount
Everything matches, but exactly $4,500.00 trips the round-number flag — it pauses for an override note.
Round number, flags are informational
The identical invoice with anomaly handling set to informational — the flag is noted but doesn't stop approval.
Round number, flags are hard blocks
The identical invoice with anomaly handling set to block — the same flag now stops it outright.
Just under an approval threshold
$24,540 sits within 5% of the $25,000 Finance Manager tier — possible invoice splitting.
Vendor's first invoice
Faraday's first-invoice date on file is this invoice's date (2026-09-27), so the new-vendor flag fires.
Small and clean, but flagged
$300.00 is within tolerance of the $347.20 PO and under the auto-approve limit — but it's a round number, and a flag overrides auto-approval.
Run
Test scenarios run: 0 of 20