---
title: "Diagnosing General Ledger System Errors"
slug: "diagnosing-general-ledger-system-errors"
updated: 2026-04-30T20:30:10Z
published: 2026-05-26T15:59:12Z
canonical: "help.idibilling.com/diagnosing-general-ledger-system-errors"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Diagnosing General Ledger System Errors

Two core General Ledger (GL) reports facilitate identifying the specific transactions associated to a GL system error journal entry. A GL system error is the condition where the GL posting process generated journal entries for a specific transaction, but the sum of the entry’s debits do not equal the sum of the credits. When this imbalance occurs, the GL process identifies the unaccounted amounts as a system error and posts them to a specific GL Account.

The purpose of these reports is to significantly reduce the time needed to research and identify the transaction(s) associated to a Gl system error. These are grid reports and are located in the Finance > General Ledger folder in Report Explorer:

- General Ledger System Error Audit Summary
- General Ledger System Error Audit Detail

The reports let you compare GL system error journal entries with the transactions in a specified date range. The amount of the GL system error will correlate to one or more transactions in the reports.

The reports are deployed as *standalone* in Reports Explorer (no need to drill down from another report) and can be run as needed according to the supported setup parameters. Each column can be used to filter and/or sort the report results. A *Totals* row is provided for applicable columns. The reports do not apply/enforce any Market-specific *User Limit To* concerning the setup criteria or presentation of displayed information.

## General Ledger System Error Audit Summary Report

This report provides a row for each transaction/activity that has incurred a General Ledger system error as described above.

### Parameters

| **Name** | **Required** | **Default Value** | **Details** |
| --- | --- | --- | --- |
| From Date | Yes | Nore | Date range cannot exceed 45 days. > [!NOTE] > **Note**: > > The larger the date range, the longer the report will take to run. |
| To Date | Yes | None |

### Columns

| **Name** | **Description** |
| --- | --- |
| Transaction Date | Date transaction/activity was created. |
| Transaction Type | Type of CostGuard transaction. For example, *POS transaction*. |
| Transaction ID | Unique ID of the transaction/activity. For example, for a POS transaction this value is the POS Receipt Number. |
| Description | Description of the transaction/activity. For example, a POS transaction can be a Sale, Exchange, or Return. |
| Account Number | IDI platform account number associated to the transaction/activity. |
| Posted Date | Date the transaction/activity was posted in the General Ledger. |
| Transaction Debit | Sum of the debit amounts from the transaction’s posted journal entries. |
| Transaction Credit | Sum of the credit amounts from the transaction’s posted journal entries. |
| Transaction Balance | Value resulting from *Transaction Debit amount* minus *Transaction Credit amount*. |
| Transaction Balance Rule | This column displays one of the following values: **DR** when the transaction balance is the result of the Transaction Debit amount greater than Transaction Credit amount **CR** when the transaction balance is the result of the Transaction Debit amount less than Transaction Credit amount > [!NOTE] > **Note:** > > The specific system error will be posted as either a debit or credit amount for the amount(s) that were not able to be posted. |

## General Ledger System Error Audit Detail Report

This report provides a row for each journal entry of each transaction/activity and indicates whether or not it has incurred a General Ledger system error. Using this report, you can see which specific entries were correctly posted to identify those that were missing (and were replaced by the GL system error (debit amounts DO NOT EQUAL the sum of the posted credit Amounts).

### Parameters

| **Name** | **Required** | **Default Value** | **Details** |
| --- | --- | --- | --- |
| From Date | Yes | None | Date range cannot exceed 45 days. > [!NOTE] > **Note**: > > The larger the date range, the longer the report will take to run. |
| To Date | Yes | None |
| Include Balanced Transactions? | No | No | Optional checkbox specifies if the report will display balanced transactions in addition to unbalanced ones. > [!NOTE] > **Note:** > > This report will produce a significant number of results when the balanced transactions are included. |

### Columns

| **Name** | **Description** |
| --- | --- |
| Transaction Type | Type of transaction. For example, *POS transaction*. |
| Transaction ID | Unique ID of the transaction/activity. For example, for a POS transaction this value is the POS Receipt Number. |
| Description | Description of the transaction/activity. For example, a POS transaction can be a Sale, Exchange, or Return. |
| Transaction Date | Date transaction/activity was created. |
| GL Category | Asset, Liability, Revenue, etc. |
| GL Account Code | Unique code representing the General Ledger account |
| GL Account Description | Description of the GL account code. |
| Rule | Indicates if the displayed entry is a Credit (CR) or a Debit (DR). |
| Debit | Dollar amount debited. |
| Credit | Dollar amount credited. |
| Posted Date | Date the transaction/activity was posted in the General Ledger. |
| Transaction Debit | Sum of the debit amounts from the transaction’s posted journal entries. |
| Transaction Credit | Sum of the credit amounts from the transaction’s posted journal entries. |
| Transaction Balance | Absolute value resulting from *Transaction Debit amount* minus *Transaction Credit amount*. |
| Transaction Balance Rule | This column displays one of the following values: **DR** when the transaction balance is the result of the Transaction Debit amount greater than Transaction Credit amount **CR** when the transaction balance is the result of the Transaction Debit amount less than Transaction Credit amount > [!NOTE] > **Note:** > > The specific system error will be posted as either a debit or credit amount for the amount(s) that were not able to be posted. |