The integration can be configured so that Tabs3 posts journal entries to one or more debit and credit accounts based on how the payment is allocated. This is done by specifying posting methods and mapping GLS accounts in the GLS Integration Setup program. Posting methods are selected using the By field, also referred to as the Primary posting method, and the Then field, referred to as the Secondary posting method.

The posting method allows you to automatically create journal entries based on one or a combination of two of the following options:

Single Debit/Credit When using the Single Debit/Credit method of integration, journal entries are always created using a single set of journal entries. For example, all payments allocated to fees can be configured to post to a bank account and to a fee income account.
Client Category When integrating by Client Category, journal entries are created based on the category the client is assigned. For example, all payments for clients assigned a Personal Injury category can be configured to post journal entries to a Personal Injury income account, whereas all payments for clients assigned a Bankruptcy category can be configured to post to a Bankruptcy income account.
Client Location When integrating by Client Location, journal entries are created based on the location the client is assigned. For example, all payments for clients assigned to the Lincoln location can be configured to post journal entries to a Lincoln income account, whereas all payments for clients assigned to the Omaha location can be configured to post to an Omaha income account.
Cost Type When integrating by Cost Type, journal entries are created based on the cost type assigned to the expense or advance that is being paid. For example, a payment that allocates to an expense cost type for photocopies can be configured to post journal entries to a photocopy income account.

Note: The Cost Type posting method is only available for payments that allocate to cost transactions.

Payment Tcode When integrating by Payment Tcode, journal entries are created based on the tcode assigned to the payment transaction. For example, all payments entered with payment tcode 91 can be configured to post to a fee income account, whereas all payments entered with payment tcode 92 can be configured to post to an expense income account.

Note: When a posting method by Payment Tcode and then by None is specified in the GLS Integration Setup, the All Other row is optional. When the All Other row is not defined, only payments using tcodes specified in the table will create journal entries.

Additionally, a tcode (or the All Other row) can be added to the table without specifying a debit account, credit account or journal. When GLS information is missing from the table, the GLS Integration Journal Entries window will be displayed when a payment is saved with that tcode. This allows the user to manually post journal entries instead of having Tabs3 automatically create them. Additionally, when using a posting method of Tcode and None, you can include only those payment tcodes you want to integrate with GLS.

Working

Timekeeper

When integrating by Working Timekeeper, journal entries are created based on the timekeeper the payment allocates to. For example, all payments that allocate to fees billed by Michael Jensen can be configured to post to an income account for Michael Jensen, whereas all payments that allocate to fees billed by Jennifer Larson can be configured to post to an income account for Jennifer Larson.

When a posting method of Working Timekeeper is specified, the amount posted to GLS can be based on working timekeeper allocations (gross figures) or fee compensation allocations (net figures). This is determined by the Include Fee Compensation amounts in posting check box. Fee compensation allocations are defined by setting up fee compensation rules for a client. Fee compensation rules allow a percentage of receipts to be allocated to timekeepers that may or may not have worked on the case.

Note: The Working Timekeeper posting method is only available for payments that allocate to fee transactions.

Primary Timekeeper

When integrating by Primary Timekeeper, journal entries are created based on the primary timekeeper assigned to the client. For example, all payments for clients with Primary Timekeeper 1 can be configured to post to an income account for Michael Jensen, whereas all payments for clients with Primary Timekeeper 2 can be configured to post to an income account for Paula Martin.
Secondary Timekeeper When integrating by Secondary Timekeeper, journal entries are created based on the secondary timekeeper assigned to the client.
Originating Timekeeper When integrating by Originating Timekeeper, journal entries are created based on the originating timekeeper assigned to the client.
None This option is only available in the Then field. Selecting the None option in the Then field allows journal entries to posted based solely on the Primary posting method (By field).

Note: When Single Debit/Credit is selected as the Primary (By) posting method, the Secondary (Then) posting method is automatically changed to None and cannot be changed.

See Also:   GLS Integration Overview
  GLS Integration Setup
  GLS Accounts Tables