Open the financial workbook of a typical cost-plus custom build, and there is usually one tab that does most of the work. The contractor knows where everything is. The owner is told the project is being managed. This is the single most common structural failure in custom construction - and it is not a small one.
Sometimes the tab is called Budget. Sometimes Project. Sometimes simply the project address. It contains contract values, change orders, invoice records, payment records, allowances, holdback, and the running estimate at completion, all in one place.
And it cannot answer the three questions that matter on a cost-plus project. It cannot answer them clearly, and more importantly, it cannot answer them independently.
The Problem with One Spreadsheet
A cost-plus project must be able to answer three distinct questions at any moment:
What does the project owe? The total of contracted obligations and approved change orders, less amounts already paid, less holdback held, equals the remaining liability.
What has the project paid? The total cash that has actually left the project account, traceable to specific invoices.
What has the owner been billed? The total drawn from the owner, including the contractor's management fee, with running reconciliation against actual project costs.
These are three different ledgers serving three different purposes. When they share a single tab, errors in one become invisible in the others. A double-billed invoice in the payment column does not show up as a discrepancy in the obligation column. A holdback released too early does not surface in the billing column. The architecture itself defeats the audit.
"The questions are different. The ledgers must be different. Anything less is a spreadsheet that balances to itself because it was edited to balance."
The Three Tabs Defined
1. Obligations - The Liability Ledger
The Obligations tab is the register of every contracted commitment on the project. It opens with the prime contract. It expands with every subcontract awarded, every supplier purchase order with a fixed price, and every approved change order. Each line carries a contracted value, a status, holdback held, amounts paid, and remaining balance.
What it tracks: dollar commitments the project has made.
What it does not track: cash movement, owner billings, or labour-and-material expenditures that have no underlying contract.
The Obligations tab answers the question what does the project owe, and to whom? If it cannot produce a current, complete answer to that question within five minutes, the architecture is broken.
2. Payments - The Cash Flow Tracker
The Payments tab is the cash movement ledger. Every cheque cut, every wire sent, every electronic transfer recorded with date, vendor, invoice reference, amount (pre-tax subtotal only, never the grand total with taxes), and the obligation it ties to.
What it tracks: money that has left the project account.
What it does not track: contracted commitments not yet paid, holdback amounts retained, or owner billings.
The Payments tab answers the question what has the project actually paid out, and against which obligations? When reconciled against the Obligations tab, it produces the running balance owed per vendor. Without this separation, the running balance is unreliable.
3. Billingsheet - The Owner-Facing Ledger
The Billingsheet records every draw issued to the owner: the period it covers, the costs incurred during that period, the management fee applied, the cumulative project total billed, and the running balance against the contract or the working budget.
What it tracks: amounts drawn from the owner.
What it does not track: vendor obligations, payment timing, or holdback per vendor.
The Billingsheet answers the question what has the owner actually been billed, and how does that reconcile to project costs incurred? On a cost-plus project, this is the tab the owner sees. The other two are the contractor's working tabs - but the owner has the right to inspect them on demand.
Why the Separation Matters
The architecture is not aesthetic. It is forensic.
When the three ledgers are separate, errors become detectable. A payment recorded with no matching obligation is a flag. An obligation closed out as paid while the payment ledger shows no corresponding cheque is a flag. A draw issued to the owner that does not reconcile to the costs incurred during the billing period is a flag. The architecture itself produces signals.
When the three ledgers are combined, the same errors are absorbed silently. The single tab will balance because it was edited to balance. The architecture has no independent reference points to test against.
The Two-Tier Payment Model
Cost-plus projects involve two distinct categories of expenditure, and the architecture must accommodate both. The first is contracted spend: every dollar that flows under a written subcontract or purchase order. These show up in the Obligations register. The second is labour and material: the day-rate carpenter, the hardware store run, the internal hours billed by the contractor's own labour pool. These typically have no underlying contracted obligation.
This is why the Payments tab will, on every project, contain entries that do not tie to the Obligations register. This is correct. Labour and material expenditures are tracked at the progress and forecast level, not at the obligation level. An auditor reading the books should expect to see this pattern. What they should not see is a contracted obligation paid out without a corresponding Obligations entry. That is the failure mode the architecture exists to detect.
| One-Tab Architecture | Three-Tab Architecture | |
|---|---|---|
| Obligations | Mixed with payments and billings | Separate register with status, holdback, and remaining balance per vendor |
| Payments | Recorded against project total, often with tax included | Pre-tax subtotal recorded against specific obligation |
| Owner Billings | Cumulative line on the same tab | Independent ledger tied to draw periods and fee structure |
| Audit Trail | The tab balances to itself | Three independent reference points that test against each other |
| Error Detection | Forensic - surfaces only on close-out review | Structural - flagged at the moment they occur |
| Owner Confidence | Trust-based | Evidence-based |
What an Owner Should See
The owner does not need to maintain three tabs personally. The owner needs to know that the contractor maintains them, and that the contractor can produce them on demand.
The owner-facing view, on a properly architected project, is the Billingsheet. Each draw arrives with a clear period, a clear cost summary, a fee breakdown, and a running cumulative total. Behind the Billingsheet, accessible on request, sit the Obligations register and the Payments ledger. The owner has the right to inspect both. The contractor has the obligation to maintain both with current data.
The owner does not need to read every entry. The owner needs to know that if a question arises, the architecture exists to answer it.
01 A custom residential project paid a railing supplier's deposit early in the build, recorded against a deposit invoice in the Obligations register.
02 Eighteen months later, the same supplier issued a final invoice for the full contract value - without deducting the deposit already paid.
03 The error was the supplier's. Their accounting team had treated the deposit as a separate transaction, disconnected from the final invoice on their side.
04 The contractor's accounts payable team, processing the final invoice in isolation, would have paid it in full. But when the invoice was applied against the obligation, the running balance went negative - structurally impossible.
05 The architecture flagged the error before payment. The corrected draw was issued, the supplier confirmed the deduction, and the project was made whole.
The structural lesson: the error was the supplier's. The architecture that caught it was the contractor's. A combined-ledger version of this same project would have paid the invoice in full - and recovered the overpayment only if someone, eventually, audited the books closely enough to find it.
The One Question to Ask
If you are an owner evaluating a contractor, or an architect advising a client on contractor selection, the diagnostic is straightforward.
"Can you produce, today, three separate views: your obligations register, your payments ledger, and your billings record?"
If the answer is yes, and the three documents arrive within a business day, the architecture exists. The contractor may still produce work that is competent or incompetent, on budget or off - but the financial structure is not the problem.
If the answer is anything else, that is your answer. A contractor who cannot produce three separate views is a contractor whose books are combined. The errors that combined books produce are not visible until they have already accumulated. By the time the owner is asking about them, the leverage to correct them is usually gone.
The question costs nothing to ask. The architecture either exists or it does not. The contractors who have it expect to be asked. The contractors who do not are the ones whose projects produce the surprises this discipline exists to prevent.
LSPP Solutions provides project audit and ongoing owner representation across Quebec and Ontario. Whether you are pre-engagement or mid-build, we can verify that your contractor's financial architecture is sound - or build the structure to make it so.
Contact LSPP