LearnERP Fundamentals

Actual vs budget: 4 steps each month

ERP Fundamentals2026-08-29

In the previous lesson we built a budget from your system data. A budget that is never reviewed becomes a forgotten file within two months, and decisions drift back to gut feel. This lesson sets a short monthly rhythm that compares actual against plan, turns every gap into a decision, and runs from WhatsApp.

Why budgets get abandoned after two months

The usual cause is not weak numbers but the absence of a fixed review date and a named owner. The budget takes a week to build, then the month starts, operations get busy, and nobody opens the file again until the first cash squeeze. A structured review costs half an hour a month and prevents the year-end surprise.

Step 1: close the month before you compare

Comparing incomplete data produces an argument about whether the number is right instead of a discussion about what to do next. Before comparing, confirm that sales invoices were issued, purchase invoices were recorded under their correct dates, cash expenses were entered, and returns were processed. Fix a closing day, for example the fifth of next month, and review right after it. Never debate a number that has not been closed.

Step 2: compare by line item, not by total

The total hides more than it shows: a rise in sales can mask a rise in purchase cost, so the month looks healthy while the margin erodes. Compare each major line on its own and express the gap as a percentage, not only an amount, because a small amount in a small line can be a large deviation. An illustrative example with hypothetical figures:

LinePlanActualGapReading
Sales100104+4%Within range
Cost of goods6068+13%Needs explaining
Payroll20200%On plan
Marketing52-60%Not executed, not a saving

The reading is clear: sales are close to plan, but cost of goods overshot by a larger percentage, so the problem sits in the margin, not the revenue. And the marketing line is not a saving, it is a plan that never happened.

Step 3: explain the gap with three questions

  1. Is the gap real or a recording error? An invoice entered twice or posted to the wrong line creates a phantom deviation. Check the three largest transactions before concluding anything.
  2. Is it timing or a permanent change? A purchase batch pulled forward from next month is timing and corrects itself. A supplier price increase is permanent and deserves a decision.
  3. Is it price or quantity? Higher supplier pricing is handled by negotiating or switching supplier; larger quantities are handled by tightening purchasing and waste.

Step 4: end with a written decision

A review that ends with "let us watch it next month" is wasted. Every deviating line ends with one of three outcomes: change the execution and keep the budget, change the budget through an explicit decision by whoever holds that authority, or keep the line under watch for one more month at most. Write the decision, its owner, and its check date in one line, otherwise it will not happen.

The review from WhatsApp in four messages

A restaurant owner with two branches never sits in front of a dashboard. On the fifth of the month he opens the chat and asks:

Owner: compare August expenses against the budget

System: August is closed. Sales are slightly above plan, cost of goods is above plan by a larger margin, and marketing was not spent. Largest deviation: material purchases.

Owner: why did purchases go up

System: the increase comes from one supplier, and unit price rose compared with last month while quantities stayed close.

In four messages he learned the cause was price, not quantity, and walked away with one decision: get a quote from an alternative supplier before next month's purchase. That is the difference between a system you read and a system you ask. Read more about running operations from WhatsApp and Arabic accounting from your phone.

Monthly review checklist

  • Is the month closed, with invoices and expenses recorded under their real dates?
  • Is the comparison by line item and not the total alone?
  • Is the gap calculated as a percentage as well as an amount?
  • Is every deviation explained: recording, timing, price, or quantity?
  • Does every deviating line have a written decision, an owner and a date?
  • Was any budget change made by explicit decision, not by neglect?
Summary: a budget is a follow-up tool, not a document you file. Close the month, compare by line rather than total, explain every deviation through the recording, timing, price and quantity questions, then end with a written decision that has an owner and a date. Half an hour a month is enough, and when the comparison is one WhatsApp message away it becomes a habit.