BC builders lien holdback accounting, explained

Most writing about BC builders lien holdbacks covers the deadlines — the lien filing window, the release window, the triggers that start the clocks. Fewer cover the quieter question every builder’s bookkeeper faces monthly: where does the holdback live in the books, and how do you know the number is right on release day?

That question matters because the holdback is not a business practice you can round off. The Builders Lien Act generally requires 10% of the value of work and materials to be retained, and the retained amount has to survive in your records — accurately, per contract — for months between billing and release. This post covers the accounting mechanics. The Act itself, available through BC Laws, is the legal authority, and your construction counsel and accountant own the judgment calls; treat this as the operational map.

The holdback cuts both ways

Start with the structural fact: a general contractor sits in the middle of two holdbacks. Looking up the chain, the owner retains 10% of your progress billings — money you have earned but cannot collect yet, a holdback receivable. Looking down the chain, you retain 10% from each subcontractor’s billings — money you owe but must not pay yet, a holdback payable. A trade contractor faces only the first; an owner-developer faces only the second; a GC carries both, on every contract, simultaneously.

Getting this into the books cleanly means separating the retained amounts from ordinary receivables and payables. A common approach — your accountant decides the treatment — is dedicated accounts: holdback receivable distinct from trade AR, holdback payable distinct from trade AP. The reasoning is practical: ordinary AR is expected to convert to cash on invoice terms, while holdback converts only when statutory windows close, and mixing the two makes your receivables aging lie about collectability and your payables aging lie about what is currently due.

The billing-cycle mechanics

Follow one progress billing through. You bill the owner $500,000 for the month. Under a typical treatment, $450,000 lands in ordinary AR — collectable on terms — and $50,000 lands in holdback receivable, where it stays until release. Revenue is recognized per your revenue policy on the full amount earned; the holdback affects when cash arrives, not whether the work happened. Mirror image below you: a subcontractor bills you $200,000, you record $180,000 in trade AP and $20,000 in holdback payable, and the statutory declaration you sign at the next draw — "accounts paid, subject to holdback" — is describing exactly that split.

Note what this implies for cash planning: on every dollar of margin-neutral flow-through work, you are financing the spread between the holdback you cannot collect and the holdback you did not pay out. On a project with heavy self-performed work the receivable side dominates, and the working-capital cost of the holdback is real even when every clock runs perfectly.

The ledger discipline: per contract, always

The GL account balances are totals, and totals are not enough. Release happens per contract — a certificate of completion on one subcontract starts that subcontract’s clock while every other contract’s holdback keeps sleeping — so the books must support a per-contract answer: how much holdback is retained on this contract, accumulated from which billings, releasable after which date. That is a subledger, exactly like AR aging under the AR control account: the sum of the per-contract holdback ledgers must equal the GL holdback balance, and a monthly tie-out between the two is the control that catches posting errors while they are one month old instead of one project old.

Worth flagging for owners of multi-year work: the Act contemplates annual or phased holdback release in prescribed circumstances, and progressive-release arrangements exist. Whether any of that applies to your project is a construction counsel question — but if it does, the per-contract ledger is what makes it administrable.

Release day: the tie-out

When a release window closes, the accounting is the easy part — holdback receivable converts to collectable AR or cash, holdback payable converts to a payment due — provided three numbers agree: the per-contract ledger balance, the GL account’s share for that contract, and the amount counsel has cleared for release after the lien search. When they disagree, the causes are usually mundane and old: a billing posted without its holdback split, a change order that adjusted contract value but not the retained calculation, an early partial payment that quietly dipped into the retained amount. Every one of those is cheap to catch monthly and expensive to reconstruct at release.

OpSphere ProBuild models this the way the Act forces you to think: a holdback ledger per contract, accumulation from payments and billings, release-window countdowns from recorded trigger events, and portfolio-wide deadline status — connected to the same budgets, invoices, and draw records the rest of the project runs on. ProBuild is available today. The deadline half of the holdback problem gets the attention because it is dramatic; the ledger half is what determines whether release day is a payment run or a forensic project.