Skip to Content
Technical Articles

SAF-T Norway Hint & Tips for Solution Implementation

Hi All,

This is a note to help you with some hint and tips for effective implementation of the SAF-T solution for Norway. SAP has provided country  specific solution (Adopting the OECD reporting standard) for statutory reporting and I have had the opportunity to work for Norway based client.

What is SAF-T ?
SAF-T stands for Standard Audit File for Tax, it is a international sandard or medium of reporting accounting information from organizations to its tax authority or any external auditors. It has been defined by Organisation for Economic Co Operation & Development (OECD). The reporting is done in XML.

Purpose of the SAF-T format
Norwegian SAF-T (Standard Audit File – Tax) is standard file format for exporting various types of accounting transactional data using the XML format.
This first version of the SAF-T Financial is limited to the general ledger level including customer and supplier transactions. Necessary master data is also included. Future versions of the SAF-T Financial will include source documents such as detailed invoice data and movements of goods and asset transactions.

To start with, I will first recommend you to go through the notes properly for a clear understanding and then have a discussion with client to ascertain what exactly they want to report. More or less you will have to map the chart of account  with,

  • Standard account provided by Norwegian tax authorities or
  • The income statement for the type of business.

For municipalities, the mapping of the accounts must be to the KOSTRA Arts accounts.

Note: I worked on the Income Statements (Næringsoppgaver) (RF-1167 )

Getting the solution

Oss Notes which needs to be implemented:

2590111 – SAF-T (NO): Collective Note for SAF-T Norway
2448711 – SAF-T Norway: Prerequisite Notes for Installation & Use of SAP Solution
2809649 – Interface Note for SAF-T Norway and System tables update

Once you have the notes implemented, you will have the following things available in system to start working on it.

Masterdata Tables

SAFTNV_INTCA_EXT
SAFTNV_INTCA_GEN
SNV_NO_MAP_TAX
SNV_NO_MAP_ACCT

SNV_NO_GRP_COD This table is required for income statement mapping. The grouping code is mapped with chart of account as per desired category eg : RF-1167 etc. Refer note 2809649.

Extraction Tables

SAFTNV_INTCA_GEN (SAF-T Header of FI documents).
SND_NO_FI_I   (SAF-T Items of FI Documents).

T.Codes
SAFTN_E  for Data Extraction.
SAFTN_D for Data deletion.
SAFTN_G for XML File generation.
SAFTN_M for monitoring.

Note: Refer note 2448711 for configuration help file in pdf format.

Configuring the solution

While you will configure the solution following the user guide provided in note 2448711, you will also require the following three sets of data to configure tax data and the grouping data. While the tax code mapping is straightforward, for the chart of account, a few couple of sittings  with client will be required to prepare the mapping. In my case I was lucky as the client proactively prepared this without much of my help. I just had to explain the following templates to them.

Template for Tax code mapping

Template for the standard account mapping

