The GLS Accounts Table for Payments Allocated to Fees window can be accessed by clicking the Fee Accounts button on the Configure Payment Integration window of the GLS Integration Setup program

This window allows you to add, change and delete account mappings for integration with Tabs3 General Ledger Software (GLS). An account mapping links a Tabs3 fee payment allocation with GLS accounts and a GLS journal.

When a posting method of anything other than Payment Tcode and None is specified, the first row in the table is an All Other row. This row allows you to map GLS accounts for any allocations that are not defined in the table. For example, let's say that a firm's posting method is Working Timekeeper. The firm can map a specific income account for certain timekeepers, while the rest of the timekeepers' income gets posted to the All Other income account. The All Other row makes it possible so that each individual timekeeper does not have to be added to the table in order for GLS Integration to occur for that timekeeper.

The first two columns in the table are determined by the Primary and Secondary posting method specified on the Configure Payment Integration window for Payments Allocated to Fees. The table also includes a Debit Account, Credit Account and Journal column. (Note: If Single Debit/Credit is selected for the Primary posting method, this window will not be displayed; instead the Assign GLS Accounts window will be opened directly.)

The columns may consist of the following, depending on the posting method:

Client Category Category number followed by category name. AO (All Other) represents where journal entries will be posted when a specific category is not included in the table.
Client Location Location ID followed by location name. AO (All Other) represents where journal entries will be posted when a specific location is not included in the table or a specific location is not defined for the client.
Payment Tcode Tcode number followed by tcode description. AO (All Other) optionally represents where journal entries will be posted when a specific tcode is not included in the table.

Note: If Payment Tcode is the Primary posting method and None is the Secondary posting method, 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, not all fields are required. The Debit Account, Credit Account, and/or Journal fields can be left blank. When a payment that applies to fees is saved and any of these fields are blank, the GLS Integration window will be displayed, thus allowing the user to specify the missing information at the time of data entry (provided the user has Detail Payment GLS View access rights).

Primary Timekeeper Timekeeper number followed by timekeeper name. AO (All Other) represents where journal entries will be posted when a specific timekeeper is not included in the table.
Secondary Timekeeper Timekeeper number followed by timekeeper name. AO (All Other) represents where journal entries will be posted when a specific timekeeper is not included in the table.
Originating Timekeeper Timekeeper number followed by timekeeper name. AO (All Other) represents where journal entries will be posted when a specific timekeeper is not included in the table.
Working Timekeeper number followed by timekeeper name. AO (All Other) represents where journal entries will be posted when a specific timekeeper is not included in the table. Firm indicates where journal entries will be posted when payments are allocated to the firm.

Note: If the Include Fee Compensation amounts in posting check box is selected, the Firm mapping indicates where journal entries will be posted when payments are allocated to the firm due to Fee Compensation Rules that are defined.

If the Include Fee Compensation amounts in posting check box is cleared, the Firm mapping will not apply.

Debit Account The GLS Debit Account # and Account Name.
Credit Account The GLS Credit Account # and Account Name.
Journal The GLS Journal # and Journal Name. The Journal # will be used for both the debit and credit journal entries for the item.

The New button can be used to add a new GLS Integration mapping. An Assign GLS Accounts window will be displayed allowing you to define a new mapping.

The Edit button or double-clicking a row can be used to edit the highlighted GLS Integration mapping. An Assign GLS Accounts window will be opened with the information for the selected mapping.

The Delete button can be used to delete the highlighted mapping from the table. Only one mapping can be deleted at a time using this button.

The Clear All button can be used to clear all GLS Integration mappings in the table.

The OK button can be used to close the GLS Accounts Table window. Any changes to the table will be saved.

The Cancel button can be used to close the GLS Accounts Table window without saving any changes to the table.

You can change the sorting order of the mappings by clicking a column heading. An ascending sort indicator will be shown in the column heading indicating the sorting order. Clicking the same column heading again will reverse the sort order and change the sort indicator to a descending sort indicator.

See also:   Overview of GLS Integration for Payments
  When Journal Entries are Created for Tabs3 Payments
  Configure Payment Integration
  Posting Methods