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

Á við um: DynamicsDynamics 365Microsoft Dynamics 365 for Financials

Introduction


On July 4, 2019 the Act on Tax on Goods and Services, binding from September 1, 2019 introduces the obligation to report in an electronic document that consist of Jednolity Plik Kontrolny VAT declaration with registers (JPK_V7M), here are further “JPK_VDEK”.

Microsoft Dynamics 365Finance supports JPK_VDEK format. Please find details on the initial featurerelease in KB 4540232 and supplemented pack I for JPK_VDEKin KB 4552887.

Thisarticle is dedicated to implementation of changes in the JPK_VDEK solution toaccommodate recent changes in the format (published on May 8, 2020), supportreporting of overdue customers invoices in case when “Overduedebt VAT” Polish local feature is used and provide more usability andflexibility in master data setup for tax reporting purposes.

Overview


The changes describedin this article are supported in following or later versions of Finance:

Dynamics 365 Finance version

Build number

10.0.12

10.0.496.0

10.0.11

10.0.464.10007

10.0.10

10.0.420.20012

Import and use thefollowing versions of Electronic reporting configurations, which deliverchanges described in this article:

ER configuration name

Type

Version

Standard Audit File (SAF-T)

Model

72

Standard Audit File model mapping

Model mapping

72.170

JPK_VDEK XML format (PL)

Format (exporting)

72.150

Import the latestversions of these configurations. The version description usually includes thenumber of the Microsoft Knowledge Base (KB) article that explains the changesthat were introduced in the configuration version.

Note: After all the ER configurations from thepreceding table are imported, set the Default for model mapping optionto Yes for “Standard Audit File model mapping” configuration.

For more informationabout how to download ER configurations from Microsoft Dynamics LifecycleServices (LCS), see DownloadElectronic reporting configurations from Lifecycle Services.

Import and use the latest version of Electronic messaging setup packagefrom Shared asset library of LCS portal: PLJPK_VDEK EM setup v.2 KB4550662.zip.
image.png

This version introduces the followingchanges in the Electronic Messaging (EM) setup:

  • Additionalfields descriptions are extended to support string 255.
  • P_68 and P_69additional fields are excluded from the list of addition fields (their valueswill be filled in automatically when Overduedebt VAT” Polish local feature is used).

Changes description


This section of the articledescribes details of the changes introduced by this hotfix to the JPK_VDEKimplementation.

‘JPK_V7M’ XSD schema published on May8, 2020

On May 8, 2020 the Ministry ofFinance of Poland published newversion for ‘JPK_V7M’XSD schema.

This XSD version is supportedin the current hotfix.

Changes in application-specific parameters setup

New version of “JPK_VDEK XML format (PL)” Electronic Reporting(ER) format contains changes in their structure which limits possibility toimport application-specific parameters from the previous version of the format.

Description of changes by Lookup fields:

Lookup name in previous 68.135 version

Description of the change in 72.150 version

ImportSelector

No change

ProceduralMarkingsSelector

MR_T’ and ‘MR_UZ’ markers are moved to a new separateSprzedazVAT_MarzaSelector’ Lookup field.

ServiceDeliverySelector

No change

DeclarationMarkersSelector

No change

ZakupVAT_MarzaSelector

No change

SalesDocumentTypesSelector

No change

PurchaseDocumentTypesSelector

No change

TaxBaseCorrectionSelector

Excluded

Reporting of overdue customers invoices

Starting fromversion 72.150 of “JPK_VDEK XML format (PL) supports reporting of overdue customers invoices in case when “Overduedebt VAT” local Polish feature is used.

Business requirement

  1. <P_68> elementof the Declaration part must report (if procedure is applied by the company)amount of taxable base for “overdue” invoices in the reportingperiod (transactions posted to deduct VAT for not payed issued invoicesduring 150 days period after payment due date)
  2. <P_69> elementof the Declaration part must report (if procedure is applied by the company)amount of VAT for “overdue” invoices in the reporting period(transactions posted to deduct VAT for not payed issued invoicesduring 150 days period after payment due date)
  3. If the procedure isapplied by the company, “Overdue” invoices in the period in which duedate (150 days), this transaction must be reported with “WEW” documenttype including, the information about the Customer from the original invoice andamount with “-“ negative sign.
  4. If procedure is appliedby the company, “Payed overdue” invoices in the period in which an overdueinvoices was payed, the transaction must be reported with “WEW” documenttype, all the information about the Customer from the original invoice and amountwith “+“ positive sign.
  5. If “overdue” and “payed overdue”transactions are in the same reporting period: it is allowed to report(if procedure is applied by the company) or not report both (together) in Salesregister. <P_68> and <P_69> elements of the Declarationpart are not reported in this case.

Supported business user scenario in Finance

“Overdue customer invoice” scenario is a scenario during which an invoiceissued to a customer can go through three stages:

  1. Invoice is issued to acustomer: tax transactions are posted; invoice is included to JPK > Ewidencja> SprzedazWiersz as usually, according to tax setup and markers setup.
  2. If the invoice is not payed for 150 days period after payment due date, thecompany can apply the Overduedebt VAT periodic task (Accounts receivable > Periodic tasks> Overdue debt VAT). Tax transactions resulting this task will bereflected in JPK_VDEK report with:
    - all the information
    about the customer fromthe original invoice (posted on step 1),
    - amounts reported in the same K_* elements as in the original invoice but withnegative sign,
    - same markers will be applied as in the original invoice,
    - <TypDokumentu> element will be marked as “WEW” (internaldocument),
    - <
    KorektaPodstawyOpodt> marker will be applied.
    Moreover, amounts (base amount and tax amount) from this invoice (internaldocument) will be included and reported in P_68 and P_69 elementsof the declaration part of the report.
  3. If for the invoice posted on step 1 and not payed for 150 days period afterpayment due date the company applied the Overduedebt VAT procedure (step 2), and the invoice was payed after that, the company must apply again ‘Overdue debt VAT’periodic task in the period when the invoice was payed. Tax transactionsresulting this task will be reflected in JPK_VDEK report with:
    - all the information
    about the customer fromthe original invoice (posted on step 1),
    - amounts reported in the same K_* elements as in the original invoice with positivesign,
    - same markers will be applied as in the original invoice,
    - <TypDokumentu> element will be marked as “WEW” (internaldocument),
    - <
    KorektaPodstawyOpodt> marker will be applied.
    Amounts (base amount andtax amount) from this invoice (internal document) will NOT be included andreported in P_68 and P_69 elements of the declaration part of thereport.

(!) If step 2 and step 3 had place in the same reportingperiod, P_68 and P_69 elements of the declaration part of thereport will not be affected.



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:

Partners

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

Customers

https://mbs.microsoft.com/customersource/northamerica/help/help/contactus

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.