The short answer
Build the close calendar as a dependency graph, not a dated checklist. For each deliverable, record its required inputs, evidence owner, due state, blocking rule, exception decision, and downstream consumers. A checked task is not ready if its evidence is missing or an upstream dependency later changes.
Key takeaways
- Model prerequisites explicitly instead of relying on calendar order.
- Separate done, accepted, blocked, and released.
- Invalidate downstream approvals when a material input changes.
Define the close unit and release points
Name the entity or property set, period, cutoff, accounting basis, target release dates, and the exact outputs governed by this register. Owner statements, distributions, management-fee review, and period lock can share inputs but need separate release decisions.
A task such as “bank rec complete” is not a useful dependency until it names the account population, statement cutoff, evidence file, preparer, reviewer, and accepted exceptions. The register coordinates work; it does not prescribe accounting treatment.
Map evidence-producing tasks to their consumers
Start at each release and work backward. Mark a hard block when proceeding would make the output unsupported; mark a qualified dependency only when an authorized reviewer may accept a documented exception under policy.
| Deliverable | Required evidence | Failure state | Downstream effect |
|---|---|---|---|
| Owner statement release | Ledger cutoff, bank/ledger proof, open-item decision | Reconciliation reopened | Statement approval invalid |
| Owner distribution | Approved statement basis and settled-cash check | Payout pending or reserve disputed | Hold that distribution |
| Management-fee review | Contract version and approved revenue base | Property scope changed | Recalculate affected fees |
| Period lock | All hard blocks cleared; exceptions approved | Late source activity found | Keep open or use governed post-close correction |
Use states that expose false progress
Prepared means evidence exists; reviewed means a named reviewer checked it; accepted means exceptions fall within the approved rule; released means the consumer may rely on it. “Complete” collapses these decisions and lets a preparer’s checkmark masquerade as release authority.
When a source report, cutoff, mapping, or exception changes, identify dependent approvals and return them to the appropriate state. Do not silently update an attachment beneath an existing sign-off.
Keep portfolio sign-off and reserve exceptions visible
When the close covers many properties, reconcile the full required population before selecting any sign-off sample. A clean sample cannot replace a missing property, reopened workpaper, or unknown version.
Treat an owner reserve deviation as its own dependency with approval, expiry, restoration trigger, and affected distribution. The close can advance for unrelated properties while the dependent release remains blocked.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
☐
Close scope and cutoff frozen
☐
Outputs and release owners named
☐
Hard and qualified dependencies distinguished
☐
Evidence location recorded for every prerequisite
☐
Blockers have owners and next checks
☐
Change invalidation rules defined
☐
Final release decisions retained
0 of 7 marked
Edge cases
- A task is complete for 24 of 25 properties: keep the remaining property visible rather than calling the portfolio done.
- A late invoice arrives after release: preserve the original release and follow the approved correction path.
- One reviewer prepares an upstream workpaper and approves a downstream release: record the role overlap for policy review.
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.
Continue the workflow
Three-way reconciliation for property managersHow to reconcile an owner statementOwner reserve release exception recordPortfolio reconciliation sign-off samplingRevision history
2026-09-18
Initial Phase 3 operational article with a distinct decision artifact, failure states, source-scope notes, and AI-assisted technical review.