This article applies to Microsoft Dynamics AX for the Poland (pl) region.

INTRODUCTION

This article describes a country-specific update about "Allowance for Bad Debts" that is available for Poland for Microsoft Dynamics AX 2009 Service Pack 1 (SP1) and Microsoft Dynamics AX 2012 R2.

More Information

On 1 January, 2013, changes to value-added tax (VAT) law regulations that are related to unpaid invoices, which are known as "Allowance for Bad Debts," came in force in Poland. Previously, because of the restriction, those regulations were rarely used by creditors and debtors were forced to do adjustments in input VAT only if creditor used those possibilities.

Since 1 January 2013, the regulations are as follows:

  • On the creditor side, it is possible to correct output VAT on unpaid invoices (receivables) under following conditions:

    • Delivery of goods or services was provided to active VAT taxpayer.

    • Debtor, on the day before submission VAT statement in which bad debt allowance will be used is active VAT taxpayer, has not been the subject of bankruptcy or liquidation.

    • Receivable is not overdue more than 2 years.

    Correction of output VAT can be done for period, in which receivable is proofed to be irrecoverable, which is meant as not paid within 150 days from original due date (It was neither sold nor paid).

  • On the debtor side, debtor is obliged to correct input VAT in period, in which passed 150 days from purchase invoice original due date for payables, which are not paid. This is unconditional requirement. It means that debtor is obliged to do correction, even if debtor did not used possibilities of allowance for bad debt.

    If invoice was paid (or receivable was sold by creditor) after allowance for bad debts was used, allowance should be reversed in VAT statement for period in which invoice was paid (or receivable was sold by creditor). If payment was partial, reversal should be done partly (proportionally to original invoice amount).

    The accountant worked with Account Payable or Account Receivable must identify periodically bad debts. The debts get bad when the invoices are not paid more than 150 days but less than 2 years later than the planned due date.

    The incoming and outgoing VAT should be corrected (reversed) for the identified debts. The final decision is up to the accountant. That means that the accountant can exclude some invoices identified automatically.

    If the debts will be paid in the next accounting period, the VAT must be reversed back proportionally to the payment sum.

Periodical procedure identifies the bad debts based on the vendor's or customer's open transactions and settlements from one side and on the payment schedule from the other side.
The VAT in identified debt sum is allocated between the VAT codes in invoice lines to be reversed.
The sums of settled payments are also allocated in the same manner between the VAT codes in invoice lines to be reversed back.
The journals may be canceled starting from the last one if there is a mistake. The transactions will be reversed.
The allocation of VAT sums happened by posting.
General ledger (GL) accounts for VAT correction posting and periods for bad debts must be set up.

You must specify the setup in the application. To do this, follow these steps:

  1. Click Basic, click Setup, and then click Company information. On the Other tab, under Country, set the Regional specific functionality value to Poland.

  2. Click General ledger, click Setup, click Overdue Debts, and then click Overdue journal calculation settings.

    • Set the Register journal type. The available options are Customer VAT journal and Vendor VAT journal.

    • Set the following setup for each record:

      • The Minimum number of days field: Minimum period that invoice is overdue, for current law is 150 days.

      • The Maximum number of days field: Maximum period that invoice will not be considered as overdue, for current law is 2 years.

      • The Calculation type field: Defines date for each overdue to be calculated. Available values are Due date and Invoice date.

      • The Validate check box If the check box is selected, it validates that transactions do not change balance on date of last posted journal.

      • The Condition field and the Payment term dates field should be empty.

  3. In the parameters for the Accounts Receivable module and the Accounts Payable module, on the Payable number sequences tab, two references must be set up:

    • VAT in overdue debts journal number

    • VAT in overdue debts voucher

  4. Specify the Account setup. To do this, click General ledger, click Setup, click Sales tax, click Ledger posting groups, and then specify the Offset Reversed Incoming Tax field and Offset Reversed Outgoing Tax field.

