This section of the article describes
details of the changes introduced by this hotfix to the JPK_VDEK
implementation.
"Item sales tax
group" and "Sales tax group" are added to the data provider
"Item sales tax
group" and "Sales tax group" fields are added to the data
provider of the report for sales and purchases registers. This allows to use
these fields additionally for setup of markers on ER format level and as a
result significantly extends flexibility of setup of application-specific
parameters of the format. Find details about particular changes in application
specific parameter below.
Changes in
application-specific parameters setup
ProceduralMarkings
"ProceduralMarkings"
look-up conditions setup is extended and includes following columns:
· Sales tax code
· Sales tax group
· Customer account Id
· Customer group
With this extension you can
specify different conditions for different Lookup results. Within one line of
setup conditions and applied by the system on a source tax transaction using “AND”
operator. If for some cases you need setup conditions which must be applied via
“OR” operator, you must specify conditions in separate lines. As soon as a tax
transaction from reporting period meets the first condition in the list,
related marker from the Lookup result will be reported for related document.
For example, consider a setup
represented on the screenshot below:
[Asset 4555957]According to this setup,
system will analyze tax transactions and if a tax transaction was posted with “VATZW”
tax code and is related to an invoice with “DE-011” Customer account,
the document related to this tax transaction will be reported with “TP” (Existing links between
the buyer and the supplier of the goods or service provider referred to in art.
32 section 2 point 1 of the Act)
marker.
Setup of conditions for <P_65> and <P_67>
element of declaration part of the report was moved from “ProceduralMarkings” Lookup
field to a specific separate “DeclarationMarkers”
Lookup field (see in this article below).
Setup of conditions for <ZakupVAT_Marza>
element of <ZakupWiersz> part of the report was moved from “ProceduralMarkings”
Lookup field to a specific separate “ZakupVAT_Marza” Lookup field (see in this article below).
Find more information specifically about
“MPP” (Split payment) marker in Implementation details section of KB 4540232.
ServiceDeliveryIndication
“ServiceDeliveryIndication”
look-up conditions setup is extended and includes following columns:
· Sales tax code
· Item sales tax group
· Customer account Id
· Customer group
With this extension you can
specify different conditions for different Lookup results. Within one line of
setup conditions and applied by the system on a source tax transaction using “AND”
operator. If for some cases you need setup conditions which must be applied via
“OR” operator, you must specify conditions in separate lines. As soon as a tax
transaction from reporting period meets the first condition in the list,
related marker from the Lookup result will be reported for related document.
For
example, consider a setup represented on the screenshot below:
[Asset 4555958]According to this setup,
system will analyze tax transactions and if a tax transaction was posted with “S8”
tax code and is related to an invoice with “DE-012” Customer account,
the document related to this tax transaction will be reported with “GTU_09” (Supply of medicines and
medical devices - medicinal products, foodstuffs for particular nutritional
uses and medical devices covered by the notification obligation referred to in
Art. 37av section 1 of the Act of 6 September 2001 - Pharmaceutical Law
(Journal of Laws of 2019, item 499, as amended) marker.
ImportTransaction
“ImportTransaction”
look-up conditions setup is extended and includes following columns:
· Sales tax code
· Sales tax group
· Supplier account Id
· Supplier group
With this extension you can
specify different conditions for different Lookup results. Within one line of
setup conditions and applied by the system on a source tax transaction using “AND”
operator. If for some cases you need setup conditions which must be applied via
“OR” operator, you must specify conditions in separate lines. As soon as a tax
transaction from reporting period meets the first condition in the list,
related marker from the Lookup result will be reported for related document.
For
example, consider a setup represented on the screenshot below:
[Asset 4555959]According to this setup,
system will analyze tax transactions and if a tax transaction was posted with “Z23_27”
tax code and with any Sales tax group and is related to an invoice
with any Vendor account and from any Vendor group, the document related
to this tax transaction will be reported with “IMP” (Designation concerning input tax on imports of
goods, including import of goods taxed in accordance with art. 33a of the VAT
Act) marker.
ZakupVAT_Marza
New “ZakupVAT_Marza”
look-up field was introduced to setup different conditions basing on following
set of criteria:
· Sales tax code
· Item sales tax group
With
this lookup field you can specify different conditions to collect amounts to be
reported in “ZakupWiersz /ZakupVAT_Marza”
element of the report. System will collect gross amount by tax transactions
which fit the specified criteria. Within one line of setup conditions and
applied by the system on a source tax transaction using “AND” operator. If for
some cases you need setup conditions which must be applied via “OR” operator,
you must specify conditions in separate lines. As soon as a tax transaction
from reporting period meets the first condition in the list, related gross
amount will be collected for reporting in “ZakupWiersz /ZakupVAT_Marza” element of the report in relation to the
document.
DeclarationMarkers
New “DeclarationMarkers”
look-up field is introduced to setup conditions for the following element of
declaration part of the report:
|
Name
|
Label En-us
|
Label PL
|
Description En-us
|
Description Pl
|
|
P_65
|
Activities mentioned in art. 122
|
Czynności o których mowa w art. 122 ustawy
|
The tax payer performed the activities mentioned in art. 122 of the VAT
Act. Tax exemption for the supply, import and purchase of investment gold.
|
Podatnik wykonywał w okresie rozliczeniowym czynności, o których mowa w
art. 122 ustawy
|
|
P_67
|
Tax
liability reduction
|
Obniżenie
kwoty zobowiązania podatkowego
|
The tax payer benefits from tax liability reduction mentioned in art.
108d of the VAT Act
|
Podatnik korzysta z obniżenia zobowiązania podatkowego, o którym mowa w
art. 108d ustawy
|
|
Inne
|
Other
|
|
|
|
Conditions
for these results can be setup by the following columns:
· Sales tax code
· Item sales tax group
· Sales tax group
· Customer account Id
· Customer group
· Vendor account Id
· Vendor group
With
this lookup field you can specify different conditions impacting <P_65>
and <P_67> elements of declaration.
For
example, consider a setup represented on the screenshot below:
[Asset 4555960]According to this setup,
system will analyze tax transactions and if a tax transaction was posted with “S23”
tax code and with “S23” Sales tax group and is related to an invoice
with “DE-014” Customer account, <P_65> (The tax payer performed the activities
mentioned in art. 122 of the VAT Act in the given period: 1-yes) will be marked.
SalesDocumentTypes
“SalesDocumentTypes” look-up
conditions setup is extended and includes following columns:
- Sales tax code
- Item sales tax
group
- Sales tax group
- Customer account
Id
- Customer group
With
this extension you can specify different conditions for different Lookup
results. Within one line of setup conditions and applied by the system on a source
tax transaction using “AND” operator. If for some cases you need setup
conditions which must be applied via “OR” operator, you must specify conditions
in separate lines. As soon as a tax transaction from reporting period meets the
first condition in the list, related marker from the Lookup result will be
reported for related document.
For
example, consider a setup represented on the screenshot below:
[Asset 4555961]According to this setup,
system will analyze tax transactions and if a tax transaction was posted with any
tax code and with any Sales tax group and with any Item sales tax
group and is related to an invoice with “DE-015” Customer account, related
document will be reported with “WEW” value (internal document) in <TypDokumentu>
element.
PurchaseDocumentTypes
“SalesDocumentTypes”
look-up conditions setup is extended and includes following columns:
- Sales
tax code
- Item
sales tax group
- Sales
tax group
- Supplier
account Id
- Supplier
group
With
this extension you can specify different conditions for different Lookup
results. Within one line of setup conditions and applied by the system on a source
tax transaction using “AND” operator. If for some cases you need setup
conditions which must be applied via “OR” operator, you must specify conditions
in separate lines. As soon as a tax transaction from reporting period meets the
first condition in the list, related marker from the Lookup result will be
reported for related document.
For
example, consider a setup represented on the screenshot below:
[Asset 4555962]According to this setup,
system will analyze tax transactions and if a tax transaction was posted with any
tax code and with any Sales tax group and with “Z23D50” Item sales
tax group and is related to an invoice with any Vendor account and group,
related document will be reported with “VAT_RR” value (RR VAT invoice referred to in art. 116 of the
VAT Act) in <DokumentZakupu> element.
“P_66” element of declaration
“P_66” field of
declaration part of the report in the new version of the format is impacted
by “SprzedazWiersz/TT_D” marker additionally to “SprzedazWiersz/TT_WNT”
marker as it was initially.
Some other fixes in different
elements of the report
Reporting of
P_27, P_10, P_42 and K_42 elements are fixed according to expected result of
bug reported #423563.
Namespaces in the report
Namespaces in the
report are in accordance with the latest published (on March 6, 2020) schema.
Validation vs XSD
schema was successfully done.