Migrating a Site to HQ Tax Groups

Overview

If a Site is already set up with taxes managed from the Site level, migrating to HQ Tax Groups comes with a few caveats.

What Triggers Migration?

It's important to first consider that the trigger to migrate an individual Site from Local Taxes to HQ taxes is the connected of the Site to the Tax Group.

It should only be migrated once everything is in place and ready to cut over

Connecting a site to a Tax Group disconnects and disables all Local Tax configurations

Before You Migrate

Assess the complexity: Hotels will likely have the same Tax Rates and Rules, while a chain with 20 locations in multiple states will require a much more complex tax setup.

Map It Out: Identify and map all known Tax Rates and Rules of each Site working with Master Item under the HQ, noting all names, Rates, and Rules associated with the Items.

As part of the mapping effort, consider the following local configurations that will need to be reconfigured at site level to properly inherit from the HQ:

Local Items: Make note of Tax Rules associated to Local Items
Auto Gratuity: Any Auto Grat that has a Tax Rule applied
Fees: Any Fee(s) that has a Tax Rule applied
Third Party: Any/all Third Party configurations that have Tax Rates applied

Complete the following checks before migrating to HQ Tax Groups:

Check BOTH the HQ and Site level catalogs for Items without taxes
Test an Item on the PAD and check that the tax is properly calculated
In Tabit Office go to Back Office > Order Search and confirm that the tax is properly calculated on the bill
Check that the Tax Rate reporting on the DSR is as expected

Learn how to configure HQ Tax Groups here.