FINANCE

Weekly Reconciliation Variance Snapshot to Snowflake

Each week, aggregates the prior seven days of reconciled and unexplained cash movements from Postgres, writes a variance snapshot to Snowflake.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionAggregate prior-week reconciliation from PostgresPostgreSQLPostgres
  • LogicShape rollup and compute WoW deltas
  • ActionWrite variance snapshot to SnowflakeSnowflakeSnowflake
  • OutputNotify FP&A Slack of refreshed datasetSlack

What it does

Turns the daily reconciliation output into a durable weekly trend dataset. It rolls up matched vs unexplained amounts by day, category, and counterparty from the operational Postgres store and lands a clean snapshot row set in Snowflake, where FP&A can trend variance over time and build cash forecasts on top.

When to use it

Use this when leadership asks why the unexplained-variance number moves week to week and the answer lives in transient operational tables. It preserves a queryable history in the warehouse so analysts can chart reconciliation health and isolate recurring problem counterparties.

How it works

  1. 1A scheduled trigger runs every Monday morning.
  2. 2Queries Postgres for the prior week's reconciliation results, grouped by day, category, and counterparty.
  3. 3A logic step shapes the rollup into warehouse-ready rows and computes week-over-week deltas.
  4. 4Writes the snapshot to a Snowflake variance table, partitioned by week.
  5. 5Posts a short confirmation with row counts and headline totals to the FP&A Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SnowflakeWarehouses, queries, shares.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.