FINANCE

Daily FX-Normalized Expense Violation Digest from Snowflake

Each morning it pulls the prior day's expenses from Snowflake, normalizes every amount to base currency using a stored daily rate table, scores each against policy.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule after overnight expense load
  • ActionQuery Snowflake for prior-day expenses joined to FX rate tableSnowflakeSnowflake
  • LogicScore each row against caps, duplicates, and receipt rules
  • LogicFilter to violations and group by employee and rule
  • OutputEmail itemized violation digest to financeOutlook

What it does

On a schedule, this batch job reads yesterday's expense rows from your Snowflake warehouse, joins them to a daily FX rate table to compute base-currency amounts, evaluates each line against spend policy, and delivers a single grouped email listing every violation by employee and rule.

When to use it

Use this when expenses are already centralized in Snowflake and you want a once-daily compliance sweep instead of per-transaction alerts. Ideal for finance teams that review reimbursements in scheduled batches rather than real time.

How it works

  1. 1A daily schedule fires the run after the overnight expense load completes.
  2. 2A Snowflake query pulls the prior day's expenses joined to the daily FX rate table, returning base-currency-normalized amounts.
  3. 3Each row is scored against category caps, duplicate detection, and missing-receipt rules.
  4. 4A filter keeps only the violating rows and groups them by employee and rule type.
  5. 5An Outlook email with the itemized violation digest is sent to the finance reviewers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  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.