FINANCE
Re-evaluate deferral schedules on contract modifications
When a contract is amended, recomputes the remaining recognition schedule in BigQuery, diffs it against the prior schedule.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: contract modifiedHTTP webhook
- ActionRecompute remaining schedule in BigQueryBigQuery
- LogicDiff vs. prior schedule, classify materiality
- ActionRoute material changes to Slack for sign-offSlack
- OutputSync approved schedule to PostgresPostgres
What it does
Contract amendments — upsells, renewals, downgrades, early terminations — change how remaining revenue should recognize. This workflow catches the modification event, rebuilds the go-forward recognition schedule, and compares it to the schedule it replaces. The outcome is that mid-term changes get reflected in deferred revenue immediately, with a human review step for anything material.
When to use it
Use it when contract changes are frequent enough that re-spreading by hand causes drift between billing and recognition. It keeps the schedule current without finance re-deriving every amendment from scratch.
How it works
- 1A webhook fires when a contract is modified in the CLM or CRM.
- 2A BigQuery action recomputes the remaining recognition rows from the amended terms and the already-recognized balance.
- 3A logic step diffs the new schedule against the prior one and classifies the change as immaterial or needs-review.
- 4Needs-review changes post to Slack with old-vs-new amounts for sign-off.
- 5A Postgres action writes the approved schedule so billing stays aligned.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Month-End Uncoded Spend Chaser via Snowflake to Slack
On a month-end schedule, queries Snowflake for unaccrued or uncoded expenses, groups them by department owner.
Receipt Upload OCR Policy Check with Manager Escalation
When an employee drops a receipt into a Drive folder, it extracts the line items, checks them against expense policy.
Weekly Proration Anomaly Audit to Notion
Each week it aggregates all flagged proration discrepancies from Snowflake, scores them against anomaly thresholds, and publishes a finance-ready audit page in Notion with totals.
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.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Draft and Send Proration Over-Billing Correction Emails
For each confirmed over-billing credit, an agent drafts a clear, customer-specific apology email explaining the proration error and the credit applied.
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.