There are two types of issues reported in the GLS Error Report: Errors and Warnings.

Errors

GLS error codes that can be received during posting are listed below. If any of these errors are detected for any item when Tabs3 attempts to post GLS journal entries, the journal entries are not created. If a GLS posting error is encountered when updating statements, the statement is updated but the journal entries are not created.

All errors are shown on a report. These entries need to be entered manually in GLS. The GLS reject codes are listed below:

Code Description of Error
10 GLS Account not found (an invalid GLS account is present in GLS Integration Setup)
11 Unassigned Account (blank GLS account is present in GLS Integration Setup)
20 Unbalanced Debit/Credit Accounts
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

Warnings

Warnings that can be received during posting are listed below. Some warnings indicate that journal entries could not be posted, while other warnings indicate that journal entries were posted but may need to be reviewed.

The following warnings indicate that journal entries could not be posted:

*** WARNING: Adjusting entries could not be completed because a Tcode was not mapped ***

It is possible to have payments integrated to GLS as unapplied, but not be able to create adjusting journal entries because GLS journal entries are not mapped for the transaction code used for the payment. The "Adjusting entries could not be completed because a Tcode was not mapped" warning will be displayed on the GLS Error Report when this occurs. If the payment does not need to be integrated, there are no changes that need to be made. However, if adjusting entries should be created, these entries must be made manually. Additionally, the Tcode used for the payment must be configured in GLS Integration Setup so that this warning is not encountered again.

 

*** WARNING: Client Funds entries may need manual adjustment ***

When Client Funds transactions have integrated to GLS, but Tabs3 is unable to adjust them when updating, undoing, or adjusting statements, the "Client Funds entries may need manual adjustment" warning will be displayed on the GLS Error Report. If the adjustments to the payment do not need to be integrated, there are no changes that need to be made. However, if adjusting entries should be created, manual journal entries must be created in GLS.

 

*** WARNING: Partial integration of Automatic Client Funds Payment ***

This warning is displayed when Client Funds integration has been set up via GLS Integration Setup, the client's Fund Application is set up for Automatic, and the Client Funds Automatic Payment Tcodes are not set up in Customization. In this case, when a Client Funds Automatic Payment is processed, the GLS journal entries for the Client Funds transaction are created, but journal entries for the automatic payment entry are not created. Journal entries for the payment entry must be created manually. Additionally, the Automatic Payment Tcodes must be configured in Customization so that this warning is not encountered again.

The following warnings indicate that journal entries were posted, but further review may be necessary:

*** 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: Adjusting entries posted for a cleared transaction ***

This warning is displayed when the original journal entry has a status of Cleared. You may need to review the newly posted journal entries in GLS to determine if they should be marked as reconciled now or at a later date.

 

*** WARNING: Adjusting entries posted for a reconciled transaction ***

This warning is displayed when the original journal entry has a status of Reconciled. You may need to review the newly posted journal entries in GLS to determine if they should be marked as reconciled now or at a later date.

 

*** WARNING: Adjusting entries posted for a deposited transaction ***

This warning is displayed when the original journal entry has a status of Deposited. You may need to review the newly posted journal entries in GLS to determine if they should be marked as reconciled now or at a later date.

 

*** 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.

Note: The Client # field on the GLS Error Report corresponds to the Reference field for the GLS journal entries related to the error.