INVOICE PROCESSING
Pre-Payment-Run Cadence Reconciliation Report
Before each scheduled payment run, builds a reconciliation report comparing every recurring vendor's expected invoice to what actually arrived.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires before the payment run
- ActionPull expected and received invoices from PostgresPostgres
- LogicBucket vendors into on-time, missing, early, mismatch
- ActionDraft exception-focused summary with OpenAIOpenAI
- OutputPost reconciliation report to AP Teams channelMicrosoft Teams
What it does
Runs ahead of your payment batch and produces a single reconciliation view of the recurring-vendor book: which expected invoices arrived on time, which are missing, and which came in early or off-amount. The result is a structured Teams summary AP can review and approve before releasing the run, replacing a manual spreadsheet check.
When to use it
Use it the day before a scheduled payment run when you need one trustworthy snapshot of recurring-invoice health across all vendors, rather than chasing each one individually.
How it works
- 1A schedule fires a fixed lead time before the payment run.
- 2Pull expected recurring invoices and received invoices from Postgres.
- 3Reconcile each vendor into on-time, missing, early, or amount-mismatch buckets.
- 4OpenAI drafts a concise, sectioned reconciliation summary highlighting only the exceptions.
- 5Post the report to the AP Microsoft Teams channel for review and sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.