Skip to content

Budget vs Actual Variance Report

Example prompt: "At the start of each month, compare last month's actual spend against our budget in the finance sheet. Flag any line items more than 10% over budget and email a summary to the finance team."

How to automate budget variance reporting with GloriaMundo

The Problem

Every month, someone on the finance team pulls actual spending numbers into a spreadsheet, lines them up against the budget, and manually calculates which departments or cost centres are over or under. The arithmetic is straightforward, but the process takes time — gathering data from multiple tabs, formatting the comparison, writing up a narrative about why marketing overspent or why infrastructure came in under budget. By the time the report reaches stakeholders, the month is half over and the conversation is retrospective rather than actionable.

How GloriaMundo Solves It

We build a scheduled workflow that runs on the first working day of each month. It reads both the budget and actual spend data from your Google Sheets workbook — one tab for planned figures, one for actuals. A code step calculates the variance for each line item (absolute and percentage), then flags anything that exceeds your threshold. An LLM step reads the flagged items and writes a plain-English summary: which areas are over budget, which are under, and what the overall picture looks like. The finished report is emailed to your finance distribution list and a condensed version is posted to Slack. Glass Box preview shows you every calculation and the drafted narrative before anything sends.

Example Workflow Steps

  1. Trigger (scheduled): Runs on the 1st working day of each month at 9:00 AM.
  2. Step 1 (integration): Read the monthly budget figures from the "Budget" tab in Google Sheets.
  3. Step 2 (integration): Read the actual spend figures from the "Actuals" tab for the previous month.
  4. Step 3 (code): Calculate the variance for each line item — amount over/under and percentage deviation. Flag items exceeding the configured threshold (e.g. 10% over budget).
  5. Step 4 (llm): Generate a narrative summary of the variances — which areas are over budget, which are under, and the overall financial position.
  6. Step 5 (integration): Email the full variance report to the finance distribution list via Gmail.
  7. Step 6 (integration): Post a condensed summary with flagged items to the #finance Slack channel.

Integrations Used

  • Google Sheets — source for both budget and actual spend data
  • Gmail — delivers the full variance report to stakeholders
  • Slack — posts a condensed summary with flagged variances to the finance channel

Who This Is For

Finance managers, controllers, and operations leads at small to mid-size businesses who produce monthly budget reports manually — particularly teams where actual spending data already lives in spreadsheets rather than a full ERP system.

Time & Cost Saved

Building a manual budget-vs-actual report typically takes 1-2 hours per month: pulling numbers, calculating variances, formatting the comparison, and writing the commentary. This workflow compresses that into a few minutes of review. At scale (multiple cost centres or departments), the savings compound. The workflow uses integration, code, and LLM steps, costing a few credits per monthly run.