Why Construction Projects Blow Their Budgets (And How Project-Based Accounting Fixes It)

Ask most contractors why a project came in over budget and the answer is usually a shrug: material prices went up, the client changed something, the site had problems nobody could have predicted. Some of that is real. But a lot of what gets blamed on bad luck is actually a visibility problem — the business simply couldn't see the overrun happening until it was already too big to fix.

The company can be profitable while every project is losing money

Here's the mechanism that catches most contractors: accounting is done at the company level — total revenue in, total costs out, one bank balance, one profit and loss statement — while the actual work happens as a portfolio of separate projects with completely different cost structures, timelines and risk profiles. A company-level view can look perfectly healthy while three sites are quietly bleeding money and one large project is subsidizing all of them. Nobody notices until that one large project ends, and suddenly the company's overall numbers fall off a cliff with no obvious single cause.

Cost has to be tracked per project — ideally per site — for an overrun to be visible while there's still time to do something about it. If materials, labor and subcontractor costs are all recorded generically as "cost of goods sold" or "expenses" without being tagged to a specific job, there's no way to know which project actually caused the number to move.

Subcontractor commitments you can't see until the invoice lands

A second, quieter cause of overruns: a subcontractor is engaged for a piece of work, verbally or on a purchase order, and that commitment doesn't show up anywhere in the project's cost tracking until the subcontractor actually invoices — sometimes weeks or months later. In the meantime, the project looks cheaper than it really is, because a real financial obligation exists that simply isn't recorded yet.

Example scenario: a contractor commits a subcontractor to electrical work worth 40 million TZS partway through a build. If that commitment isn't logged anywhere until the subcontractor's invoice arrives two months later, every cost report produced in between understates the true committed cost of the project by that exact amount — and any decision made off those reports, including whether to take on more work, is being made on incomplete information.

Proper subcontractor management means recording the commitment at the point it's made, not at the point it's invoiced — so a project's true committed cost is always visible, even for work that hasn't been billed yet.

Progress billing that isn't tied to actual completion

The third common failure point sits on the revenue side, not the cost side. Construction projects are typically billed in stages as work progresses, rather than as one lump sum at the end. When progress billing is disconnected from a real measure of how much work has actually been completed — invoiced on a rough estimate, a fixed schedule, or simply "what feels fair to ask for this month" — a project can look cash-positive for months while actually running behind, or the opposite: genuinely ahead of schedule but under-billed, quietly starving the business of cash it has already earned.

Billing tied to a real percentage of completion against a defined scope of work keeps invoicing honest in both directions — the client is billed for what's actually been done, and the contractor isn't left financing work out of pocket that should already have been paid for.

What proper project-based accounting actually looks like

Fixing this isn't about hiring more accountants or checking numbers more often — it's about tracking the right things from the start of a project instead of trying to reconstruct them at the end. A few pieces make the biggest difference:

• A bill of quantities as the baseline. Before work starts, the project is itemized — materials, labor, and specific work items, each with a quantity and a rate. Every actual cost afterward is measured against this baseline, so an overrun can be traced to the exact line item causing it rather than argued about in general terms.
• Cost tracked per project and per site, not blended into a single company-wide expense figure, so a struggling project is visible in the numbers while it's still recoverable.
• Subcontractor commitments recorded when they're made, not when they're invoiced, so committed cost is always current.
• Progress billing tied to a real completion percentage against the bill of quantities, not a flat schedule or a guess.
• Retention tracked separately from the main contract value — the percentage a client withholds until practical completion or the end of the defects liability period is easy to lose track of once it's buried inside a general accounts-receivable balance, and released retention that never gets followed up on is money quietly left on the table.

Why this needs to sit on the same books as the rest of the business

Project accounting only earns its keep if it's connected to the company's real accounting — the same chart of accounts, the same bank reconciliation, the same reporting — rather than living in a separate spreadsheet that someone has to manually reconcile against the "real" books every month. A separate system for project tracking tends to drift out of sync with actual bank activity and actual invoicing within a few months, which is exactly when the numbers matter most.

Vitabu ERP's Construction Management add-on covers project and site registers, bills of quantities, subcontractor management, progress billing and retention tracking — built on the same accounting core as the rest of Vitabu ERP, so project cost and billing flow straight into the company's real financial reports instead of sitting in a parallel spreadsheet. See current pricing or register to explore the Core ERP it runs on.