INVOICE PROCESSING
Build a monthly vendor reconciliation close report
On the first of the month, totals all Stripe payments per vendor against all Dropbox invoices for the prior month and emails finance a per-vendor variance report for the books…
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule on the 1st
- ActionSum prior-month Stripe payments by vendorStripe
- ActionSum prior-month invoices by vendor from PostgresPostgres
- LogicJoin sides and compute per-vendor variance
- OutputEmail close report to finance via OutlookOutlook
What it does
Produces the month-end vendor reconciliation that finance needs to close the books. It aggregates the prior month's outbound Stripe payments by vendor, aggregates the matching invoice totals from your Postgres ledger, and computes the variance per vendor so any gap is obvious before close.
When to use it
Use it as part of the monthly close when you need a single document showing, per vendor, total paid versus total invoiced and the difference. It saves the controller from rebuilding the same pivot every month.
How it works
- 1A schedule fires on the first calendar day of each month.
- 2The flow pulls all outbound Stripe payments dated in the prior month and groups the totals by vendor.
- 3It reads the invoice ledger in Postgres for the same period, grouped by vendor.
- 4A reconciliation step joins both sides and calculates paid, invoiced, and variance for every vendor.
- 5It renders a per-vendor variance table with totals and a flag on any nonzero variance.
- 6The finished close report is emailed to the finance distribution list through Outlook.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OutlookMail, calendar, contacts.
- 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.