An automated setup program uses your Canadian tax definitions to create most of the codes required to implement GTM. Before executing this program, understand the options it provides and the default logic it uses.

GTM codes for tax types, tax zones, and tax environments consist of text strings that uniquely identify the province, county, and city of a tax jurisdiction. In Canada, there are thousands of these codes; setting them up manually would be a tedious process.

Therefore, by default, CAN to GTM–Setup generates codes based on its code generation rules (Code Generation Rules in CAN to GTM-Setup (2.13.22.9)). These rules systematically select characters from the province code, county name, and city name in the tax master.

To determine if generated codes are suitable for your company, run the setup and review the audit trail. If you need a different coding scheme, read the rest of this section and change the settings for the code generation rules as necessary. Then, rerun the setup with Delete Previous GTM set to Yes and Convert Tax Masters set to Yes.

For Canadian taxes, the default generated code format for tax zones, tax types, and tax environments is:

PPP is the 3-character province code, CCCC the 4-character county or district name, and ccccccc the 7-character city name. A dash (–) separates each text string.

The rules used to determine the characters to select depends on:

Code Generation Rules in CAN to GTM–Setup (2.13.22.9) lists the default number of characters for each text string under the different conditions. However, you can change the number of characters and use a different separator or no separator. You can do so as long as the total number of generated characters—including the separator and any ending integers—is 16 or less.

Setup retains the capitalization from the original Canadian code or name. If the original code or name contains punctuation such as a period, the code generation rules treat it the same as any other non-blank character.

By default, the setup generates tax classes that directly correspond to your Canadian GST master records. To distinguish the two sets of codes, it appends the letter P to the GST + PST code. For example, if your current GST classes are 0, 1, and 2, the generated GTM classes are 0, 1, and 2 (for GST only) and 0P, 1P, and 2P (for GST + PST). The system does not automatically generate tax usages.

You can override this behavior by creating your own map for the setup program and specifying it in the Class File field. The same class file is also referenced in the programs that convert master data and transaction records.

Create a class file if:

The class file is an ASCII file with text strings in the following format:

GTM tax classes can have a maximum of three characters, and tax usage codes eight characters. A null string (“ ” or “”) represents an unused value.

The class file can have any name or extension. However, commas instead of blank characters separate code values in .csv files. Place the file in the home directory for the Progress session. A .csv file is a Windows comma-separated value file format that saves recorded values in a spreadsheet.

The generated codes for tax zones, tax environments, and tax types consist of text strings that identify the province, county, and city. By default, the code generation rules define the structure of these text strings. However, if you need a different naming convention, you can create geographic files for province codes, county names, and/or city names.

See Code Generation Rules.

Create a separate file for each kind of text string and reference the file in CAN to GTM–Setup as shown in Province, County, and City Files in CAN to GTM–Setup (2.13.22.9).

A geographic file is the same as a class file, except that it uses the format:

This program creates eB2.1 and later records as described in New GTM Records.

Setup defines Global Tax Management Control (2.13.24) as described in Updates to GTM Control Settings.

In GTM, company sites require a corresponding company address record because taxes are calculated using address, not site. The setup creates any missing company address records for company sites. However, the setup does not populate these new address records with the city, county, province, and country. Supply this information manually in Company Address Maintenance (2.12).

If the setup did not generate codes for these tax jurisdictions, you must set up tax zone codes to support these new addresses. Do the setup in Tax Zone Maintenance (2.13.3.13). Then, assign the tax zone to the address.

CAN to GTM–Setup prints a report of updated tax master records for GST and PST rates. For GST rates, the report shows the GST class, description, starting and ending effective dates, the GST percent, and the general ledger tax accounts for accounts payable and accounts receivable. For PST, the report shows the province/county/city, tax effective date, tax rate for the effective date, whether PST is based on GST, and the generated GTM tax zone and sums-into zone.

After you run CAN to GTM–Setup, verify that the GTM setup is correct before you continue with the conversion. The errors listed in Troubleshooting the GTM Setup can cause issues or unexpected values. Before proceeding to the master conversion, review the audit trail, the GTM reports for the new records, and Global Tax Management Control settings, and correct any errors.

Subsequent setups do not automatically overwrite records that previous ones created. To set up new records, first delete the old ones. If you rerun the setup, remove the records the earlier setup attempt created. Rerun the setup with Delete Previous GTM set to Yes and Convert Tax Masters set to Yes.

The following is a technical description of how the setup updates the database.

The menu-level program for CAN to GTM–Setup is txcancnv.p. This program calls subprograms (primarily txcantax.p) that set the GTM tax values in the individual database tables.