Issue in tax determination by condition technique

[Former Member]

Hi All

ln case of argentina taxation there is provincial surcharge which is also known as gross income tax that is applied during vendor invoices.. The nature of this tax during the invoice entry is same as the Vat line item. Now the vendor applies this surcharge based on the region were he is identified as perception iibb agent.. So the percep iibb can appear more than once more in the vendor invoice.... In case of Buenos aries this percep iibb gets changed in even month.. So instead of creating new code every month i ws looking into the option for tax condition technique.. Here I maintained my Vat in ftxp for the tax code I1 and then I maintained the condition record for the iibb condition type in FV11. I had created new access sequence with reference to the access aeq 003 that is used for Vat condition type. The new access seq was assigned to the iibb condition type to provide the option of tax rate maintenance with validity dates.. In Fi posting the rate is determined correctly but during MIRO, it gives the message as tax condition xxxx not maintained in tax code I1. I don't understand the issue as i maintained the tax condition record for I1.

Regards

Nikhil Kothari

[Former Member]

This message was moderated.

[Former Member]

Hi Nikhil,

In FV11 what is the from date and to date you have maintained and what is the posting date and document date of MIRO. If it is before the from date of FV11 it will say the error. You might try to change the from date in FV12.

Hope it helps.

[Former Member]

Hi

thanks for the reply.

I had successfully posted the FI docs. With the same settings, now i trying to post the MIRO. The document date and posting date is also correct. The error I get says no entry found in table A053 and A003. These are the access sequence table assigned to std tax conditions were the key fields are country/tax code/jurisdiction and country/tax code respectively. In my case I had taken the reference of A003 and had enabled the validity dates. So, I don't get it as to why the system checks for this std tables in case of MIRO and not in case of FI posting.

Thanks & Regards

Nikhil Kothari