What’s missing in most SAF-T solutions?

13-07-16 | Blog

A fundamental element in having a complete solution is a tax auditor’s perspective and validation. After all, these reports are really for the purpose of reconciling your tax filing results and can affect your company reputation or incur heavy tax fines. We can write the ABAP codes but we would not be confident with the mapping of the SAP tables to the SAF-T schema for the elements released by each tax administration. 7 elements for the SAF-T Poland/JPK reports, 18 fields for Fichier des ecriture comptables, and how many for SAF-T Luxembourg/FAIA, etc; all different requirements per country*. 
In a previous post (see: 5 key criteria SAP users need to consider when choosing a solution for preparing SAF-T reports), we shared the SAP FAQ document on SAP JPK (SAP SAF-T Poland) reports, and there it states that the current SAP built-in solution does not deliver the 7 JPK (SAF-T Poland or JPK: Jednolity Plik Kontrolny) structures themselves nor produce the XML reports. Our research also found other companies suggesting other extraction tools or methods but it is unclear if they have been able to determine the mapping to the SAF-T schema. Perhaps they will work on it on a case by case basis, customising it to the customer’s system set up. But you will definitely still need an auditors’ expertise.

*Terms and definitions post to be found here: 6 definitions to help you understand SAF-T better