We have incorporated a new report – Balance confirmation / Demand for payment. The report is available in the Polish Localisation Package of Oracle NetSuite under an additional licence and can be generated with the following filters:

• Subsidiary – indication of the business entity for which the report should be generated;
• Date – indication of date as at which the settlements should be reviewed in NetSuite;
• Document type – type of printout generated, you may choose either Balance confirmation or Demand for payment;
• Objective type – type of counterparty for whom the report should be generated, you may choose either Customer or Vendor;
• List only transactions in open status – allows to determine whether you wish to include unreconciled transactions only or all transactions recorded in the system;
• Customer / Vendor – allows to choose the counterparty for whom the report should be generated;
• Accounting book – an option to indicate the accounting book for which the report should be generated.

In the Output settings section you are allowed to choose some additional parameters of the data shown on the printout:

• Description – you may enter any textual description;
• Print bank account number – a parameter allowing you to decide whether bank account details should be shown on the printout; 
• Bank account number – here you can choose the bank account number;
• Select document language – this allows for selecting a language for the report generated. Printouts are available in Polish, English and German;
• Include for day phrase in the document title – this is for including the phrase informing of the exact day for which the report has been generated.

A printout of the Balance confirmation report in Polish. 

A printout of the Balance confirmation report in English:

A printout of the Demand for payment report in Polish:

A printout of the Demand for payment report in English: 

We have incorporated a new field – PLP Description Line - available for the sales transactions item. PLP Description Line allows you to enter any additional information that should be displayed on PLP sales printouts.

Under the system configuration, it is now possible to define the width of the PLP Description Line field that will be displayed on the printout. The width can be defined by indicating the number of columns the field should include.

We have ensured the possibility to define various FX rates for different document items for VAT purposes in the Polish Localisation Package available under Oracle NetSuite. We have also developed an accurate presentation of the data on sales printouts. 

When a single FX rate for VAT settlements has been applied to the entire document, data is presented in a standard manner, i.e. in the invoice header.

We have incorporated tools for translating the names of goods and services displayed on the Polish Localisation Package printouts available in Oracle NetSuite. This enables the use of various language versions for the names of goods and services, as long as the required data is provided in relevant files.

We have allowed for the configuration of invoice contents on reverse-charge invoice printouts in three different areas:

• invoice header;
• tax rate information;
• legal basis.

The values presented may be individually adjusted to one of three available language versions – Polish, English or German, according to the type of the VAT transaction:

• domestic reverse charge;
• intra-community sales of goods;
• intra-community acquisition of goods;
• exports of goods;
• exports of services;
• transactions taxed under local regulations – goods;
• transactions taxed under local regulations – service.

We have added a new field for counterparty address details – PLP Addressee - allowing for entering counterparty names that exceed the NetSuite default character limit.

When creating or updating counterparty details, by employing PLP Update GUS / VIES functionalities, the system will automatically check the length of the counterparty name and populate the Addressee or PLP Addressee field – depending on whether or not the name exceeds the character limit.

We have incorporated some improvements in terms of generating payment files from the PLP Bank Payments module for Journal-type transactions and Vendor Prepayment, preventing transaction browsing inaccuracies.

• Journal – we have eliminated excessive transactions related to sales entries with a counterparty specified in the PLP Customer field;
• Vendor Prepayment – we have secured documents from doubling in cases where both accounts identified in the transaction accounting entry are indicated in the Transaction Account filter.