INVOICE PROCESSING
Reconcile Vendor Statement Line Items Against Recorded Invoices
On a scheduled run, pulls each vendor statement's line items and matches them against invoices recorded in Postgres, then posts a Slack digest of unmatched, mismatched…
How it runs
The automated pipeline, trigger to output.
- TriggerMonth-end schedule fires
- ActionLoad vendor statement line items
- ActionQuery recorded invoices from PostgresPostgres
- LogicMatch line items and classify discrepancies
- LogicFilter out fully matched rows
- OutputPost per-vendor gap digest to SlackSlack
What it does
Compares the line items a vendor lists on their statement against the invoices you actually have on record in your accounting database, then reports exactly where the two disagree: charges on the statement you never recorded, invoices you recorded that the vendor omitted, and amount mismatches on shared invoice numbers.
When to use it
Run it monthly (or whenever a vendor statement lands) so AP catches missing invoices, duplicate billings, and price discrepancies before cutting a payment. Ideal for finance teams managing recurring vendors where statement drift quietly accumulates.
How it works
- 1A schedule fires at month-end and loads the parsed statement line items (invoice number, date, amount) for each active vendor.
- 2It queries Postgres for all recorded invoices belonging to those vendors over the same period.
- 3A reconciliation step joins both sets on invoice number, classifying each row as matched, statement-only, ledger-only, or amount-mismatch.
- 4A filter drops fully matched rows so only exceptions remain.
- 5A Slack message delivers a per-vendor gap digest with totals and the specific discrepant invoice numbers for AP to resolve.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.