FINANCE

Month-End Revenue True-Up and Variance Alert

On the last business day of each month, this compares scheduled deferral revenue in BigQuery against actual recognized revenue, flags variances above a threshold.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLast business day of month schedule
  • ActionQuery expected vs actual recognition in BigQueryGoogle BigQueryBigQuery
  • LogicFilter contracts exceeding variance threshold
  • ActionFormat prioritized true-up worklist
  • OutputEmail worklist or all-clear to close teamOutlook

What it does

Runs the month-end true-up automatically. It queries BigQuery for the revenue that should be recognized this period from the deferral schedule, compares it to what was actually posted, and surfaces any contract whose scheduled and actual amounts diverge beyond your tolerance.

When to use it

Use this during financial close when you need to catch missed recognitions, double-counts, or schedules that drifted because a contract was amended mid-term. It replaces the manual variance pivot the controller builds every month.

How it works

  1. 1A schedule trigger fires on the last business day of the month.
  2. 2A BigQuery action pulls expected recognition for the period and joins it against actuals.
  3. 3A logic step keeps only contracts whose absolute or percentage variance exceeds the configured threshold.
  4. 4An action formats the flagged contracts into a prioritized true-up worklist with dollar deltas.
  5. 5An Outlook output emails the worklist to the close team, or sends an all-clear if nothing breached the threshold.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OutlookMail, calendar, contacts.
  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.