INVOICE PROCESSING
Explain Why a Recurring Invoice Grew and Log It to Notion
An agent investigates a flagged recurring invoice, gathers the prior-period numbers from Postgres, writes a plain-English explanation of what drove the increase.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: flagged invoice ID receivedHTTP webhook
- ActionQuery current and prior invoices in PostgresPostgres
- LogicAgent analyzes deltas and drafts explanation
- ActionWrite structured audit record to NotionNotion
- OutputPost Notion link to reviewers in SlackSlack
What it does
When an invoice is flagged for creep, this agent does the legwork a controller would: it pulls the current and prior invoices, identifies which lines and quantities moved, reasons about the likely cause, and produces a clear written summary plus a structured record for the audit trail.
When to use it
Use this when raw diffs are not enough and reviewers want context — a narrative that says "seat count rose 40 to 75, driving most of the increase" rather than a table of deltas. It is ideal for finance teams that keep an auditable log of every variance investigation.
How it works
- 1A webhook from your upstream auditor fires with the flagged invoice ID.
- 2The agent queries Postgres for the current and prior-period invoices.
- 3It analyzes the deltas and drafts a plain-English explanation of the drivers.
- 4It assembles a structured audit record with amounts, deltas, and its assessment.
- 5The record and narrative are written to the Notion finance-audit database.
- 6A Slack note links reviewers to the new Notion entry.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.