D365 Project Operations

We design the account, cost centre, dimension and entity structure D365 Project Operations will use, testing it against the reports finance actually publishes. Getting this wrong is the single most expensive thing to unwind later, so it is agreed in writing before configuration starts.

Deliverables:

• Chart of accounts design
• Dimension model
• Reporting map

Trial balance, open items, fixed asset registers and the agreed depth of comparative history are loaded and reconciled line by line to the legacy system, with your controller signing each reconciliation.

Deliverables:

• Loaded balances
• Reconciliation pack
• Sign-off

Every activity in your month-end is mapped with its owner, dependency and timing, from accruals and allocations to intercompany and consolidation, so D365 Project Operations is configured around the real close rather than an idealised one.

Deliverables:

• Close calendar
• Process maps
• Control points

One full period is closed in both the legacy system and D365 Project Operations, and every variance is explained before go-live is approved. This is the step that turns finance from nervous to confident.

Deliverables:

• Parallel close results
• Variance log
• Go-live decision

General ledger, sub-ledgers, tax codes, currencies, bank formats and approval workflows are configured in Microsoft Dynamics 365 ERP, with automated bank feeds and payment file formats tested against your banks.

Deliverables:

• Configured ledgers
• Tax matrix
• Bank integration

Cutover happens at a period boundary with a timed runbook, and our consultants sit with your team through the first close in D365 Project Operations, then hand over documented procedures and a tuning backlog.

Deliverables:

• Cutover runbook
• First close support
• Procedure documentation