INVOICE PROCESSING
Hold Recurring Stripe Invoices That Spike Above a Percentage Cap
Compares each finalized recurring invoice total against the customer's prior invoice total and, if the increase exceeds a configured cap, voids the auto-charge and alerts billing.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe invoice.finalized eventStripe
- ActionFetch prior invoice totalStripe
- LogicCompute percentage increase vs prior period
- LogicBranch: increase over the cap?
- ActionPause auto-advance to hold the chargeStripe
- OutputAlert billing in Slack with the totalsSlack
What it does
This is the simplest creep guard: a total-versus-total check. For each finalized recurring invoice it reads the previous invoice's amount, computes the percentage increase, and stops any charge that jumps more than your allowed cap, regardless of which line items caused it.
When to use it
Use this as a blunt but reliable backstop when you do not need line-level detail and just want to never silently bill a customer 3x their usual amount. It pairs well with the line-item auditors as a catch-all.
How it works
- 1Stripe fires `invoice.finalized` for a recurring invoice.
- 2The flow fetches the customer's prior invoice total.
- 3A logic step computes the period-over-period percentage increase.
- 4A branch checks the increase against the configured cap.
- 5If exceeded, the invoice auto-advance is paused so it will not charge.
- 6A Slack alert reports the old total, new total, and percentage jump to billing.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 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
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.
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.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
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.
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.
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.
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.