Three-way match, without the AP backlog.

What this actually looks like.

How you'd actually build it.

Each step is its own agent-or-pipeline component. Don't try to do this in one giant prompt — the failure modes compound.

1. Listen for new invoices

   Webhook from your ERP (NetSuite, SAP, QuickBooks, Sage) on every new AP invoice. Pull the matching PO and goods-receipt record automatically. This is the trigger.
2. Three-way match with tolerances

   Algorithm compares line items, quantities, unit prices, totals across the three documents. Configurable tolerance bands by vendor, category, and total value. This is deterministic logic — NOT an LLM call. The LLM is for the next step.
3. Draft the vendor follow-up

   For each out-of-tolerance line, generate a specific question: "Invoice #4471 line 3 shows 50 units at $14.20; PO #882 shows 50 at $13.80. Please confirm or send a credit memo." This is the writer agent — needs to be polite and specific.
4. Track to resolution

   Full activity trail per invoice. Auto-escalates if vendor doesn't respond inside your window. Auto-captures early-payment discounts on clean invoices. AP reviews a queue instead of building one.

What it runs on.

No vendor lock-in. Every piece is replaceable. The orchestration outlasts the model — when Claude 5 or GPT-6 ships, swap the model, keep the pipeline.

What this actually returns.

Calibrated to mid-market scale (50–1000 staff, $1M–$200M revenue). Your numbers will vary; the framework gives you the order of magnitude to plan against.

Build it yourself, or have us ship it.