Budget Utilisation Reports
Budget reporting in REDA Financials doesn't live in a separate report you have to remember to run — the budget records are the report, recalculated with every posting. This article shows how Meridian's controller reads them: the monthly ritual, the numbers that matter, and the early-warning signals built into every line.
Access you'll need. Any REDA Financials permission set can open the Budgets tab and read these figures; what you see is limited to the budgets your role can view. Creating, editing, and posting budgets requires the Accounting Admin v2 or Accounting Controller v2 permission set.
Three altitudes
| View | Where | Tells you |
|---|---|---|
| Budget header | The budget record's Budget Totals panel | The whole budget's health: Total Budgeted, Effective, Committed, Actual, Available, and Total Utilization % in one glance |
| Budget lines | Budget Lines tab / list views | Per-account: the same arithmetic plus Variance, Utilization %, and the Is Over Budget flag |
| The paper trail | Budget Entries + the POs/PIs behind Committed and Actual | Why each number is what it is |
The columns, decoded
Every figure on a budget line is one of four ingredients or a formula over them. Meridian's FY2026 numbers make the arithmetic concrete:
| Column | Formula | Meridian FY2026 (whole budget) |
|---|---|---|
| Budgeted | Typed when the budget was built | $340,000 |
| Effective Budget | Budgeted + Approved Increases − Approved Decreases | $340,000 (no amendments yet) |
| Committed | Posted PO lines not yet invoiced | $4,800 (the uninvoiced half of Sterling's $9,600 PO) |
| Actual | Posted purchase-invoice lines | $4,800 (Sterling's first bill) |
| Available / Variance | Effective − Committed − Actual | $340,000 − $4,800 − $4,800 = $330,400 |
| Utilization % | (Committed + Actual) ÷ Effective | $9,600 ÷ $340,000 = 2.82% |
| Is Over Budget | Committed + Actual > Effective | Unchecked — comfortably inside |
The month-end read, Meridian style
Start at Utilization %
Compare it to the share of the year gone. End of June ≈ 50% of the year: a line at 70% utilization is running hot, one at 20% is either disciplined or mis-planned. (Utilization counts Committed and Actual — promises are spending too.)
Filter for trouble
A budget-lines list view filtered on Is Over Budget (or sorted by Utilization % descending) surfaces the problem accounts across every budget and entity in one screen — the flag is a simple checkbox, so it filters and reports beautifully.
Explain before you amend
For each hot line, split the story: how much is Actual (bills already in) vs Committed (open POs that might still be trimmed)? A big Committed number is a lever; a big Actual number is history. Then fund what's real via Budget Entries — the variance trail stays honest because the original Budgeted never moved.
Beyond the built-ins
- Salesforce reports and dashboards work on budget lines like any records — a "Utilization by entity" dashboard is a few clicks for your admin, refreshed live.
- Actuals in full detail live in your financial reporting (P&L by month, by cost center) — the budget line's Actual is the buying-side rollup, the ledger is the complete picture.
- Pre-purchase checks are the Budget Analysis modal — the same figures, pointed forward.
- The paper trail per number: Committed traces to posted POs, Actual to posted purchase invoices, Effective to approved Budget Entries — every figure on the line has documents behind it, one related list away.
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Comparing the ledger's expense to the line's Actual and calling it a bug | They measure different pipelines: Actual counts purchase invoices; the ledger also carries journals, depreciation, allocations | Spend control → budget columns; full financial picture → financial reports |
| Judging utilization without splitting Committed from Actual | A "70% used" line that's mostly open POs is a very different problem from one that's mostly bills | Committed is a lever (POs can be trimmed); Actual is history — read both columns |
| Expecting month-by-month budget columns | Lines are annual by design; there is no built-in monthly phasing | Compare utilization to the share of the year elapsed; slice monthly actuals in reporting |
| Screenshotting figures for the board pack at random times | Live numbers move with every posting — two screenshots disagree | Snapshot on a schedule (report subscription or monthly export) so trends compare like with like |
Where to go next
- Budget Entries (Amendments) — acting on what the report shows.
- Understanding Budgets — the arithmetic behind every column.
- Income Statement — the ledger-side view of spending.
Frequently asked questions
Committed counts. A big open PO drives utilization up before a single invoice arrives — correctly, because that money is promised. Check the Committed column to see how much of the "spend" is still reversible.
Budget Actuals track purchase invoices — the buying pipeline the budget controls. Expenses arriving by other routes (journal entries, depreciation runs, allocations) hit the ledger but not the budget line. For full-ledger comparisons, use financial reports; for spend control, the budget view is the right lens.
Budget figures are live, not snapshotted. For trend lines, a scheduled Salesforce report subscription (or your admin exporting the lines monthly) builds the history — worth doing for board packs.
Nothing separate ships — deliberately. The budget record's totals panel, the line columns, list views and the standard report builder are the reporting surface, always current. Anything fancier (dashboards, subscriptions) your admin assembles from the same line data in a few clicks.
They're the same calculation wearing two hats: quote Available when the question is "may we spend more?" and Variance when the question is "how are we tracking against plan?" — finance audiences expect the word variance, purchasing audiences expect available.
Was this article helpful?