20.4 Closing Down Project Finances
Key Takeaways
- Project financial close settles final invoices and accruals, closes open commitments, agrees contract final accounts, and releases unused funds.
- Unreleased budget is trapped capacity that the portfolio cannot redeploy to other work.
- Open purchase orders left behind allow spend to continue against a project nobody is monitoring.
- Ongoing operating, licence, and support costs must be transferred to a named business-as-usual budget holder rather than simply ending.
- Reconciled and archived cost data is the organisation’s evidence base for estimating the next project, and it is lost if closure is skipped.
Outcome 22d is the one candidates skip: know how to close down finances at the end of a project. It looks administrative, which is exactly why it is examined — a project that stops managing money at go-live leaves the organisation carrying open commitments, unclaimed retentions, and budget it cannot re-use.
Closing down finances at project end (LO22d)
Financial close is the controlled shutdown of the project's money, not only the technical handover. Incomplete financial close leaves orphan commitments, unreleased budgets, and audit findings.
Typical financial close steps
| Step | Actions |
|---|---|
| 1. Confirm delivery and acceptance status | Know which work is complete, incomplete, or transferred — cost follows scope reality |
| 2. Finalise supplier accounts | Agree final applications, retentions, claims, credits; close purchase orders |
| 3. Capture final actuals and accruals | Ensure late invoices and work-in-progress are recognised in the correct period |
| 4. Resolve contingencies and reserves | Return unused contingency/management reserve per organisational rules; document draws |
| 5. Close cost codes / prevent further charges | Stop rogue timesheets and late bookings to a dead project |
| 6. Reconcile budget, actuals, and funding | Final variance explanation; grant or capitalisation compliance if applicable |
| 7. Release or reassign remaining funds | Formal return to portfolio/finance; update forecasts to zero remaining for closed work |
| 8. Archive financial records | Contracts, invoices, approvals, EV history — retention for audit |
| 9. Lessons learned on cost | Estimating accuracy, contingency use, supplier performance for future projects |
| 10. Confirm business-as-usual cost ownership | Operating costs after transition sit with BAU budgets, not a zombie project code |
Scenario D — project "closed" but POs open
Technical go-live happened, but three supplier POs remain open and staff still book time to the project code. Twelve months later finance discovers a six-figure tail. Proper financial close would have forced PO closure or transfer, cut charging, and handed residual warranty work to a BAU cost centre with a named owner.
Scenario E — retention and final account
A construction package holds retention until defects are cleared. Financial close plans the final account timeline, retention release criteria, and who holds the defect liability budget after project closure so benefits and assets are not stranded without funding for snagging.
Answer pattern for LO22b–d
For monitoring/forecast scenarios:
- State PV, EV, AC from the facts (or say what data you need).
- Compute or interpret CV, SV, CPI, SPI with correct formulas.
- Give a plain-language status (ahead/behind, under/over).
- Offer a forecast (EAC conceptual) and options if out-turn breaches tolerance.
- Name the report types suited to the audience.
- For end-of-life scenarios, walk financial close steps and BAU cost ownership.
Combined with budget creation and cost types (LO22a), this completes APM PMQ budgeting and cost control: structure the money, measure value earned against plan and spend, report for decisions, and shut the finances down cleanly.
Why financial closure is a governance activity
Three things happen if finances are not formally closed.
Money stays trapped. Unspent budget that is never released cannot be redeployed to other work in the portfolio. On a large programme this is a material misallocation of organisational capacity, not a bookkeeping detail.
Commitments stay open. Purchase orders left open can still be drawn against after the project has closed, with no one monitoring them. Retentions, warranties, and final accounts have dates that will pass unclaimed if nobody owns them.
The record is lost. Cost actuals are the raw material for estimating the next project. A project that closes without reconciling and archiving its cost data removes the only evidence base the organisation has for improving its estimates.
What must be settled
| Closure activity | What it settles | Consequence if skipped |
|---|---|---|
| Final invoices and accruals | All work done is invoiced and recorded in the right period | Costs land after closure with no budget to absorb them |
| Open purchase orders | Remaining commitments are closed or formally transferred | Spend continues against a closed project |
| Contract final accounts | Variations, claims, and retentions are agreed | Disputes crystallise later without project knowledge available |
| Contingency and reserve | Unused funds are formally released | Budget is trapped and unavailable to the portfolio |
| Transfer of ongoing costs | Operating, licence, and support costs move to a business-as-usual budget | Operations inherits costs it never planned for |
| Reconciliation and archive | Final position agreed with finance and records retained for audit | No audit trail and no estimating data for future projects |
| Lessons on cost performance | Estimating accuracy and cost drivers captured | The next project repeats the same estimating errors |
The transfer of ongoing costs is the item most often missed in exam answers, and it connects directly to transition management: licences, support contracts, and maintenance do not stop when the project does. Naming the receiving business-as-usual budget holder is part of closing the project's finances properly.
Which set of actions best describes project financial close?
A project closes having delivered a new system. Six months later, operations discovers it is being charged annual software licence and support fees that no budget holder expected. What was missed at project financial closure?