I find this question to have been posted earlier, but without a definite reply or a reference to a solution.  It is in reference to the SAF-T file and the use of GroupingCategory in conjunction with GroupingCodes instead of StandardAccountID as the mapping option.

Background:

We are based in Norway and need to comply with the Norwegian SAF-T regulation.  These regulations allows us to choose how we want to map our GL-accounts. However, the SAF-T file has to correspond to how we report taxes, and since we report taxes using schema RF-1167, we need to map our GL-accounts to these RF-1167 codes.  In other words, we cannot map our GL-accounts towards the Standard SAF-T accounts.  The Norwegian SAF-T Financial Data - technical description (see norwegian-saf-t-financial-data---technical-description.pdf (skatteetaten.no) pages 12-13 explains how this can be done by using the tags GroupingCategory (value = RF-1167) in conjunction with the corresponding set of codes in the GroupingCode tag.  These codes have been downloaded from GitHUB, and setup similarly to how we would set up the SAF-T standard codes. 

We have more or less followed the setup instruction as posted in a separate topic in this forum, with a slight and irrellevant difference in the naming of the Accounting Attribute (NO2 instead of SAF-T):

• In Accounting Rules > Audit Interface > Basic Data > Audit Formats, create an Audit Format with File Name: SAF-T, File Type: SAF-T and File Template ID: SAF-T Norwegian Template.
• Right click on the newly created record, go to Audit File Basic Data.
• Enter a new record and enter Audit Contact Person information.

• Select the relevant Code Part Attribute,
  1. Update the company using the Norwegian Template (AccountingAttribute, AccountingAttributeCon and AccountingAttributeValue). 
  2. Once the update is done, a new Accounting Attribute as ‘NO2’ will be created with Norwegian Chart of Accounts.  

• Map the relevant RF-1167 Tax Codes.

However, when generating the file using the Audit Interface, the system populates the StandardAccountID tags with our RF-1167 codes. 

RF-1167 codes are not equal to standard saf-t account codes, however, since the values are put in the StandardAccountID tag instead of the GroupingCode tag (and we do not get a GroupingCategory indication), the Norwegian Tax Authorities reads this as Standard SAF-T accounts.  Needless to say, this generates a validation error once recieved and validated at the tax authorities. 

We are on IFSAPP 10, UPD11.  We have just received patches for UPDT 12-17, but there is no reference to this issue in any of the release notes / bill of deliveries. 

I hope somebody have managed to find that the SAF-T solution as it has been delivered here in Norway do in fact support the use of GroupingCategory and GroupingCode, and can share some insight as to how I need to set up the systems data.