Tabs3 can create GLS journal entries for cost entries that are merged if the two systems are integrated and the Import Cost Totals Only check box has been selected.

If you are integrated with GLS and have cleared the Import Cost Totals Only check box, then journal entries are not created because of the excessive number of GLS journal entries that would be generated. However, you can print a Transaction File List to obtain summarized totals for any desired transaction code and date range. Journal entries for these totals can be posted manually to GLS at any time you desire (i.e., daily, weekly, monthly).

If you are integrated with GLS and have selected the Import Cost Totals Only check box, then Tabs3 will automatically create journal entries in GLS. However, journal entries will only be created if the transaction code used is configured to integrate with GLS and has both debit and credit general ledger account numbers configured. If the transaction code is configured to integrate with GLS but only one or neither of the general ledger account numbers are configured, then an error will be generated. Likewise, if the transaction code is configured to integrate with GLS but a journal number is not configured, then an error will be generated.

When merging entries into Tabs3, one-sided journal entries cannot be posted. They can only be posted in pairs. Tabs3 will create and post zero amount journal entries for cost transactions with amounts of zero. A new set of journal entries is created when either the Client ID or transaction code number changes.

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

GLS FIELD SOURCE
Trans # Automatically assigned by GLS.
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 transaction code description.
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.
User ID User ID running the merge program.
Date Entered System Date when the merge program is run.

See also:   GLS Error Codes