INVOICE PROCESSING
Catch Per-Line-Item Invoice Anomalies from Outlook and Alert Discord
Triggers on new vendor invoices in Outlook, compares each individual line item against its own historical price.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice email arrives in OutlookOutlook
- ActionExtract per-line items, unit prices, and quantitiesOpenAI
- ActionFetch each line item's historical price for the vendorPostgres
- LogicCompare each line to its baseline; collect drifted lines
- ActionUpdate line-item price historyPostgres
- OutputPost drifted-line alert to Discord channelDiscord
What it does
A stable invoice total can still hide a line item that doubled while another dropped. This workflow checks drift at the line-item level. When an invoice arrives in Outlook, it matches each line against that item's own pricing history for the vendor and flags any single line whose unit price or quantity-adjusted cost moved beyond tolerance. The Discord alert names the specific lines that changed, so reviewers see the real culprit instead of a vague total variance.
When to use it
Use this for vendors with itemized invoices where the mix shifts month to month and a stable bottom line can mask a sharp increase on one component. Ideal for usage-based or multi-product billing.
How it works
- 1A new invoice email arrives in Outlook and triggers the run.
- 2The workflow extracts each line item with its description, unit price, and quantity.
- 3It queries Postgres for each line item's historical price for that vendor.
- 4A logic step compares each line to its own baseline and collects the ones that drifted.
- 5Line histories are updated with the new prices.
- 6If any line drifted, a Discord alert posts the offending lines with old and new prices and the percentage change.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect DiscordCommunity channels + voice + bots.
- 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
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.