Polish Functionality for Microsoft Dynamics NAV - read more
page-template,page-template-full_width,page-template-full_width-php,page,page-id-17302,page-child,parent-pageid-6378,ajax_fade,page_not_loaded,,qode-child-theme-ver-1.0.0,qode-theme-ver-17.0,qode-theme-bridge,wpb-js-composer js-comp-ver-5.5.2,vc_responsive

Polish Functionality

Microsoft Dynamics NAV

Polish Functionality


Polish Functionality is an add-on module certified by Microsoft that extends the standard Microsoft Dynamics NAV version with local functionalities. The module has been developed and prepared by IT.integro’s consultants and translators. Its main objective is to make Microsoft Dynamics NAV compliant with local legal and business requirements. For this purpose, the module has been equipped with:


  • functionalities required by Polish law (e.g. VAT Date);
  • functionalities that facilitate daily users’ tasks (such as improvements for issuing sales credit memos);
  • the Polish language layer.
Polish Functionality

Local solutions  for general ledger management

Polish Functionality

Additional columns: Debit Amount and Credit Amount

In the standard version of Microsoft Dynamics NAV, transactions amounts are displayed in one column with debit amounts presented as positive values and credit amounts as negative values. The add-on functionality implemented within Polish Functionality enables you to display two additional columns in multiple windows. The two columns are displayed: Debit Amount and Credit Amount. This enables each user to view transaction values in its custom layout.

Posted document number information

As required by Polish law, the posting number used to register a document in the company’s accounting books must be included on each document in paper form. In order to facilitate the search for a document posting number, the standard Microsoft Dynamics NAV version has been enhanced with a message feature. The message with the document posting number is displayed after the document has been posted successfully.

Document numbering templates

The document numbering templates functionality has been designed to define various sets of number series for specific document types. It is possible to define other common settings to each template, e.g. the report that is to replace the primary report assigned to a certain document type within the standard functionality.


The functionality can be also used to create numbering templates for:

  • sales documents,
  • purchase documents,
  • transfer orders.

Posting an adjustment (red storno)

According to the provisions under Polish law, G/L accounts expenditures can be recorded only on the debit side whereas income – on the credit side. This ensures the so called turnover clarity. Therefore, some transactions have to be posted as adjustments.


The Polish Functionality module has been designed to:

  • enforce posting on the appropriate side of the relevant general ledger accounts;
  • post warehouse transaction adjustments (shipments for warehouse movements, write-off of the posting of expected costs, etc.);
  • adjust any posting with a single click (postings in the General Ledger, Inventory and Jobs areas).

Posting Description

With this Polish Functionality feature, it is easier to enter transaction descriptions for transactions posted and registered in the G/L Entry table. Additionally, as it is possible to block changes in selected descriptions, the method for describing transactions can be standardized.

Number series in master templates

With the standard functionality of Master Templates, it is possible to define default parameters for various setup options. The system uses these settings to automatically fill in record fields that will be created based on a selected master template. Additionally, Polish Functionality enables the user to set up a default numbering series in templates defined for customers, vendors and fixed assets.

Importing NBP (National Bank of Poland) exchange rates

The standard system version of Microsoft Dynamics NAV enables the recording of multi-currency transactions. In general ledger entries, transaction amounts are displayed as their PLN equivalents calculated based on a selected currency exchange rate whereas in analytical ledgers two amounts are presented i.e. the amount in the transaction currency and the equivalent amount calculated in the same way as the amounts in relevant general ledger entries. In order to streamline the management of multi-currency transactions, the standard functionality of Microsoft Dynamics NAV  supports currency setup and registration of currency exchange rates to be applied for transactions in a specific currency for a selected period.


Polish Functionality simplifies exchange rate registration, enabling the user to import exchange rates from the dedicated Web portal maintained by the National Bank of Poland.

Adjusting exchange rates

Exchange rate adjustment or balance sheet valuation means the recalculation of open receivable and payable accounts as well as cash in hand and at bank accounts based on the same exchange rate. Exchange rate adjustment should be carried out at least once a year.


The Polish Functionality module for Microsoft Dynamics NAV includes the following enhancements:

  • the possibility of running the Adjust Exchange Rates batch job separately for receivables, payables and bank accounts;
  • the possibility of posting detail entries or entries aggregated by currency by using running the Adjust Exchange Rates batch job;
  • the possibility of running the Adjust Exchange Rates batch job in the test mode, only for simulation purposes (without posting recalculated values).