Template for the GL Grouping (for income statement

Note:

  • If you are mapping for income statement then standard account mapping is not required. However you can still map the SAP GLS and the standard account will show ‘0’ by default.
  • The templates will help you copy and paste the data directly in SM30 maintenance.
  • You may want to create a z maintenance program for these tables for user so that going forward they can add any new GL or tax code for reporting. Otherwise it creates a dependency and user will come back to you for such minor maintenances.

Generating the XML file

One very good feature of this solution is that XML file generation is in built, you can run the data extraction program first using SAFTN_E and then download the XML using T.code SAFTN_G. However you have to follow the file naming conventions as prescribed by the tax authorities.

For example: SAF-T Financial_999999999_20160401235911_1_12.xml

Where:

  • “SAF-T Financial” states the SAF-T type of file
  •  “999999999” represents the organization number belonging to the owner of the data.
  • “20160401235911” represents the date and time when the file was created using a 24-hour clock.
  • “1_12” represents file 1 of 12 total files in the export (same selection)

The solution also gives you the option to rectify the data. You can discard the xml file, and delete the extracted data first using SAFTN_D and then re extract the rectified FI items and then re- generate the XML file. All previous file generation activity can be checked/monitored using SAFTN_M.

What to verify in the XML file

Once you download the XML file, open it and check the following:

  • The version and the schema locn are appearing correctly (1st and 2nd line of the file)
  • All Company code data like address, registration numbers etc are appearing correctly.
  • There’s no <NA> appearing against any tax code or GL. This implies you might have missed out mapping any tax code or GL
  • That the period wise GL opening and closing balance of both PnL and Balance sheet type are appearing correctly. If not you need to check note 2869463 and 2878351.

 

I hope it gives you some idea on how to go ahead with implementing the solution. You can also refer the Skatteetaten website for more details on SAF-T. Also for technical details like xml file structure or for downloading the XML file validator you can refer to Github. https://github.com/skatteetaten/saf-t

Thank you for checking this article. I hope you find it helpful.

Best Regds
Subhadeep

17 Comments
You must be Logged on to comment or reply to a post.
  • @subhadeep.das

    Hello Subhadeep,

    In your precious post about Hint & Tips for SAF-T Norway implementation you are showing an example of “Organization number” (i.e. 999999999) as owner of the data. Could you please explain how this “Organization number” is defined into the customizing?

    Thanks in advance for your attention and support.

    Kind Regards

    Giovanna Scamardella

     

     

    • Hi Giovanna,

      Thanks for your comment.

      Organization number is not a part of customizing. you download the file and rename it as per given convention.

      Note: Organization number is the registration number that you maintain in global parameters (OBY6). The info inside the xml file will come from this area.

      Best regds

      Subhadeep

      • Hello Subhadeep,

        your note that organization number has to be maintained in OBY6 to be shown in xml file is helpful. Is it field STCEG that has to be maintained?

        We do not have own company code for Norway. When I enter registration Number of Norway in field STCEG I get error message that first two characters of the VAT registration number do not correspond to the coutry’s ISO code (because company address is not in Norway).

        Do you know where to maintain Norwegian registration number (to be shown in xml file)  in cases with no own company code for Norway?

        Many thanks for your support in advance.

        Kind regards

        Elke

         

         

        • Hello Elke,

          Apologies for replying late.

          STCEG is meant for vat reg number. For organization number you should check the field in additional data. Refer below screen.

           

          Best regds

          Subhadeep

          /
          • Hello Subhadeep,

            thank you very much for your detailed information and screenshot which field has to be maintained.

            In our case the field “Legal organizational number” is not available. I assume this field can only be maintained in additional data when company code is created with country key Norway. Hence we will have to change program to be able to add registration number in xml file.

            Best regards

            Elke

  • Hi Subhadeep Das ,

    Thanks a lot for this great resume. In the Header of the XML file we have the “Tax Registration Number” and the “Contact Person” field that are empty. Do you know where in SAP we can retrieve those fields and populate them?

    Thanks for your feedback!

    • Hi Youssef,

       

      Apologies for replying late. You can check the OBY6 settings and its additional data screen. You should get the required field there.

      Best regds

      Subhadeep

  • Hello Subhadeep,

    In our SAP system, the fields Norway Company First Name and Norway Company Last Name do not appear in OBY6. I’ve searched in SAP Support Portal for any note, KBA, to add them in T001Z table, without any luck.

    Do you know? It should be similar to Tax Registration Number…. thank you in advance, Maria.

  • Hello Subhadeep;

    We are in the process of testing the xml file with Altinn/Norwegian tax authorities and received a feedback that some of the fields in the file are not anonymised (i.e organization number as an example). How do we ensure that the number is anonymised for test purposes?

    Thank you;

    Andrej

     

    • Hi Andrej,

       

      One of the way is that you can open the file in notepad mode and re write the fields with some random number . This should be only for testing.

       

      Best regds

      Subha

      • Hi Subha;

        Thank you for the response. One other question: when upload files to Altinn, we got an validation error  related to RegistrationNumber and Name in the Customer MasterFiles section. We have addressed this with SAP, but wanted to check: it seems the Tax Registration number needs to be populated in customer master. Should this be in Tax number 2 or Tax number 5?

        Thank you;

         

        Andrej

  • Hi Subhadeep,

    Many thanks for this wonderful article.

    I would like to know the below questions.

    1. As you mentioned we need to implement three notes. Out of these 2590111 having 72 notes. So all 72 we need to implement as a pre-requisite.
    2. All these 72 notes are technical notes and what are the customization required for a functional consultant?
    3. In “Configuring Solution” having three-part 1. Template for Tax code mapping 2. standard account mapping and 3.  GL Grouping (for income statement). — Now in that 3A.  I am not able to see (GL Grouping (for income statement) in customization path (Financial Accounting (New) >> General Ledger Accounting (New) >> Periodic Processing >> Report >> Standard Audit File – Taxation >> Country-Specific Settings) 3B.  For all three customizations (Tax Code Mapping, Standard Account Mapping and G/L Grouping) from where I can get the detail? from the business?
    4. And Shall we need to add the country (RO) in “General Setting”?

    Regards,

    Tarak Nafade

  • Hi Tarak,

     

    • You will require all the notes, there are quite a few correction notes which have come over a period of time. The critical one is the note which rectifies the opening and closing balance.
    • You have to create the GL grouping, take help from client in this. They should be able to guide you. For mapping if you are unable to view the standard grouping list in sap then you need to check for any missing notes. The list should appear.
    • Country is NO.

     

    Best reds

    Subhadeep

    • Hi Subhadeep,

      Many thanks for your help.

      I also need your help in the below points.

      1. Apart from SAT-T Norway Application Help (SAP Note 2448711) what are the setting we need to maintain in OBY6 for file creation?
      2. If my Co. Code does not belong to Norway the where I can maintain OBY6 setting?
      3. Do you have any user manual for Data Extraction, Deletion, File Generation, Monitoring and Validation and Submission of SAF-T file?

      Regards,

      Tarak Nafade

  • Dear Subhadeep,

     

    First of all, thanks for the information. Still a lot to read but it is very good to start with.

    This may sound too obvious. One of the prerequisites should be the installation of Norway localisation package, right? Almost all notes are referring to the component ‘FI-LOC-SAF-NO’.

     

    Kind regards,

    Chan