INVOICE PROCESSING
Block auto-approval when an invoice exceeds its negotiated rate
Receives each invoice via webhook from your AP system, checks the total against the vendor's contracted rate stored in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice posted to approval webhookHTTP webhook
- ActionFetch contracted rate and tolerancePostgres
- LogicCompare invoiced total to allowed rate
- ActionEscalate over-rate variance for sign-offSlack
- OutputReturn approve or hold decision to callerHTTP webhook
What it does
This workflow acts as a gate in your accounts-payable pipeline. When your AP or procurement tool posts an invoice to the webhook, it looks up the vendor's contracted or last-approved rate in Postgres, compares the invoiced total, and returns a structured decision: auto-approve if within terms, or hold for review if the amount exceeds the negotiated price. Held invoices are escalated so a person decides before money moves.
When to use it
Use it when invoices flow through an automated approval queue and you need a programmatic check that vendors are billing the rate you actually agreed to. Best for teams with negotiated contracts where overbilling and unauthorized increases are the real risk.
How it works
- 1Your AP system POSTs a new invoice payload to the webhook trigger.
- 2A Postgres step fetches the vendor's contracted rate and tolerance.
- 3A logic step compares invoiced total to the allowed rate.
- 4Within terms: the flow returns an approve decision to the caller.
- 5Over terms: it returns a hold decision and posts the variance to Slack for sign-off.
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 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.