New functions are added to the Accounts Receivable module and the Accounts Payable module under Periodic as the VAT in overdue debt menu item. The available functions are as follows:

  • Create When we create a journal, user sets up the date on which debt amount will be calculated. Interval of dates will be calculated automatically based on setup in the Overdue journal calculation settings.

    ImportantWhen you create a journal, all overdue unpaid invoices for journal periods are automatically included. It also includes invoices for which payments were processed in that period. Information will be available in the Paid amount currency field and the Paid tax amount currency field.

  • Lines

    • The General tab includes information about customer's or vendor's invoices that contain bad debts appeared in reporting period. The tab has the following information:

      • Customer's or Vendor's identification data

      • Invoice data.

    • The Total tab displays cumulate amounts for all invoices that contain bad debts and are not paid until the end of reporting period. There are overdue amount and overdue tax amount.

    • The Overview tab On the tab, the Exclude check box allows you to exclude any invoice from journal that they do not want process. If any part of that invoice was already processed (VAT refund is finished), it is impossible to exclude. Totals amounts that are presented in the columns are reflected on the header of the form. The amounts are recalculated when filtering the lines.

      There is an Inquiries button that allows you to move to the customer or vendor transaction for that invoice.

  • Post It allows you to create VAT reverse transaction for invoices that are included in the journal. Posted journal can be canceled. This function is available only for last journal. During cancelation you can select the type of correction transaction, either correction or reverse. There is a Correction check box.

  • Inquiries The following is available to inquire:

    • Counting
      Contains summary information for customer or vendors, and invoices.

    • Voucher transaction
      Transactions that are created during post or cancelation.

    • Posted sales tax
      Posted sales tax transactions that are located into tax codes from invoices.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/support/Customers

https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htmIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.

  2. Apply these changes in a test environment before you apply the hotfix in a production environment.



For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics AX 2009 Service Pack 1

  • Microsoft Dynamics AX 2012 R2 with cumulative update 6 (CU6) installed
    For more information about cumulative update 6 for Microsoft Dynamics AX 2012 R2, click the following article number to view the article in the Microsoft Knowledge Base:

    2850972 Cumulative update 6 for Microsoft Dynamics AX 2012 R2

  • Microsoft Dynamics AX 2012 R2 with hotfix 2853581 installed

Restart requirement

You must restart the Application Object Server (AOS) service after you apply this hotfix.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For Microsoft Dynamics AX 2009 SP1

File name

File version

File size

Date

Time

Platform

Axupdate.exe

Not applicable

62,120

24-May-2013

18:27

x86

Kb2840744glp.xpo

Not applicable

64,554,884

24-May-2013

17:21

Not applicable

Metadata.xml

Not applicable

72

24-May-2013

17:21

Not applicable

Kb2840744.xpo

Not applicable

75,688,046

24-May-2013

17:23

Not applicable

Metadata.xml

Not applicable

72

24-May-2013

17:23

Not applicable

Axsetupsp.exe

5.0.1100.45

1,637,040

24-May-2013

18:26

x86

Cabextractor.dll

Not applicable

19,632

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.dll

5.0.1100.9

150,440

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

539,328

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

17,336

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,824

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,824

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

539,328

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,824

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

539,328

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1500.1212

16,320

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,824

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

543,424

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

17,848

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,824

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

535,232

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

547,520

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

18,872

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

559,808

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

20,408

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

531,136

24-May-2013

18:21

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

16,312

01-Aug-2012

15:28

x86

Axsetupsp.resources.dll

5.0.1100.40

527,040

24-May-2013

18:26

x86

Microsoft.dynamics.setup.reportingservices.resources.dll

5.0.1000.45

15,800

01-Aug-2012

15:28

x86

Cabextractor.dll

Not applicable

23,216

24-May-2013

18:27

x64

For Microsoft Dynamics AX 2012 R2

File name

File version

File size

Date

Time

Platform

Aximpactanalysis.exe

Not Applicable

61,136

16-Jul-2013

17:22

x86

Axupdate.exe

Not Applicable

61,120

16-Jul-2013

17:22

x86

Dynamicsax2012r2-kb2840744-foundation.axmodel

6.2.1000.2411

32,442,096

05-Aug-2013

03:04

Not Applicable

Dynamicsax2012r2-kb2840744-syplabels.axmodel

6.2.1000.2411

4,705,008

05-Aug-2013

03:04

Not Applicable

Dynamicsax2012r2-kb2858835-foundation.axmodel

6.2.1000.1948

48,880

17-Jul-2013

14:33

Not Applicable

Axsetupsp.exe

6.2.1000.1154

1,391,280

16-Jul-2013

17:22

x86

Axutillib.dll

6.2.120.0

929,968

05-Aug-2013

03:04

x86

Microsoft.dynamics.servicing.operations.dll

6.2.73.8303

37,168

16-Jul-2013

17:22

x86

Axsetupsp.resources.dll

6.2.147.8303

387,776

05-Aug-2013

03:04

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

379,584

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

379,584

05-Aug-2013

03:04

x86

Axsetupsp.resources.dll

6.2.147.8303

371,392

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

383,680

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

395,968

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

379,584

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

387,776

05-Aug-2013

03:04

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

379,584

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

379,584

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

379,584

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

395,968

05-Aug-2013

03:05

x86

Axsetupsp.resources.dll

6.2.147.8303

375,488

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

416,448

05-Aug-2013

03:03

x86

Axsetupsp.resources.dll

