Development Project Status: Under Discussion

OpenVPMS was developed from an Australian point of view, and as such does not support all jurisdictions. This is an umbrella project to identify changes required for different jurisdictions.

Taxation

• tax is calculated per line item

Some jurisdictions expect tax to be calculated on the invoice total.
There are differences between the two calculations, due to rounding.

• product prices are displayed and stored tax inclusive

Product prices should be displayed and stored tax exclusive where the tax is calculated on the invoice total.
Prices should be stored ex tax where they need to be reported as such.

• tax rates are not stored historically

Tax rates may change over time. There may be reporting requirements to determine what tax rate or rates were used to arrive at an invoice total.

• tax rates are based on the practice location

Some jurisdications base taxes on the location of the purchaser, rather than where the sales took place.

See http://jira.openvpms.org/jira/browse/OVPMS-916

2. Reporting

The default reports are geared towards Australian reporting requirements.
A standard set of reports could be provided for each jurisdiction.

3. Postcodes (Zip codes)

By default, OpenVPMS ships with Australian postcodes.
While it would be possible to ship post code data for each locale, it may be simpler to provide a tool which loads postcodes from CSV files

Additionally, there is limited support for cities with multiple postcodes.
See http://jira.openvpms.org/jira/browse/ARCH-24

4. Localisation

The OpenVPMS web application supports localisation. The archetypes however do not.
They can be edited manually but this makes upgrades difficult.