1. Implementing Financials for EMEA
  2. Enter Transactions – Receivables and Payables Poland

Enter Transactions – Receivables and Payables Poland

Reportable transactions must meet the minimum requirements x in the Tax Reporting for EMEA documentation. Additional requirements and assumptions for specific cases are as follows.

Common requirement is to specify the Document Fiscal Classification on the header of the Receivables transaction or of the Payables invoice. For more details about VAT and Correction VAT invoices, and Sales and Purchases through Taxpayer Representatives, see the Enter Transactions in Payables and Receivables section.

Define Product Category and User Defined Fiscal Classification

Define Product Category and User Defined Fiscal Classification on transaction line level

Here’s an example of how you define Product Category and User Defined Fiscal Classification on transaction:

Receivables Transaction
  • Receivables Transaction
    • Define Product Category and User-Defined Fiscal Classification on line level.
  • Payables Transaction
    • Define Product Category on line level.
    • Define User-Defined Fiscal Classification on line level.
  • Taxable Sales and Purchase Transaction
    • Define Product Category and User-Defined Fiscal Classification:
    • Create Taxable Transactions in a spreadsheet.
  • Purchase Order
    • Define Product Category and User-Defined Fiscal Classification on line level.
  • Sales Order
    • Define Category and User-Defined Fiscal Classification on line level.
    • Select Edit Tax Determinant.

Define Additional Information

Define additional information for customs transactions and transactions with split payment mechanism.

You can define additional information such as Customs Document Number, Customs Document Date, and Importing Party Name in the Global Descriptive Flexfields (GDF) defined on Payables and Receivables transaction header level.

Transactions with split payment mechanism must be reported in the JPK_VAT XML file (field MPP) with value 1. You can define specific Document Fiscal Classification code and assign tax reporting type ORA_JEPL_SPLIT_PAYMENT with tax reporting code MPP (split payment mechanism) or you can define payables and receivables transactions with GDF ‘Split payment’ with value Yes.

The Document Fiscal Classification can be used for standard and imported payables and receivables transactions or for Taxable Sales or Purchase transactions. The GDF ‘Split payment’ is not supported for Taxable Sales or Purchase transaction.

For payables and receivables transactions, you can use GDF ‘Split Payment’ on header level. The

Generate VAT file for Poland process is checking first if transaction has assigned Document Fiscal Classification with tax reporting type ORA_JEPL_SPLIT_PAYMENT and value MPP. When the tax reporting type ORA_JEPL_SPLIT_PAYMENT is not defined, the process checks the Split Payment GDF on payables or receivables transaction header.

GDFs for additional customs transactions and GDF for split payment mechanism:

  1. Follow the Receivables Invoice Example
  2. Define detail header information and click Show more - Miscellaneous.
  3. Click Regional Information and select Transactions for Poland.
  4. Define detail header information and click Show More - Additional information.
  5. Click Regional Information and select Invoices for Poland.
Note: For imported receivables transactions, you should import additional Customs Document Number, Customs Document Date, and Importing Party Name in the global descriptive flexfields defined on AR Invoice header interface:

GDFs for Payables Invoice Header Interface

The GDFs attributes for Payables invoice header interface are same as the GDFs attributes used in the Create Invoice user interface.

Define Final Invoice With Applied Prepayment Invoice

Based on the changes valid from October 1, 2019 in the field RozdajFaktury should be displayed value ZAL not only for Prepayment Invoices but also for prepaid Final Invoices. All Prepayment Invoices with Document Fiscal Classification ‘PL Prepayment Invoice’ should be reported with the value ZAL. This is because the subsequent rule to report also final invoice with ZAL is valid from October 1, 2019. The final invoices with applied Prepayment Invoice is defined with Document Fiscal Classification value, ‘PL Regular Invoice’.

The process steps how to define Final Invoice with applied Prepayment invoice:

  • In Payables the user should create Final Invoice with Document Fiscal Classification ‘PL Regular Invoice’ and with standard functionality the payed Prepayment invoice should be applied to the Final Invoice.
  • In Receivables the user should create final invoice with Document Fiscal Classification ‘PL Regular Invoice’ and in the line GDF ‘Prepayment Invoice’ the user should define payed Prepayment Invoice Number.

To create an invoice, follow these steps:

  1. Navigate to Invoice Lines, and select Details.
  2. From the Regional Information field, select Transaction Lines for Poland.
  3. From the Prepayment Invoice field, select the invoice you want to use..
  4. Save the invoice.

Related Topics