FINANCE

Month-End Uncoded Spend Chaser via Snowflake to Slack

On a month-end schedule, queries Snowflake for unaccrued or uncoded expenses, groups them by department owner.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule fires on month-end close days
  • ActionQuery Snowflake for uncoded/unaccrued spendSnowflakeSnowflake
  • LogicGroup transactions by department owner, drop empty owners
  • ActionDM each owner their open items in SlackSlack
  • OutputPost close-status summary to finance channelSlack

What it does

At month-end close it pulls every spend line that is still missing a GL code or accrual flag from your Snowflake ledger, groups the orphan transactions by the responsible department owner, and sends each owner a personalized Slack direct message that lists their open items, amounts, and the close deadline. Owners get one clean to-do instead of a finance-wide all-hands ping.

When to use it

Run it on the last two business days of each month when the accounting team is racing to close the books and chasing department heads for missing expense coding. Ideal when spend data lives in Snowflake and your company runs on Slack.

How it works

  1. 1A schedule fires on the configured close days.
  2. 2Snowflake query returns transactions where `gl_code IS NULL` or `accrued = false`, joined to the owner directory.
  3. 3A logic step groups rows by owner and skips owners with zero open items.
  4. 4For each owner, a Slack action posts a DM with their itemized list, totals, and deadline.
  5. 5A final output posts a summary of who was chased and how much is still uncoded to the finance close channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.