A compressed ERP timeline does not remove work. It moves the work out of the project plan and into the finance team's first month-end close. A CFO who asks for a slower go-live is not asking for delay. They are asking for the risk to be paid for before cutover, while it is still cheap.
Where the saved weeks go
Every week taken out of an implementation plan comes from one of four places: reconciling the migrated data, user acceptance testing, running the old and new systems side by side, or training. None of them looks like progress in a status report, so they are the first to be cut. They are also the four activities that decide whether the first close works.
The risk does not disappear. It arrives at the first period-end after go-live, when the people who normally close the books are learning a new system, the opening balances have not been proven, and the project team's attention has already moved to the next phase.
What a slower go-live buys
- A reconciled opening position. The trial balance, the receivables and payables ageing and the inventory valuation agree to the legacy system before cutover, not after.
- A rehearsed close. At least one full period-end has been run on migrated data, so the team has met the surprises while the old system is still the system of record.
- Acceptance by the owners. Each department head signs off the scenarios that matter to their area. The project team does not mark its own homework.
- A fallback that has been written down. If cutover fails, everyone knows who decides, by when, and what the way back is.
How should the go-live date be chosen?
Choose it against the finance calendar, not the contract calendar. Avoid cutting over in the weeks before a quarter-end, a year-end, an audit or a VAT return. In the UAE that means looking at when the VAT returns and, for companies in scope, the corporate tax filings fall, and leaving room to correct the opening position before either of them depends on the new system.
A go-live that slips by a month and lands in a quiet period is usually cheaper than one that holds its date and lands in a close.
Five questions to put to the project
- What was reconciled to the legacy system before the date was confirmed, and who signed it?
- Has a full period-end been run on migrated data?
- Who owns acceptance in each department, and have they run their own scenarios?
- What is the written fallback, and what is the last moment it can be used?
- Who is on the finance side when the project team leaves, and what are they measured on?
If any of these has no answer, the date is a hope, not a plan. The CFO's role is to say so early, in writing, when changing the date costs a conversation rather than a restatement.