INVOICE PROCESSING
Match Vendor Statement Charges to Stripe Payments
On a schedule, reconciles each vendor statement's billed amounts against payments actually made through Stripe.
How it runs
The automated pipeline, trigger to output.
- TriggerReconciliation schedule fires
- ActionLoad vendor statement line items
- ActionQuery payments from StripeStripe
- LogicMatch charges to payments and set settlement status
- ActionWrite reconciliation results to PostgresPostgres
- OutputAlert finance in Slack on mismatchesSlack
What it does
Answers the question "did we actually pay what this vendor says we owe?" by lining up statement charges against the payments recorded in Stripe. Each statement invoice is classified as paid in full, unpaid, partially paid, or overpaid, giving finance a settlement view rather than just a billing view.
When to use it
When you pay vendors via Stripe and need to confirm that statement balances reconcile to real money movement before closing the books. Catches double payments, short payments, and stale balances the vendor hasn't credited yet.
How it works
- 1A schedule triggers the reconciliation run.
- 2Statement line items for each vendor are loaded.
- 3Stripe is queried for charges and payouts tied to those vendors over the matching period.
- 4A reconciliation step matches statement amounts to Stripe payments and assigns a settlement status to each.
- 5Results are written to a Postgres reconciliation table for audit.
- 6A filter isolates non-clean statuses, and a Slack alert summarizes the mismatches for finance.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.