Budget vs. actual for mortgage lenders: explain the variance

Keep the original plan visible

A useful budget is a record of assumptions, not just a column of target numbers. Preserve the production volume, staffing, expense, and timing assumptions used when the plan was approved. Keep the original budget separate from subsequent forecasts so management can see what changed.

When reporting actual results, align the period and accounting scope with the budget. An expense recognized in a different month, a new account mapping, or a revised corporate allocation can create a variance without representing a new operating trend.

Start with volume before explaining cost per loan

Illustrative example: a monthly plan includes $800,000 of expense and 100 funded loans, or $8,000 per loan. Actual results show $840,000 and 80 loans, or $10,500 per loan. Expense is 5% above plan, while funded volume is 20% below plan. Both contribute to the higher ratio.

Calling the entire $2,500-per-loan difference an overspending problem would hide the production effect. Show the underlying dollar variance and volume variance first. Then ask which expenses were expected to vary with production and which represented capacity the business had already committed to.

Give every significant variance an explanation

Choose a review threshold appropriate to the business and apply it consistently. A dollar threshold can identify large items; a percentage threshold can highlight smaller categories moving sharply. Neither threshold should replace judgment about recurring or strategically important items.

• Volume: did actual production differ from the plan?
• Spending: did payroll, vendor charges, or other expenses change?
• Timing: was a planned item recognized earlier or later?
• Definition: did a mapping, allocation, or reporting boundary change?

Use these labels to organize investigation, then attach evidence. An explanation such as “timing” is incomplete without the expected recognition period and the person responsible for confirming it.

Keep current-month and year-to-date views together

A single month can exaggerate the effect of irregular billing or production timing. A year-to-date view can reveal whether a short-term variance is reversing or becoming persistent. Display both, and retain enough historical detail to investigate unusual movements.

For each recurring category, add a short note about the operating driver. A technology variance might involve a changed contract, a new service, or a classification change. The report should help locate the evidence rather than imply that one cause has already been proven.

Close the loop with a decision log

Finish the review with a small list of actions: the question, owner, next step, and date for the next check. Keep forecast changes separate from actuals and budget. Revising the forecast should make the outlook clearer without erasing the gap between the original plan and actual results.

GlassStack’s reporting and analysis includes budget-versus-actual views and historical trends. A connected data foundation helps those views use consistent definitions, while the management team supplies the operating context needed to decide what to do.

Common questions