DBD: GL Imbalance Prevention & Resolution Guide

Section 1: Common Causes of GL Imbalance

Understanding these root causes helps accounting teams proactively avoid imbalances before running period-end processes.

1.1 Interrupted or Double-Posted Journal Updates

This is the most common cause of significant ledger variances. If a network connection drops, a session times out, or a user is disconnected during a major batch update (such as a Sales Journal, Purchase Journal, or G/L Transaction Register run), the system may partially or fully double-post the journal entries.

• Symptom: G/L account balances are exactly doubled for invoices within a specific audit control number. The G/L Detail Transaction Register (U-1) shows identical invoices posted twice.
• Real-World Impact: A network disruption during a Sales Journal update can cause thousands of dollars in doubled entries across dozens of records, requiring table corrections across multiple background data files (GL6 , AR6 , AR7 , ARK , ARL ).

Prevention:

• Verify Network Stability: Ensure a stable, hardwired network connection before running any Print & Update operation. Avoid running critical ledger updates over unstable Wi-Fi or questionable VPN connections.
• Do Not Re-Run Failed Updates: If you are disconnected or kicked out mid-update, do not attempt to re-run the process. Immediately check the first invoice in the batch. If the amount is doubled, stop and contact Support before taking further action.
• Time Your Batches: Run exceptionally large batch updates during off-peak hours when overall network traffic is low.

Resolution:

• This scenario requires technical Support to safely isolate and extract the duplicated records across background files. Do not attempt manual adjustments or journal entries to fix a double-post.

1.2 Cross-Period Posting Errors

This occurs when related sides of an accounting transaction (such as a vendor refund and its corresponding A/P entries) are split across different accounting periods, preventing the Accounts Payable ledger from tying to the Trial Balance.

• Symptom: The A/P Trial Balance does not match the A/P G/L account. The variance matches the exact dollar amount of a transaction that was partially posted in one period and finalized in another.
• Real-World Impact: Entering an A/P invoice at the tail end of one fiscal period but posting the corresponding cash disbursement in the subsequent period creates an immediate A/P imbalance that blocks year-end closing routines.

Prevention:

• Align Accounting Periods: When processing vendor refunds, credit memos, or cross-ledger adjustments, double-check that all related transaction components are coded to the exact same accounting period.
• Follow Prescribed Procedures: Follow documented vendor refund workflows precisely—never substitute standard debit memos for the prescribed process.
• Pre-Close Verification: Before closing out any accounting period, run a diagnostic check to verify that all components of active refunds or adjustments have been fully posted.

Resolution:

To move the misposted entry into the correct period, choose one of the following methods:

• Option A (Journal Entry): Generate a reversing G/L journal entry (e.g., debit Cash / credit A/P in the earlier period, then reverse that entry in the subsequent period).
• Option B (Purchase Journal Adjustment): If the target A/P period is still open, enter an offsetting Purchase Journal entry (negative value in the incorrect period, positive value in the correct period), then print and update.

1.3 LOT Unit of Measure with Split Shipping

A known system behavior where utilizing a LOT/1 unit of measure structure combined with specialized split shipping causes the A/P G/L distribution to double.

• Symptom: The A/P G/L distribution doubles specifically for orders utilizing a LOT Unit of Measure across multiple ship-to locations. This frequently leaves small rounding variances (such as $.01 ) that steadily accumulate across multiple purchase orders.

Prevention:

• Manual Review: When using a LOT unit of measure alongside split shipping destinations, manually review and adjust the A/P G/L distribution lines while entering the vendor invoice.
• Alternative UOM: Consider utilizing an alternative unit of measure structure if split shipping configurations are consistently required for that specific product or order type.

Resolution:

• Modify the G/L distribution fields directly on the A/P invoice entry screen to strip out the duplicated variance. For accumulated historical penny variances, adjust the balance directly via a standard G/L journal entry.

1.4 AR Subledger vs. GL Discrepancies

Phantom or orphaned transactions appearing in the A/R subledger (such as unexplained opening balances) can cause the A/R Trial Balance to drift out of alignment with the A/R General Ledger control account.

• Symptom: An invoice or unexpected amount appears in the A/R Trial Balance as an "Opening Balance" that was completely absent when the prior period was closed. The A/R Trial Balance total no longer matches the A/R G/L account.
• Prevention: Always compare the A/R Trial Balance directly against the A/R G/L account at the close of every period. If a new, unexplained opening balance layout appears, investigate it immediately—do not carry it forward into future periods.
• Resolution: Contact Support to evaluate and zero out the orphaned subledger transaction record. Once corrected, reprint your balancing reports and proceed with the update.

