Microsoft Dynamics 365 Business Central, IFRS and Finance Transformation

Picture a perfectly configured Business Central. Every process automated. Every entry posted. No error messages, no red flags. And the revenue figure is wrong. Not a bug, the system did exactly what it was told to do. The specification simply wasn't aligned with the accounting standard.

That scenario is the reason this blog series exists, and it's the reason this post exists: before we go deep on individual standards, I want to show you the whole map: Every BC module the series touches, and why IFRS reaches into each one.

IFRS is not a "finance module" problem

The most common misconception I meet on implementations is that IFRS lives in the G/L. It doesn't. Standards attach to transactions: a sales order, a lease, a production output, a foreign-currency invoice and transactions are born in operational modules, long before they ever reach the general ledger.

By the time a posting arrives in the G/L, the important IFRS decisions have usually already been made: Which WIP method the project carries, Which costing method sits on the item card, Whether the sales line was split by performance obligation, Which depreciation book the asset belongs to. If those upstream decisions are wrong, no amount of journal-entry heroics at period-end fixes the pattern.

The ERP is the instrument. The standard is the score. The system plays the notes, the standard writes the music …!

So here is the map: fifteen Business Central modules and features scoping an IFRS-aware implementation, with the standards each one carries.

1. The financial core

Finance Management

The general ledger, journals, batches and posting setup are where every IFRS adjustment ultimately lands. IFRS 16 interest journal, IFRS 9 ECL provision movement, IAS 12 deferred tax posting. BC gives you the machinery (journal templates, recurring journals, dedicated batches); the standard tells you what those journals must contain. A disciplined batch-and-dimension structure here is what makes every other module's compliance auditable.

Fixed Assets

Dual depreciation books deliver parallel local-GAAP and IFRS asset accounting (IAS 16), the FA-as-master architecture carries IFRS 16 right-of-use assets, and the Write-Down posting type is how IAS 36 impairment losses reach the ledger. One module, three standards.

2. The revenue engine: five modules, one standard

IFRS 15 is the standard that proves the "transactions, not ledgers" point, because compliant revenue recognition in BC is spread across five different modules depending on how you earn it:

Sales

Point-in-time recognition, control transfers at a moment, the posted sales invoice is the revenue event. The sales order is also your IFRS 15 contract record, and one line per performance obligation is the discipline that makes everything downstream possible.

Projects (Jobs)

Over-time recognition via WIP methods, percentage of completion for the contract asset–liability pattern and completed contract where recognition waits. The WIP account classification (balance sheet vs P&L) is the most misconfigured setup in the module, and it directly drives your contract assets and liabilities.

Subscription Billing

BC has a native IFRS 15 engine (BC 2024 onward): Billing schedules, Deferred revenue posting, and Periodic release routines. It automates the mechanics standalone selling prices, breakage estimates and modification accounting remain judgement calls that you configure into it.

Deferrals

Deferral templates are the lightweight workhorse for straight-line release of prepaid income and expenses. IFRS 15 decides whether deferral is even permitted.

Service Management

Stand-ready obligations (such as annual maintenance released monthly) and point-in-time chargeable work reflect different revenue recognition patterns. The distinction also sits within the IAS 37 boundary between an assurance warranty (a provision) and a service warranty (a performance obligation).

3. The cost side

Inventory

IAS 2  in Business Central module form covers costing methods such as FIFO, average, and standard costing, while LIFO remains available in configuration but is not permitted under IFRS since 2005.

It also includes the Adjust Cost batch job, which is essential for ensuring inventory valuation accuracy, and the net realisable value (NRV) test with its mandatory reversal process. You must also ensure the inventory period close is completed in Business Central.

Manufacturing

Production orders, standard costing and variance capitalisation all feed IAS 2 cost of conversion. And a trap worth its own post: there are two things in BC called "WIP" manufacturing WIP is inventory; project WIP is an IFRS 15 contract position. They are not interchangeable.

Landed Cost

Item charges (or a landed-cost app) allocating freight, duty and handling into item cost are not a nice-to-have. IAS 2 requires costs of purchase to include them. Expensing freight that belongs in inventory misstates both margin and the balance sheet.

4. The cross-border pair

Withholding Tax

One of the places BC genuinely helps with IAS 12: WHT posting groups deduct at source on cross-border payments and keep the reclaimable balances visible. While deferred tax, the other half of IAS 12, remains a manual schedule and journal.

Currency

IAS 21 end to end: exchange-rate setup, the Adjust Exchange Rates batch revaluing monetary items at period-end, realised FX posting automatically on settlement, and Additional Reporting Currency for presentation-currency needs. The machinery is excellent; the risk is simply not running it. An unrun batch means unrealised FX of exactly zero, which is a guaranteed audit finding.

5. The reporting layer

Financial Reports

The most powerful, most underused feature in BC for IFRS work. Row definitions become your statement lines, including the five mandatory P&L categories arriving with IFRS 18  and column definitions filtered by dimension give you IFRS and local GAAP side by side from one dataset.

Dimensions

The backbone of parallel reporting. A REPORTING_FRAMEWORK dimension (LOCAL / IFRS / IFRS_ADJ) plus an IFRS_STANDARD dimension means every adjustment is findable, filterable and defensible. When the auditor says "show me everything you posted for IFRS 16", the answer is one filter.

Consolidated Financial Statements

BC's consolidation module handles business units, account mapping and currency translation for IFRS 10. What it doesn't post, the non-controlling interest split, intercompany eliminations, unrealised IC profit. These becomes a controlled set of manual journals in the consolidation company.

The map on one page

The pattern across all fifteen: in none of these modules will BC stop you posting something non-compliant. No warning, no flag, no audit exception. The question is never "did BC post it?".

It’s "should it have?" That question belongs to the person who understands both the system and the standard. That translation is what this series is for.

See it live: I'm presenting "Dynamics 365 Business Central & IFRS — Where Accounting Standards Meet ERP Reality" at the UK Dynamics 365 & Power Platform User Group National In-Person Meeting, London, 28 July 2026  12 standards, worked journal-level examples, and the configuration behind every module on this map.

And if you're new here: the deep-dive series on IFRS 16, IFRS 15, IFRS 9 etc. in BC with full worked examples is already running on bcforfinance.com. Stay tuned!

📝 This post reflects the author's professional views and is for informational purposes only. It does not constitute legal, financial, or accounting advice.