Trial Balance Review

By Nupur Mittal

Co-founder at OCTA — works with accounting firms on month-end close and reconciliation automation.

A trial balance review verifies that a period's trial balance is mathematically correct, classifies every account to its financial statement section, and flags anything that looks wrong before detailed testing begins. It confirms debits equal credits, checks that each balance runs in its normal direction, compares every account to the prior period, and produces a condensed balance sheet and income statement. This page walks through the full process step by step, the checks a careful reviewer runs, and how accounting firms scope their review faster with OCTA Flow while a human approves every reclassification and adjustment.

Why trial balance review matters, and where it goes wrong

The trial balance is the single source every other close deliverable is built from — the balance sheet, the income statement, the tax return, the audit workpapers. If an account is misclassified, running the wrong direction, or has moved sharply from the prior period without explanation, that error propagates into everything downstream. A trial balance review exists to catch those problems at the source, before anyone spends hours testing a number that was wrong from the start.

For a firm, the difficulty is that a review has to cover every account on the trial balance — often 30, 50, or more lines — and most of them are fine. The value is in finding the handful that aren't: the account that doesn't foot, the asset sitting in a credit balance, the accrual that jumped 25% with no obvious cause. Doing that by eye, account by account, every period, for every client, is slow and easy to under-scope when a preparer is rushing to close. The goal is a trial balance that ties exactly, is fully classified, and carries a documented explanation for every unusual movement — not a TB that "looks close enough" to move on from.

The trial balance review process, step by step

A rigorous trial balance review follows a consistent sequence. The steps below are the full procedure OCTA Flow executes; they also stand alone as a best-practice process any firm can follow.

1. Foot the trial balance. Total every debit balance and every credit balance on the period's trial balance. The two totals must be equal. If they aren't, report the out-of-balance amount and stop — nothing downstream (classification, flux analysis, a condensed financial statement) is reliable until the TB ties.

2. Classify every account to its financial statement section. Balance sheet accounts sort into Current Assets, Non-Current Assets, Current Liabilities, Non-Current Liabilities, or Equity. Income statement accounts sort into Revenue, Cost of Revenue, Operating Expenses, Other Income, Other Expense, or Tax. Use the client's chart of accounts mapping when one exists; otherwise apply standard account-type logic based on the account name and number.

3. Verify each account's normal balance sign. Assets and expenses normally run debit balances; liabilities, equity, and revenue normally run credit balances. Flag anything running the wrong way:

• Assets with credit balances — negative cash, negative receivables
• Liabilities or equity with debit balances — negative accounts payable without a documented reason
• Revenue with a debit balance — returns and reversals exceeding gross revenue for the period
• Expenses with a credit balance — reversals exceeding the charges booked

4. Build the condensed financial statements. Roll the classified accounts into a condensed balance sheet with subtotals for each section, and a condensed income statement with gross profit, operating income, and net income. Confirm Total Assets equals Total Liabilities plus Equity — a second, independent check on top of the initial footing.

5. Run flux analysis against the prior period. Compute the dollar change and percent change for every account. Flag anything that moves more than 20% and more than $25,000 (or the engagement's performance materiality, if it's lower) from the prior period. Also flag any account that carries a balance in one period and is zero in the other — that pattern often points to a coding error rather than a real business change.

6. Review activity in the largest accounts. For the handful of accounts with the biggest balances, pull the underlying general-ledger detail and scan for unusual descriptions, journal entries posted outside the normal sub-ledger flow, round-dollar amounts, and postings dated right at period end — the usual fingerprints of a plug, a late adjustment, or an entry that needs a closer look.

7. Compile the follow-up list. Pull everything flagged in steps 1 through 6 into a single prioritized list — critical items needing immediate resolution, high-priority unusual balances, and medium-priority flux items that need an explanation from the account owner — so detailed testing starts from a scoped list of real issues, not a blank trial balance.

The trial balance checks, worked example

Here's a condensed extract from a professional-services company's trial balance at December month-end, showing the three checks that matter most: the footing, a flux flag, and an unusual balance.

Footing check. Total debits and total credits both equal $5,521,500 — the trial balance is in balance. If they didn't match, this account list would be reported unusable until the difference was found and corrected.

Flux flag. Accrued Liabilities (GL 2100) moved from $185,000 in the prior period to $232,000 this period:

A $47,000, 25.4% increase clears both the 20% and $25,000 thresholds, so it's flagged for an explanation from the account owner before the balance is relied on.

Unusual balance flag. Accounts Receivable (GL 1200) shows a $18,500 credit balance this period, versus a normal $142,000 debit balance last period. Receivables is an asset account — it should almost always carry a debit balance. A net credit here is most often caused by customer credit memos and overpayments exceeding open invoices, but it needs to be confirmed rather than assumed, and it's flagged high-priority because it affects AR aging and DSO reporting until it's resolved.

Key controls and red flags

The difference between checking boxes and a reliable trial balance review is what you watch for. A careful reviewer flags:

• Trial balance doesn't foot — debits and credits are out of balance, the single most serious flag
• Asset accounts carrying credit balances — negative cash, negative receivables
• Liability accounts carrying debit balances — negative accounts payable with no documented reason
• Retained earnings movement inconsistent with net income and dividends declared
• Income statement accounts sitting at zero when the business had ongoing activity that period
• Account balances that swing more than 20% and more than $25,000 from the prior period with no known business reason
• Deferred tax balances inconsistent with known temporary differences

