INVOICE PROCESSING
Goods-Receipt Webhook Reconciler for Pending Invoices
When a warehouse goods-receipt event arrives by webhook, this completes the three-way match for any invoice that was waiting on that receipt and notifies the buyer in Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerGoods-receipt event posted to webhookHTTP webhook
- ActionFind pending invoices awaiting this receiptPostgres
- LogicCheck received qty covers invoiced qty
- ActionSet covered invoices clear-to-payPostgres
- OutputNotify buyer of result in SlackSlack
What it does
Closes the loop from the receiving side. Many invoices arrive before the goods are logged as received, so they sit in a pending-receipt hold. This listens for receipt events and re-runs the match the moment the missing piece shows up.
When to use it
When invoices frequently land before receiving confirms delivery, leaving them parked as exceptions that someone has to manually re-check later. This makes the release automatic and immediate.
How it works
- 1The receiving system posts a goods-receipt event to the webhook trigger.
- 2The flow looks up invoices in Postgres on hold for that PO and awaiting receipt.
- 3A logic step verifies received quantity covers the invoiced quantity within tolerance.
- 4If covered, the invoice match is completed and set to clear-to-pay in Postgres.
- 5If the receipt is partial, the invoice stays on hold with an updated short-receipt note.
- 6The buyer is notified in Slack that the invoice is now cleared or still short, with the quantities shown.
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.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
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.
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.
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.
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.
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.
Detect duplicate Front invoices and archive originals to S3
Parses each Front vendor invoice, checks it against a history table for duplicates, archives the source PDF to S3 with a normalized key, and alerts AP when a duplicate is caught.
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.