FINANCE

Month-end deferred-revenue drift reconciler against the GL

On a schedule before close, recompute every active contract's recognition waterfall, compare it to the booked GL deferred-revenue balance.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled run before month-end close
  • ActionRead active contracts and booked GL balances from SnowflakeSnowflakeSnowflake
  • LogicRecompute expected recognized + deferred per contract
  • LogicCompare modeled vs. booked, flag drift over threshold
  • ActionWrite drift exceptions to Snowflake reconciliation tableSnowflakeSnowflake
  • OutputEmail categorized exception list to controllerGmailGmail

What it does

Runs a full-population recomputation of deferred-revenue schedules and reconciles the modeled ending balance against the deferred-revenue liability booked in the GL. Any contract whose recomputed waterfall disagrees with what was recognized is surfaced as a drift exception, so controllers find broken schedules before they sign off rather than after.

When to use it

Use it as a pre-close control when mid-term amendments, cancellations, or manual journal entries have a habit of leaving recognition schedules and the ledger out of agreement. Replaces the manual tie-out spreadsheet finance dreads every month.

How it works

  1. 1A scheduled trigger fires a few days before month-end close.
  2. 2The flow reads all active contracts and their booked GL balances from Snowflake.
  3. 3It recomputes each contract's expected recognized and deferred balances for the period.
  4. 4A branch compares modeled vs. booked and isolates contracts exceeding a materiality threshold.
  5. 5Drift exceptions are written to a Snowflake reconciliation table.
  6. 6A categorized exception list (over- vs. under-recognized) is delivered to the controller via email.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.