Exchange rate adjustment registers

The history of exchange rate adjustments is stored in exchange rate adjustment registers. The Polish Functionality module offers enhancements for the standard register window and a dedicated posting report. This ensures that the user gets a complete history and overview of the exchange rate adjustments performed.

Information about the name and version of the accounting software

The accounting act regulations impose the obligation to print accounting program details such as its name and version on official accounting reports:


“(…) Accounting books with the accounting method indicated, should be (…) permanently marked with the (full or shortened) name of the business entity to which they relate (each bound book, each separate account sheet, also if in the form of a computer printout or a list displayed on a computer screen), name of the accounting book type and name of the processing software (…)”.


Thus, the standard reports within the Polish Functionality module for Microsoft Dynamics NAV contain the accounting software name and version information.

Balance sheet and profit & loss statement

Balance sheet and profit & loss statement are required by Polish law. The structure of these reports is subject to the Act; therefore the ERP system should enable the implementation of statutory report templates. The Balance Sheet and Profit & Loss features within Polish Functionality facilitate statutory reporting. It is possible to set up multiple versions of reports, balances and profit and loss accounts.

Account Schedules

The 3 additional options for using account schedules have been implemented into Polish Functionality:

  • Shared account schedule – The account schedule that has been selected to be shared contains lines that can be used in formulas in all account schedules. This way, it is not necessary to reenter the same parameters to calculate amounts in a specific report line in multiple account schedules. For such a line, settings should be defined only once i.e. in a shared account schedule. For other worksheets, the user only has to link the specific entry with a relevant line in a shared account schedule.
  • Saving account schedule results – This function has been designed to control the values changing in financial ledgers. Each version of account schedule results is identified by its number that is assigned automatically when the version is saved based on a selected number series.  Each saved account schedule is stamped with a date and time of saving.
  • The source of the amount calculated in the Formula type line – With this modification, it is possible to display the amount calculation method in the Account Schedule Overview window in lines with a selected Total line type.  As a result, there is no need to switch between the Preview and Edit windows within the account schedule. In the standard Microsoft Dynamics NAV version, the Preview window contains the calculated amount while the Edit window contains a line formula definition.

Local solutions for VAT management

Polish Functionality

VAT Settlement Date

Polish law allows VAT settlement in periods other than the ones in which the document was posted. The VAT Date feature, as a part of the Polish Functionality module, can be used to allocate VAT transactions to a specific accounting period, regardless of the document posting date.

Postponed VAT (marking approved sales credit memos)

The postponed VAT feature is used every time the VAT amount is to be suspended as it is not possible to settle it at a given time. It is relevant for handling sales credit memos. Under Polish law, it is possible to deduct an invoice VAT amount only upon confirmation of sales credit memo receipt by the customer. Therefore, it is necessary to postpone the VAT amount for the period between the issue of the sales credit memo and the customer’s confirmation of sales credit memo receipt.

Sales/Purchase VAT Register

The Sales/Purchase VAT Register report is a basic report used for calculating amounts of sales and purchase VAT amounts in selected periods. The report displays a VAT amount as well as detailed customer or vendor information for each document.


The VAT base amount and VAT amount are displayed separately for specific VAT rates. The program also displays the total VAT amount and total of VAT amounts for each combination of the VAT Bus. Post. Group and VAT Prod. Post. Group fields. In the Sales/Purchase VAT Reg. report, you can view VAT entries based on VAT posting groups or VAT IDs, depending on the option selected while defining the setup for report printing.

VAT Application Worksheet

The VAT application worksheet is a tool available within Polish Functionality designed to enable VAT settlement before VAT is paid to the Tax Office. With this tool, the Microsoft Dynamics NAV  user gets complete control over VAT transactions such as VAT deferral and payment as well as changes of the VAT date.

VAT Declaration

VAT Declaration is a standard tool that is used to prepare statements for the Tax Office. In the standard Microsoft Dynamics NAV version, the tool uses accounting periods. Within Polish Functionality, the accounting period used as the settlement period for VAT statements has been replaced with the VAT period. This enables the user to issue statements for each selected, predefined VAT period, regardless of the accounting period used to post the transaction in ledgers.

