FINANCE

Deferral Schedule Anomaly Detection Agent

On a weekly schedule, an agent scans BigQuery deferral schedules for anomalies — orphaned rows, negative recognition, schedules that overrun their contract term.

CategoryFinance
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionLoad active schedules and source contracts from BigQueryGoogle BigQueryBigQuery
  • ActionAgent classifies anomalies and drafts root causes
  • LogicRank findings by impact and confidence
  • OutputFile triaged anomalies as Asana tasksAsanaAsana

What it does

Applies agent judgment to keep the deferral dataset clean. It pulls the current schedules from BigQuery and looks for patterns rules-based checks miss: rows with no matching contract, negative or zero monthly amounts, recognition extending past the contract end, or totals that no longer reconcile after edits. For each finding it reasons about the likely root cause before reporting.

When to use it

Use this as an ongoing data-quality safety net, especially when multiple sources (Stripe, manual, amendments) feed the same schedule table. It catches drift between true-ups so problems surface before close instead of during audit.

How it works

  1. 1A weekly schedule trigger starts the run.
  2. 2A BigQuery action loads active deferral schedules with their source contracts.
  3. 3The agent inspects the data, classifies each anomaly by type, and drafts a probable cause and suggested fix.
  4. 4A logic step ranks findings by dollar impact and confidence.
  5. 5The output files the triaged list as Asana tasks for the revenue team to clear.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect AsanaTasks, projects, milestones — everywhere.
  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.