Catching these consistently, every account and every period, is what turns a trial balance review from a formality into a genuine gate before detailed testing.

What a completed trial balance review produces

A finished review isn't just a footed spreadsheet — it's a documented workpaper a reviewer can sign off on and testing can be scoped from. A complete trial balance review package includes:

How OCTA Flow automates trial balance review

OCTA Flow does the mechanical checking for you and leaves the judgment — and the sign-off — with your team. The workflow mirrors the process above:

1. Pick the Trial Balance Review Skill. Flow already knows the full procedure: foot the TB, classify every account to its financial statement section, check each balance's normal sign, build the condensed statements, run flux analysis, and flag unusual items.
2. Connect your data. Point Flow at the accounting system, or upload the period's trial balance, the prior-period comparative, the chart of accounts structure, and GL detail for the largest accounts.
3. Run. Flow foots the trial balance, classifies and maps every account to its financial statement line, checks each balance against its normal sign, computes flux against the prior period, and builds the condensed balance sheet and income statement.
4. Review findings by severity. Instead of scanning every line of a 40-plus-account trial balance, Flow surfaces only what needs attention — ranked by severity, each with a recommended action: escalate an out-of-balance TB, request an explanation for a flux item, reclassify a mismapped account, or accept an unusual balance with a documented reason. Your team works the exceptions, not every account.
5. Sign off. Once the TB ties, classifications are confirmed, and flagged items are resolved or explained, Flow assembles the workpaper with the full audit trail intact.

The result: the account-by-account checking is done in a fraction of the time, and your people spend their hours on the handful of accounts that actually need judgment before testing starts.

Control and trust: Flow proposes, you approve

This is what matters most to a firm putting its name on the numbers: OCTA Flow never writes to your books on its own. Every reclassification and proposed adjusting entry is a proposal that a person reviews and confirms before anything is posted. Flow does the checking and shows its reasoning; a person makes the call.

That control model runs through the whole review:

• Findings, not silent changes. Flow raises what it found and what it recommends — you decide whether to resolve, reclassify, escalate, or accept it with a documented reason.
• Severity and escalation built in. An out-of-balance trial balance or a broken retained-earnings roll-forward is flagged critical and can be escalated to a controller, CFO, or auditor rather than quietly carried forward.
• A complete audit trail. Every classification, flux flag, proposed entry, approval, and override is logged, so the review is fully traceable end to end.

You get the speed of automation with the accountability of human sign-off — exactly what the account that feeds every other financial statement requires.

What the review draws on

To run a trial balance review, Flow uses the same sources a preparer already works from:

• The detailed trial balance for the period (required)
• Entity type — C-corporation, LLC, and so on — since classification and normal-balance logic vary slightly by entity structure (required)
• The prior-period trial balance — to run flux analysis and carry forward comparatives (optional)
• The chart of accounts structure — to map each account to its financial statement line the way the firm already does it (optional)
• GL detail for the largest accounts — to review the underlying activity behind the top balances (optional)

Flow works from whatever your client has connected — it matches each input by its purpose, so it doesn't matter what the files are named or which accounting system they came from.

Related skills and terms

Frequently Asked Questions

What is a trial balance review? A trial balance review verifies that a period's trial balance is mathematically correct (debits equal credits), classifies every account to its financial statement section, checks that each balance runs in its normal direction, compares every account to the prior period, and produces a condensed balance sheet and income statement — all before detailed testing begins.

How do you review a trial balance? Foot it to confirm debits equal credits, classify every account to Balance Sheet or Income Statement sections, check each balance against its normal sign (debit for assets and expenses, credit for liabilities, equity, and revenue), build the condensed financial statements, run flux analysis against the prior period, and review GL detail behind the largest accounts.

What does it mean when a trial balance doesn't foot? It means total debits and total credits don't match — the trial balance is out of balance. This is the most serious flag in a review: nothing built from that trial balance (classification, flux analysis, financial statements) is reliable until the imbalance is found and corrected.

What is flux analysis in a trial balance review? Flux analysis compares each account's current-period balance to its prior-period balance and computes the dollar and percent change. A common threshold flags any account that moves more than 20% and more than $25,000 (or the engagement's performance materiality) with no known business reason, so it gets an explanation before being relied on.

Why would an asset account have a credit balance? Assets normally carry debit balances, so a credit balance is unusual and needs investigation. For cash, it usually signals outstanding items exceeding the balance or a bank error. For accounts receivable, it's often customer credit memos or overpayments exceeding open invoices. Either way, it should be confirmed, not assumed.

Can trial balance review be automated? The footing, classification, sign-checking, and flux analysis can be automated and reviewed, while judgment calls — accepting an unusual balance, deciding how to resolve an imbalance — stay with your team. That's the model OCTA Flow uses.

Does OCTA Flow post reclassifications or adjustments directly to my accounting system? No. Flow proposes every reclassification and adjusting entry; a person on your team reviews and approves before anything is posted to the books. Nothing is written automatically.

See how firms scope faster, fully-explained trial balance reviews with human sign-off → start a 30-day OCTA Flow trial.