Introduction
As from first of July 2018, a new VAT regulation implementing a mechanism that is called split payment will come into force.
General idea: Payment for an invoice will be split between two bank accounts; net value will be transferred to the regular bank account and the VAT value will be transferred to the VAT bank account.
Payments using the split payment mechanism shall be made in Polish zlotys by using a bank transfer message that is provided by a bank or a savings and credit union, intended to make payments in a split payment mechanism, in which the taxpayer indicates:
-
The amount that corresponds to all or part of the tax amount that results from the invoice to be paid in the split payment mechanism.
-
The amount that corresponds to all or part of the gross sales value.
-
Invoice number, in connection with which the payment is made.
-
The number by which the supplier of the good or service provider is identified for tax purposes.
Setup and generating Multicash payments
Before generation payments with split payment mechanism, it is necessary to setup payment specification (specification parameter is equal to Split) in the method of payment.
When a user generates a vendor payment with the Split parameter in Payment specification, the system creates the Multicash file with VAT amount, Tax ID number, Invoice number and additional information, which are filled in the PaymNote field of the MultiCash format. Additional information is filled from the Note field in the payment journal line and VAT amount, Tax ID number, Invoice number are filled in from the first invoice, marked for settlement in the payment journal line.
Hotfix information
You need to import the following or a higher version of the ER configurations from LCS shared asset library to use Spli payment mechanism:
-
Payment model.version.19
-
Payment model mapping 1611.version.19.19
-
MultiCash (PL).version.19.5
Fix downloading instructions are here:
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.
