Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. An incorrect general ledger account is used for payment tolerances when the Payment Tolerance Warning check box is selected in the General Ledger Setup dialog box in Microsoft Dynamics NAV

An incorrect general ledger account is used for payment tolerances when the Payment Tolerance Warning check box is selected in the General Ledger Setup dialog box in Microsoft Dynamics NAV

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

↑ Back to the top

Symptoms

Assume that you click to select the Payment Tolerance Warning check box in the General Ledger Setup dialog box in Microsoft Dynamics NAV. When you post a customer payment journal or a vendor payment journal that has a payment discount tolerance and a payment tolerance, the debit account or the credit account for the payment tolerance and the payment discounts is used incorrectly in the general ledger entries. In certain scenarios, the payment tolerance amount is registered for the debit account even though the credit account should be used in the general ledger entries.
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 5.0

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In 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 additional support questions and issues that do not qualify for the specific update in question.

↑ Back to the top



Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
  • The Modify permission for the object that you will be changing.
  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.


Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, follow these steps:
  1. Change the code in the PostDtldVendLedgEntries function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code 1
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Discount Tolerance":
      BEGIN
        IF GLSetup."Pmt. Disc. Tolerance Posting" =
          GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Tolerance Accounts"
        THEN BEGIN
          IF (DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Credit Acc.";
          END;
        END ELSE IF GLSetup."Pmt. Disc. Tolerance Posting" =
          GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Discount Accounts"
        THEN BEGIN
          IF (DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Credit Acc.";
    …
    Replacement code 1
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Discount Tolerance":
      BEGIN
        IF GLSetup."Pmt. Disc. Tolerance Posting" =
          GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Tolerance Accounts"
        THEN BEGIN
          IF (-DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Credit Acc.";
          END;
        END ELSE IF GLSetup."Pmt. Disc. Tolerance Posting" =
          GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Discount Accounts"
        THEN BEGIN
          IF (-DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Credit Acc.";
    …
    Existing code 2
    … 
    DtldCVLedgEntryBuf."Entry Type"::"Payment Tolerance":
      BEGIN
        IF GLSetup."Payment Tolerance Posting" =
          GLSetup."Payment Tolerance Posting"::"Payment Tolerance Accounts"
        THEN BEGIN
          IF (DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Credit Acc.";
          END;
        END ELSE IF GLSetup."Payment Tolerance Posting" =
          GLSetup."Payment Tolerance Posting"::"Payment Discount Accounts"
        THEN BEGIN
          IF (DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Credit Acc.";
    …
    Replacement code 2
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Tolerance":
      BEGIN
        IF GLSetup."Payment Tolerance Posting" =
          GLSetup."Payment Tolerance Posting"::"Payment Tolerance Accounts"
        THEN BEGIN
          IF (-DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Tolerance Credit Acc.";
          END;
        END ELSE IF GLSetup."Payment Tolerance Posting" =
          GLSetup."Payment Tolerance Posting"::"Payment Discount Accounts"
        THEN BEGIN
          IF (-DtldCVLedgEntryBuf."Amount (LCY)" >= 0) THEN BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Debit Acc.";
          END ELSE BEGIN
            VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
            PaymentTolAcc := VendPostingGr."Payment Disc. Credit Acc.";
    …
  2. Change the code in the AutoEntrForDtldVendLedgEntries function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code 1
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Discount Tolerance":
      BEGIN
        CASE GLSetup."Pmt. Disc. Tolerance Posting" OF
          GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Tolerance Accounts":
            BEGIN
              IF DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
                AccNo := VendPostingGr."Payment Tolerance Debit Acc.";
              END ELSE BEGIN
                VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
                AccNo := VendPostingGr."Payment Tolerance Credit Acc.";
              END;
            END;
          GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Discount Accounts":
            BEGIN
              IF DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
                AccNo := VendPostingGr."Payment Disc. Debit Acc.";
              END ELSE BEGIN
                VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
                AccNo := VendPostingGr."Payment Disc. Credit Acc.";
    …
    Replacement code 1
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Discount Tolerance":
      BEGIN
        CASE GLSetup."Pmt. Disc. Tolerance Posting" OF
            GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Tolerance Accounts":
              BEGIN
                IF -DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                  VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
                  AccNo := VendPostingGr."Payment Tolerance Debit Acc.";
                END ELSE BEGIN
                  VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
                  AccNo := VendPostingGr."Payment Tolerance Credit Acc.";
                END;
              END;
            GLSetup."Pmt. Disc. Tolerance Posting"::"Payment Discount Accounts":
              BEGIN
                IF -DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                  VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
                  AccNo := VendPostingGr."Payment Disc. Debit Acc.";
                END ELSE BEGIN
                  VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
                  AccNo := VendPostingGr."Payment Disc. Credit Acc.";
    …
    Existing code 2
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Tolerance":
      BEGIN
        CASE GLSetup."Payment Tolerance Posting" OF
          GLSetup."Payment Tolerance Posting"::"Payment Tolerance Accounts":
            BEGIN
              IF DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
                AccNo := VendPostingGr."Payment Tolerance Debit Acc.";
              END ELSE BEGIN
                VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
                AccNo := VendPostingGr."Payment Tolerance Credit Acc.";
              END;
            END;
          GLSetup."Payment Tolerance Posting"::"Payment Discount Accounts":
            BEGIN
              IF DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
                AccNo := VendPostingGr."Payment Disc. Debit Acc.";
              END ELSE BEGIN
                VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
                AccNo := VendPostingGr."Payment Disc. Credit Acc.";
    …
    Replacement code 2
    …
    DtldCVLedgEntryBuf."Entry Type"::"Payment Tolerance":
      BEGIN
        CASE GLSetup."Payment Tolerance Posting" OF
          GLSetup."Payment Tolerance Posting"::"Payment Tolerance Accounts":
            BEGIN
              IF -DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                VendPostingGr.TESTFIELD("Payment Tolerance Debit Acc.");
                AccNo := VendPostingGr."Payment Tolerance Debit Acc.";
              END ELSE BEGIN
                VendPostingGr.TESTFIELD("Payment Tolerance Credit Acc.");
                AccNo := VendPostingGr."Payment Tolerance Credit Acc.";
              END;
            END;
          GLSetup."Payment Tolerance Posting"::"Payment Discount Accounts":
            BEGIN
              IF -DtldCVLedgEntryBuf."Amount (LCY)" < 0 THEN BEGIN
                VendPostingGr.TESTFIELD("Payment Disc. Debit Acc.");
                AccNo := VendPostingGr."Payment Disc. Debit Acc.";
              END ELSE BEGIN
                VendPostingGr.TESTFIELD("Payment Disc. Credit Acc.");
                AccNo := VendPostingGr."Payment Disc. Credit Acc.";
    …

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 5.0


Removal information

You cannot remove this hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981697 An incorrect G/L account is used when you post a payment to apply an invoice where "Full VAT" was used if the "Adjust for Payment Discount" setting is enabled in the "General Ledger Setup" form in Microsoft Dynamics NAV 2009

↑ Back to the top

Status

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

↑ Back to the top

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.

↑ Back to the top

Keywords: kb, kbqfe, kbmbspartner, kbmbsquickpub, kbmbsmigrate, kbnoloc, kbsurveynew, kbmbscodefix

↑ Back to the top

Article Info
Article ID : 2423241
Revision : 2
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 334