INVOICE PROCESSING
Agent That Resolves Invoices Missing a Goods Receipt
An agent works the queue of invoices that have a PO but no matching receipt, emails the vendor or warehouse for proof of delivery, and re-runs the match once the receipt arrives.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled missing-receipt sweep
- ActionRead PO and partial receipt contextSnowflake
- ActionEmail vendor or warehouse for proof of deliveryGmail
- LogicRe-run match when receipt arrives
- ActionMark cleared invoices approvedSnowflake
- OutputEscalate stale cases to AP lead in SlackSlack
What it does
Most three-way match failures are not pricing errors, they are a missing or unposted goods receipt. This agent owns that backlog: it figures out which side is missing, chases the right party, and clears the invoice once the receipt is filed, instead of leaving it stuck.
When to use it
Use this when receipts lag invoices and a growing pile of two-way matches blocks payment. It is agent-driven because resolving each case takes reasoning, follow-up, and judgment rather than a fixed branch.
How it works
- 1A scheduled sweep finds invoices in `missing_receipt` status.
- 2The agent reads the PO and any partial receipt context from Snowflake.
- 3It drafts and sends a targeted email via Gmail to the vendor or the receiving team asking for proof of delivery.
- 4As receipts get posted, the agent re-runs the three-way match.
- 5Cleared invoices are marked approved in Snowflake.
- 6Cases still unresolved past the SLA are escalated to the AP lead in Slack with the full chase history.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect GmailRead, draft, send, label.
- 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.