FINANCE

Reforecast Deferral Schedule on Stripe Contract Amendment

When a Stripe subscription is upgraded, downgraded, or canceled mid-term, this voids the remaining deferral rows in BigQuery and rebuilds the schedule from the change date forward.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe subscription updated or canceledStripeStripe
  • LogicResolve change date and recognition impact
  • ActionVoid future deferral rows in BigQueryGoogle BigQueryBigQuery
  • ActionRecompute and insert reforecast rows in BigQueryGoogle BigQueryBigQuery
  • OutputPost amendment change note to SlackSlack

What it does

Keeps deferral schedules correct when deals change. On a Stripe subscription update or cancellation it locks the periods already recognized, voids the future scheduled rows in BigQuery, and writes a fresh forward schedule based on the new contract value and remaining term.

When to use it

Use this whenever mid-term changes are common — seat expansions, plan downgrades, or early cancellations. Without it, an amended contract leaves stale future recognition rows that quietly overstate or understate revenue until someone notices at audit.

How it works

  1. 1A Stripe webhook fires on subscription updated or deleted.
  2. 2A logic step determines the effective change date and whether the change affects future recognition.
  3. 3A BigQuery action marks all schedule rows after the change date as voided, leaving recognized periods untouched.
  4. 4An action recomputes the remaining recognizable amount and spreads it across the new remaining months.
  5. 5A BigQuery action inserts the reforecast rows, and the output posts a change note to Slack for the revenue analyst.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.