Source State DataField in Company's Address instead of Tax Category DocType

Instead of having to set In-State, Out-State; Why do we not set source state in Company-Address DocType. This has following advantages:

  1. In case of multi-dispatch location in multiple states, it would work seamless: Based on Dispatch state & Delivery state. Current system would have issue in that.
  2. In multi-company-multi state with common clients, it would work seam less: Based on Dispatch state & Delivery state. Current system would have issues in that.
  3. We don’t have to set it on Supplier and Customer level, which are generally way more than number of companies.
  4. No need for “Tax Category” DocType. Seems redundant.

This is just a suggestion. Tax Category DocType may have some technical compulsion need. If so, pls do share…

This currently works partially the way you are suggesting.


  • Dont use tax category in any of the parties or addresses
  • Just use it in the sales taxes and charges template and purchase taxes and charges template

Template selection should work automatically out of the box (only for the front end).

We are in the process of further simplifying this:

  • Move configuration related to inter-state and reverse charge from tax category to sales/purchase taxes and charges template
  • Explicit check to exclude transactions from GST
  • Enforce taxes if it’s not excluded
  • Make sure this works in the backend as well

Still, first preference will be given to the tax category if it’s set in party or address. This will support a more complex template configuration (like a template GST TDS for sales to govt). If the tax category is not used, it will work well without it as well.

This is up next and should come to production in a month or so.

1 Like