Localisation, the tax engine and statutory reporting

How D365 layers country and region functionality onto a legal entity, how the tax engine determines and posts tax amounts, and how Electronic Reporting answers statutory filing obligations — taught D365-first because the Plex source material is silent on localisation.

What you will be able to do

• Explain how a legal entity's country/region context activates Microsoft-shipped localisation features
• Trace how a tax amount is determined from the intersection of a sales tax group and an item sales tax group
• Distinguish between Microsoft-shipped localisations, ISV localisations, and bespoke builds
• Describe what Electronic Reporting is and how it replaces country-specific custom reports
• Frame the discovery questions that surface the client's actual statutory and tax obligations from Plex or from processes outside Plex

Introduction

The Plex source material says almost nothing about localisation, tax, or statutory reporting. No primary Rockwell source describes a tax engine, a country-specific configuration layer, an e-invoicing capability, or a statutory reporting framework. The posting-rules adapter marks tax accrual as mapping_status: gap with confidence: low.

Country/region activation: how D365 layers localisation

D365's localisation model begins with a single setting: the country/region registered on the legal entity. When a legal entity is configured for Germany, German localisation features activate automatically — German VAT reporting, German payment formats, German Intrastat configuration, German fiscal document layouts.

The tax determination engine

D365 determines tax through a structured intersection model. Understanding it is essential because Plex's tax mechanism is undocumented, and the D365 design must be built from the client's obligations, not from a Plex configuration export.

The Tax Calculation Service and Globalization Studio

For complex, multi-jurisdictional tax determination, D365 offers the Tax Calculation Service (TCS) — a microservice within Globalization Studio that provides configurable, jurisdiction-aware tax determination. TCS extends the native intersection model with:

Electronic Reporting: the statutory output framework

Electronic Reporting (ER) is D365's framework for producing structured output files — VAT returns, Intrastat declarations, SAF-T files, payment formats, and e-invoice XML — without code. An ER solution consists of three layers:

Electronic Invoicing: the clearance-model add-on

A growing number of countries mandate clearance-model e-invoicing — structured XML submitted to a government platform in real time (or near-real time) before an invoice is legally valid. Examples include Italy (SDI), France (Chorus Pro), Saudi Arabia (ZATCA), Mexico (CFDI), and Brazil (NF-e).

The discovery questions: surfacing hidden obligations

Because Plex's localisation capabilities are undocumented, the programme must surface the client's actual obligations through structured discovery. These questions must be asked during the Discover phase, not assumed:

Withholding tax

Some jurisdictions require that a portion of a payment to a vendor is withheld and remitted directly to the tax authority. D365 supports this through:

Conditional sales tax

In some jurisdictions, sales tax is not remitted to the authority until the customer actually pays the invoice — the cash accounting or conditional tax regime. D365 supports this through dedicated conditional sales tax codes, sales tax groups, and ledger posting groups.

Knowledge check

Summary

Localisation on the Plex path is defined by an absence: the source material does not describe tax, statutory, or country-specific capabilities. The D365 target, by contrast, provides a comprehensive localisation framework — automatic country activation, a structured tax engine, Electronic Reporting for statutory output, and an…