A top-side journal entry is a manual accounting adjustment posted directly to a company’s general ledger during the financial close, bypassing the sub-ledger systems that normally originate transactions like invoices, payroll runs, and inventory movements. Finance teams use these entries to record consolidation eliminations, acquisition fair value adjustments, period-end accruals, and late-breaking corrections that the transactional systems weren’t built to handle. Because they sit outside automated controls and rely on human judgment, they carry a higher risk of error and manipulation than routine postings, and both internal reviewers and external auditors watch them closely.
How a Top-Side Entry Differs From a Normal Journal Entry
In a typical accounting cycle, transactions originate in a sub-ledger. Accounts payable, accounts receivable, fixed assets, and payroll each maintain their own detailed records, and those totals roll up into the general ledger automatically. A top-side entry skips that origination step. Someone in accounting creates the adjustment and posts it straight to a general ledger control account, with no corresponding update to the detailed records underneath.
That disconnect is the defining feature. If a top-side adjustment increases the accounts receivable balance on the consolidated general ledger, the individual customer balances in the AR sub-ledger stay unchanged. The GL total and the sub-ledger total won’t match until the next reconciliation cycle catches up. For anyone doing month-end reconciliations, that mismatch is a known feature of the process rather than a defect, but it has to be tracked.
The manual nature is the other distinction. Automated sub-ledger postings run through built-in validation rules across thousands of transactions. A top-side entry has none of that. The preparer calculates the adjustment, often in a spreadsheet, and posts it with whatever controls the organization has layered on top. The gap between automated safeguards and manual judgment is exactly why these entries draw so much attention.
What Companies Actually Use Them For
Top-side entries exist because financial reporting involves adjustments that transactional systems were never designed to produce. The legitimate uses fall into a handful of categories.
Consolidation and Intercompany Eliminations
When a parent company consolidates its subsidiaries into one set of financial statements, it has to eliminate transactions between group entities. If a subsidiary sold $5 million in goods to another subsidiary, that revenue and its matching cost need to come out, or the consolidated income statement would double-count activity that never involved an outside party. Accounting standards require that all intra-entity balances and transactions be eliminated in consolidated financial statements.1PCAOB. Audit Focus – Journal Entries These eliminations happen as top-side entries at the consolidated level because no single subsidiary’s ledger can perform them.
Intercompany profit embedded in inventory is a common example. If one subsidiary sold inventory to another at a markup and the receiving subsidiary hasn’t yet sold it to an outside customer, the unrealized profit has to be stripped out. The adjustment brings inventory back to the original cost to the group.
Fair Value Adjustments After an Acquisition
After an acquisition, the acquirer must restate the target company’s assets and liabilities at fair value. The target’s own books still carry historical costs. Nobody goes into the acquired company’s sub-ledgers and reprices every asset one by one. Top-side entries at the consolidated level record the fair value step-ups (or step-downs) for property, intangibles, and contingent liabilities. Any excess of the purchase price over the total fair value of identified net assets is booked as goodwill through the same mechanism.
Accruals, Estimates, and Non-Cash Items
Period-end accruals for bonuses, warranty reserves, restructuring charges, and impairment losses often require top-side entries. These involve judgment about amounts that won’t be finalized until a later period. Operational systems don’t produce them because there’s no underlying invoice or transaction to trigger the entry. Someone has to estimate the liability and post it by hand.
Late-Discovered Error Corrections
Sometimes an error surfaces after a sub-ledger has closed for the period. If the correction is material but the closing window is too tight to reopen the sub-ledger, a top-side entry provides a workaround. The financial statements get corrected on time, and the sub-ledger fix follows in the next period. This is where auditors sharpen their focus, because “we found it too late to fix properly” can be a legitimate explanation or a convenient excuse.
Documentation and Internal Controls
The manual nature of these entries is what makes control design so important. Every well-run organization layers safeguards around them.
Segregation of Duties
The person who prepares a top-side entry should never be the same person who approves and posts it. Combining those roles creates a straightforward path for both accidental errors and deliberate manipulation. The preparer should also not have access to cash, deposits, or payment processing, because the ability to move money and adjust ledger records at the same time is the classic setup for concealing fraud.
In practice, many organizations use three roles: a preparer who calculates and documents the entry, a reviewer who validates the accounting logic, and a senior approver who authorizes the posting. Smaller organizations that can’t fully segregate need compensating controls, such as after-the-fact reviews by someone independent of the process.
Supporting Documentation
Every top-side entry needs a paper trail that answers three questions. What accounts are affected? Why is the adjustment necessary? How was the amount calculated? A complete package usually includes the journal entry form, a memo explaining the business rationale, supporting calculations, and any source documents such as contracts, invoices, or third-party valuations.
Vague descriptions like “to correct balance” or “year-end adjustment” are red flags. The documentation should be specific enough that someone unfamiliar with the entry could reconstruct the reasoning months later.
System Access and Audit Trails
Accounting systems should restrict direct GL posting to a small group of authorized users. The system needs to log who prepared the entry, who approved it, and when each step happened, producing an audit trail that can’t be altered after the fact.1PCAOB. Audit Focus – Journal Entries If an ERP system lets anyone with GL access post a top-side entry with no secondary approval workflow, that’s a control gap worth fixing before an auditor finds it.
Review of Recurring Entries
Management should periodically review the population of top-side entries to spot patterns. If the same adjustment appears every quarter, it’s a signal that the underlying process belongs in a sub-ledger or should be automated. Recurring top-side entries create persistent manual risk and suggest an operational gap that hasn’t been addressed. Auditors notice these patterns quickly, and they factor into assessments of whether internal controls are working as designed.
Why Auditors Treat Them as High-Risk
Auditors focus on top-side entries because they represent one of the most accessible ways for management to override normal controls. PCAOB standards address this risk directly.
PCAOB Auditing Standard 2401 (Consideration of Fraud in a Financial Statement Audit) starts from the premise that material misstatements due to fraud often involve recording inappropriate or unauthorized journal entries throughout the year or at period end, or making adjustments to financial statement amounts through consolidating adjustments and reclassifications that aren’t reflected in formal journal entries.1PCAOB. Audit Focus – Journal Entries That description reads like a definition of top-side entries, which is exactly why they get the scrutiny they do.
AS 2301 reinforces the point by requiring auditors to examine journal entries and other adjustments for evidence of possible material misstatement due to fraud as a specific response to management override risk.2PCAOB. AS 2301 – The Auditor’s Responses to the Risks of Material Misstatement The standard also requires auditors to review accounting estimates for bias and evaluate whether unusual transactions may have been structured to enable fraudulent reporting.
The PCAOB directs auditors to use professional judgment in determining the nature, timing, and extent of journal entry testing.1PCAOB. Audit Focus – Journal Entries There’s no blanket rule requiring 100% testing, but auditors often test every top-side entry anyway because the population is small and the risk is high. Thirty manual adjustments per quarter present a very different challenge than a sub-ledger with 30,000 automated transactions, and sampling a handful of judgment-based entries may not catch the one that matters.
Red Flags in a Top-Side Entry Population
Auditors look for specific patterns that suggest an entry may not be legitimate:
- Entries posted after the closing deadline, in the gap between the preliminary close and the final reporting date, when preliminary numbers are already known.
- Missing or vague documentation, with no supporting calculations or a one-line description that doesn’t explain the business purpose.
- Preparers or approvers who fall outside the authorized user list in the system log.
- Round-number adjustments that land results exactly on a target, such as bringing earnings per share from $0.98 to $1.00 or hitting an analyst consensus figure precisely.
- Entries with no reversing component. Many legitimate accruals reverse in the following period, and an entry that books income once with no later reversal can indicate the amount was fabricated.
The WorldCom Lesson
The most infamous case of top-side entry abuse is WorldCom, where executives used manual journal entries to reclassify billions of dollars in ordinary operating expenses (primarily line costs for network capacity) as capital expenditures. Capital expenditures are spread across multiple years on the balance sheet instead of hitting the income statement immediately, so the reclassification made current-period profits look dramatically higher than they actually were.
Internal auditors eventually discovered roughly $3.9 billion in operating expenses that had been shifted to capital accounts. The SEC later determined that WorldCom had overstated its assets by approximately $11 billion. Many of the fraudulent entries lacked invoices, receipts, or any genuine supporting documentation, which is exactly the gap that proper internal controls over top-side entries are meant to close.
WorldCom’s collapse was a direct catalyst for the Sarbanes-Oxley Act of 2002, which imposed the internal control requirements over financial reporting that now govern every public company. The case remains a textbook illustration of why top-side entries demand strong controls and independent scrutiny.
When the Pattern Itself Is the Problem
A one-time top-side entry to correct a late-discovered error or handle an unusual transaction is normal. A pattern of recurring top-side entries covering the same issue quarter after quarter is not. Regulators and auditors view heavy reliance on manual journal entries as a sign that something is broken in the underlying accounting process.
Manual journal entries are considered high-risk, and organizations are expected to keep them to an absolute minimum. When auditors find that an entity routinely posts the same type of top-side adjustment, such as a monthly correction to revenue recognition because the billing system doesn’t handle a certain contract type, they may conclude that internal controls have a significant deficiency or even a material weakness. A material weakness in internal control over financial reporting is a serious finding for any public company, triggering required disclosure and often a decline in investor confidence.
The fix is straightforward in concept, if not always in execution. If an adjustment is recurring, it should be automated or pushed down into the sub-ledger where it belongs. Building the logic into the transactional system eliminates the manual risk, creates an audit trail from the start, and removes the segregation-of-duties burden that every top-side entry carries. Treating these entries as a permanent workaround rather than a temporary bridge means accepting risk that doesn’t need to be there.