The ledger is closed. The statements are due Friday. Then a number still has to change. Nobody wants to reopen the books. So the fix goes on top of the statements. That's a topside entry.
Do you work on statements for a parent and its subsidiary? If so, you've likely met a topside entry. A topside journal entry can be perfectly valid. It lives where most controls don't reach, so it needs its own paper trail.
What is a topside entry?
A topside entry is an adjustment made at the financial statement or consolidation level, not in the general ledger. It often lives in a spreadsheet. The ledger keeps its balances. Only the reported numbers change. Two common uses: removing transactions and balances between companies in the same consolidated group, and fixing a late item after the ledger is closed. Reviewers and auditors check them closely because they often bypass the ledger's normal controls. Each one needs a preparer, an approver, and support. It also needs a note on whether it gets pushed down to the ledger, and into which period.
- A topside entry changes the statements, not the ledger: the general ledger keeps its original balances.
- Eliminations are a common kind: when you consolidate a parent and a subsidiary, their transactions and balances with each other come out.
- Every topside entry still has to balance: the elimination in the example below carries $55,000 of debits and $55,000 of credits.
- Late fixes need to be pushed down: a $6,500 accrual made only on the statements leaves the ledger's year-end balances $6,500 off from the issued statements, and pushes the expense into January.
- Auditors test them on purpose: topside entries are manual, often late, and skip the usual posting steps.
They usually come from three places.
- Consolidation eliminations. Two companies in the same group bill each other. Each ledger is right on its own. The consolidated statements would count the same dollars twice.
- Late adjustments. A reviewer finds a missed accrual after the ledger is closed. The fix goes on the statements so they go out on time.
- Presentation reclassifications. A balance moves to a different line. Say a vendor was overpaid, leaving a debit balance in accounts payable. That balance gets shown as a receivable.
A normal journal entry goes in the ledger. So does an adjusting journal entry at month-end. A topside entry does the same work one level up, where the ledger never sees it.
Categorizes the routine. Flags what needs you.
See Growthy on a sample book. Read-only bank access.
Get startedThe numbers here are made up. Parent Co bills its subsidiary, Sub Co, $40,000 in management fees this year. Sub Co pays $25,000. So $15,000 is still owed at year-end.
Each company books its own side right. Parent Co shows $40,000 of fee revenue and a $15,000 receivable from Sub Co. Sub Co shows $40,000 of fee expense and a $15,000 payable to Parent Co.
When you consolidate the two, that activity comes out. Nobody outside the group paid that $40,000 or owes that $15,000. The topside entry at consolidation:
Net income for the group stays the same. Revenue and expense each drop by $40,000.
Here is what that does to the top line. Say Parent Co's total revenue is $900,000, fee included. Sub Co's is $300,000. Added up, that's $1,200,000. After the elimination, consolidated revenue is $1,160,000.
Neither company's ledger moves. Parent Co's books still show the receivable, and they should. You redo the elimination each period with that period's numbers, and it never gets posted to either company's own ledger.
Now take one company, again with made-up numbers. The December ledger is closed. Then the reviewer finds a $6,500 contractor bill for December work. It was never recorded. The statements go out with a topside entry:
Leave it there and two things go wrong. First, the ledger's net income runs $6,500 higher than what you issued. So do its retained earnings. Second, the bill gets entered and paid in January. January picks up $6,500 of December's expense.
The fix is to get it pushed down (posted into the ledger itself; not the same thing as pushdown accounting in acquisitions). The clean way is to reopen December with approval and post the same accrual dated December 31. Reverse it on January 1. The January bill then nets to zero. Then retire the topside entry. Mark it pushed down, note the ledger entry it became, and keep it on file. That way next year's prior-year column won't count the $6,500 twice.
Can't reopen the year? Post it in January against opening retained earnings: debit retained earnings, credit accrued expenses. Charge the January bill to accrued expenses, not expense. Skip the reversal. The ledger's December balances and income statement still won't show the $6,500, so keep the topside entry for next year's prior-year column.
Eliminations and presentation reclasses stay on top and get redone every period. Late fixes belong in the ledger, so they get pushed down.
It might seem that any entry outside the ledger is a way to hide something. In most cases, it's routine work: every consolidation needs eliminations. Topside entries still get extra attention, for plain reasons.
A ledger entry usually goes through posting rules, an approval step, and an audit trail. A topside entry often skips all three. It's typed into a spreadsheet by hand, usually late in the close, and often by the most senior person on the file. Reviewers look for those traits.
The auditing standards on fraud (AU-C 240 for private companies, PCAOB AS 2401 for public ones) tell auditors to test journal entries and other adjustments made while preparing the statements, including consolidating adjustments that never go through a formal journal entry. So expect an auditor to ask for each topside entry and its support. Internal reviewers should ask too.
Control Checklist for Every Topside Entry
Keep this with each entry:
- Prepared by. One named person.
- Approved by. A different named person, with a date.
- Support attached. The invoice, intercompany rec, or note that triggered it.
- Reason in the memo. One sentence a stranger could follow next year.
- Recurs or pushes down. Mark eliminations and reclasses as recurring. Give late fixes a push-down date, a target period, and an owner.
- Tied out. Start from the ledger trial balance, add the topside entries, and tie out to the issued statements at $0.00.
That last check catches a common miss: an amount typed straight into one statement without a balancing entry.
A topside entry isn't a red flag. An undocumented one is. Record who made it and who approved it. Attach the support. Then decide whether it stays at the top or goes down into the ledger. The same goes for an unknown item parked in a suspense account inside the ledger. For more terms like this one, see the bookkeeping glossary.
Growthy categorizes transactions automatically and asks when it's unsure. You review and approve before close, not after the statements go out. Its Trial Balance report shows what the ledger says before anyone adjusts on top.
Related: Tick and Tie · True-Up in Accounting
Get started with Growthy
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice.
