FINANCE
Processor-vs-Ledger Variance Alert
On each scheduled run, reconciles Stripe payouts against the booked amounts in Snowflake and raises a PagerDuty incident only when the unreconciled variance breaches your…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly business-hours schedule
- ActionPull recent Stripe payoutsStripe
- ActionFetch booked ledger entries from SnowflakeSnowflake
- LogicMatch payouts to ledger and sum variance
- LogicCompare variance to tolerance threshold
- OutputOpen PagerDuty incident on breachPagerDuty
What it does
Compares actual processor payouts to what your ledger expected, line by line, and escalates only material breaks. Small rounding differences stay silent; a real reconciliation gap pages the on-call finance engineer immediately.
When to use it
Use this when missed or misbooked payouts cost you days to discover. It turns end-of-month reconciliation surprises into same-day catches, which matters most for teams with high payout volume or tight close deadlines.
How it works
A scheduled trigger runs hourly during business hours. An action pulls recently arrived Stripe payouts with their settlement dates and amounts. A Snowflake query fetches the corresponding booked entries. A logic step matches payouts to ledger rows and sums the absolute unreconciled variance. A second logic branch checks that variance against your configured tolerance: under threshold, the run ends quietly; over threshold, an action opens a PagerDuty incident with the offending payout IDs and the dollar gap so the on-call can investigate.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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 Finance workflows
Detect Annual-to-Monthly Downgrade Refunds Owed
Catches subscriptions switched from an annual term to monthly partway through the prepaid year, computes the unused prepaid balance owed back.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Expense Submission Webhook Instant Triage and Routing
Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.
Accrual Chase Board in Monday with Per-Owner Tasks
On a schedule it reads open uncoded expenses from Snowflake and creates or updates a Monday item per department owner.
Real-Time Uncoded Expense Nudge on New Spend Event
When a new expense lands without a GL code, a webhook fires and the workflow immediately Slack-nudges the spending owner to code it on the spot.
Monthly Vendor Spend Anomaly Brief for Finance Leads
Once a month, an agent analyzes the full expense ledger for vendor and category spend anomalies, drafts a narrative brief with the top outliers and likely causes.
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.