Detailed VAT Entries

The Detailed VAT Entries functionality has been added to the standard Microsoft Dynamics NAV version to ensure the improved control and handling of changes of the VAT amount to be settled in a selected period.


Generally, this concept resembles other detailed system entries such as detailed customer and vendor ledger entries. This means that in the Detailed VAT Entries window, the system creates separate entries for detailed information on any changes in VAT entries amounts. The VAT entry amount is the sum of all amounts registered in detailed VAT entries related to a specific VAT entry.

Posting VAT documents in general journals

Polish accounting regulations oblige each business entity to enter all key information about the contracting party in the Sales/Purchase VAT Register. In the case of purchase invoices from one-time vendors, it is not necessary to set up separate cards for settlement purposes. For these purposes, Polish Functionality provides general journal enhancements that support VAT transaction posting with the capability of entering customer data without linking it to a settlement card.

Posting a full VAT amount

Under Polish legal requirements, the VAT register should show a net amount for all VAT transactions. To meet this requirement, the Polish Functionality module, enables the manual entry of a VAT base amount for transactions for which only a VAT amount is to be posted.


This feature is particularly useful for recording purchases from outside the EU. For such transactions, it is necessary to post two documents:

  • vendor purchase invoice – to include a purchase net value and payable amount;
  • SAD document – to include a VAT amount and other additional costs due to custom duties.


Net value which is a basis for VAT calculation is posted based on a purchase invoice, and therefore it cannot be posted again based on a linked SAD document when a VAT amount is posted. Therefore, when a SAD document is posted, the VAT base used for calculation is displayed only for information purposes. This ensures that purchase transactions are displayed correctly in the VAT register.

Non-deductible VAT

In some cases, it is not possible to deduct the full sales VAT amount. Because only a part of the VAT amount can be included in the VAT register, the remaining part should be added to the purchase amount and posted as costs. For item or fixed asset purchases, the non-deductible VAT amount is added to the purchase value of an item or fixed asset, and then it is posted as a part of a purchase cost.


The solution implemented within Polish Functionality enables the user to:

  • set up the partial deduction of a sales VAT amount;
  • post purchase transactions including a VAT amount which is partially deductible;
  • add the non-deductible VAT amount to the acquisition cost of items and fixed assets.

Inter-company sales orders and invoices

As required by Polish law, the VAT amount calculated for some purchase types is included in the VAT sales register as sales VAT and it is posted on a relevant cost account. If goods and services are provided free of charge, such a transaction must be treated similarly. The Polish Functionality module provides a tool that simplifies the process of additional VAT recording for this type of transactions.

Inter-company sales orders and invoices

As required by Polish law, the VAT amount calculated for some purchase types is included in the VAT sales register as sales VAT and it is posted on a relevant cost account. If goods and services are provided free of charge, such a transaction must be treated similarly. The Polish Functionality module provides a tool that simplifies the process of additional VAT recording for this type of transactions. VAT-UE Declaration


VAT-UE Declaration is an overview of intra-community transactions carried out in a specified period of time. The obligation to submit this declaration has been set in the VAT Act. Polish Functionality has been equipped with a tool that supports and automates data preparation for VAT-‑UE Declaration.

VAT-27 Declaration

VAT-27 Declaration is an overview of transactions (including item and service delivery) completed in a specified period with the customer as a tax payer. It should be filled in by, among others, tax payers who use reverse charge VAT for sales of sensitive goods such as laptops, smartphones, tablets, telephones, metals, waste paper as well as services in the scope of greenhouse emission trading. Polish Functionality has been equipped with a tool that supports and automates data preparation for the VAT‑27 Declaration.

Service Tariff No.

For some sales services sold outside Polish borders, the sales VAT register should contain a brief description of the service rendered in order to enable the user to validate a calculated VAT amount. The service tariff number feature that is available within Polish Functionality provides a list of service tariff numbers and service descriptions which can be assigned by the user to a selected transaction.

Polish Functionality for
Microsoft Dynamics NAV 2017

Local solutions for cash management

Polish Functionality

Cash management

Flexibility and on-going control over the cash balance are important aspects of cash flow management. The cash management feature included in the Polish Functionality module ensures that cash transaction management is optimized and can be customized based on the user’s needs.

Bank Statement Journal

