The Key Type determines the format of the client numbering for the firm. Since client numbers can be alpha, numeric or alphanumeric, they are referred to as Client IDs. Client IDs typically include a decimal point. We recommend you set up your Client ID format so that the portion of the Client ID to the left of the decimal represents the client and the portion of the Client ID to the right of the decimal represents an individual matter for that client. Changes to the Key Type must be made using the Change Key Type program. You can select to have an alphanumeric, numeric or mixed Key Type.

Numeric The Numeric option allows for a maximum of 12 numeric characters in a Client ID. Only numbers will be allowed for Client IDs when the Numeric option is selected. The number of digits following the decimal is determined by the Decimal Places. Tabs3 can automatically assign new Client IDs when using the Numeric Key Type.
Mixed The Mixed option allows for a maximum of 12 alphanumeric characters in a Client ID. The characters to the left of the decimal point in the Client ID can be any combination of letters and numbers. The characters to the right of the decimal must be numbers. The number of digits following the decimal is determined by the Decimal Places. Tabs3 cannot automatically assign new Client IDs when using the Mixed Key Type; however, it can automatically assign new matter numbers.

Caution: Be sure you are aware of the integration considerations before you select a Key Type of Mixed.

Alpha The Alpha option allows for a maximum of 12 alphanumeric characters in a Client ID. Any combination of letters and numbers can be used before and after the decimal point as long as the overall number of characters does not exceed 12. The Decimal Places field is not available when using an Alpha Key Type. Tabs3 cannot automatically assign new Client IDs when using the Alpha Key Type.

Caution: Be sure you are aware of the integration considerations before you select a Key Type of Alpha.

Note: When using a Mixed or Alpha Key Type, only the letters A-Z and numbers 0-9 can be used in the Client ID. Special characters are not allowed.

Note: If you specify a Mixed or Alpha Key Type, a message will be displayed indicating that integration with certain cost recovery systems requires a Numeric Key Type. You will be asked to confirm that you want to use a Mixed or Alpha Key Type. (See also: Integration Considerations)

Maximum Client ID Allowed

Tabs3 always assumes the maximum number of digits or characters to the left of the decimal. This maximum number of characters allowed is directly dependent on the Decimal Places specified. For example, when using a Numeric Key Type with 2 Decimal Places, you can have a maximum Client ID of 999999999.99. However, if using 6 Decimal Places, you can have a maximum Client ID of 99999.999999. A maximum of 12 characters including the decimal point is allowed for a Client ID.

See also:   Sample Client IDs

Integration Considerations

If you plan on integrating with certain cost recovery systems, the Tabs3 Key Type must be set to Numeric.

Integration with PracticeMaster requires an identical Key Type and Decimal Places.

Other Considerations

When adding a new client or a new matter for an existing client, Tabs3 can automatically assign the next available Client ID or matter number. However, when using an Alpha Key Type, this option is not available. Likewise, when using a Mixed Key Type, Tabs3 can automatically assign the next available matter number for an existing client, but cannot assign the next available Client ID for a new client. Keep this in mind when deciding on which Key Type to use for your firm.

Additionally, when sorting by Client ID, the Client ID is evaluated one character at a time from left to right when using the Alpha and Mixed Key Types. Because of this, your clients may not be in the order you expect in lookup windows and on statements and reports. For example, if you have a client with a Client ID of 9KEM.01 and a client with a Client ID of 10KEM.01, client 10KEM.01 will be shown before client 9KEM.01 because the first character in "10KEM.01" (i.e., "1") is less than the first character in "9KEM.01" (i.e., "9").

See also:   Key Type Comparisons