FINANCE
Flag contracts where billing and recognition timelines diverge
Scans BigQuery deferred-revenue and billing tables nightly, computes the gap between each contract's billing schedule and recognition schedule.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule after ETL load
- ActionQuery billed vs. recognized by period in BigQueryBigQuery
- LogicFilter to contracts past divergence threshold
- LogicSkip run if no contracts diverge
- OutputPost flagged contracts to Slack finance channelSlack
What it does
Every night this workflow joins your invoiced-billing schedule against your revenue-recognition schedule in BigQuery, period by period, and surfaces any contract where the two have drifted apart. The outcome is a short, actionable list of contracts that need a manual deferral adjustment before close — instead of finding them during the audit.
When to use it
Run this when you bill annually but recognize monthly (or any cadence mismatch), and you want an early-warning signal that the deferred-revenue balance on a contract no longer ties to its billing. Ideal for SaaS and subscription finance teams running ASC 606 / IFRS 15 schedules.
How it works
- 1A nightly schedule fires the run after the ETL load window.
- 2A BigQuery query joins billing_schedule and recognition_schedule on contract_id and period, computing cumulative billed minus cumulative recognized.
- 3A logic step filters to contracts whose absolute divergence exceeds the configured dollar or percentage threshold.
- 4If the filtered set is non-empty, a Slack message lists each flagged contract, its divergence, and the period it first broke.
- 5If everything ties, the run exits quietly so the channel stays signal-only.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 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 Finance workflows
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.
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.
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 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.
Overdue Accrual Escalation Emails to Owners and Managers
On a schedule it flags uncoded spend that has stayed open past the chase deadline and emails each delinquent owner via Gmail.
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.