INVOICE PROCESSING
Re-Match Blocked Invoices When a Goods Receipt Posts
When the warehouse posts a goods-receipt event, it finds invoices previously blocked for missing or short receipts on that PO and re-runs the three-way match.
How it runs
The automated pipeline, trigger to output.
- TriggerGoods-receipt posted webhook from warehouseHTTP webhook
- ActionUpsert receipt and load blocked invoices for POPostgres
- LogicRe-run three-way match on new received qty
- OutputRelease matched invoices and update gaps in PostgresPostgres
What it does
Unblocks invoices the moment receiving catches up. Many invoices fail matching only because goods arrived after the invoice. This flow listens for receipt postings and retroactively clears the invoices they satisfy.
When to use it
Use it when invoices routinely get stuck on missing-receipt or quantity-short exceptions and an operator has to remember to re-check them after each delivery. This makes the receipt event drive the re-match automatically.
How it works
- 1The warehouse system sends a goods-receipt posted webhook with the PO number and received quantities (trigger).
- 2The flow writes or updates the receipt record in Postgres, then loads invoices on that PO currently in a receipt-related exception state.
- 3A logic step re-runs the three-way comparison using the new cumulative received quantity against invoiced quantity and PO price.
- 4Invoices that now match within tolerance are flipped to Approved with a re-match note.
- 5Invoices still short are kept in the queue with their updated remaining-quantity gap for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
Nightly audit that flags duplicate payments already made
Runs every night to scan the last 90 days of Stripe payments against your Postgres invoice ledger.
Agent that codes Front invoices to GL accounts and drafts a bill
An agent reads each Front vendor invoice, assigns GL account codes per line item using your chart of accounts and past coding history.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
Gate invoice approvals on a duplicate cross-check
When an approver clicks Approve in your AP system, a webhook re-validates the invoice against paid history in Postgres and Stripe charges.
Catch duplicate invoices as they hit your AP inbox
Watches your accounts-payable Gmail inbox for incoming invoice emails, fingerprints each one, and routes likely duplicates to a review label instead of into the approval queue.
Block duplicate Stripe payouts before they send
When a new vendor invoice is queued for payment in Stripe, cross-check it against your paid-invoice history in Postgres and halt any payout that matches an already-paid invoice.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.