Month-end reconciliation between QuickBooks and the project budget is the quiet discipline that separates builders who know their margin from builders who guess at it. The accounting system records what was paid; the project budget records what was committed. The two views never agree on their own. The job of the bookkeeper, working with the project manager, is to make them agree on a calendar that the lender, the tax preparer, and the owner can all rely on. The work is not glamorous. It is the work that makes every other report defensible.
The four reconciliation points
A complete month-end reconciliation touches four distinct relationships, and skipping any one of them produces a report that looks clean but contains buried errors. Each point answers a different question.
| Reconciliation point | Question it answers | Source documents |
|---|---|---|
| Transactions to budget lines | Is every QuickBooks charge tied to a budget line on a project? | QB cost transactions, project budget |
| Vendors to master list | Does each vendor in QB match a single record in the master vendor list? | QB vendor list, project vendor list |
| Draw billings to receivables | Does each lender draw billed match a receivable funded or pending? | Draw schedule, AR aging, deposit log |
| Retainage to liability | Does retainage withheld on subs match the retainage payable on the balance sheet? | Sub invoice register, GL retainage account |
On 926 Stratford, a $430,250 build, the four points produce roughly 90 QuickBooks transactions a month at peak production, 12 to 18 active vendors, two draws billed across the month, and a retainage liability that grows by 5 to 10 percent of every sub invoice. None of those numbers are large. The work is in matching them, not in computing them.
The month-end calendar
A workable cadence for a builder running five to ten concurrent projects looks like this. Earlier dates are aggressive but achievable; later dates are common in shops where bookkeeping competes with field operations.
| Date | Action | Owner |
|---|---|---|
| Last day of month | Cut off bills payable, post all credit card charges, close timesheets | Bookkeeper |
| 5th of following month | Books closed in QuickBooks, prior month period locked | Bookkeeper |
| 10th | Project budget vs. actual run for every active job | PM with bookkeeper |
| 15th | Reconciliation complete, orphan list resolved | Bookkeeper, PM, controller |
| 20th | Month-end reports out to owner, lenders, project owners | Controller |
The 5th-15th-20th rhythm matters because anything later than the 20th misses the window for a draw correction in the same month. If the reconciliation finds a coding error that affects a draw billed on the 25th of the prior month, fixing it on the 22nd puts the correction in the next draw cycle. Fixing it on the 19th puts it in the current cycle.
The orphan-transaction problem
An orphan transaction is a charge in QuickBooks that has no matching budget line on any active project. The shape varies. The job address on the credit card receipt is illegible. The vendor invoice references a job number that does not exist. A general-overhead expense was tagged to a project by mistake. The cumulative effect is that the project actuals are wrong and the overhead is wrong by the same amount, with the sign flipped.
On 926 Stratford the typical orphan rate runs at three to five charges per month, mostly from credit card receipts where the field employee did not write the job address on the slip. Each orphan is a 10-minute investigation: check the date, the vendor, the amount, and ask the buyer or PM what the purchase was for. The discipline is to resolve every orphan before closing the period. Carrying orphans into the next month is how a $200 mystery charge from January is still on the books in April.
The orphan-budget problem
The mirror image of the orphan transaction is the orphan budget line. A line on the project budget has not been touched in 60 days. It still shows budgeted dollars; it still affects the percent-complete calculation; and nobody knows whether it is a future commitment or a line that is never going to spend.
On 926 Stratford the “built-in cabinetry” line carries $14,800. At month four, framing is done, drywall is partway in, and nothing has hit the line yet because cabinets do not install until month seven. That is a healthy orphan: future spend, on a line that will see action. The unhealthy version is the $1,200 “temporary fencing” line that sat untouched because the PM rented from a different vendor and coded the cost to “site protection” instead. The line will never spend, the actuals are wrong by $1,200 in two places, and the budget total is overstated by an entire line item.
The rule is to walk every untouched line at month-end and decide its disposition. Either it is future spend (leave it), it was miscoded (move the actual transactions to the right line), or it is dead (zero the budget and add an explanatory note). The effort runs 20 to 30 minutes a project per month. Projects that skip the walk drift further from reality every period.
Cost codes as the connective tissue
The mechanical glue between QuickBooks and the project budget is the cost code structure, exposed in QuickBooks through the Class field or through Items mapped to a chart of cost codes. A consistent code list, used on every transaction and every budget line, is what makes reconciliation possible at all. A residential builder who uses the standard NAHB cost code structure or a tightened internal version will reconcile in a morning. A builder whose codes drift by project will spend two days a month on the same task.
The recommended structure has a cost code on every transaction (mandatory in QuickBooks via a custom field rule), a class on every transaction tying it to a project, and a Type field distinguishing labor, materials, subcontract, equipment, and other. Three dimensions per transaction is enough to slice the data every way the lender, the tax preparer, or the owner will ever ask.
Why the bookkeeper and the PM both have to be in the room
The reconciliation cannot be done by the bookkeeper alone, and it cannot be done by the project manager alone. The bookkeeper has the QuickBooks view: every transaction posted, every vendor on file, every invoice scheduled to be paid. The PM has the field view: what was actually delivered, which sub showed up, which work order was issued, which change happened on Tuesday afternoon. Pairing the two views in a 30 to 45 minute meeting on the 12th of each month surfaces the coding questions that neither view can answer alone.
On 926 Stratford a typical month-12 reconciliation meeting works through an agenda the bookkeeper produces in advance: the orphan transaction list with three to five items, the dead-budget candidates with two to four items, the variances larger than $500 with five to ten items, and the open commitments where work was performed but the vendor invoice has not arrived. The meeting closes with each item assigned a disposition and an owner. Items that need follow-up land on the bookkeeper’s list for the 13th and 14th, and the close completes on the 15th.
Open commitments and the work-in-place reconciliation
The hardest reconciliation is the one that does not show up in QuickBooks at all. Work is in place that has not been invoiced. The framer finished the second-floor walls on the 28th but his invoice does not arrive until the 9th. The drywall sub is 80 percent complete on the installation but the invoice will not come until the work is finished. The lumber yard delivered on the 30th but the bill is dated the 4th of the following month and posts in the wrong period.
The fix is an open-commitment register that the PM updates weekly with an estimate of work-in-place by line item. At month-end the bookkeeper accrues the open commitments to the right period, posts a journal entry to align cost-of-goods-sold to project actuals, and reverses the accrual when the invoice posts in the following month. Without the accrual the project P&L oscillates: under-stated in one month, over-stated the next, and the lender sees a draw schedule that does not match the books.
On a $430,250 build the typical month-end open commitment runs $8,000 to $25,000 across two to four trades. Accruing it correctly takes 15 minutes. Skipping the accrual produces a P&L variance of 5 to 8 percent that nobody can explain in March because the work happened in February.
Vendor 1099 reconciliation
Year-end reveals every vendor data problem accumulated over the prior twelve months. The 1099 list pulls from QuickBooks vendor records and their year-to-date payment totals. Three errors recur.
- The same vendor exists under two name spellings, splitting payments below the $600 threshold on each record and producing zero 1099s when one was required.
- A vendor is flagged 1099-eligible when the company is incorporated and exempt, or vice versa.
- The W-9 on file is from 2022 and the vendor changed entity type in 2024, so the 1099 is issued under the old EIN.
The fix is a January reconciliation pass that runs every payee against the W-9 on file, merges duplicate vendor records in QuickBooks, and flags any vendor without a current W-9 for follow-up. Expect 5 to 10 percent of vendors to need attention in any given year.
Year-end review: the rolling 12-month picture
The year-end product of monthly reconciliation is a per-project rolling 12-month budget vs. actual report. For 926 Stratford, closed in November on a 10-month build, the report shows budget of $430,250, actual of $437,820, variance of $7,570 or 1.76 percent over. The variance breaks down by cost code into framing under by $1,400, plumbing rough over by $2,100, finish carpentry over by $4,200, and the rest in noise. That report, produced cleanly, is the input to next year’s budget on comparable projects.
Builders who reconcile every month produce that report in an hour at year-end. Builders who do not reconcile produce it in a week, and the numbers are still subject to argument. The discipline of the 5th, the 15th, and the 20th compounds into a year-end close that the tax preparer files without a single follow-up question.
Where the work cannot be skipped
Reconciliation is the work that makes every downstream report trustworthy. The draw schedule depends on it. The job profitability report depends on it. The 1099 list depends on it. The bid on the next project, priced from historicals, depends on it. The cost of skipping a month of reconciliation is rarely visible in that month. It is visible six months later, when a draw rejection or a tax notice or a bid that loses money traces back to a coding error nobody caught when there was time to fix it.
A bookkeeper who reconciles the four points on the 5th-15th-20th cadence, resolves orphans before close, walks the budget for dead lines, and runs a January vendor pass is doing the unflashy work that produces the only construction financials worth showing a banker. Everything else is built on top of that.