INVOICE PROCESSING
Triage unmatched invoices with an agent that chases the vendor
When an invoice fails PO matching, an agent investigates the cause, drafts and sends a clarifying email to the vendor, opens a tracked exception in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerMatch failure webhook receivedHTTP webhook
- ActionGather PO, vendor, and history contextPostgres
- LogicAgent reasons about root cause and next step
- ActionSend tailored clarification to vendorGmail
- ActionOpen tracked exception recordPostgres
- OutputSummarize case to AP channelSlack
What it does
Handles the messy long tail of invoices that don't cleanly match a PO. A webhook hands the failed invoice to an agent that reasons about why it failed — missing PO, wrong quantity, unrecognized vendor — gathers the relevant records, then composes a specific follow-up to the vendor and opens a tracked exception so nothing gets dropped.
When to use it
Use this when your match-and-approve flow rejects invoices and a human currently spends time diagnosing each one and writing back to vendors. The agent does the investigation and the first draft of outreach.
How it works
- 1The matching system fires a webhook with the failed invoice and reason code.
- 2The agent pulls related PO, vendor, and prior-invoice context from Postgres.
- 3It reasons through the likely root cause and decides what the vendor must clarify.
- 4It sends a tailored follow-up email requesting the missing or corrected information.
- 5It records a tracked exception with status and next action in Postgres.
- 6It posts a concise case summary to the AP channel so the team has 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.
- 3Connect GmailRead, draft, send, label.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Dollar-Threshold Match Variance Escalation Chain
Routes three-way match variances up an approval ladder by dollar size — small ones to the line manager, large ones to the controller.
Front vendor invoice to Airtable approval packet with line-item parse
Watches a Front inbox for vendor invoice emails, extracts header and line-item data from the body and PDF attachment, and writes a structured.
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.
Three-Way Match Exception Router by Variance Type
When a new invoice fails three-way match against its PO and receiving record, this workflow classifies the mismatch (price, quantity, or missing receipt) and routes each variance…
Route parsed Front invoices to the right Slack approver by amount
Parses an incoming Front vendor invoice and posts an interactive Slack approval card to the approver whose spending threshold matches the invoice total.
Three-way match Front invoices against purchase orders in Postgres
Parses a Front vendor invoice and runs a three-way match against the matching purchase order and receipt records in Postgres, posting pass or exception results to Slack.
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.