Standard Audit File (SAF) electronic reporting is available in the Polish version of Microsoft Dynamics AX

This article applies to Microsoft Dynamics AX for the Polish (pl) region.

Within From 1 July 2016, taxpayers in Poland will be obliged to transmit data in a unified format, the so called Standard Audit File (SAF), at the request from tax authorities. The list of reports is below:

  • Accounting books

  • Bank statement

  • Inventory

  • VAT invoices

  • VAT register

A new functionality, which is enable the extraction of data, in accordance with logical structure defined by tax authorities is prepared, in order to build the SAF. The feature was implemented using Application Integration Framework (AIF) services and XSL transformation (XSLT). XSLT allows setting up the selection of Dynamics-relater requisites and mapping them to the e-report elements. In addition, we can set up the relation between VAT codes and e-report elements using Tax reporting codes.

Settings of AIF

1. Open AOT, export XSLT file from the applicable resource into a folder (say, C:\TMP\XSL)

Feature Resource

PL SAF Accounting books AifOutboundPortReportSAFAccountBooks_PL

PL SAF Bank statement AifOutboundPortReportSAFBankStatement_PL

PL SAF Inventory AifOutboundPortReportSAFInvent_PL

PL SAF VAT invoices AifOutboundPortReportSAFVATInvoice_PL

PL SAV VAT register AifOutboundPortReportSAFVATSalesPurch_PL



2. System administration > Setup > Services and Application Integration Framework > Outbound ports for electronic audit reports

a. Click "Create / Update ports". This will populate the list of default ports.

Feature Default port Default XSLT ID/Default AIF port

PL SAF Accounting books “SAF Accounting books (Poland) ”SAFAccountingBooksPoland

PL SAF Bank statement “SAF Bank statement (Poland)” SAFBankStatementPoland

PL SAF Inventory “SAF Inventory (Poland)” SAFInventoryPoland

PL SAF VAT invoices “SAF VAT invoices (Poland)” SAFVATInvoicesPoland

PL SAV VAT register “SAF VAT sales and purchase register (Poland)” SAFVATSalesAndPurchaseReg

Notes

i. For better performance, please make sure the Execute business operations in IL parameter is enabled (Tools > Options > Development > General). Please note that global compilation and rebuilding IL is a mandatory step after the hotfix installation.

ii. The folder where the XSL was exported to (step 1) is used only for editing the XSL (if needed) and uploading it back to Dynamics AX. The transformation does not use the file in the folder after the step 2.d.

iii. For debugging purpose, you may want to get the non-transformed XML. To achieve that clear the XSLT ID field.



Setting of Sales tax reporting codes for VAT invoices and VAT sales and purchase register

As a part of setup for SAF VAT invoices and SAF VAT sales and purchase register reports you need to set up tax reporting codes and map them to elements of XML Schema. The below examples refer to the VAT sales and purchase registers report.

1. Save the schema file (for example, Schemat_JPK_VAT(1)_v1-0.xsd) into a folder (say, C:\TMP\XSD).

2. Open the Sales tax reporting XML codes form (General Ledger > Setup > Sales tax > External > Sales tax reporting XML codes)

3. Click the Import button. Select the schema file with and click "OK".

4. New record in XML schemas list will be created. Choose Type of schema (for example, "SAF VAT sales and purchase register (Poland)").

5. Open the Reporting codes form (General Ledger > Setup > Sales tax > External > Sales tax reporting codes). Map reporting codes to xml schema elements that refer to VAT (for example, ones that start from "K_", like "K_10").

a. Amounts on these reporting codes will be exported to selected tags.

b. Note: if tax transaction contains reporting codes which are mapped both to sales and purchase sides, it will be present both in sales and purchase parts of resulting xml file.

c. You can use arithmetic operations during the mapping, effectively allowing mapping multiple tax reporting codes to one schema element (see below: element P_13_1 refers to the reporting code "1001" which is a sum of reporting code "1" and (-) reporting code "2").Exporting the report file1. By default report menu items are added to General ledger > Reports > External > Services and Application Integration Framework. For example, the below is applicable to Invoice list 2016 (Hungary):

a. Select the invoice date and/or invoice ID ranges (fields Invoice date / "From", "To", Invoice ID / "From", "To")

i. Selected dates / invoice IDs affect the query ranges, not vice versa. To use advanced filtering please use Select button.

b. Select the Format value (by default the format created on Setup, step 2.a is used)

c. Select the Filename value (by default the Default export path from Setup, step 2.c is used)

Click OK. The report is exported to the specified path.

Resolution

The changes in the hotfix enable this feature.

Important: This hotfix contains one or more reports. Make sure that you have imported all of your modified reports into the AOT, and then install the hotfix, and redeploy the reports.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+ContactsCustomers

https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htmIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.


Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must apply these changes in a test environment before you apply the hotfix in a production environment.
For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics AX 2012 R3

  • Microsoft Dynamics AX 2012 R2

  • Microsoft Dynamics AX 2009 SP1

Restart requirement

You must restart the Application Object Server (AOS) service after you apply the hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×