Tidy bookkeeping does not always mean balanced bookkeeping. Many finance teams only notice an error when the financial statements are almost finished, the debit and credit totals refuse to match, and the source of the error is unclear. The trial balance works as a checking tool to prevent this, and it is an essential stage in the accounting cycle. This article covers the functions of a trial balance, the five steps to prepare one from the general ledger, an example of a balanced table, and the limitations that are often overlooked.
In short, a trial balance (neraca saldo) is a list of all ending balances of general ledger accounts on a specific date, arranged in debit and credit columns whose totals must be equal. Its function is to verify the balance of double-entry bookkeeping before the financial statements are prepared, serving as a checkpoint after every transaction has been posted to the general ledger.
In practice, a trial balance has four main functions: recapping the balance of every account, detecting imbalances early, providing the basis for preparing financial statements, and monitoring account positions across periods. It is prepared after all ledger postings are complete and before the adjusting entries, so errors can be identified before they affect the financial statements.
A full cycle can contain up to three versions:
A trial balance is drawn directly from the general ledger once every transaction has been journalized and posted. The process is compact: calculate the ending balance of each account, copy it into a four-column worksheet according to its normal balance, add up the debit and credit columns, then make sure both totals match exactly.
The five steps in detail:
The table below summarizes the trial balance of the design studio “Arah Kreatif” as of 31 July 2026, the result of posting eight ledger accounts over one month of operation. The pattern reads quickly: accounts with a normal debit balance, namely assets and expenses, fill the left column; liabilities, capital, and revenue fill the right column. Both totals meet at Rp98,000,000.
|
101 |
Cash |
51,000,000 |
|
|
102 |
Accounts Receivable |
10,000,000 |
|
|
121 |
Equipment |
25,000,000 |
|
|
201 |
Accounts Payable |
7,000,000 |
|
|
301 |
Owner’s Capital |
60,000,000 |
|
|
401 |
Service Revenue |
31,000,000 |
|
|
501 |
Salaries Expense |
7,000,000 |
|
|
502 |
Rent Expense |
5,000,000 |
|
|
Total |
98,000,000 |
98,000,000 |
Every figure is derived from seven transactions during the month; however many transactions there are, the column principle stays the same.
No. A trial balance only tests the arithmetic equality of total debits and credits, not whether the entries themselves are correct. According to AccountingTools, four types of error still slip through even when the totals match: a transaction that was never recorded at all (omission), an entry posted to the wrong account (commission), a wrong amount entered on both sides at once, and two errors that cancel each other out (compensating errors).
When the totals do not match, the difference itself can be the first clue. A difference divisible by 9 points to a transposition, digits swapped such as 540 written as 450. A difference divisible by 2 may mean one balance sits in the wrong column; look for an account worth half the difference. Both are early indications, not certainties.
In implementation practice, a difference that recurs every month is usually a symptom of records scattered across many spreadsheets, not merely a typing error. In a modern ERP (Enterprise Resource Planning) system such as SAP S/4HANA Finance, every accounting entry is recorded once into the Universal Journal, a single table called ACDOCA that SAP positions as the single source of truth. The debit-credit balance is maintained from the moment a document is posted; the balances are read directly through the Trial Balance app in SAP Fiori, available at any time without a manual month-end recap. You can explore how it works in our overview of the SAP finance module (FICO).
A trial balance is an internal working document in a four-column format (account code, account name, debit, credit) that lists every general ledger account, including revenue and expenses, to verify that the books are in balance. A balance sheet, or statement of financial position, is a formal report for external parties that presents only three elements: assets, liabilities, and equity.
Re-add both columns, then match every balance against the general ledger. Use the difference as a clue: a difference divisible by 9 points to swapped digits (a transposition, for example 540 written as 450), while a difference divisible by 2 usually means one balance sits in the wrong column; look for an account worth half the difference.
A trial balance is prepared at the end of an accounting period, once all ledger postings are complete and before the financial statements are produced. In one full cycle, it can be prepared up to 3 times: before adjustments (unadjusted), after adjustments (adjusted), and after the closing entries (post-closing).
The trial balance is the checkpoint between bookkeeping and financial statements: matching totals are a necessary condition, not a guarantee that the books are correct. At a small scale, the discipline of the five steps above plus tracing differences is enough; once transaction volumes and the number of entities grow, the balance is safer in the hands of a system. As an SAP Platinum Partner through its United VARs membership, Soltius helps companies move bookkeeping and balance verification to SAP S/4HANA Finance, from implementation through to post go-live support.
To discuss your company’s readiness for SAP S/4HANA Finance, visit soltius.co.id.