The report definitions for Tabs3 Billing include Client ID ranges. If you change the Key Type, you may need to edit your report definitions to reflect the new Key Type. Changing only the Decimal Places does not require changes to the report definitions.

The Client ID format will automatically be changed for any archived transactions. Allow additional time to run this program if you have large archive files.

The Merge Data Capture Transactions program requires a numeric Key Type for select data capture interface programs. If you want to use an alpha or mixed Key Type, an updated data capture interface program may be required. If you are planning on changing your Key Type, call Tabs3 Software Sales Department for pricing to update your data capture interface program.

If you want to change the Key Type or Decimal Places, make sure you merge any existing data using the Merge Data Capture Transactions program before doing so. Otherwise, entries using the old Client ID format will be rejected.

If you use Tabs3 Billing Remote, the Key Type and Decimal Places must be the same in Tabs3 Billing and Tabs3 Billing Remote. If you change the Key Type or Decimal Places, you must merge all transactions from the remote workstation(s) before changing the Key Type or Decimal Places. Otherwise, entries using the old Client ID format will be rejected. Make sure to change the Key Type/Decimal Places in Tabs3 Billing Remote Customization after changing the Key Type/Decimal Places in Tabs3 Billing. If you use the Tabs3 Billing Remote validation files, you must recreate these files after changing the Key Type.

Changing the Key Type or Decimal Places in Tabs3 Billing will automatically change the Key Type and Decimal Places in Trust and PracticeMaster.

When changing the Key Type from Alpha to Numeric, Alpha to Mixed, or Mixed to Numeric, some Client IDs may need to be renumbered prior to changing the Key Type. Clients in the current Key Type must match both the decimal places desired and use the same alpha/numeric format as required by the new Key Type. For additional information about this process, see Knowledge Base Article R11049, “Changing the Key Type or Decimal Places."

Tabs3 Billing will not allow certain renumbering situations to occur due to the possibility of duplicate or inaccessible Client IDs. For example, if you attempt to change the Decimal Places from 3 to 2 and select to remove digits from the beginning of the decimal digits, Tabs3 Billing checks to make sure that the single digit being removed is equal for all clients. For example, if the single digit being removed for all clients is "0," then Tabs3 Billing will perform the renumbering. However, if any client has a different value for that digit, a warning will be displayed and you will not be allowed to renumber using the specified parameters. In certain situations such as these, it may be possible to renumber the clients that are different before attempting to change the Key Type.

If using a Key Type of Mixed or Alpha, the Client ID field in reports and statements will not accept Name Search values in place of Client IDs. Using Name Search values will work only when the Key Type is set to Numeric.

If you are integrated with QuickBooks using the QBXML format, changing the Key Type in Tabs3 Billing will correspondingly change the account numbers of all customers and jobs in QuickBooks. Furthermore, any clients that existed in Tabs3 but not in QuickBooks will be added to QuickBooks.

If you are integrated with NetDocuments, the Key Type value cannot be changed. Changing the Decimal Places value is allowed and will not affect the link between clients in PracticeMaster and NetDocuments. However, the Insert Zeros value must be set to “Beginning” when changing the Decimal Places value.

Note: If you are changing the Decimal Places value, you may encounter issues with sorting lists of clients in NetDocuments. See Knowledge Base Article R11786, “NetDocuments Integration,” for more information.