INVOICE PROCESSING
Catch Brand-New Line Items on Recurring Stripe Invoices
Detects when a finalized recurring Stripe invoice contains a line item that never appeared on the customer's previous invoices.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe invoice.finalized eventStripe
- ActionFetch customer invoice historyStripe
- LogicDetect line items with no prior precedent
- LogicBranch: at least one new line item?
- ActionPause auto-advance to hold the invoiceStripe
- OutputSend approval request to Slack approverSlack
What it does
It focuses on one specific risk: charges that are entirely new versus prior periods. For each finalized recurring invoice it builds the set of historical line-item descriptors for that customer and flags any item on the current invoice that has no prior precedent.
When to use it
Use this when add-ons, overage fees, or one-time charges sometimes get attached to recurring invoices by mistake or without sign-off. It is narrower than a full diff and produces very few false positives, so it is good as a lightweight guardrail.
How it works
- 1Stripe fires `invoice.finalized` for a subscription invoice.
- 2The flow fetches the customer's recent invoice history.
- 3A logic step builds the historical set of line-item descriptors and finds items with no match.
- 4A branch proceeds only when at least one genuinely new line item exists.
- 5The invoice is held by pausing auto-advance.
- 6A Slack message with approve/reject context is posted to the revenue approver.
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
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.