It's 11 pm, the steering committee is tomorrow, and the budget tracking spreadsheet shows a burn rate nobody can explain — because three versions of the file are circulating, the field base hasn't sent its May expenses, and a formula broke at row 148. If that scene sounds familiar, this article is for you: it describes what a good project budget tracking table must contain, column by column, how to build it cleanly in Excel, and above all when the spreadsheet stops being the tool and becomes the problem.
We'll cover the reference structure (columns, tabs, calculation rules), the indicators that actually matter, the hygiene rules that prevent 90% of spreadsheet accidents, and what real-time budget tracking in an ERP like Abvius changes.
Project budget tracking: the template, the indicators and the method
Reading time: ~5 min
- What a budget tracking table is (really) for
- The essential columns, one by one
- The two rates to track — and their gap
- Structuring tabs: lines, donors, sites
- The hygiene rules that save a spreadsheet
- When Excel hits its structural limits
- Real-time budget tracking in Abvius
- Mini FAQ
What a budget tracking table is (really) for
The budget tracking table is not the financial report sent to the donor: it is the internal steering tool that answers three questions every month. Where are we against the approved budget? At this pace, where will we land? What must be decided now (accelerate, reallocate, request an amendment)? A table that only records the past is a rear-view mirror; good budget tracking is a decision-oriented dashboard that then feeds donor reporting without reprocessing.
The essential columns, one by one
Approved budget — the contractual version in force, amendments included. Actual expenditure — cumulative since project start, sourced from the accounts (not re-keyed). Commitments — orders placed and contracts signed but not yet paid: the most frequently missing column, yet the one that prevents end-of-project surprises, as explained in our article on commitment accounting. Forecast to complete — the estimate of remaining spend to closure. Landing — actuals + commitments + forecast: the figure that drives decisions. Available — budget minus landing. Burn rate — actuals / budget. Each row of the table maps to a line of the contractual budget, not to an accounting code: bridging the two is the job of the analytical chart of accounts.
The two rates to track — and their gap
The financial burn rate alone says nothing: 50% spent is excellent at mid-project and alarming in the first quarter. The useful indicator is the comparison between financial consumption and time elapsed: at 60% of the timeline, consumption between 50 and 70% is generally healthy; below, the project underspends (risk of returning funds and missing results); above, it overspends (risk of running out before the end). It is this gap, line by line, that triggers decisions — one of the essential financial KPIs of project steering.
Structuring tabs: lines, donors, sites
One summary tab per budget line (the steering committee view); one tab per donor if the project is co-funded, each in its contract's nomenclature; one tab per site or base if implementation is spread out; and a single "data" tab where accounting extracts land — never direct entry into the presentation tabs. On a multi-donor project, the central difficulty is allocating each expense across funding sources: our guide to shared cost allocation covers this in detail.
The hygiene rules that save a spreadsheet
One source of truth: a single, shared master file, with field contributions arriving as accounting extracts, not parallel files merged by hand. No re-keying: expenditure comes from an accounting export; any manual re-entry eventually diverges. Lock formulas and strictly separate entered data from calculated cells. Version: a dated monthly snapshot, archived, to answer "why did the figure change since the last committee". Document: a notes sheet stating sources, exchange rates applied and the data cut-off date.
When Excel hits its structural limits
Even impeccably maintained, a spreadsheet is a time-lag: it shows the situation as of the last extract, not today's. It blocks nothing: an expense exceeding a budget line is observed after the fact, never prevented. It doesn't trace who changed what. And it doesn't natively split an expense across several donors with their respective eligibility rules. These limits — detailed in our article on the 5 major risks of Excel in financial management — become critical beyond two or three simultaneous grants, or as soon as a field team contributes to the tracking.
Real-time budget tracking in Abvius
In Abvius, the budget tracking table is no longer a file to build: it is a permanent view, fed by every entry. Contractual budget, actuals, commitments and available balance are continuously up to date; eligibility rules and per-line caps are checked at the moment of spending, not at the moment of discovery; multi-donor allocation is carried by each entry; and the same data feeds internal steering and donor-format reports. The time saved isn't measured only in spreadsheet hours: it is measured in ineligible expenses avoided because the alert came before the expense.
Mini FAQ
How often should budget tracking be updated?
Monthly at minimum, aligned with the monthly accounting close. In critical periods (project end, funding crisis), switch to weekly.
Should we track commitments or only paid expenses?
Both: tracking limited to payments systematically understates real consumption and leads to over-committing in the project's final months.
Is a free Excel template enough to start?
For a single project with one donor, yes — applying the hygiene rules above. It is the multiplication of grants and contributors that makes the spreadsheet structurally insufficient.
How should currencies be handled in the table?
One original-currency column, one applied-rate column (per the contract's method, InforEuro for the EU), one counter-value column — never a mental conversion inside the cell.
Budget tracking that is always current and alerts before the expense rather than after: request an Abvius demo.