INVOICE PROCESSING
Draft a vendor dispute email for invoices that breach the rate card
When an invoice is flagged as over the negotiated rate, an agent assembles the contract evidence and drafts a professional dispute email back to the vendor.
How it runs
The automated pipeline, trigger to output.
- TriggerFlagged-invoice webhook receivedHTTP webhook
- ActionRetrieve rate card and invoice detailsSnowflake
- LogicCompute overage and affected period
- ActionDraft vendor dispute email with evidenceOpenAI
- OutputStage dispute as Gmail draft for approvalGmail
What it does
This workflow turns a detected overcharge into a ready-to-send vendor dispute. Given a flagged invoice, an agent gathers the negotiated terms, calculates the exact overage, and writes a clear, polite email citing the agreed rate and the contract clause, attaching the math. It logs the dispute as a tracked case so nothing falls through.
When to use it
Use this when your team detects overcharges but loses recovery dollars because nobody writes the follow-up. It's for AP and procurement teams who want disputes drafted automatically with evidence, while keeping a human in the loop on the actual send.
How it works
- 1An incoming flagged-invoice signal arrives by webhook and triggers the run.
- 2The agent retrieves the vendor's negotiated rate card and the original invoice details.
- 3It computes the overage amount and the billing period affected.
- 4It drafts a dispute email referencing the agreed rate, the variance, and the relevant clause.
- 5The draft and a tracked case record are saved, and the email is staged in Gmail as a draft for a human to review and send.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect GmailRead, draft, send, label.
- 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.