FINANCE
Recompute deferred-revenue waterfall on Stripe contract amendments
Watches Stripe subscription amendments and, when contract terms change, recalculates the full deferred-revenue release schedule in Snowflake and posts a recompute summary…
How it runs
The automated pipeline, trigger to output.
- TriggerStripe subscription updated (amendment)Stripe
- LogicContinue only if TCV or term changed
- ActionFetch open schedule rows from SnowflakeSnowflake
- LogicRecompute ratable release from effective date
- ActionWrite superseding schedule rows to SnowflakeSnowflake
- OutputPost recompute delta to finance Teams channelMicrosoft Teams
What it does
When a customer contract changes mid-term — an upsell, downgrade, term extension, or price override — the recognized revenue schedule no longer matches the new commercial reality. This workflow detects the amendment in Stripe, rebuilds the deferred-revenue waterfall from the amendment effective date forward, writes the new schedule rows into Snowflake, and tells the finance team exactly what moved.
When to use it
Run it if you recognize revenue ratably over a contract term and you process amendments through Stripe subscription updates. It removes the manual spreadsheet rework that revenue accountants do every time a deal is restructured, and keeps the warehouse schedule audit-ready.
How it works
- 1Stripe fires a `customer.subscription.updated` event when a subscription line item, quantity, or price changes.
- 2A logic step compares old vs new terms and continues only if the change alters total contract value or term length (ignores cosmetic metadata edits).
- 3It pulls the current open schedule rows for that contract from Snowflake.
- 4It recomputes the remaining ratable release amounts from the amendment effective date, prorating the catch-up or release-back delta.
- 5The new schedule rows are written back to Snowflake, superseding the prior version.
- 6A summary of the delta — old vs new monthly recognition and any catch-up entry — is posted to the finance channel in Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.