INVOICE PROCESSING
Mismatch-Triggered Stripe Payment Hold
On a nightly schedule, reconciles pending vendor payments against PO and receipt data.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly reconciliation schedule fires
- ActionLoad payment-queued invoices with PO and receiptPostgres
- LogicRe-validate three-way match before payout
- ActionPause Stripe payout for failed matchesStripe
- OutputEmail buyer the list of held paymentsGmail
What it does
Guards outbound money. Before vendor payouts run, it re-checks each scheduled payment's invoice against its PO and goods receipt. Payments tied to clean matches proceed; payments tied to a mismatch get their Stripe payout held and the buyer is notified to investigate before funds move.
When to use it
Use it when you pay vendors through Stripe and want a final automated checkpoint that stops overpayments and payments for goods never received. It is the safety net between approval and actual disbursement.
How it works
- 1A nightly schedule kicks off the reconciliation run.
- 2The flow reads all invoices queued for payment from Postgres and joins their PO and receipt records.
- 3A decision step re-validates vendor, quantity, and price tolerances.
- 4Clean matches are left to pay on schedule.
- 5For mismatches, the corresponding Stripe payout is paused (transfer/payout updated to hold).
- 6The buyer receives an email listing each held payment, the variance, and the reason.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect GmailRead, draft, send, label.
- 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.