When bank statements are registered, it is important to control the bank account balance on an ongoing basis. With its Bank Statement Journal, the Polish Functionality module provides an overview of the open balance, registered transaction balance, projected balance after posting, both in the standard currency used for the bank account and a local currency. Moreover, the Bank Statement Journal window provides improvements for transaction recording and account settlement.

Calculating and posting currency exchange rate differences in banking transactions

Under Polish law, foreign currency cash withdrawals from the cash desk and bank accounts should be converted based on the exchange rate valid as of date when the payment in the foreign currency was made to the cash desk or bank account. This means that the withdrawal amount in the local currency should be equivalent to the respective payment amount in the same currency. This process is very similar to inventory valuation. The methods used for cash withdrawal and payment settlement are also basically the same: FIFO, LIFO, weighted average.  In the Polish Functionality module, the recalculation of cash withdrawals in a foreign currency is based on FIFO, because it is the most commonly used costing method.

Electronic banking

Most banks operating on the Polish market offer software that enables companies to enter transfers at their headquarters and send them to banks in an electronic form. The Electronic Banking functionality within Polish Functionality enables the user to set up transfers to a customer’s bank in Microsoft Dynamics NAV. Such transfers can be exported and sent as files into a banking system. Moreover, with this module it is possible to import bank statement files into Microsoft Dynamics NAV and settle the statements automatically.

Local solutions for receivables and payables management

Polish Functionality

Sales price rounding precision

In the standard Microsoft Dynamics NAV version, it is possible to define the rounding precision of specific amounts. It applies to all amounts within the system. Polish Functionality enables the user to define different rounding precision settings for prices. For example, purchase prices can be entered with a precision of five decimal places, whereas sales prices are registered with a precision of two decimal places.

Printing fiscal receipts

Polish Functionality provides a tool that supports communication between Microsoft Dynamics NAV and fiscal printers in order to print fiscal receipts as a confirmation of sales transactions registered within the system.

Printing sales documents

All printouts issued within Polish Functionality are complaint with statutory requirements and include all required items. It applies to printouts of sales invoices, sales credit memos, service sales invoices and service sales credit memos.

Sales pro-forma invoice

With Polish Functionality, it is possible to print pro-forma invoices for sales orders.


Pro-forma invoices are issued before a sales transaction is invoiced ultimately. They are used in two scenarios:


  • Based on a sales pro-forma invoice, the customer makes an advance payment for an order. In such a case, the pro-forma invoice confirms the amount to be paid in advance.
  • A pro-forma invoice is issued for transactions related to product sales to non-EU countries. It is delivered to the Customs Authorities in order to prepare a SAD document.

Sales Credit Memo

A sales credit memo is issued if some corrections in the sales invoice must be made. As part of the Polish Functionality module, the following improvements have been added to facilitate the creation of sales credit memos:


  • correction line wizard,
  • correction types that enable the user to control the accuracy of created corrections;
  • the possibility of issuing one sales credit memo for multiple sales invoices.

Selection of a bank account in sales documents

Many companies use multiple bank accounts managed by various banking institutions which allows them to optimize the costs of handling financial transactions. Therefore, the standard sales functionality in Microsoft Dynamics NAV has been enhanced with the possibility of selecting a bank account (out of all accounts defined in the system). The account information will be printed on a relevant sales document.

Multiple interest rates

Interest rates used to calculate a late payment interest can vary in different periods. The Polish Functionality module provides a tool for calculating various interest rates depending on the period when the payments were overdue.

Corrective memos

Polish accounting rules allow companies to issue a corrective memo, if a VAT invoice that was received contains minor errors (such as a mistake in the customer’s address). Polish Functionality for Microsoft Dynamics NAV contains a tool for issuing corrective memos that enables the user to enter both incorrect data that was included in a received document and correct data.

Settlement invoice of an employee prepayment

Most companies pay their employees prepayments for business-related purchases. Such prepayments are settled with invoices that confirm respective purchases. In the standard Microsoft Dynamics NAV version, two or more postings are needed to settle an employee prepayment. With the new feature of the Polish Functionality module, only one positing is needed to complete this process.

Customer and vendor templates

