IFRS is not a report. It is a second set of facts.
Most groups we meet keep IFRS in a consolidation workbook. Local GAAP posts in the ERP. At quarter-end someone maps accounts, reverses local tax treatments, books IFRS 16, 9 or 15 adjustments, and emails a pack the auditor will politely distrust. The workbook is not a control. It is a second ledger with no posting date and no named owner.
A global Dynamics 365 rollout that still needs that workbook has not finished. IFRS has to be produced from the same postings as the statutory books, or you will argue the numbers every close.
What the chart must carry
A compliant chart is not a long list of account names. It is a structure that can hold local statutory reporting and IFRS without cloning the company. That means a shared natural account, a local statutory overlay (often a financial dimension or a reporting tree), and an IFRS overlay that can reclassify leases, revenue, ECL and deferred tax without a second set of journals typed by hand.
On Finance & Operations this is the native story: multiple ledgers, posting layers, consolidation, and, where we add it, Asset Leasing Accounting for IFRS 16 so the lease is data, not a year-end surprise. On Business Central you can get close with dimensions and consolidation — until lease accounting, expected credit loss or multi-book inventory force you onto F&O. We say that in the first week, not after you have bought the wrong licences.
The adjustments that cannot live in Excel
IFRS 16: every lease is a schedule, a liability, a right-of-use asset and a set of dated postings. If that sits in a spreadsheet, the auditor will sample it and you will fail the sample.
IFRS 15: performance obligations and contract assets have to follow the contract, not the invoice date your sales team prefers.
IFRS 9: ECL is a model with stages, not a percentage someone typed in March. The model can live in a calculation; the posting must land in the ledger with an audit trail.
We implement those as first-class processes on the platform you actually run. That is why financial-services clients get FSAH as an accounting hub: the core system can stay, the IFRS and group books become Dynamics 365.
One close, two (or three) views
The test is simple. Can the group controller produce local management, local statutory and IFRS from the same trial balance, on the same day, without a mapping file that only one person understands? If not, the rollout is not global. It is a collection of country projects that share a logo.
Software Dynamics designs the chart, the dimensions and the consolidation once, then attaches country books: Kenya PAYE and eTIMS, South African VAT, Nigerian statutory, European IFRS pack. The country team does not invent a new chart. They inherit one and configure the statutory layer.
What to ask any partner before you sign
Ask to see a chart that already carries IFRS and at least two statutory books. Ask who owns the lease schedule. Ask whether a local tax journal can post without breaking the IFRS pack. Ask who will still be in the room at the first year-end under the new books.
We answer those before the statement of work, because a global Dynamics 365 programme that cannot close IFRS is not a programme. It is a very expensive local implementation with a travel budget. If that is the risk you are trying not to buy, start with us.