Auditors review ledger data as software processes balances and generates a structured XAF audit file.
Anyone who has ever babysat a mission-critical enterprise resource planning (ERP) database during month-end or year-end close knows the specific kind of dread that sets in when a statutory tax export starts chewing through millions of general ledger rows. While the progress indicator crawls across the screen, system resources spike, concurrent users complain about sluggishness, and the finance team stares at the clock. For organizations operating in the Netherlands, Microsoft has rolled out a targeted cure for that exact bottleneck in Dynamics 365 Finance.

Listed under Microsoft's AI at Work roadmap (ID 576799) as generally available starting in June 2026, the update introduces significant performance optimizations inside Globalization Studio for generating the mandatory Dutch Audit File Financial—known locally as the XML Auditfile Financieel or XAF. Designed specifically for legal entities whose primary address is in the Netherlands, the enhancement re-engineers how Dynamics 365 Finance compiles and exports XAF 4.0 files, shifting heavy balance calculations into the background and pairing them with a modernized Electronic Reporting (ER) mapping architecture.


Auditors review ledger data as software processes balances and generates a structured XAF audit file. Why XAF 4.0 Changed the Game for Dutch Finance Teams​

To appreciate why Microsoft rebuilt the plumbing beneath this report, it helps to look at the regulatory landscape in the Netherlands. For years, Dutch businesses generated their digital audit trails using the legacy XAF 3.2 standard, which Microsoft's localization documentation designates for reporting periods prior to December 31, 2025. Starting January 1, 2026, the Dutch Tax Administration (Belastingdienst) transitioned to the XAF 4.0 schema.

According to Microsoft Learn's release plan documentation for the regulatory update, XAF 4.0 was published in February 2025 (following a November 2024 consultation version) to modernize and streamline the digital audit schema. The updated standard trims the number of data elements down from roughly 250 to about 90, enforces alignment with the Dutch standard chart of accounts known as ReferentieGrootboekSchema (RGS), improves machine-readability, and prepares the groundwork for future harmonized European Union digital tax frameworks such as ViDA (VAT in the Digital Age) and SAF-T.

While a leaner XML schema is great news for tax authorities and auditors, generating the export from a high-volume ERP environment still requires aggregating massive ledger tables and mapping every account accurately. Why force the ERP server to calculate every trial balance from scratch at the exact moment an auditor or tax controller asks for the file?

Summary: Regulatory Context​

  • Legacy Standard: XAF 3.2 applies to reporting periods before December 31, 2025.
  • Current Mandate: XAF 4.0 applies starting January 1, 2026, consolidating schema elements from ~250 to ~90 and aligning with Dutch RGS account codes.
  • Eligibility: This Dynamics 365 Finance localization applies to legal entities with a primary address in the Netherlands.

Under the Hood: Two Architectural Upgrades​

Microsoft's performance overhaul for the Dutch audit file—available starting in Dynamics 365 Finance version 10.0.48—applies exclusively to the XAF 4.0 format. It does not retroactively accelerate XAF 3.2 exports. Instead of relying on brute-force runtime queries, the update splits the optimization across two core mechanisms:

1. Pre-Aggregated General Ledger Dimension Set Balances​

Historically, running a dimension-heavy financial report meant the system had to compute ledger balances on the fly when the report was triggered. The updated XAF 4.0 workflow hooks into Dynamics 365 Finance's Performance enhancement for general ledger dimension set balance calculation feature.

When an administrator enables this capability and turns on balance tracking for the required financial dimension sets—specifically the main account dimension set used by the Dutch XAF 4.0 feature—Dynamics 365 Finance precalculates and stores those balances in optimized tables that consume less storage space. A background process automation job called the General ledger balance process runs every five minutes by default, continuously updating the ledger balances as new transactions post. When a finance user later requests the XAF 4.0 export, the report pulls directly from these pre-aggregated trial balance figures rather than computing everything from scratch.

2. A Dedicated Electronic Reporting (ER) Model Mapping​

The second pillar lives inside Microsoft's no-code/low-code Globalization Studio and Electronic Reporting framework. Previously, both XAF 3.2 and early iterations of XAF 4.0 (prior to version 47.8) relied on an older model mapping built directly into the base Audit file model configuration.

Starting with version 47.8 of the Audit File Financial XAF 4.0 in XML (NL) format, Microsoft introduced a separate, standalone ER configuration named Audit file model mapping. Engineered specifically around XAF 4.0 and current ER best practices, this decoupled mapping replaces the legacy embedded mapping whenever the Netherlands performance improvement feature is switched on, cutting runtime overhead and making future regulatory updates easier to maintain.

Reporting ScenarioER Format UsedModel Mapping UsedRequired Feature Management Switch
XAF 3.2 (Before Dec 31, 2025)Audit file (NL)Old model mapping (built into Audit file model)None
XAF 4.0 (From Jan 1, 2026, pre-v47.8)Audit File Financial XAF 4.0 in XML (NL)Old model mapping (built into Audit file model)None
XAF 4.0 Optimized (From Jan 1, 2026, v47.8+)Audit File Financial XAF 4.0 in XML (NL)Audit file model mapping (new, separate configuration)[Netherlands] Audit File Financial XAF 4.0 - performance improvement ( plus GL dimension set balance feature)