The standard Microsoft Dynamics NAV functionality enables the user to use a customer template while creating a customer card based on the card of a previously entered contact. The Polish Functionality module contains two important modifications in this area:

  • the possibility to set up a default number series in a customer template;
  • the use of vendor templates based on customer templates, including a default numbering series.

Multiple receivables/payables accounts

For each customer (vendor), one card is usually defined within the system. Each customer/vendor card can be linked with a customer/vendor posting group which means with one receivables (payables) G/L account. However, it is often required that receivables (payables) of a customer (vendor) should be posted to various G/L accounts. It depends on the receivables (payables) type. (for example current payables or paid deposits).

With the Polish Functionality module, it is easier to handle various types of receivables (payables) by using posting group substitutions. This enhancement ensures that a default posting group that is assigned to the customer (vendor) card is copied to all documents. However, the user can change the group while entering a document, without changing a default customer (vendor) posting group in a relevant card.

Customer/vendor compensations

In Microsoft Dynamics NAV, contracting parties are defined as customers or vendors, depending on the type of transactions they conduct. However, it happens that the same contracting party is entered in purchase or sales transactions. In such a case, all relevant information about this contracting party must be registered twice i.e. for the customer and vendor. As payables and receivables of a contracting party are registered without any link, it is necessary to compensate receivable against payable amounts.  The Polish Functionality module enables the user to control the receivables/payables balances on an ongoing basis and compensate them by linking customer and vendor cards for a given contracting party by using a contact card.

The following enhancements within Polish Functionality support the compensation of receivables and payables for one contracting party:


  • Viewing the balance for a customer/vendor – the payables balance can be viewed only in the customer card, whereas the receivables balance – in the vendor card.
  • Suggesting and posting compensation – Polish Functionality offers features that support the posting of payables and receivables compensation for one contracting party.
  • Single balance confirmation – payables of the contracting party can be included in the Customer Balance Reconciliation document, whereas its receivables can be registered in the Vendor Balance Reconciliation.

Customer/vendor balance reconciliation

At the end of each fiscal year (or, if necessary, other accounting periods) companies prepare reports on their accounts receivable and payable to reconcile them with relevant customer and vendor balances. Vendors and customers are obliged to validate such statements by settling the payables and receivables balances registered in their systems and provide their feedback on the process. The Polish Functionality module provides Customer Balance Confirmation and Vendor Balance Confirmation reports that show receivables and payables at specific dates.

Prepayment invoices

Polish VAT regulations require the company to issue a prepayment invoice for any prepayments the customer has paid for the sales order delivered. The Polish Functionality module extends the standard Microsoft Dynamics application with customization options that ensure compliance with Polish law.

Contractor data in the National Official Business Register (BIR)

The Polish Functionality module enables you to connect from Microsoft Dynamics NAV from the Polish National Official Business Register search engine to search for business entities based on registration numbers. It is possible to create and update customer, vendor and contact data based on data retrieved from the Polish National Business Online Register.

Quarterly reporting for the Central Statistical Office of Poland

The quarterly report (DNU-K) compiled for the Central Statistical Office lists all services sold and purchased from non-residents. The Polish Functionality module provides a tool for preparing data for DNU-K reporting purposes.

Local solutions for fixed assets management

Polish Functionality

Fixed assets classification

Polish regulations require the grouping of fixed assets according to their current statutory classification. The official fixed asset classification includes 3 grouping levels:


  • group – e.g. means of transport,
  • subgroup – e.g. motor vehicles,
  • type – e.g. passenger cars.

The standard Microsoft Dynamics NAV functionality has been enhanced with the capability of assigning a type (based on fixed assets classification) to each fixed asset. In the latest system version, fixed assets reports with various setup options enable the user to group data by FA classification numbers which have been assigned to fixed assets.

New fixed assets classification (KŚT 2016)

The Regulation of the Council of Ministers of 3 October 2016 (Journal of Laws 2016, item 1864) on the fixed assets classification, introduces new classification symbols. The regulation obliges business entities to use the 2016 classification for balance sheet related purposes in order to classify fixed assets based on a proper group, subgroup and type. Polish Functionality has been enhanced with a tool for creating a table based on the valid fixed asset classification (provided that the number can be mapped unambiguously between KŚT 2010 and KŚT 2016). Fixed assets reports can be generated for both classifications.

Fixed asset appreciation in a purchase invoice

