INVOICE PROCESSING
Investigate a flagged billing spike and draft a vendor inquiry
When a vendor invoice spike is flagged, an agent reads the line items, compares them to prior invoices to find what changed.
How it runs
The automated pipeline, trigger to output.
- TriggerSpike-flagged webhook with invoice idHTTP webhook
- ActionPull invoice and vendor historyBigQuery
- LogicDiff line items to attribute increase
- ActionDraft vendor clarification emailOutlook
- OutputNotify reviewer with summarySlack
What it does
Takes a flagged spike beyond a simple alert: an agent opens the suspect invoice, reads its line items, and works out which charges drove the increase versus the vendor's prior bills. It then writes a specific, polite inquiry email naming the exact lines in question instead of a vague "why is this higher."
When to use it
Use this when spikes are common enough that manually diffing line items eats your AP team's time. It produces a ready-to-send draft so a human only reviews and clicks send.
How it works
- 1A spike-flagged webhook from your detection flow triggers the run with the invoice id.
- 2The agent pulls the flagged invoice and the vendor's recent invoice history from BigQuery.
- 3It diffs line items to attribute the increase to new charges, quantity changes, or rate changes.
- 4It drafts a clarification email citing the specific lines and the prior amounts.
- 5The draft is created in Outlook for an AP reviewer to approve and send, and a summary is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect OutlookMail, calendar, contacts.
- 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.