SAF-T – Part 2 (Config)

This blog provides a guide on preparing Microsoft Dynamics 365 Finance & Operations for compatibility with the Standard Audit File for Tax (SAF-T) report. It covers the importation of SAF-T configurations for Denmark, Norway, and Lithuania, focusing on the master and source data required for SAF-T compliance.

SAF-T was initially published in 2005 and has since been adopted by several European countries, including Portugal, Luxembourg, France, Austria, Poland, Lithuania, Norway, Denmark, and Romania, up until 2023. SAF-T is already released for Lithuania, Norway and Denmark in D365FO that can be installed via Microsoft repositories in Electronic reporting.

Before importing the actual SAF-T configuration, please ensure that the following features are enabled via System administration > Workspaces > Feature management, specifically for the legal entity’s primary address:

– Minimize memory consumption by storing datasets at ER reports runtime.

– Optimization of query data source creation time during execution of ER reports.

– Optimize datasets memory consumption at ER reports runtime.

– Accelerate the ER labels storage.

– Use application specific parameters from previous versions of ER formats.

– Standard Audit File for Tax (SAF-T) electronic report.

– Dimension attributes values collection optimization in ‘MasterFiles’ report section of SAF-T for Norway*

* This specifically designed for Norwegian SAF-T (i.e., SAF-T(NO))

To import the SAF-T standard configuration for Danish, Lithuanian, or Norwegian legal entities, please follow the steps outlined below:

• Navigate to Organization administration > Workspaces > Electronic reporting and click on Electronic reporting parameters and set “File” for attachment document types.

• On “Configuration providers” choose Microsoft and click on “Repositories”.

• Choose “Global” type and click on “Open” to connect to Microsoft repositories.

• Search for “SAF-T format” and import the actual configuration based on the legal entity’s primary address. It is recommended to import the newest version of the configuration, as it will include the latest hotfixes or developments.

Note: As of May 2023, Microsoft has released SAF-T configurations for Norway, Lithuania, and Denmark.

Note: The SAF-T configuration itself is shared and can be imported regardless of the company you are importing it for.

Note: The mapping table for each configuration is company specific.

After importing the actual SAF-T configuration, it is necessary to activate the model mapping model as the default, based on the SAF-T configuration. There are two date model mappings available for SAF-T format configurations: “SAF-T General model mapping” and “SAF-T Financial data model mapping”.

• For SAF-T Format (DK) and SAF-T Format (LT), it is necessary to activate “SAF-T General model mapping” as the ‘Default for model mapping’.

• For SAF-T Format (NO), “SAF-T Financial data model mapping” must be enabled.

Note: Only one data model mapping can be enabled as ‘Default for model mapping’ for SAF-T at the same time.

Currently, “SAF-T General model mapping” is associated with source documents such as Sales Invoices, Purchase Invoices, Payments, Movement of Goods, and Asset Transactions. On the other hand, “SAF-T Financial data model mapping” lacks a comprehensive mapping for these specific purposes.

“SAF-T General model mapping” provides general data source mapping for the following master data:

AnalysisTypeTable: The data tables for analytical accounting contain transaction-level details, including financial dimension values.

Assets: The asset information and valuation, along with the corresponding supplier ID, are captured in the relevant data tables.

BankAccounts: Bank accounts.

Customers: Debtors.

GeneralLedgerAccounts: General ledger accounts and balances.

MovementTypeTable: Stock movement types.

PhysicalStock: Physical stock and information on stock entries.

Products: Products and services of a company.

Suppliers: Creditors.

TaxTable: The tax tables of a company.

UOMTable: Table for units of measurement (UOM).

Additionally, it offers general data source mapping for the following transactional data:

GeneralLedgerEntries: Accounting transactions.

Journal: Journal information.

Transactions: Accounting transactions.

Transactions (Line): Transaction lines.

SourceDocuments: Source documents.

            SalesInvoices: Invoices covering sales transactions.

            PurchaseInvoices: Invoices covering purchase transactions.

            Payments: Information on received or perfomed payments.

            MovementOfGoods: Information on quantities of goods received or issued.

            AssetTransactions: Details of all transactions related to an asset.

I hope that this post has delivered valuable insights on SAF-T and the process of importing configurations from Microsoft repositories. If you have any further questions or feedback, please don’t hesitate to use the ‘Leave a Reply’ feature. Your thoughts and inquiries are greatly appreciated!