With standard Microsoft Dynamics NAV, purchase invoices can be used only to post fixed asset acquisition and maintenance costs. The enhancement of the fixed asset functionality in the Polish Functionality module makes it possible to record fixed asset appreciation by using the purchase invoice.

Annual depreciation plan

In order to estimate the expected value of fixed assets as well as tangible and intangible assets, many companies perform an annual depreciation simulation. The Polish Functionality module provides the Annual Depreciation Plan report that specifies expected depreciation costs of fixed assets for a selected year.

Local solutions for inventory management

Polish Functionality

Polish Classification of Products and Services (PKWiU)

The PKWiU functionality, as a part of the Polish Functionality module for Microsoft Dynamics NAV, enables the user to register purchase and sales transactions using PKWiU codes for a given product. If needed, the code is printed on sales invoices.

General business posting group in transfer orders, production orders and assembly orders

In the standard Microsoft Dynamics NAV, transfer orders, production orders and assembly orders are posted by default using the setup defined in the General Posting Setup window on the lines with a blank Gen. Bus Posting Group field. Leaving the Gen. Bus. Posting Group field empty when defining general posting setup, may cause a user’s error. To prevent such errors, Polish Functionality enables the user to select a business posting group code on the Transfer Order, Production Order and Assembly Order cards. It is also possible to define a default code for a relevant general business posting group for such orders.

Packaging tax calculation

Companies selling or consuming goods on the local market are obliged to prepare a packaging tax declaration for the Tax Office. The Polish Functionality module provides tools that make it easier to prepare such declarations by:

  • defining a packaging list,
  • collecting data on inventory sales and consumption in combination with a defined packaging list,
  • calculation and reporting on a packaging tax amount for the aforementioned transactions and items.


Poland’s accession to the European Union resulted in new reporting requirements imposed on business entities that trade with EU member states. Business units are obliged to submit Intrastat declarations in a specified form and manner as well as to report intra-community trade and goods turnover to custom authorities. The standard Microsoft Dynamics NAV provides tools that simplify the creation of Intrastat declarations. With additional modifications in the Polish Functionality module, it is also possible to export Intrastat declaration in the XML file format.

Physical inventory counting document

At the end of the fiscal year, users carry out physical inventory counting in order to reconcile physical on-hand inventory with values registered in the Microsoft Dynamics system. Polish Functionality provides the Physical Inventory Counting Document report which can be archived by the accounting department as a confirmation of the completed physical inventory counting process.  The physical inventory counting document includes posted inventory values and quantities as well as names of company employees who, with their signatures, confirm that quantities and amounts shown in the document match the actual inventory levels.

Warehouse activity documents

Typical warehouse operations in Microsoft Dynamics NAV include: physical inventory, inventory revaluation and warehouse movements. The system enables the user to print the inventory movement document that is available in the Item Reclass. Journals window. Polish Functionality provides additional reports which can be used to record and view warehouse transactions:

  • Inventory Write Down Document – The document is available in the Item Journals window before the operation is posted.
  • Posted Inventory Write Down Document – The document is available in the Financial Management module reports after the operation has been posted.
  • Inventory Revaluation Document – The document is available in the Revaluation Journals window before the operation is posted.

Analysis and reports


The Polish Functionality module provides statutory reports that should be created at the closure of each month as well as other reports that support users in their daily work. All reports can be created for any period, not only for a month period.


Polish Functionality reports include:

Polish Functionality

G/L Account Net Change and Balance

The report shows values such as Open Balance, Period Balance, Period Net Change, Balance to Date for all or selected general ledger accounts.

G/L Journal

The report lists all general ledger entries in a chronological order.

G/L Register Posting Document

The report shows a posting entry for a G/L register and other important information. It confirms transaction posting.

Analytical G/L Register

As with G/L Register Posting Document report, the document confirms the transaction posting and displays a posting entry. However, it is more detailed and includes information about entry dimensions, subsidiary ledgers and currencies used.

Analytical G/L Document

The report shows data similar to data listed in Analytical G/L Register, however it provides better filtering capabilities. The report header displays source information for the posted transaction.

G/L Purchase Invoice, G/L Purchase Credit Invoice, G/L Sales Invoice, G/L Sales Credit Memo

