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. The VAT for the prepayment deduction is calculated incorrectly in the Swiss version of Microsoft Dynamics NAV with the "Date Sensitive VAT Rate tool" installed

The VAT for the prepayment deduction is calculated incorrectly in the Swiss version of Microsoft Dynamics NAV with the "Date Sensitive VAT Rate tool" installed

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • French (Switzerland) (fr-ch)
  • German (Switzerland) (gr-ch)
  • Italian (Switzerland) (it-ch)

↑ Back to the top

Symptoms

In the Swiss version of Microsoft Dynamics NAV with the "Swiss Date Sensitive VAT Rate tool" installed, the VAT is calculated for the prepayment deduction incorrectly when the old VAT rate and the new VAT rate have to be considered. For example, consider the following scenario:
  • You set the VAT value in the VAT posting setup.
  • You post a prepayment invoice for a sales order.
  • You post the payment for the posted prepayment invoice.
  • You change the Shipment Date / Expected Receipt Date in the sales order line and then post the sales order.
  • You check the VAT entry for the sales order in General Ledger.
In this scenario, Microsoft Dynamics NAV calculates the VAT amount by using the new VAT rate for the deduction of the prepayment incorrectly. Therefore, the VAT amount is incorrect. You expect the VAT for the prepayment deduction to be calculated by using the old VAT rate.
This problem occurs in the following products:
  • The Swiss version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Swiss version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

↑ 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 2009 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 Prepayment % - OnValidate function in the Sales Line table (37) as follows:
    Exsiting code
    ...
         VATPostingSetup.GET("VAT Bus. Posting Group",GLAcc."VAT Prod. Posting Group");
      END ELSE
        CLEAR(VATPostingSetup);
      "Prepayment VAT %" := VATPostingSetup.GetVATPercent("Shipment Date",SalesHeader."Posting Date");
      "Prepmt. VAT Calc. Type" := VATPostingSetup."VAT Calculation Type";
      "Prepayment VAT Identifier" := VATPostingSetup.GetVATIdentifier("Shipment Date",SalesHeader."Posting Date");
      CASE "Prepmt. VAT Calc. Type" OF
        "VAT Calculation Type"::"Reverse Charge VAT",
    ...
    Replacement code
    ...
       VATPostingSetup.GET("VAT Bus. Posting Group",GLAcc."VAT Prod. Posting Group");
      END ELSE
        CLEAR(VATPostingSetup);
      IF "Prepmt. Amt. Inv." = 0 THEN BEGIN
        "Prepayment VAT %" := VATPostingSetup.GetVATPercent("Shipment Date",SalesHeader."Posting Date");
        "Prepmt. VAT Calc. Type" := VATPostingSetup."VAT Calculation Type";
        "Prepayment VAT Identifier" := VATPostingSetup.GetVATIdentifier("Shipment Date",SalesHeader."Posting Date");
      END;
      CASE "Prepmt. VAT Calc. Type" OF
        "VAT Calculation Type"::"Reverse Charge VAT",
    ...
  2. Change the code in the Prepayment % - OnValidate function in the Purchase Linetable (39) as follows:
    Exsiting code
    ...
        VATPostingSetup.GET("VAT Bus. Posting Group",GLAcc."VAT Prod. Posting Group");
      END ELSE
        CLEAR(VATPostingSetup);
      "Prepayment VAT %" := VATPostingSetup.GetVATPercent("Expected Receipt Date",PurchHeader."Posting Date");
      "Prepmt. VAT Calc. Type" := VATPostingSetup."VAT Calculation Type";
      "Prepayment VAT Identifier" := VATPostingSetup.GetVATIdentifier("Expected Receipt Date",PurchHeader."Posting Date");
      CASE "Prepmt. VAT Calc. Type" OF
        "VAT Calculation Type"::"Reverse Charge VAT", 
    ...
    Replacement code
    ...
       VATPostingSetup.GET("VAT Bus. Posting Group",GLAcc."VAT Prod. Posting Group");
      END ELSE
        CLEAR(VATPostingSetup);
      IF "Prepmt. Amt. Inv." = 0 THEN BEGIN
        "Prepayment VAT %" := VATPostingSetup.GetVATPercent("Expected Receipt Date",PurchHeader."Posting Date");
        "Prepmt. VAT Calc. Type" := VATPostingSetup."VAT Calculation Type";
        "Prepayment VAT Identifier" := VATPostingSetup.GetVATIdentifier("Expected Receipt Date",PurchHeader."Posting Date");
      END;
      CASE "Prepmt. VAT Calc. Type" OF
        "VAT Calculation Type"::"Reverse Charge VAT",
    ...

Prerequisites

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


Removal information

You cannot remove this hotfix.

↑ 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: kbsurveynew, kbnoloc, kbmbscodefix, kbqfe, kbmbsmigrate, kbmbspartner, kb, kbmbsquickpub

↑ Back to the top

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