Summary: Technical Architecture​

  • Version Floor: Requires Dynamics 365 Finance 10.0.48 or later and ER format Audit File Financial XAF 4.0 in XML (NL) version 47.8 or later.
  • Background Processing: The General ledger balance process updates balances every 5 minutes by default, eliminating scratch calculations at report runtime.
  • Decoupled ER Mapping: Activates a standalone Audit file model mapping configuration instead of the legacy mapping embedded in Audit file model.

Step-by-Step Admin Guide: Enabling Faster XAF 4.0 Exports​

This update is not turned on automatically; it is categorized as an administrator-enabled feature. Furthermore, from an enterprise IT governance perspective, flipping switches that alter how general ledger balances are stored is never something you do on a whim on a Friday afternoon.

Microsoft Learn explicitly warns administrators to review any existing customizations that rely on the previous balance data model before enabling the general ledger dimension set balance feature in production. Always run full functional and performance testing in a sandbox or User Acceptance Testing (UAT) environment first.

Once your sandbox validation gives you the green light, follow this exact sequence to deploy the optimization:

Step 1: Enable the Feature Management Switches​

  1. In Dynamics 365 Finance, navigate to System administration > Workspaces > Feature management.
  2. Search for and enable Performance enhancement for general ledger dimension set balance calculation.
  3. Search for and enable [Netherlands] Audit File Financial XAF 4.0 - performance improvement.
    • Note: This second switch is the master toggle that instructs Finance to use the new ER model mapping and unlocks the dedicated export format parameter in General ledger parameters.

Step 2: Set Up Financial Dimension Sets and Balance Tracking​

  1. Go to General ledger > Chart of accounts > Dimensions > Financial dimension sets.
  2. Verify that the main account dimension set (which the Netherlands XAF 4.0 performance feature relies upon) is defined.
  3. Select the relevant dimension set and click Enable balances to initiate background tracking.
  4. Click the Balance status button to monitor progress.
    • Crucial Operational Caveat: For large enterprise databases, the initial balance calculation can take several hours to complete. Any reports that depend on dimension sets will remain unavailable until this initial background pass finishes. Plan your deployment window accordingly!

Step 3: Import the Required ER Configurations from Dataverse​

  1. Navigate to Organization administration > Electronic reporting > Configurations.
  2. Import the latest versions of the following Electronic Reporting configurations from Dataverse (checking the version description for associated Microsoft KB article numbers):
    • Audit file model (Model)
    • Audit file model mapping (New separate Model mapping)
    • Audit File Financial XAF 4.0 in XML (NL) (Format, version 47.8 or later)

Step 4: Configure the General Ledger Export Parameter​

  1. Go to General ledger > Ledger setup > General ledger parameters.
  2. On the Ledger tab, locate the Ledger transactions export format field (this field is only visible when the Netherlands XAF 4.0 performance feature is enabled).
  3. Select Audit File Financial XAF 4.0 in XML (NL).

Step 5: Map Main Accounts to Dutch RGS Codes​

To ensure the exported XML populates the <RGScode> element under the company > generalLedger > ledgerAccount node, associate your main accounts with the Dutch standard chart of accounts:

  1. Create a Consolidation account group (for example, named RGS).
  2. Add your main accounts to this group and enter the corresponding standard RGS code in the Consolidation account field.
  3. You may optionally fill in the Consolidation account name field for internal clarity, though XAF 4.0 does not include that description field in the exported XML.

Step 6: Generate the Audit File​

  1. Navigate to General ledger > Periodic tasks > Audit file.
  2. Enter your desired reporting range in the From date and To date fields.
  3. In the Consolidation account group field, select the RGS group you configured (this parameter is optionally required for XAF 4.0 reporting starting January 1, 2026).
  4. Notice what is missing: when the [Netherlands] Audit File Financial XAF 4.0 - performance improvement feature is enabled, the Format mapping dropdown is hidden from the dialog box because the system automatically enforces the format you configured in General ledger parameters. (If the performance feature were turned off, you would manually pick between Audit File Financial XAF 4.0 in XML (NL) and the legacy Audit file (NL) format here.)
  5. Click OK to generate the XML output.

The Practical Takeaway for ERP Administrators​

It is worth noting that while Microsoft promises "significantly faster" exports and reduced system load for large transactional volumes, neither the roadmap entry nor the official technical documentation publishes a specific percentage speedup or benchmark runtime. In real-world ERP environments, your mileage will depend on transaction density, batch server allocation, and how cleanly your chart of accounts is structured.

Still, from an architectural standpoint, shifting dimension balance aggregation from an on-demand reporting bottleneck to an incremental five-minute background task is textbook database optimization. As long as IT and finance teams respect the two big operational hurdles—testing custom code against the updated balance data model in UAT and scheduling around the multi-hour initial balance calculation—Dutch legal entities on Dynamics 365 Finance 10.0.48 or later can close their books and satisfy Belastingdienst XAF 4.0 audits without bringing their ERP environment to a crawl.

 

References

  1. Dynamics 365 Finance: Globalization Studio - Create faster XAF audit files for Netherlands Microsoft 365 Roadmap 2026-10-16T19:09:13.597758Z
  2. Audit file (XML Auditfile Financieel, XAF) - Finance | Dynamics 365 | Microsoft Learn learn.microsoft.com
  3. Create faster XAF audit files for Netherlands | Microsoft Learn learn.microsoft.com