[
https://issues.apache.org/jira/browse/OFBIZ-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272435#comment-14272435
]
Pierre Smits commented on OFBIZ-5403:
-------------------------------------
This is not an extreme case. It is common practice in the accounting domain to
separate such important aspect as tax collected and paid into gl transactions
per percentage per type (e.g. sales high and sales low & paid high and paid
low). As it eases on auditing.
> Implement separate glAccounts per TaxAuthoritiy-ProductCategory combination
> ---------------------------------------------------------------------------
>
> Key: OFBIZ-5403
> URL: https://issues.apache.org/jira/browse/OFBIZ-5403
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Jacques Le Roux
> Labels: Tax,, accounting, transactions
>
> In current setup only 1 glAccount can be defined for each combination of
> TaxGeo, TaxAuthority and Internal Organization.
> However, it is common that multiple tax rates exist per TaxGeo (e.g. VAT
> rates of 0, 6 and 21% for The Netherlands) and it also customary to report
> separately for sales and purchasing per tax rate and audit registered tax
> bookings vs sales and purchases per period.
> As such implementing a glAccount per
> TaxGeo-TaxAuth-IntOrganisation-ProductCategory, and upgrading applicable
> transaction processing services would facilitate the above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
