key criteria SAP users need to consider when preparing SAF-T reports

22-06-16 | Blog

We had a recent conference call with the Polish operations arm of a global company. They wanted to find out more about the solution we have been developing to address the SAF-T Poland reports being mandated by the government from 1 July 2016. They have also identified a local consulting firm to potentially help them meet this requirement.

What the Polish team of this global company was not aware of is that first version of the SAP built-in solution provides SAP users with the “means to extract relevant transactional data into Extraction tables” but does not deliver the five JPK (SAF-T Poland or JPK: Jednolity Plik Kontrolny) structures themselves nor produce the XML report. This can be found on the SAP JPK FAQ document available from the SAP website. This means the team will still need to ask an external auditor to validate the data, make some changes to ensure it ties back to the results of their filed tax reports, store the data into the extract tables, and then generate the XML report for submission. So in light of the short timeframe to produce the JPK report, companies still have 4 more steps after data extraction and before submission.

We begin to wonder how much or how little customers understand the complications behind and the time needed to produce these SAF-T Poland SAP/JPK reports or any other SAF-T reports for other countries. We reminded ourselves of our goal for developing our SAF-T solution that is more than just a data extraction tool and would like to share this with you through this post.

We started developing our SAP ABAP Add-On solution to address the SAF-T report requirement back in 2010 when the OECD introduced SAF-T. And we have always worked upon the principle of creating a complete solution that would make life easier for our customer – the users. Therefore, we wanted our solution to:

1. Lessen the number of steps needed to generate an audit-ready XML report with a pre-validated mapping of the SAP tables to the SAF-T schema for a specific country*

2. Extract large data volume from any source type and into any output format (note: XML is the official OECD format but it works poorly as a working format for preparation and auditing step, so we offer several additional formats.)

3. Provide autonomy for your auditors to extract the data and prepare for the report submission within your security parameters

4. Be SAP certified ABAP Add-On that gives you the stability of a plug-in and the benefits of an ongoing maintenance of the software

5. Save time and resources for your IT team by setting up a single solution for all country SAF-T reports


The scope of our SAF-T software development could have stopped at just being able to extract the data from the system. But there are actually more steps remaining for you to do once the raw data have been extracted.

When it comes to selecting the right solution to help you prepare for your SAF-T reports, we believe the 5 elements above should also be your key criteria for consideration.

Lead developer for TJC SAF-T solution

*Find out more in our next post to be published in 2 weeks: What’s the most important and helpful element missing in most SAF-T solutions?