The four reports display a posting entry as well as statutory information about, for instance, general ledger accounts, subsidiary ledger accounts, transaction currencies, currency exchange rates etc. The reports are the confirmation of a posted purchase or sales transaction. They can be printed based on a posted purchase or sales invoice or sales credit memo and purchase credit memo.

Bank Account – Detail Trial Balance

The report shows details of transactions posted on selected bank accounts. It can be used at the closing of an accounting or financial period. Within Polish Functionality for Microsoft Dynamics NAV, it is possible to print reports with debit and credit amount columns.

G/L Account Net Change and Balance

These reports supplement the G/L Account Net Change and Balance report. They are based on subsidiary ledger entries including receivables and payables entries. The reports show values such as Open Balance, Period Balance, Period Net Change, Balance to Date for all customers and vendors based on posting groups (receivables or payables accounts).

Customer Ledger Entry Journal and Vendor Ledger Entry Journal

which supplement the G/L Journal report. They are based on subsidiary ledger entries including receivables and payables entries. The reports list all entries in the customer or vendor ledgers in a chronological order.

Aged Accounts Receivable

These reports list open receivables and payables entries in six selected periods by a payment date or posting date.

Aged Accounts Payable/Aged Accounts Payable

The report provides a tabular view of aged accounts payable/receivable, facilitating data analytics as well as data sorting, filtering and copying at the same time.

Customer – Balance at Date and Vendor – Balance at Date

These reports provide a detailed and comprehensive overview of receivables and payables balances. Polish Functionality for Microsoft Dynamics NAV 2016 offers enhanced reporting capabilities for prepayments and substitute posting groups (multiple payables and receivables accounts).

Vendor – Detail Trial Balance and Customer – Detail Trial Balance

The reports show detailed trial balance entries for a selected customer or vendor. Polish Functionality has been enhanced with the capability of filtering customer and vendor entries per G/L groups used in specific receivables and payables ledger entries.

Aged Inventory

This report shows inventory quantities and values for any four selected periods.

FA Card

This report combines data from FA List and FA Detail reports with details grouped by a FA depreciation book.

FA Phys. Inventory List

The report is printed when an actual fixed asset book value and quantity are reconciled with registered values and quantities for financial reporting purposes.

FA Receipt

The report is printed when a fixed asset has been received and is ready for use. This document has to be signed by company representatives.

FA Disposal

The report is printed if a fixed asset has been removed from the register, because it was sold or disposed.

The Polish Functionality module for Microsoft Dynamics NAV incorporates some improvements of standard reports.

The improved reports include:

Bank Account – Detail Trial Balance

The report shows details of transactions posted on selected bank accounts. The debit/credit columns have been added to the report.

Customer – Balance to Date and Vendor – Balance to Date

The reports display detailed balance for selected customers and vendors. The report supports prepayment management and substitute posting groups (for multiple receivables and payables accounts).

Vendor – Detail Trial Balance and Customer – Detail Trial Balance

The reports show detailed trial balance entries for a selected customer or vendor. The reports have been enhanced with the capability of filtering customer ledger entries and vendor ledger entries based on posting groups.

Standard Audit File (SAFT/JPK)

Polish Functionality

General Information

Polish Functionality supports the creation of SAFT files (Standard Audit Files for Tax) based on the JPK_VAT, JPK_FA, JPK_WB, JPK_KR, JPK_MAG structures for Microsoft Dynamics NAV. The file structures have been designed based on the guidelines for file structures published by the Ministry of Finance. The JPK_VAT file structure is an exact representation of the current VAT‑ 7 (17) declaration. According to the requirements specified by the Ministry of Finance, all data entries in the JPK_VAT file are to be consistent with a VAT-7 statement submitted by a taxpayer.


The data sent in the JPK_VAT file includes:

  • Sales – The registration of item sales and purchase transactions, for which the entity is obliged to charge a sales VAT amount.
  • Purchase – The registration of a VAT purchase.

Executing file export

The JPK module in Polish Functionality has been designed to enable the user to create JPK_VAT, JPK_KR, JPK_FA, JPK_MAG in the xml format. Files to be sent to the Tax Office should be generated as required within an external system i.e. (packed, encoded, signed with an electronic signature).

Export File Register

The JPK module enables the user to save the JPK_VAT, JPK_KR, JPK_FA, JPK_MAG and JPK_WB files in a database and reexport them. The register is also used to save the file containing setup that is used to generate data.