AWRA OpsHub Search
Intermediate Certificate on pass

Budget Management

Use spending budgets to watch expense and procurement spend, and GL budgets to compare each revenue and expense account with actuals month by month.

3 lessons 40 min 5-question assessment 70% to pass

What you’ll learn

  • Connect finance reports to source modules, controls, and operational decisions
  • Review accounting, tax, budget, payment, reconciliation, and close evidence
  • Identify finance exceptions before they distort reports or manager decisions
  • Prepare finance records for audit, period close, and executive review

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Reading 12 min

Choose the right kind of budget

Budget Management focuses on spending budgets by category and department, GL budgets per account over twelve months, spreading an annual figure, budget against actual through a chosen month, and variance. In AWRA, finance control works best when operational activity, accounting records, tax treatment, approvals, attachments, and reports stay connected.

The practical goal is trust. Finance users should know where a number came from, which source module created it, who reviewed it, and what evidence supports the balance, tax, payment, budget, or close decision.

In practice, a finance manager creates a GL budget under Accounting, GL Budgets starting in January for the Nairobi branch, types an annual 1,200,000 for rent so it spreads 100,000 a month, and enters monthly sales targets. In June they compare through May: sales are under budget, shown in orange, and fuel is over. Separately, the department manager checks the spending budget before approving a procurement request.

Budget control path

1

Plan

Budget scope, start month and owner are set.

2

Lines

Annual or monthly figures go on each account or category.

3

Spend

Postings and procurement draw against the budget.

4

Compare

Budget against actual is read through a chosen month.

5

Act

Variances against you are explained or corrected.

Finance model

  • Finance reports should trace back to source records and review decisions.
  • Tax, budget, and accounting setup choices affect many downstream reports.
  • Attachments and review notes make balances defensible during audit or close.
  • Exceptions should be owned before they become reporting noise.
02
Lesson 2 of 3 Workshop 14 min

Build a GL budget

The operating routine is to use a spending budget for departmental spend, a GL budget for the income statement, compare actuals through the latest closed month, and explain every unfavourable variance. This keeps finance work from becoming a spreadsheet-only exercise disconnected from AWRA source activity.

Before acting, check budget type, start month, department, branch or project, account lines, actuals to date, variance and its direction, and procurement impact. These checks protect report accuracy, cash visibility, tax treatment, procurement decisions, and audit readiness.

A strong finance user can explain the next action from the record itself, whether the action is reviewing a ledger line, chasing a receivable, reconciling a payment, approving a budget, or closing a period.

Budget decision guide

Finance signal Review Action
Revenue under budget GL budget variance Review sales pipeline
Expense over budget Account actuals Explain or correct coding
Purchase over spending budget Remaining budget Approve with context
Wrong branch Budget dimension Correct the scope

Finance decisions

  • Finance action should follow the current balance, source module, and control state.
  • High-impact edits, deletes, overrides, and close decisions need clear reasons.
  • Operational context helps finance teams interpret margins, cash, and aging.
  • Reports are more useful when exceptions have owners and next actions.
03
Lesson 3 of 3 Practice 14 min

Read budget against actual

Finance closure should leave proof. Useful evidence includes GL budget lines, budget against actual for the month, spending budget report, procurement request, variance notes, and approval decisions, connected to the exact account, transaction, report, payment, tax setting, budget, reconciliation, or close item.

Managers should review patterns such as unmatched payments, aged balances, failed sync, suspicious adjustments, tax setup gaps, budget overruns, and unresolved period-close blockers.

In practice, closure means budget decisions show owner, spend, variance, and procurement impact clearly.

Budget review checklist

Right budget type is used
Scope is clear
Actuals are compared through a closed month
Unfavourable variance is explained
Procurement impact is documented

Financial proof

  • Finance work is complete only when the balance and evidence can be defended.
  • Close routines should surface unresolved risk instead of hiding it.
  • Audit packs and exports should preserve source context, not just report totals.
  • Good finance governance protects cash, tax, margins, budgets, and trust.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center