Force balancing in banking is a manual accounting workaround: an operations team posts a journal entry to make the general ledger match its sub-ledgers when the cause of a mismatch hasn’t been found yet, parking the unexplained difference in a temporary suspense account so the bank can meet its reporting deadline. The books look balanced. The underlying problem isn’t solved, just moved. Regulators and auditors treat every forced entry as a red flag worth investigating, because the same mechanic that closes an honest gap can also hide a fraudulent one.
How the Entry Works
Every large bank keeps a general ledger, the master record of its financial position, and a set of subsidiary ledgers underneath it that track detail for specific areas like customer deposits, loan portfolios, and trading desks. At the end of each business day or reporting period, the totals from each sub-ledger should roll up cleanly into the corresponding control account in the general ledger. When they don’t, the bank has an out-of-balance condition.
Normally, reconciliation staff trace the mismatch to its source: a duplicate posting, a failed batch upload, a timing delay between systems. When the deadline is hours or minutes away and the cause still hasn’t been found, some institutions force balance instead. The team creates a manual journal entry for the exact amount of the discrepancy and posts it directly to the general ledger. The numbers now match on paper, but nothing has been explained.
The forced entry doesn’t fix anything. It shifts an unsolved problem from one place, an unbalanced ledger that can’t be published, to another, a balanced ledger containing an unexplained adjustment. The real investigation still has to happen after the deadline passes, and in practice that follow-up often slips.
Where the Money Lands: Suspense Accounts
The forced entry needs somewhere to sit, 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 across many operational areas, not only for force balancing.
When staff force-balance a ledger, they debit or credit the suspense account for the exact discrepancy. The general ledger control now ties to the sub-ledger total, and the suspense account carries the open item. On the surface, everything reconciles. Underneath, the suspense account is accumulating items that still need resolution.
Suspense accounts are designed to be invisible in normal financial reporting. They don’t appear as customer-facing balances or as line items most managers review daily. That makes them attractive hiding places for errors and, in bad cases, fraud. Federal examiners are trained to look specifically at suspense account activity. FFIEC examination guidance requires banks to reconcile these accounts frequently using someone independent from the transactions, keep full transaction records, and maintain a timely process for resolving discrepancies.
Why Banks Do It
The short answer is deadlines. Banks operate under strict regulatory reporting schedules. Daily call reports, period-end financial statements, and filings with the Federal Reserve and OCC all have hard cutoffs. Publishing an unbalanced ledger isn’t an option; it would signal a breakdown in the accounting infrastructure and could trigger immediate supervisory concern.
The underlying causes of imbalances vary. System migrations, software glitches, failed batch processing between legacy platforms, manual keying errors during high-volume periods, and timing mismatches between systems that settle at different hours can all produce discrepancies. In a bank processing millions of transactions daily, even a tiny error rate generates a meaningful number of mismatches.
A well-run institution treats each force balance as an emergency procedure, not a routine one. The entry is supposed to be temporary, the investigation should start immediately, and the suspense balance should clear within days. When force balancing becomes frequent, it starts feeling routine, and the urgency around follow-up fades. That’s the pattern regulators watch for most closely.
The Fraud Risk
Force balancing creates an opening for fraud precisely because it bypasses the automated controls designed to catch unauthorized transactions. In a normal workflow, every dollar that enters the general ledger has a traceable path from a specific transaction in a sub-ledger. A forced entry breaks that chain. It 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 drawing attention, the person periodically moves it between suspense accounts or re-dates it, a technique forensic accountants call “re-aging.” The longer an item sits unresolved, the harder it becomes to trace to its origin.
This is why the PCAOB’s auditing standard on fraud, AS 2401, tells auditors to specifically target journal entries recorded at the end of a reporting period with little explanation, entries made by people who don’t normally make journal entries, and entries posted to unusual or seldom-used accounts. Force-balanced entries check several of those boxes by nature.
How It Differs From a Normal Correcting Entry
Not every manual journal entry is a force balance. Routine adjustments happen constantly. 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 of the discrepancy is unknown when the entry is made. The whole point is to close the books before the root cause has been identified. If the cause were known, staff would post a correcting entry to the right account instead of parking the difference in suspense. Auditors watch the ratio of explained to unexplained adjustments for exactly this reason.
Controls a Bank Is Expected to Have Around It
Banks that use force balancing are expected to surround the practice with tight controls. The FFIEC baseline for concentration and suspense accounts calls for dual signatures on general ledger tickets, frequent independent reconciliation, full retention of transaction and identifying information, and a defined process for timely resolution.
Most institutions layer additional controls on top of that baseline:
- Sign-off from a senior operations manager or controller before the forced entry can be posted, with the approver personally accountable for the override.
- Documentation covering the dollar amount, the accounts affected, the reason the automated reconciliation failed, and the expected timeline for resolution.
- Aging limits that cap how many days a forced entry can sit in suspense before escalation. OCC 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 by internal audit of open suspense items and the adequacy of investigations.
What Regulators Do When They Find a Pattern
When examiners find that force balancing is frequent, poorly documented, or producing aged suspense items nobody is resolving, consequences escalate quickly. The OCC communicates concerns through Matters Requiring Attention, or MRAs. An MRA 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 “important” issues the bank is expected to address “over a reasonable period of time.” For more severe problems, the Fed escalates to Matters Requiring Immediate Attention, or MRIAs, covering situations that pose “significant risk to the safety and soundness of the banking organization” or represent “significant noncompliance with applicable laws or regulations.”
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 how well a bank’s operational controls are actually working.
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 internal controls over financial reporting. A force balance is by definition a workaround that bypasses standard automated controls. If external auditors find that force balancing is frequent or that the controls around it are weak, they may conclude a material weakness exists in the bank’s internal control environment.
AS 2401 requires auditors to design procedures specifically addressing the risk of management override of controls, including an understanding of both automated and manual controls over journal entries and whether those controls are “suitably designed and have been placed into operation.” 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. The real exposure is a qualified opinion or an adverse finding on internal controls, either of which can rattle investors and draw more regulatory attention.
When It Turns Into a SAR Filing
If 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 to file a Suspicious Activity Report with FinCEN. Under federal regulations, a bank must file 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 come from illegal activity, the transaction is designed to evade Bank Secrecy Act requirements, or the transaction has no business or apparent lawful purpose.
The 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 another 30 days to try, 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 accumulate without investigation risks missing the SAR deadline, which is itself a regulatory violation.