A tax rule defines the tax rate applicable on the actual selling price i.e every rule has line items with attributes like min_amount,max_amount and rate. Currently, the rules decided by us are:

S.noNameDescriptionMin Amount(Exclusive)Max Amount(Inclusive)Rate(in percent)
1GST_0For actual selling price between 0(exclusive) and 99999999(inclusive) tax rate of 0% will be applicable0999999990
2GST_3For actual selling price between 0(exclusive) and 99999999(inclusive) tax rate of 3% will be applicable0999999993
3GST_5For actual selling price between 0(exclusive) and 99999999(inclusive) tax rate of 5% will be applicable0999999995
4GST_12For actual selling price between 0(exclusive) and 99999999(inclusive) tax rate of 12% will be applicable09999999912
5GST_18For actual selling price between 0(exclusive) and 99999999(inclusive) tax rate of 18% will be applicable09999999918
6GST_28For actual selling price between 0(exclusive) and 99999999(inclusive) tax rate of 28% will be applicable09999999928
7GST_APPARELFor actual selling price between 0(exclusive) and 1000(inclusive) tax rate of 5% will be applicable, whereas for actual selling price between 1000(exclusive) and 99999999(inclusive) tax rate of 12% will be applicable010005
10009999999912
8GST_FOOTWEARFor actual selling price between 0(exclusive) and 1000(inclusive) tax rate of 5% will be applicable, whereas for actual selling price between 1000(exclusive) and 99999999(inclusive) tax rate of 18% will be applicable010005
10009999999918

Every rule has a name, description , and as discussed above the rule line items.

A new field in the Oms client_sku_pojo relation has been introduced with the identifier as "tax_rule_name" , this attribute will indicate the name of the tax_rule which will be applicable for that global_sku_id for tax computation purpose.

If current tax rules does not conform to client's requirements then they can provide us the rule to use for them and the same rule then can be added to the tax handler app.



Customised Tax Computation Logic

The tax-handler app offers customised tax computation logic for every country, i.e it simply detects the country for which tax model is to be used from the form provided to it. If the logic corresponding to that country exists in the tax-handler app then, it will be used to calculate the tax . In a nutshell, this customised tax computation logic will allow developer to code country level tax logic by simply creating an API corresponding to that country containing that logic and then is ready to go.



Migration of current Clients to new Tax Logic

Below is the suggested data format to be shared by Client


Distinct_HSN_IdTax_rule_name


Client_sku_idTax_rule_name



OR










Note 

  • If the tax rules for some SKUs are not present in our tax rules list, then share those details as well.
  • If there is a context like two rules applicable for an HSN ID, then they will have to share only on SKU level to maintain 1-1 mapping.