How to change to tax inclusive pricing from tax exclusive pricing
Mandalay CS can allow for product pricing to be either inclusive or exclusive of tax. A commercial user of Mandalay CS will usually find it easier to work without tax included in the price, however councils usually publishing and manage their tip fees to be tax inclusive. If you are a user of Mandalay and are currently using Mandalay CS with exclusive pricing but publish inclusive rates then you need to make calculation on each price before entering into Mandalay. This can sometimes introduce rounding issues. To avoid these issues it is best to move to a tax inclusive pricing model. This article explains the steps required to move to this setup.
Create new Season
The process of moving to inclusive pricing will require that a new season be created to start on a particular day in the future. This will be the day that you plan to move to the inclusive pricing model. It is probably best to set this to the beginning of a new month.
Use the the same process that you would use to create a new season when performing periodical pricing increases.
Tip: Set the start time of the new season to be just after operations complete for all sites to make it easier to test after making the configuration change in the final step.
Setup new price with GST included
Once the new season has been created you will then need to increase each products price to be inclusive of GST. Remember to only do this against the new season created in the first step.
Tip: Use the 'Use this season for Administration session' on the seasons tab to speed up the process of increasing prices.
Change system configuration
Note: This next step should only occur after operating hours as it needs to be coordinated across all sites.
On the night of the pricing model change, the configuration of the system will need to be changed. This is done in the Configuration Manager program. The setting to change is located on the Company Details tab and is called Price Inclusive of Tax. This is a global setting so can be performed on any computer but will require replication to occur to synchronise the change to all database hosts.
After the change has been made and synchronised across the enterprise, the Ticketing system will need to be restart in order for the new change to take affect. Its a good idea to request that all users shut down Ticketing and the end of the day before the change is made.