Poland: Retail-specific scenarios for "RO/FP" document types in Polish Jednolitego Pliku Kontrolnego VDEK (JPK-V7M) in Dynamics 365 Finance

Applies to: DynamicsDynamics 365Microsoft Dynamics 365 for Financials


On July 4,2019 the Act on Tax on Goods and Services, binding from September 1, 2019 introducesthe obligation to report in an electronic document that consist of JednolityPlik Kontrolny VAT (JPK_VAT) with the declaration (Jednolity Plik Kontrolny  VDEK – “JPK_VDEK”) – JPK-V7M.

MicrosoftDynamics 365 Finance supports JPK_VDEK format. Find details on the initialfeature release and further updates in the following KB articles:

KB number



JPK_V7M replacing JPK_VAT (SAF VAT) from October 1, 2020 in Dynamics 365 Finance


supplemented pack I for Standard Audit File VAT declaration with registers (JPK_V7M) in Dynamics 365 Finance


VAT declaration with registers JPK-V7M (VDEK) in Excel format in Dynamics 365 Finance


VAT declaration with registers JPK-V7M (VDEK) unlock partial generation possibility in Dynamics 365 Finance


VAT declaration with registers JPK-V7M (VDEK) – mandatory split payment reporting in Dynamics 365 Finance

This article is dedicated to implementation of changesin the JPK_V7M solution to support additionally retail-specific scenarios accordingto clarifications, published in Q&A section of the official "Taxportal" of the Ministry of Finance of Poland.


The changesdescribed in this article are supported in following or later versions ofFinance:

Dynamics 365 Finance version

Build number









Import anduse the following versions of Electronic reporting configurations, whichdeliver changes described in this article:

ER configuration name



Standard Audit File (SAF-T)



Standard Audit File model mapping

Model mapping


JPK_V7M XML format (PL)

Format (exporting)


JPK-V7M Excel format (PL)

Format (exporting)


Import thelatest versions of these configurations. The version description usuallyincludes the number of the Microsoft Knowledge Base (KB) article that explainsthe changes that were introduced in the configuration version. Use “Issuesearch” tool of the LCS portal tofind the KB by the number.

Note: After all the ER configurations fromthe preceding table are imported, set the Default for model mappingoption to Yes for “Standard Audit File model mapping” configuration.

For more informationabout how to download ER configurations from the Microsoft global repository,see DownloadER configurations from the Global repository.

Import and use thelatest version of Electronic messaging setup package from Shared asset libraryof LCSportal: PL JPK_VDEK EM setup.zip.

Hotfix Information

Report“RO” and “FP” document types for retail operations

Starting fromversion 83.169 of “JPK-V7M XML format (PL)” supports reportingof “RO” and “FP” document types for retail operations in case when “Supplementaryinvoices for retail sales for Poland” local Polish feature is used.

Business requirement

Basing on clarifications, published in Q&A section of the official"Tax portal" of the Ministry of Finance of Poland the following rulesto report sales invoices for retail:

  • All fiscal receipts printed and given to the customersmust be aggregated and reported as document of "RO" type (summarizedinvoice). Sales to non-domestic customers must be excluded from aggregation andreported as normal invoice (with no Document type marker). Aggregation shouldbe done for reporting period.
  • Salesdocuments reported as "RO" (summarized invoice) are not subject forGTU markers.
  • Domesticsales aggregated for reporting as "RO" taxable document must beadditionally reported as separate taxable document of "FP" documenttype if customer requested an invoice for this sale.
  • Invoicesmarked as "FP" document type must be excluded from totals in both"SprzedazCtrl" and all related P_* values of the declaration part.
  • Salesdocuments reported as "FP" are subject for GTU markers. 

Initial assumptionsunderlying the solution in the reporting of fiscal documents in JPK-V7M

  1. All the documents coming from POS are previously fiscalized.
  2. Information about fiscal receipts processed on POS is reflected correctly in the system data base tables:
    • RetailTransactionTable
    • RetailTransactionSalesTrans
    • RetailTransactionTaxTrans
  1. In case when customer provided a VAT number for the fiscal receipt on POS, it is stored in RetailTransactionFiscalCustomer.SerializedData
  2. All the fiscal receipts and pre-aggregated fiscal documents posted via Retail statement, which must be aggregated for reporting purposes, are posted in Customer invoice journal of the system in “Fiscal document” or “Fiscal document converted to invoice” statuses.
  3. In case when an invoice was created on POS, it is correctly reflected in the RetailTransactionSupplementaryInvoice table.
  4. In case when a fiscal receipt was converted from fiscal document to an invoice (for non pre-aggregated fiscal documents only), it is reflected as “Fiscal document converted to invoice” status of invoice in Customer invoice journal of the system.
  5. Only posted retail transactions of “Sales” type are considered as retail-invoices for the purpose of reporting as “FP” document type.
  6. Specific scenarios like “gift-card” are out of scope of the current implementation.

