Wrong purchase tax entry

[Former Member]

Dear Sir,

We have found several cases in our company where user has created wrong PO with CST Tax Code but Vendor belong to VAT (My Plant and Vendor in Same Region), resulting VAT part entered at CST (Cost) and we are not able to take credit of VAT which is loss to the company.

Now my company want to link VAT or CST with the vendor code region. So that if vendor is region is same that of Plant we have some validation at miro or migo that CST entry should not be allowed, and if plant region and vendor region is different than VAT entry should not be allowed.

We are having separate tax code for VAT, CST rate wise.

Regards

Rajeev Gupta

[ajitkumar]

why dont you have the correct tax code maintained in the info record? It will default from there to PO,

Also which access sequence you are using?

[Former Member]

Thanks Ajit,

Actually in the info record also the user has put wrong tax code and access sequence is JST1.

Regards

Rajeev Gupta

[Prasoon]

Hi,

   As Mr. Ajit already explained, one option is maintaining correct tax code at info record level.

   Another option could be configuring the tax code to be defaulted in the PO. This can be achieved by creating a new condition table with plant region, vendor region (and material if required) and assign the condition table to a new access sequence (You may check the standard access sequence 0003 and the tables assigned - in M/07). Assign the access to the tax condition types like NAVS or MWST . Maintain the condition record in MEK1 with tax code. Now, each time when the access are fulfilled, the tax code will be defaulted in PO, so that manual error can be avoided.

   Refer the link: Purchasing: Automatic Determination of Tax Code du (SAP Library - Release Notes for Release 3.0A)

Regards,

AKPT

[Former Member]

Thanks for update, we are using JIPS and JIPC condition for vat and cst. We will check your solution then come back to you.

Regards

Rajeev Gupta

[Prasoon]

Hi,

    I can suggest one more option for even better control. That is to maintain the access sequence of the tax conditions based on fields other than tax code; say, plant/region/material group. In this case, the tax code is dummy. If the condition records are maintained (in FV11) for the above combination, system will default the tax conditions (in PO - Invoice - Tax tab), irrespective of the tax code (You may give any default tax code in info record or through condition technique as explained above).

Regards,

AKPT

[ajitkumar]

have you tried it like this say from acc seq  Say JTAX or JST1?

[Prasoon]

Hi,

   We are already using the plant/material group (table 359) combination with JST1 and the same is working fine!.

Regards,

AKPT

[Prasoon]

Hi,

   Refer the document:

Regards,

AKPT