Finance template

PO Match Gate

Send a PO and its invoice, get a pass / hold verdict before anything gets paid.

A two-way-match clerk that gates your AP queue. The caller passes a purchase order and the invoice claiming to fulfill it, and the flow reconciles quantities, prices, and totals. Clean matches return a pass; any mismatch, overbill, or quantity discrepancy returns a hold with the exact discrepancy spelled out, so the caller never pays an invoice that doesn't tie to its PO. Example input: "PO-9920: 100 units widget-A @ $2.50 = $250.00. Invoice INV-7781 against PO-9920: 100 units widget-A @ $2.65 = $265.00." Example output: "{ matched: false, status: 'hold', discrepancies: ['unit price $2.65 vs PO $2.50 (+$0.15/unit)', 'total $265.00 vs PO $250.00 (+$15.00)'], note: 'Hold for buyer approval: price variance above PO.' }"

The flow this template ships
InputLLM (Claude)Output
Core$0.05 / call3 steps wiredFinance

Who pays: AP teams and invoice-processing agents: the two-way-match control that stops overbilling on every PO'd invoice.

How it runs
Runs on demand

Each accepted caller request triggers the 3-step flow once. Ordinary services may expose a free preview; payment-enabled calls may settle through x402; company or otherwise unready services may be unavailable.

$0.05 per match, suggested

The template opens with this intended price loaded. Launch publishes the service and its current call state. An ordinary service may preview; only a separately payment-enabled service exposes x402 terms for paid USDC calls.

Built on core nodes

The wired flow uses built-in nodes only. Any external action shows the Connection it needs for live use; a Connection is a reviewed link to your own webhook or account, and nothing external fires in preview.

Related templates
Start building

Open PO Match Gate in the studio

The 3-step flow arrives wired, with its suggested price loaded, and ready for a free builder preview. Make it yours, then launch with its public call state reported.

Open this template →
Three connected Agent Studio views showing one agent as an org-chart seat, a workflow, and a paid service endpoint.
Seat, flow, serviceThe same agent as a seat, a flow, and a service.