Force balancing in banking is a manual accounting workaround: when a bank’s general ledger doesn’t match the sub-ledgers feeding into it and the reporting deadline is about to hit, the operations team posts a journal entry for the exact amount of the discrepancy and parks it in a suspense account. The books balance on paper. The underlying cause stays unexplained. That gap between appearance and reality is why regulators, auditors, and forensic accountants treat every forced entry as something worth a second look.
How the Entry Actually Gets Made
Every large bank keeps a general ledger as the master record of its financial position. Feeding into it are subsidiary ledgers that track detail for specific areas like customer deposits, loan portfolios, or trading desks. At the close of each business day or reporting period, the totals from each sub-ledger should roll up and tie to the matching control account in the general ledger. When they don’t, the bank is out of balance.
In a normal workflow, the reconciliation team traces the mismatch to its source: a duplicate posting, a failed batch upload, a timing delay between systems. When the deadline is minutes away and the root cause hasn’t been found, some institutions force balance instead. An operations team member creates a manual journal entry for the exact dollar amount of the gap and posts it directly to the general ledger. The numbers now match. Nothing has actually been fixed.
The forced entry just moves the problem. Instead of an unbalanced ledger that can’t be published, the bank has a balanced ledger that contains an unexplained adjustment. The real investigation still has to happen after the deadline passes, and this is where things often go sideways: once the pressure is off, the follow-up slips.
Where the Money Sits: Suspense Accountsh2>
The forced entry has to land somewhere, and that place is a suspense account. A suspense account is a temporary holding account for items that can’t yet be classified into their correct permanent account. Banks use these accounts for all kinds of unresolved items, not only force balances.
When operations force balances a ledger, it debits or credits the suspense account for the exact discrepancy. The general ledger control account now ties to the sub-ledger total, and the open item sits in suspense. Suspense accounts are not customer-facing and don’t appear in the balances most managers review daily, which is precisely what makes them attractive hiding places for errors and, in the worst cases, fraud.
Federal banking examiners are trained to look specifically at suspense account activity. The FFIEC’s examination guidance requires banks to reconcile these accounts frequently using someone independent from the transactions, maintain full transaction records, and establish a timely process for resolving discrepancies.
Why Banks Resort to It
The short answer is deadlines. Daily call reports, period-end financial statements, and filings with the Federal Reserve and OCC all have hard cutoffs. Publishing an unbalanced ledger would signal a breakdown in the bank’s accounting infrastructure and could trigger immediate supervisory concern.
The underlying causes of imbalances vary: system migrations, software glitches, failed batch processing, manual keying errors, and timing mismatches between systems that settle at different hours. In an institution processing millions of transactions a day, even a tiny error rate produces a meaningful number of mismatches.
A well-run bank treats every force balance as an emergency procedure. The entry is supposed to be temporary, the investigation should begin immediately, and the suspense balance should clear within days. Once force balancing starts feeling routine, the urgency around follow-up fades. That drift is the pattern regulators watch most closely.
How It Opens the Door to Fraud
Force balancing creates an opening for fraud precisely because it bypasses the automated controls that catch unauthorized transactions. In a normal workflow, every dollar entering the general ledger has a traceable path from a specific transaction in a sub-ledger. A force balance breaks that chain. The entry exists because a person decided it should, not because a transaction generated it.
The classic scheme: someone diverts funds, then uses a forced entry or suspense posting to cover the resulting gap. Because suspense accounts carry high volumes of legitimate temporary items, a fraudulent entry can blend in. To keep the item from aging out and attracting attention, the person periodically moves it between suspense accounts or re-dates it, a technique forensic accountants call re-aging. The longer the item sits, the harder it becomes to trace to its origin.
This is exactly why the PCAOB’s auditing standard on fraud, AS 2401, requires auditors to specifically target journal entries recorded at the end of a reporting period with little or no explanation, made by people who don’t normally make journal entries, or posted to unusual or seldom-used accounts. Force-balanced entries check several of those boxes by nature.
Controls Banks Are Expected to Have
Banks that use force balancing are expected to surround the practice with tight controls. The FFIEC examination guidance for concentration and suspense accounts sets the baseline: dual signatures on general ledger tickets, frequent independent reconciliation, full retention of transaction and identifying information, and a defined process for timely discrepancy resolution.
Most institutions layer additional controls on top of that baseline:
- Management authorization. The forced entry typically requires sign-off from a senior operations manager or controller before it can be posted, and that approver is personally accountable for the override.
- Documentation. Every forced entry must capture the dollar amount, the accounts affected, the reason the automated reconciliation failed, and the expected timeline for resolution.
- Aging limits. Internal policy sets a maximum number of days a forced entry can sit in a suspense account before it escalates. The OCC’s guidance on problem bank supervision states that activity flowing through suspense accounts should clear in a relatively short time period and directs examiners to sample aged items.
- Independent review. Someone outside operations, usually internal audit, periodically reviews all open suspense items and the adequacy of the investigation efforts.
Regulators view the absence of controls around manual overrides as a deficient practice, meaning one that deviates from sound governance, internal control, or risk management principles and could adversely affect the bank’s condition if left unaddressed.
What Regulators Do When They Find It
When examiners find that force balancing is frequent, poorly documented, or producing aged suspense items that nobody is resolving, the consequences escalate quickly. The OCC communicates concerns about deficient practices through Matters Requiring Attention, or MRAs. An MRA is not a suggestion. It identifies the deficient practice, explains the potential consequences of inaction, and requires the bank to commit to a specific corrective action plan with milestones and accountability.
The Federal Reserve uses a parallel framework. Its SR 13-13 guidance defines Matters Requiring Attention as issues that are important and that the Fed expects the bank to address over a reasonable period of time. For more severe problems, the Fed escalates to Matters Requiring Immediate Attention, or MRIAs, which cover situations posing significant risk to the safety and soundness of the banking organization or representing significant noncompliance with applicable laws or regulations.
A pattern of unresolved force balances can land in either category depending on scale. A handful of well-documented forced entries with fast resolution times might draw a recommendation. Hundreds of aged items with thin documentation and no clear investigation trail could trigger an MRIA or a formal enforcement action. The volume and aging of suspense items is one of the most direct measurements examiners use to gauge whether a bank’s operational controls actually work.
Audit and Sarbanes-Oxley Exposure
For publicly traded banks, force balancing creates a specific problem under Sarbanes-Oxley. Section 404 requires management to assess and report annually on the effectiveness of its internal controls over financial reporting. A force balance, by definition, is a workaround that bypasses the bank’s standard automated controls. If external auditors find that force balancing is frequent or that the surrounding controls are weak, they may conclude a material weakness exists in the internal control environment.
The PCAOB’s guidance on journal entry testing puts force-balanced entries squarely in the auditor’s crosshairs. AS 2401 requires auditors to design procedures specifically addressing the risk of management override of controls, including testing specific entries with the characteristics most associated with fraud: end-of-period timing, lack of explanation, posting to unusual accounts, and entries made by people outside the normal workflow.
A bank that relies heavily on force balancing is essentially telling its auditors that its automated reconciliation process regularly fails. That invites deeper testing, larger sample sizes, and harder questions about whether the financial statements are materially accurate. Audit costs rise, but the real exposure is a qualified opinion or an adverse finding on internal controls, either of which can rattle investors and bring additional regulatory attention.
When It Triggers a SAR Filing
If the investigation into a forced entry uncovers evidence that the underlying discrepancy involves illegal activity, money laundering, or a transaction with no apparent lawful purpose, the bank has an obligation to file a Suspicious Activity Report with the Financial Crimes Enforcement Network. Federal regulations require a SAR for any transaction or pattern of transactions involving $5,000 or more where the bank knows, suspects, or has reason to suspect that the funds derive from illegal activity, that the transaction is designed to evade Bank Secrecy Act requirements, or that the transaction has no business or apparent lawful purpose.
The filing deadline is tight. A SAR must be filed within 30 calendar days of the bank first detecting facts that may warrant a report. If no suspect has been identified by that point, the bank gets an additional 30 days to try to identify one, but reporting cannot be delayed beyond 60 days from initial detection. For force-balanced entries that sit in suspense for weeks before anyone investigates, the clock may already be running by the time the investigation begins. Letting aged suspense items pile up without investigation risks blowing past SAR filing deadlines, which is itself a regulatory violation.
Force Balance vs. a Normal Correcting Entry
Not every manual journal entry is a force balance, and the distinction matters. Routine adjustments happen constantly in bank accounting. An accountant might post a correcting entry to fix a miscoded transaction, record an accrual at month-end, or reclassify an item between accounts. These entries have a known cause, a clear audit trail, and they resolve the underlying issue at the time of posting.
A force balance is different because the cause is unknown at the moment the entry is made. The whole point is to close the books before the root cause has been identified. If the cause were known, the team would post a correcting entry to the right account instead of parking the difference in suspense. That’s why auditors pay attention to the ratio of explained versus unexplained adjustments. A bank with a high volume of well-documented correcting entries has an active reconciliation process. A bank with a high volume of entries posted to suspense accounts at the close of business with minimal documentation has a force-balancing habit, and that is a fundamentally different risk profile.