Integration can be enabled for individual Tabs3 Billing cost transaction codes. This is done by adding each desired cost transaction code to a table using the GLS Integration Setup window.

When adding a cost entry in Tabs3 Billing, the integration works differently depending on whether or not a Debit account, Credit account, and Journal have been mapped to the tcode.

Automatic

When all three items have been mapped, the integration is automatic when a cost is saved. You can verify what journal entries were created by accessing the cost transaction in the Cost Entry window and clicking the button or pressing Ctrl+J. A GLS Integration window will be displayed (provided you have Detail Cost GLS View access rights).

Alternatively, the GLS Integration window can also be displayed each time a cost is saved by clicking the button or Ctrl+J to save the cost instead of the button or Ctrl+S.
Manual When one or more of the three items is not mapped, the integration is not automatic when a cost is saved. Instead, a GLS Integration window will be displayed allowing you to manually post the journal entries (provided you have Detail Cost GLS View access rights).

Changing a cost amount or date in Tabs3 will make adjustments in GLS; however, changing a journal entry in GLS will not make changes to the Tabs3 cost entry. As a rule of thumb, changes and deletions should be made to the original entries in the system in which they were generated.

Note: For task based billing clients, an Expense ID is entered in lieu of a transaction code. Accordingly, the GLS integration options for the Cost transaction code associated with the Expense ID are used.

AP Note: Firms that use Tabs3 Accounts Payable post journal entries for costs to GL using the AP software. Therefore, these firms typically do not configure Tabs3 Billing transaction codes to integrate with GL because the integration is handled by AP.

Source of the GL Journal Entry Fields

The following indicates the source of the GL journal entry's fields:

GLS FIELD SOURCE
Trans # Automatically assigned by GL.
Date Date field from the cost transaction.
Account The GLS Accounts Table for Expense & Advance Cost Entries.
Debit/Credit The Amount field from the cost transaction.
Description The first 120 characters of the Description field from the cost transaction.
Check # 0.
Jrnl The GLS Accounts Table for Expense & Advance Cost Entries.
Reference Tabs3 Client ID.
Status The Status will be cleared, indicating that the journal entry is Outstanding. (Note: If a change is made to a Tabs3 transaction where reversing journal entries were created, the Status will show R [Reconciled] for the original journal entry and reversing journal entry to the bank account.)
User ID User ID entering the cost transaction.
Date Entered System Date when the cost transaction is entered.

See also:   How GLS is Affected When a Tabs3 Cost is Changed
  How GLS is Affected When Costs are Written-Up/Down
  How GLS is Affected When Costs are Split
  GLS Integration Overview