INVOICE PROCESSING
Goods-Receipt Webhook Triggers Held-Invoice Match and Release
When a warehouse posts a goods-receipt event via webhook, finds any invoice that was previously held waiting on that receipt, completes the three-way match.
How it runs
The automated pipeline, trigger to output.
- TriggerGoods-receipt event posted to webhookHTTP webhook
- ActionFind held invoices for received PO lines in PostgresPostgres
- LogicRe-run match with confirmed received quantities
- ActionRelease vendor payment via Stripe on passStripe
- ActionUpdate invoice to PAID with receipt event idPostgres
- OutputPost release confirmation to Teams AP channelMicrosoft Teams
What it does
This closes the loop on invoices that arrived before the goods did. The moment receiving confirms a shipment, the workflow finds the invoice that was parked waiting on that exact receipt, finishes the match, and pays the vendor without anyone re-touching it.
When to use it
Use this when vendors invoice on shipment but your policy is to pay only after receipt. Instead of an AP clerk periodically rechecking held invoices, the receipt event itself drives the release the instant goods land.
How it works
- 1The warehouse system posts a goods-receipt event to the inbound webhook, triggering the run.
- 2Postgres is queried for invoices in HELD_AWAITING_RECEIPT tied to the received PO lines.
- 3A logic step re-runs the match now that received quantities are known, against PO and invoice.
- 4If the now-complete three-way match passes, Stripe releases the vendor payment.
- 5Postgres is updated to PAID with the receipt event id linking the trigger to the release.
- 6A confirmation is posted to the AP channel in Microsoft Teams.
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 StripeCustomers, subscriptions, payments.
- 4Connect Microsoft TeamsChannels, chats, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.