FINANCE

Daily Stripe-vs-Snowflake Proration Reconciliation Sweep

Runs nightly to compare every prorated Stripe invoice against the expected amount in your Snowflake billing model.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule after invoice settlement
  • ActionQuery Stripe proration line items for the windowStripeStripe
  • ActionQuery Snowflake for expected prorationSnowflakeSnowflake
  • LogicJoin and rank per-line deltas
  • ActionWrite discrepancies to Snowflake audit tableSnowflakeSnowflake
  • OutputPost top mismatches to finance SlackSlack

What it does

This is the batch counterpart to event-driven detection: once a day it pulls all prorated invoice line items from Stripe for the prior 24 hours, joins them against the expected proration computed in your Snowflake billing tables, and flags every row where the billed and modeled amounts disagree. The output is a ranked discrepancy list so finance can triage the largest dollar gaps first.

When to use it

Use this as a safety net even if you have real-time detection — scheduled reconciliation catches events that were missed, replayed, or arrived out of order, and gives auditors a daily signed-off ledger of proration accuracy.

How it works

  1. 1A daily schedule triggers the sweep after invoices have settled.
  2. 2The workflow queries Stripe for proration line items created in the window.
  3. 3It queries Snowflake for the modeled expected proration per subscription.
  4. 4The two sets are joined and per-line deltas are computed and ranked.
  5. 5Discrepancies above threshold are written back to a Snowflake reconciliation table for the audit trail.
  6. 6A summary with the top mismatches is posted to the finance Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  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.