Supported business userscenario in Finance

To report“RO” and “FP” document types for retail operations use parameters of the "Retail-specificsales marking" group of parameters of the Wygenerowanie JPK_V7M (EMGenerateJPKVDEKReportController_PL) executable class (Tax > Setup > Electronic messaging >Executable class settings):

  • "Aggregatefiscal documents" check box activating "Criteria to collectcustomer invoices for aggregation ("RO" - summarized invoices)"records to include to collect and aggregate fiscal receipts to be reported as“RO” document type.
  • "Reportretail POS invoices" option to collect retail-invoices with “Invoicedate” in the reporting period to report them as “FP” document type.
  • "Reportfiscal document converted to invoice" option to collect invoices fromCustInvoiceJour table in "Fiscal document converted to invoice"statuses with “FiscalDocDate_PL” in the reporting period and report them as"FP“ document type.

“Aggregate fiscaldocuments“ parameter

By default,this check box is disabled. When "Aggregate fiscal documents"check box is marked, domestic invoices in "Fiscal document" or"Fiscal document converted to invoice" status with “Date ofVAT register” in the reporting period are reported as aggregated one “RO”document for the reporting period (month or part of the reporting month). Definecompany-specific criteria of “Domestic” fiscal documents to beaggregated by using “Criteria to collect customer invoices for aggregation("RO" - summarized invoices)”. When "Aggregate fiscaldocuments" check box is not marked, system does not aggregate anydocuments - they are reported as "standard" ones with no TypDokumentuapplied - report works as it is before this change.

Aggregated“RO” document is included into the report with following header fields:

Reporting tag







Sprzedaz paragonowa




The last date of the reporting period


The last date of the reporting period



“Report retail POSinvoices” parameter

By default, this check box is disabled. Whenparameter is activated, system collects retail-invoices fulfilling thefollowing criteria:

  • Theremust be a Retail-invoice (inRetailTransactionSupplementaryInvoice table) for such Retail transaction (inRetailTransactionTable table)
  • RetailTransactionTable.Type = RetailTransactionType::Sales
  • retailTransactionTable.entryStatus= RetailEntryStatus::Posted and retailTransactionTable.StatementIdfield value is not empty
  • “Invoicedate” (RetailTransactionSupplementaryInvoice.InvoiceDate) is in thereporting period

    Fields ofthe “Retail POS invoices” must be filled in as following:

Reporting tag





“BRAK” or RetailTransactionFiscalCustomer.SerializedData


Name of the customer from the Customer master data (RetailTransactionSupplementaryInvoice.AccountNum) or “BRAK”









Fields ofthe SAFTTaxTransByReportingCode_PL table are filled in from the following datasources:

Table name

Used field name


Type, EntryStatus, StatementId, Channel, Store, Terminal, TransactionId


TaxCode, TaxPercentage, TaxBaseAmount, Amount, IsExempt, Channel, StoreId, Terminal, TransactionId


InvoiceId, InvoiceDate, AccountNum, CustInvoiceJour, Channel, Store, Terminal, TransactionId


TaxGroup, TaxItemGroup, TransDate, Currency, Channel, Store, TerminalId, TransactionId


SerializedData, Channel, Store, Terminal, TransactionId

"Report fiscaldocument converted to invoice" parameter

By default, this check box is disabled. Whenparameter is activated, system collects invoices from CustInvoiceJour table byusing the same “Criteria to collect customer invoices for aggregation” definedfor Domestic invoices for aggregation with following additional criteria:

  • CustInvoiceJour_PL.FiscalDocState_PL= “Fiscal document converted to invoice”
  • CustInvoiceJour_PL.FiscalDocDate_PLin the reporting period

    Theseinvoices are treated in the preprocessing as "standard" ones withonly difference that their type  is setto "FP".

    When "Reportfiscal document converted to invoice" parameter is disabled, this setof tax transactions and related Customer invoices are excluded from the set oftransaction reported in "standard" way in case when they wereaggregated and reported as “RO” document type.

More information

You can 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:





In 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.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.