This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • OFBiz's Tax Authority Data Model

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Depending on what is passed in various things may be looked up in the database, like TaxAuthorities where the internal organization has a nexus (sufficient presence for taxation) based on productStoreId -> payToPartyId and the shipping (or if no shipping then billing) address. Another important lookup is the ProductCategory or categories relevant to the product. For example, in Australia staple foods are not subject to Goods and Services Tax, but prepared foods are. So flour, milk and eggs are tax free, but once you've baked a cake, if you sell it tax is payable. So you would organise these into two separate product categories.


The PartyTaxAuthInfo entity is used to keep track of information about the TaxAuthority for a given Party. This is used for customers as well as internal organizations (ie the company or divisions of it and such) to keep track of tax ID numbers whether the Party is tax exempt for the TaxAuthority, and also (mainly for internal organizations) if the Party has a "tax nexus" in/for the TaxAuthority. By tax nexus I mean that the organization has a sufficient presence there to be required to collect taxes on behalf of the TaxAuthority.