FINANCE

Month-end exception report for still-uncoded card charges

Near close, scans for any corporate-card charges still missing memos or GL codes, ranks them by amount and age, and emails the controller a prioritized exception report.

CategoryFinance
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPre-close schedule (days before month-end)
  • ActionQuery period charges still uncoded in BigQueryGoogle BigQueryBigQuery
  • LogicRank by amount and aging, group by cardholder
  • ActionWrite narrative summary with LLMOpenAI
  • OutputEmail exception report to controllerGmailGmail

What it does

A few days before close, this workflow finds every card charge that has slipped through without a memo or GL code, prioritizes them by dollar amount and how long they've been outstanding, and delivers a clean exception report so the controller knows exactly what blocks the books.

When to use it

Use this in the final stretch of the monthly close when you need a single authoritative list of what's still uncoded and who owns it. Complements the per-charge and daily workflows by catching whatever fell through.

How it works

  1. 1A schedule fires a few business days before month-end.
  2. 2The flow queries BigQuery for all card charges in the period that remain without a memo or GL code.
  3. 3Results are ranked by amount and aging, and grouped by responsible cardholder.
  4. 4An LLM writes a short narrative summary highlighting the largest and oldest exceptions.
  5. 5A formatted exception report is emailed to the controller and finance leads.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  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.