1.5 Duplicate GL Distribution on Sales Journal

The system can occasionally generate duplicate G/L distribution lines internally within a Sales Journal batch, causing the U-1 report to fall out of balance.

• Symptom: The G/L Detail Transaction Register explicitly shows an individual invoice's G/L distribution posted twice under the exact same audit control number.
• Prevention: Always print and thoroughly review the G/L Detail Transaction Register (U-1) before confirming any updates. Scan specifically for duplicate line items repeating under an identical audit control number. If the U-1 report lists an active imbalance, stop and do not execute the update.
• Resolution: Contact Support to extract the duplicate record strings directly from the underlying GL6  file. You can safely reprint and process your update after the fix is applied.

Section 2: Interrupted Sessions & Data Mismatches

When standard operations are abruptly cut off, background reporting tables can occasionally drift out of sync with your live viewing screens.

2.1 Orphaned Records from Check Reconciliation

Residual tracking lines can occasionally remain in the G/L after a check reconciliation execution fails to fully purge background staging entries.

• Symptom: The G/L displays a clear imbalance tied directly to a specific audit control number. However, when you run the corresponding audit report, the transaction is marked explicitly as "matched and cleared," yet the G/L balance continues to carry the weight of the transaction, blocking your month-end closeout.
• Prevention: Always allow the check reconciliation update utility to finish its archival cycle completely before navigating away from the screen or closing the terminal session.
• Resolution: Contact Support to run an integrity validation check. Technicians will isolate and drop the orphaned records from the G/L tables (typically the FIDO file) without disrupting your cleared check history.

Section 3: Reconciliation Controls (Period-End)

Execute these core validation checkpoints every single accounting period before running your final Period End Processing routines.

Section 4: Diagnostic Reporting & Navigation Lookup

When investigating a ledger variance, use the following application paths and reports in sequence to quickly isolate the broken transaction or period mismatch.

4.1 Sub-Ledger Tying Tools

• Accounts Payable (A/P) Verification: Compare your A/P Aged Trial Balance (AP > AP Reports > Trial Balance) against your designated Accounts Payable G/L liability accounts. Verify that all Purchases Journals and Disbursements Journals have been fully printed and updated for the period.
• Accounts Receivable (A/R) Verification: Compare your A/R Aged Trial Balance (AR > AR Reports > Trial Balance) against your designated Accounts Receivable G/L asset accounts. Verify that all Sales Journals and Cash Receipts Journals have been fully printed and updated for the period.

💡 Note: Unposted sub-ledger journals are the number one cause of temporary balance discrepancies between sub-ledgers and the Trial Balance. Use Journal History Inquiry (GL > Journal History Inquiry) to check historical postings.

4.2 G/L Detail and Control Audit

• G/L Account Analysis / General Ledger Report: Run this specifically for your suspected variance accounts (e.g., Accounts Payable, Accounts Receivable, Unbilled Costs, or Inventory) via GL > GL Reports > Transaction Detail Report (U-1) or GL Trial Balance (GL > GL Reports > Trial Balance). Scan the output for consecutive, identical line items carrying the exact same dollar amount and transaction date.
• Purchases & Sales Journal History Registers: Cross-reference these registers against your transaction posting dates. Scan the Purchases Journal for vendor credit memos or refunds, and scan the Sales Journal for customer invoices or credits where the transaction date falls in one period but the applied accounting period was inadvertently locked into another.

Section 5: When to Contact Support

Contact Support immediately if:

• You experience a hardware or session disconnection during any live Print & Update operation.
• The G/L Detail Transaction Register (U-1) explicitly shows an imbalance and you cannot find an unposted subledger journal.
• You discover duplicated line records sharing an identical audit control number.
• An unexplained opening balance layout suddenly appears in a subledger that wasn't present at the prior month's close.
• You identify an active balance in the G/L for a batch that your reporting flags register as cleared.
• You suspect active data file structural errors within files like GL6 , AR6 , AR7 , ARK , ARL , or FIDO .

Do NOT under any circumstances attempt to:

1. Re-run an update process that was interrupted mid-stream.
2. Manually edit or force overrides on background system data files.
3. Force-update or close a period using a report that contains an active imbalance flag.