Skip to main content
Operating Playbooks

Kill the monthly close. Run continuous close on a project graph.

Month-end is a 1980s artifact. On a project graph, the close is always-on — and finance moves from autopsy to navigation.

9 min readFor Finance leads
TL;DR
  • Monthly close exists because legacy systems could not reconcile in real time. That constraint is dead.
  • Continuous close means books are 95% complete every day. Month-end becomes a 2-hour confirmation, not a 5-day fire drill.
  • The unlock is one project graph, not a federation of accounting + ops + field tools.
  • Controllers who ship this redirect 30–40% of their team’s capacity to forward-looking work.
  • Pilot one division for one quarter in parallel with the legacy close. The case writes itself.

Ask any construction controller why the close takes five days and you will get a list of dependencies — pay-app cutoffs, vendor invoice delays, field accruals, retention recalculations. Each dependency is a reconciliation problem between systems that do not share a model. Eliminate the model gap and the dependencies collapse. That is the entire argument for continuous close.

In 2026, the technology to do this is no longer exotic. It is the operating model that has not caught up. Most construction finance teams are running 1980s rituals on 2026 software. Killing the monthly close is the cleanest reset available.

1. Why monthly close existed in the first place

Monthly close was a workaround for batch systems. Mainframe accounting platforms could not reconcile sub-ledgers continuously, so the industry agreed on a 30-day cycle: cut everything off, reconcile in batch, post the period. That logic was sound when the systems were batch. It has been obsolete for 15 years and ritualized for 15 more.

2. What continuous close looks like in practice

On a project graph, every cost-coded transaction (PO, timesheet, invoice, daily log) lands in the same model. AI accrues automatically. The variance vs budget is computed every night. By the morning of the first business day, the books are 95% there. The remaining 5% is judgment, not data hunting.

  • Day-by-day WIP, not month-end WIP.
  • AI-suggested accruals based on field activity, not spreadsheet guesses.
  • Real-time cost-to-complete that updates with every change order and daily log.
  • Month-end becomes: review judgment items, sign, publish. Two hours, not five days.

3. The cultural shift inside the finance team

  • Finance stops being month-end fire-fighters. They become forward-looking advisors.
  • PMs stop hating the controller. The numbers they see on Wednesday match the close.
  • The CEO gets a real number every Monday — not a stale number every 30 days.
  • Controllers redirect 30–40% of their team’s capacity from reconciliation to scenario work.

This shift is bigger than the technology change. Finance teams that operate continuously stop being seen as a tax on the business and start being seen as a steering function. That is a permanent identity change, and it is hard to reverse once the org has tasted it.

4. The five reconciliation pains continuous close eliminates

  • Field accrual estimation: AI computes from daily logs and crew clocks, not back-of-envelope.
  • PO matching: three-way match runs in real time as receipts hit the graph.
  • Retention recalculation: lives in the contract record, recomputes automatically.
  • CO recovery accruals: AI tracks recoverable vs non-recoverable in real time.
  • Sub pay-app validation: AI pre-validates against schedule, daily logs and prior pay-apps before the form is filed.

5. The honest case for the controller’s desk

If you are the controller deciding whether to champion this, the case writes itself in three numbers:

  • Days to close: from 5 to under 1. That is 60+ days a year recovered across the team.
  • Cost-to-complete variance: typically tightens by 30–50% within two quarters.
  • Audit prep time: drops dramatically because the trail is continuous, not reconstructed.

6. Objections from the audit committee

  • “Continuous close weakens controls.” The opposite. Every entry has a typed event trail. Auditors ship faster, not slower.
  • “Our auditors require period close.” You still have a period close. It is a 2-hour confirmation, not a 5-day creation.
  • “We need a forensic snapshot.” The graph stores immutable point-in-time views. Snapshots are queries, not exports.
  • “The controller is overloaded as is.” That is the symptom. Continuous close is the cure.

7. How to start: one division, one quarter, parallel run

You do not need to bet the firm on this. Pick one division. Run continuous close in parallel with the legacy month-end for one quarter. Measure the gap on three dimensions: cost-to-complete accuracy, days to close, and auditor turnaround. By month three, the legacy close becomes obviously redundant. By month six, you retire it.

The orgs that make this move in 2026 will spend 2027 with a finance function that steers the business in real time. The ones that do not will spend 2027 still doing five-day closes, while their competitors compound the operating advantage every quarter.

Reading something that matches a workflow you own? Bring it in.
Human approval
Source attribution
No fabricated stats
Explicit POV
Author
PS
Priya Shah
Head of AI, Ezelogs

Walk us through one problem.

No scripted demo — bring one project, one workflow, one bottleneck.