INVOICE PROCESSING
Flag Silent Price Hikes on Recurring Vendor Invoices via Email
Watches your invoice inbox, compares each new vendor invoice against that vendor's historical baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice email arrives in labeled Gmail inboxGmail
- ActionExtract vendor, total, and line items from the invoiceOpenAI
- ActionLook up vendor's historical invoices to build baselinePostgres
- LogicCompute price drift % and compare against tolerance
- ActionRecord this invoice's amounts to the history tablePostgres
- OutputPost drift alert to finance Slack channelSlack
What it does
Many vendors raise prices quietly between billing cycles, and the increase hides inside an otherwise routine invoice. This workflow catches that drift automatically. When a new invoice email arrives, it extracts the vendor, the total, and the per-line amounts, looks up what that same vendor has charged historically, and computes the percentage change. If the increase exceeds your threshold, it posts a structured alert to Slack so finance can question it before it gets paid.
When to use it
Run this if you pay the same vendors on a recurring basis (SaaS, utilities, logistics, retainers) and want a tripwire on silent rate increases. It is most valuable for teams that approve invoices by habit and rarely re-check the numbers.
How it works
- 1A new invoice email lands in a labeled Gmail inbox and triggers the run.
- 2The agent parses sender, vendor name, invoice total, and line items.
- 3It queries Postgres for that vendor's prior invoices to build a rolling baseline.
- 4A logic step computes drift percentage and compares it to your tolerance.
- 5If drift is within tolerance, the invoice is logged and the run ends quietly.
- 6If drift exceeds tolerance, a Slack alert fires with the old price, new price, delta, and a link to the source email.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, 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
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.