Tabs3 Billing can create GL journal entries for cost entries that are merged if the two applications are integrated. If you are not integrated with GL, journal entries will not be created; however, you can print a Transaction File List to obtain summarized totals for any desired transaction code and date range. These totals can be posted manually to your GL journal file at any time you desire (i.e., daily, weekly, monthly).

If you are integrated with GL, then Tabs3 Billing will automatically create journal entries in GL. However, journal entries will only be created if the transaction code is configured to integrate with GL and has both debit and credit general ledger account numbers configured. If the transaction code is configured to integrate with GL but only one or neither of the general ledger account numbers are entered in the transaction code file, then an error will be generated.

When merging entries into Tabs3 Billing, one-sided journal entries cannot be posted. They can only be posted in pairs.

Tabs3 Billing will create and post zero amount journal entries for cost transactions with amounts of zero.

Tabs3 Billing Remote Note: Tabs3 Billing will not create journal entries for transactions with Save in the Status field. Payment entries cannot be merged from Tabs3 Billing Remote.

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

GL FIELD SOURCE
Trans # Automatically assigned by GL.
Date Date field from the cost or payment transaction.
Account The GL Accounts Table for Expense & Advance Cost Entries.
Debit/Credit The Amount field from the cost or payment transaction.
Description The first 120 characters of the transaction code description.
Check # 0.
Jrnl The GL 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:   GL Error Codes