Is it allowed to use NA in GroupingCategory and GroupingCode?

[TonjeH1]

We have customers with shared chart of accounts across different companies in different countries (running on Dynamics 365 FO). This means that a lot of the main accounts are not in use for the Norwegian companies. Is it allowed to use NA in GroupingCategory and GroupingCode for Main accounts that are not in use for the reporting company?

[Alireza-Eshaghzadeh]

Hi @IngeridRobole ,
Do you have any updates on this?
Can we use "NA" for ledger accounts where a Grouping Category has not been defined on https://github.com/Skatteetaten/saf-t/blob/master/SAF-T_Financial_1.3/Grouping%20Category%20Code/CSV/naeringsspesifikasjon.csv?

Example:

[IngeridRobole]

In cases where it is not possible to map an account to a GroupingCategory/GroupingCode in the income statement, "NA" can be used in the elements. However, it is worth noting that all accounts included in the income statement must be mapped to it.

[TonjeH1]

Thank you. My question may seem unusual, but it stems from a requirement within Microsoft's solution where all accounts must be mapped, regardless of whether they have transactions or not. A shared chart of accounts may be used across multiple companies, where not all accounts are relevant to each company. Therefore, mapping to "Not Applicable" (NA) may be necessary. If the SAF-T file only includes accounts with opening and closing balances and transactions, accounts mapped to NA will be excluded.