How to Build a CIP Schedule That Reconciles to Your Books

A CIP schedule is a project-by-project breakdown of capitalized construction costs — land, hard costs, soft costs, fees, and carry — showing budget, costs to date, current-period activity, and estimated cost to complete, reconciled to the Construction in Progress balance on the general ledger. If yours doesn’t tie to the GL, it isn’t a schedule; it’s a hope.

Every developer has something called a CIP schedule. Auditors ask for it, lenders ask for it, partners ask for it. The problem is that in most shops it’s a standalone spreadsheet, maintained from memory, that agrees with the general ledger only in the month someone forces it to. Here’s how to build one that stays true by construction.

The columns that matter

A working CIP schedule has, per project and per cost category:

1. Approved budget — from the development pro forma, by category
2. Costs to date — cumulative capitalized costs from the ledger
3. Current period — this month’s additions
4. Committed — signed contracts and POs not yet billed
5. Estimated cost to complete — budget minus costs minus committed, adjusted for known changes
6. Variance — projected final vs approved budget

Columns 2 and 3 must come from the general ledger — not from a parallel tally. That’s the entire trick, and it’s where most schedules fail.

Why most CIP schedules don’t reconcile

Because the ledger can’t produce the rows. If your chart of accounts holds development costs in a handful of generic accounts — “Construction Expense,” “Professional Fees,” “Interest” — then land, hard, soft, fees, and carry can’t be read from the books, and the schedule has to be maintained by hand from invoices and memory. Two months of that and the schedule and ledger have quietly diverged.

The fix is structural: a chart of accounts with a dedicated CIP block whose account ranges mirror the schedule’s rows — land accounts, hard-cost accounts, soft-cost accounts (with financing interest split by capital-stack layer), fee accounts, carry and reserve accounts. Then the CIP schedule becomes a report: every row is a ledger balance, reconciliation is automatic, and the spreadsheet version — if you keep one — is generated, not maintained.

We’ve built exactly this structure for a multi-project development group; the full account architecture is in our CIP chart of accounts case study.

The three reconciliations that keep it honest

1. Schedule total ↔ GL CIP balance, monthly, to the dollar — any difference is named and cleared in the month it appears.
2. Hard costs ↔ contractor pay applications — the schedule’s hard-cost lines should tie to approved pay apps net of retainage.
3. Draw-funded costs ↔ lender draw schedule — every draw request maps to schedule categories, so the lender’s records and yours never drift. (This one gets its own discipline: draw reconciliation.)

Multi-entity wrinkles

When costs are paid by one entity but belong to another project entity — routine in SPE structures — the schedule must follow the project, not the payer. That requires dedicated intercompany CIP-transfer accounts with a documented path up the ownership chain, or the schedule becomes unreconcilable the first time costs cross entities.

The takeaway

Don’t build a better spreadsheet. Build a ledger that can produce the schedule — then the schedule is always right, the auditor’s request is an export, and the lender’s draw package reconciles by design.

---

We build CIP structures and maintain lender-ready CIP schedules as part of our construction accounting service — or get a candid read on yours with a free books review.

#construction#cip#real-estate