If an error is encountered in a transaction, the rejected transaction is not merged into Tabs3. (Note: As an exception, a transaction with an error code of 35, 36, or 37 is merged as indicated.) Since each transaction that is successfully merged is marked as such, you can either resolve the reason for any rejected transaction and then re-merge; or, you can manually reenter any rejected transaction in Tabs3. For example, if a transaction was rejected because the client does not exist in Tabs3, you may want to consider adding the client in Tabs3 and then re-merging the files. When re-merging the files, the transactions that were successfully merged originally will not be merged again.

The Tabs3 error codes that can be received during the merge are listed below:

Code Description of Error/Warning
10 Client Not Found in Tabs3 client file or Secure Client. Indicates the client does not exist in the main Tabs3 data files or the client is a secure client and the user performing the merge does not have access to that client.
15 Inactive Client. Indicates the client in Tabs3 is set to an Inactive status.
20 Timekeeper Not Found in Tabs3 timekeeper file. Indicates the timekeeper does not exist in the main Tabs3 data files.
30

Invalid Tabs3 Transaction Code. Indicates the Transaction Code is invalid. This error can occur for any of the following reasons:

  • A fee transaction code was used to make a cost transaction.
  • A positive amount was entered for a transaction with a finance charge credit transaction code (Type 9).
  • A Type 6 (progress fee) transaction was entered for a non-billable client.
  • A task based billing transaction was entered for a non-task based billing client.
  • The transaction code does not exist in the Tabs3 transaction code file.
  • A payment transaction code (Type 1, 2 or 3) was used. Payment transactions cannot be merged.
31 Invalid Task Based Billing Code. Indicates the Task Based Billing Code specified is invalid.
35 Amount or Hour for a Description Only Transaction. Indicates that a Type 4 (description only) transaction has a non-zero Amount or Hours field. This transaction is merged with 0 in the Amount and Hours fields.
36 Hour for a Progress Fee Transaction. Indicates that a Type 6 (progress fee) transaction has a non-zero Hours field. This transaction is merged with 0 in the Hours field.
37 Task Based Billing Code Not Provided. Indicates a transaction was merged with a transaction code for a task based billing client. Transactions for task based billing clients require a task based billing code instead of a transaction code. The merged transaction must be edited in Tabs3. If this error is not fixed, the next time the Data File Integrity Check is run in Tabs3, it will report an error 81. Editing can be accomplished by using the appropriate file or by using the Change WIP Transactions program to change the tcode to a valid task based billing code. If the client was set up as a Task Based Billing Client by mistake, clearing the client's Task Based Billing Client check box will resolve the problem. If the transaction was entered for the wrong client, you can use the Transfer Transactions program to move the transaction to the correct client. If applicable, GLS journal entries were also created and merged using the GLS accounts assigned to the transaction code.
40 Category Not Found in Tabs3 category file. Indicates the category does not exist in the main Tabs3 data files.
60 Fee Hours To Bill are too large. Indicates that the Hours to Bill field being imported is greater than 9,999.99 or less than -999.99.
61 Fee Hours Worked are too large. Indicates that the Hours Worked field being imported is greater than 9,999.99 or less than -999.99.
62 Fee Rate is too large. Indicates that the Rate field being imported is greater than 9,999.99.
63 Fee Amount is too large. Indicates that the Amount field being imported is greater than 9,999,999.99 or less than -999,999.99.
65 Cost Units are too large. Indicates that the Units field being imported is greater than 99,999.99 or less than -9,999.99.
66 Cost Rate is too large. Indicates that the Rate field being imported is greater than 9,999.999.
67 Cost Amount is too large. Indicates that the Amount field being imported is greater than 9,999,999.99 or less than -999,999.99.

Key Type Mismatch If the Tabs3 Key Type does not match the Key Type in the import data, the error report will include a message indicating a Key Type mismatch. In this situation, no data will be merged into Tabs3. The Key Types must match in order for the data to be imported.

GLS Error Codes

If an error is encountered when Tabs3 Billing attempts to create General Ledger journal entries, the transaction is merged into Tabs3 Billing but the GLS journal entries are not created. These journal entries need to be entered manually in GLS. The GLS reject codes are listed below:

Code Description of Error/Warning
10 GLS Account not found (an invalid GLS account is present in GLS Integration Setup)
11 Unassigned GLS account (blank GLS account is present in GLS Integration Setup)
20 Unbalanced Debit/Credit mappings
21 Tabs3 amount and GLS Journal Entries amount do not match
30 Invalid GLS journal
40 Date for GLS journal entry out of valid range

GLS Warnings

Warnings that can be received during posting are listed below. Warnings indicate that GLS journal entries were posted but may need to be reviewed.

*** WARNING: The following entry was posted using today's date ***

This warning is displayed when journal entries are posted with a date prior to the Date through which books are closed specified in the GLS Date Restrictions.

 

*** WARNING: This entry was posted beyond the Date Restrictions ***

This warning is displayed when journal entries are posted with a date outside of the Restrict Journal Entries to xxx Days in the Future or Restrict Journal Entries to xxx Days in the Past specified in the GLS Date Restrictions.

 

*** WARNING: The following entry was posted into a prior year ***

This warning is displayed when journal entries are posted with a date prior to the current year.

 

*** WARNING: The following entry was posted to an inactive account ***

This warning is displayed when journal entries are posted to an inactive GLS Account.

 

Note: Only one type of warning will be displayed for each journal entry posted. The warnings listed above are listed in order of priority. For example, if warnings for both "posted using today's date" and "posted to a prior year" are encountered, only the warning for an entry posted using today's date will be displayed for that journal entry.