6.2.147.8303

371,392

05-Aug-2013

03:03

x86


Objects that are affectedThis hotfix affects the following objects:
The following objects are changed:

  • \Classes\CustVendReversePosting

  • \Classes\CustVendVoucher

  • \Classes\CustVendSettle

  • \Classes\NumberSeqReference_Vendor

  • \Classes\NumberSeqReference_Customer

  • \Data Dictionary\Tables\TaxLederAccountGroup

  • \Data Dictionary\Tables\VendParameters

  • \Data Dictionary\Tables\CustParameters

  • \Forms\TaxAccountGroup

The following objects are added:

  • \Classes\OverdueJournalCreate_W

  • \Classes\OverdueVATJournalCreate_W

  • \Classes\CustOverdueVATJournalCreate_W

  • \Classes\VendOverdueVATJournalCreate_W

  • \Classes\TaxReverseTaxOverdueVATCancel_W

  • \Classes\TaxReverseTaxOverdueVAT_W

  • \Classes\OverdueVATJournalCancel_W

  • \Classes\OverdueVATJournalPost_W

  • \MenuItems\Action\OverdueVATJournalCreate_W

  • \MenuItems\Action\OverdueVATJournalPost_W

  • \MenuItems\Action\OverdueJournalCreate_W

  • \MenuItems\Display\CustOverdueVATDebtCounting_W

  • \MenuItems\Display\VendOverdueVATDebtCounting_W

  • \MenuItems\Display\OverdueJournalSettings_W

  • \MenuItems\Display\VendOverdueVATJournalTable_W

  • \MenuItems\Display\CustOverdueVATJournalTable_W

  • \MenuItems\Display\CustOverdueVATJournalLines_W

  • \MenuItems\Display\VendOverdueVATJournalLines_W

  • \Forms\VendOverdueVATJournalTable_W

  • \Forms\CustOverdueVATJournalTable_W

  • \Forms\CustOverdueVATJournalLines_W

  • \Forms\VendOverdueVATJournalLines_W

  • \Forms\CustOverdueVATDebtCounting_W

  • \Forms\VendOverdueVATDebtCounting_W

  • \Forms\OverdueJournalSettings_W

  • \Data Dictionary\Views\VendOverdueVATDebtCounting_W

  • \Data Dictionary\Views\CustOverdueVATDebtCounting_W

  • \Data Dictionary\Tables\TaxReverseLink_W

  • \Data Dictionary\Tables\VendOverdueVATJournalTable_W

  • \Data Dictionary\Tables\CustOverdueVATJournalTable_W

  • \Data Dictionary\Tables\CustOverdueVATDebtJournalLine_W

  • \Data Dictionary\Tables\VendOverdueVATDebtJournalLine_W

  • \Data Dictionary\Tables\CustOverdueVATTurnJournalLine_W

  • \Data Dictionary\Tables\VendOverdueVATTurnJournalLine_W

  • \Data Dictionary\Tables\OverdueJournalSettings_W

  • \Data Dictionary\Maps\OverdueTurnJournalLine_W

  • \Data Dictionary\Maps\OverdueDebtJournalLine_W

  • \Data Dictionary\Maps\OverdueJournalType_W

  • \Data Dictionary\BaseEnums\OverdueCalcType_W

  • \Data Dictionary\BaseEnums\ComparisonCondition_W

  • \Data Dictionary\BaseEnums\OverdueJournalType_W

  • \Data Dictionary\ExtendedDataTypes\Exclude_W

  • \Data Dictionary\ExtendedDataTypes\OverdueVATMaxDays_W

  • \Data Dictionary\ExtendedDataTypes\CustOverdueVATVoucher_W

  • \Data Dictionary\ExtendedDataTypes\VentOverdueVATVoucher_W

  • \Data Dictionary\ExtendedDataTypes\OverdueJournalId_W

  • \Data Dictionary\ExtendedDataTypes\OverdueVATMinDays_W

  • \Data Dictionary\ExtendedDataTypes\CustOverdueVATJournalId_W

  • \Data Dictionary\ExtendedDataTypes\VendOverdueVATJournalId_W

Validation of the application hotfix installationTo validate the installation of the application hotfix, open the SysHotfixManifest class in the Application Object Tree (AOT). Then, verify that there is a method whose name includes the Knowledge Base (KB) article number of the installed hotfix. Additionally, you can cross-check the affected objects by comparing the KBXXXXXX.txt file against the objects in the AOT. By doing this, you can make sure that the objects are changed correctly in the SYP layer or in the GLP layer.

Note The XXXXXX placeholder represents the KB article number of the installed hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

974255 Impact Analysis feature for Dynamics AX 2009

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein 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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×