Finance | Project Operations, Human Resources, ...

D365 F&O anmd SAF-T and Main accounts with Legal entity override

(3) Share

Report

Posted on by KB-06020946-0

I am currently working in a D365 F&O, versionm .046:

We have a common COA for all LE in this enviroment. For a number of the main accounts we have setup a LE override, meaning the the Norwegian Company will
not use these accounts. When generating the SAF-T report, we get error messages on the accounts marked with not to be used by the Norwegian LE.

Is there any solution to avoid these error by setting up these accounts as well in the Additional Consolidation Accounts?
The setup looks like this.

Anyone having an idea if the Consolidation Account Name need to be filled in?

Main account	Main account name	Consolidation account group	Consolidation account	Consolidation account name	SAT level
10050	NAME	SAF-T	1.16.00		0

Thank you in advance for your kind help here.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Assisted by AI

ANInnoSolutions 534 on at

Like (0)

Report
Copy link

Link copied!
Hi KB-06020946-0,

1) Issue
When generating the Norwegian SAF‑T report in D365 Finance (version 10.0.46), error messages occur for main accounts that are excluded for the Norwegian legal entity using Legal Entity overrides.

Even though these accounts are configured as “not to be used” for the Norwegian company, they are still included and validated during SAF‑T generation.

Example setup:
Main account: 10050
Main account name: NAME
Consolidation account group: SAF-T
Consolidation account: 1.16.00
Consolidation account name: (empty)
SAF-T level: 0

2) Reason
The SAF‑T report does not consider Legal Entity overrides when validating accounts.

Instead, the report:
- Evaluates the entire shared Chart of Accounts (COA)
- Requires all main accounts to comply with Norwegian SAF‑T structure and mapping rules

As a result:
- Accounts that exist in the COA but are not enabled for the Norwegian legal entity
- Still trigger validation errors if required SAF‑T attributes or mappings are missing

Regarding the example:
- The Consolidation account group = SAF-T is correctly assigned
- The Consolidation account (e.g., 1.16.00) is correctly populated and represents the required SAF‑T mapping
- The Consolidation account name is not required and can remain empty

Additional clarification:
- Additional Consolidation Accounts are only used for consolidation and are not used by SAF‑T reporting
- The Consolidation account name field is not validated by the SAF‑T process

3) Resolution
Recommended approach:
Ensure that all main accounts in the shared COA, including those not used by the Norwegian legal entity, have:
- A valid Consolidation account group (SAF-T)
- A populated Consolidation account (Norwegian standard mapping)
- Required account metadata (e.g., account type and classification)

Important:
Even a single unmapped account in the COA (regardless of LE override) can trigger SAF‑T errors.

Not valid solutions:
- Using Additional Consolidation Accounts → does not affect SAF‑T validation
- Filling Consolidation Account Name → not required for SAF‑T

Summary
The setup in the example is valid for SAF‑T, and the Consolidation account name does not need to be populated.

However, SAF‑T validates the full Chart of Accounts and does not respect Legal Entity overrides.
To avoid errors, all accounts must have valid SAF‑T mappings, regardless of whether they are used in the Norwegian legal entity.

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References:

Microsoft Licensing Guide

Microsoft Doc`s/Learn

Was this reply helpful? Yes No
Suggested answer

Giorgio Bonacorsi 3,439 on at

Like (1)

Report
Copy link

Link copied!

Hello,

sorry, I'm not familiar with this report, but I found the MS guide concerning the SAFT-Report for the noverge: https://learn.microsoft.com/en-us/dynamics365/finance/localizations/norway/emea-nor-satndard-audit-file-for-tax

As you mention, the first option is doing the mapping of the main account using the consolidation group.

However, the guide mentions that you can alternatively way, doing the mapping directly in the Electronic report.

Thank you,

Giorgio

Was this reply helpful? Yes No
Suggested answer

Alireza Eshaghzadeh 15,211 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @KB-06020946-0

I recommend first reading my blog post about SAF-T (NO) version 1.3, where I explain the main account mapping setup in more detail:
SAF-T(NO) – Version 1.3 – DynFOTech
SAF-T Format (NO) Configuration Updates and Improvement – DynFOTech

If you have a common chart of accounts across legal entities, you should still map the relevant main accounts in the selected Consolidation account group. The legal entity override controls whether the account can be used in that legal entity, but the SAF-T mapping is based on the main account mapping setup used by the report.
Regarding your question about Consolidation account name: this field is optional for SAF-T. The important fields are:
Main account
Consolidation account group
Consolidation account
Consolidation account name

For Accounts in the LE COA that does not find standard main account you can use Other.

Was this reply helpful? Yes No