What your regions share decides how to move finance without risking the quarter

Ask a CFO whether the new system went live on time, and most will say yes. Far fewer can say the first month-end close on it was on time.

The sequence of a rollout decides which close is at risk and how many regions share that risk. Finance should make that call, with the project team.

Phasing protects the close you can least afford to miss

In a phased rollout, one region moves while the others keep closing on the old system. If the first region’s close slips, the consolidated numbers still come from systems that work. The risk stays inside one region’s books.

Each phase also proves the design before the next region depends on it. The chart of accounts, the intercompany rules, and the landed-cost model get tested in real closes.

A global consumer-products manufacturer is moving off AX 2012 with Ludia this way. Strategy and architecture work came first. Then Finance and Supply Chain rolled out across North America and Asia-Pacific in phases, one region at a time.

The template decides whether phase two costs less than phase one

Phasing only pays when region two configures what region one already designed. That takes one global template: the shared design decisions made once, each written down with its reason.

The template holds the chart of accounts and its dimensions, the intercompany rules, the costing method, and the landed-cost model. Local tax and legal requirements sit on top of it for each country.

The rules around a template move during a rollout. The US Supreme Court struck down the IEEPA tariffs on February 20, 2026, and refunds are not automatic. New Section 301 tariffs of 10 to 12.5 percent on 60 economies followed on July 24, 2026.

In a phased plan, you fix the landed-cost design once in the template, before the next region goes live.

Phasing has a cost, and it sits between the regions

While regions sit on two systems, anything that crosses between them needs a temporary link. Intercompany sales, shared inventory, and consolidation all have to work across the old system and the new one.

Each of those links is built, tested, and then thrown away. A shared-service finance team closes in two systems for as long as the phases last.

A single cutover concentrates the risk in one weekend. A phased rollout spreads the cost across temporary links, and the more your regions trade with each other, the higher that cost climbs.

When a single cutover is the safer call

A single cutover is the safer choice in four situations.

The regions share a warehouse or a finance team. Splitting shared stock or shared people across two systems for months creates more risk than it removes.

Intercompany volume is heavy. When most transactions cross regions, the temporary links cost more than the phases save.

There is little to separate. A business in one country with a few entities on one ledger has no natural phases.

The old system can’t hold. Dynamics AX 2012 R3 has been out of extended support since January 2023, and Dynamics GP support ends December 31, 2029. Keeping an unsupported system alive for extra phases is a risk of its own.

A single cutover is made safe by rehearsal. Run full practice cutovers, close a prior month in parallel, and give finance a real go or no-go vote before the weekend.

People carry the rollout, and agents help them close

The controllers in the first region become the best trainers for the next one. Their admins work alongside our consultants from the first sprint, and every design decision is written down with its reason. By the second phase, your own team teaches the process.

Agents at work: during the first closes on the new system, controllers can use the Finance Agent for reconciliation and variance review. They still sign off the close.

The platform also moves between phases. Microsoft now publishes Dynamics 365 changes continuously to its AI at Work roadmap, so each region goes live on a slightly newer system than the last. Test the template again before every phase.

What finance and operations leaders should decide first

Map what your regions share before you choose the sequence. Shared warehouses, shared finance teams, and intercompany volume decide the answer more than headcount does.

Put the template decisions in writing. Each one needs a reason, so region two configures what region one designed.

Protect the close, not the go-live date. Rehearse the cutover and close a prior month in parallel before any region moves.

Fund one phase at a time. Give each phase a scope, an owner, and a reason for its place in the order, as we did for a 2,000-person MEP contractor.

Check the legacy clock. If the old system is out of support, the cost of waiting belongs in the comparison.

How we know this

This point of view comes from Ludia’s Finance and Supply Chain delivery across regions and entities. Product status is as of Sept 29, 2026.

1. Phased rollout for a global consumer-products manufacturer: Ludia client results.
2. Phased plan with a scope, an owner, and a reason for each phase: A 2,000-person MEP contractor moves service and finance forward on one plan.
3. IEEPA ruling: Congressional Research Service, Supreme Court Rules Against Tariffs Imposed Under IEEPA (2026); Holland & Knight, Supreme Court Strikes Down IEEPA Tariffs (Feb 2026).
4. Section 301 tariffs from July 24, 2026: Honigman, Section 122 Tariffs Expire for Many Imports, But New Section 301 Tariffs on 60 Economies Replace Them (July 2026).
5. AX 2012 R3 support dates: Microsoft Learn, Dynamics AX 2012 R3 lifecycle.
6. Dynamics GP support dates: Microsoft, Announcing End of Support for Dynamics GP (Sept 25, 2024).
7. Finance Agent: Microsoft, Build the future of agentic ERP (Sept 23, 2026).
8. Continuous roadmap: Microsoft, One always-on roadmap (Aug 25, 2026).