FINANCE

Weekly digest of stale pending expenses

Every Monday, scans the expense tracker for reimbursements still awaiting approval, ranks them by age and amount, and sends managers a digest so nothing sits unpaid past your SLA.

CategoryFinance
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionQuery tracker for pending reimbursementsAirtableAirtable
  • LogicCompute aging and flag over-SLA items
  • OutputSend ranked aging digest to finance managerSlack

What it does

Reads your expense tracker each week and finds every reimbursement still in a pending or under-review state. It calculates how long each has been waiting, sorts the oldest and largest to the top, and delivers a single digest to the finance manager. Items past your approval SLA are highlighted so they get cleared first.

When to use it

Use this when expenses pile up unreviewed and employees chase finance for status. A scheduled summary keeps aging visible without anyone manually filtering a spreadsheet, and prevents reimbursements from quietly slipping past payroll cutoffs.

How it works

  1. 1A weekly schedule triggers the run every Monday morning.
  2. 2The flow queries the expense tracker for all rows still marked pending or under review.
  3. 3Logic computes days-waiting for each and flags any beyond the configured SLA threshold.
  4. 4The results are formatted into a ranked digest, oldest and highest-value first.
  5. 5The digest is posted to the finance manager's Slack channel with the over-SLA items called out.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  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.