How to Audit a General Ledger: Steps, Controls, and Sampling

Auditing a general ledger means working through a defined sequence: plan the engagement and set materiality, assess internal controls, reconcile the subsidiary ledgers to the trial balance, select transactions through sampling, test journal entries for signs of manipulation, perform substantive testing on high-risk account balances, obtain external confirmations from third parties, review subsequent events and going concern, collect a signed management representation letter, and evaluate the aggregated results to issue an opinion. Each phase builds on the one before it, and the amount of work in each phase depends on what the earlier phases revealed.

Plan the Engagement and Set Materiality

Every general ledger audit opens with planning. The audit team develops an overall strategy, identifies significant accounts and disclosures, and assesses where the financial statements are most likely to contain material misstatements.1PCAOB. AS 2101: Audit Planning The output of planning is a decision about how much work each area of the ledger requires.

Materiality is the central number set during planning. It is the dollar threshold above which a misstatement could influence the decisions of someone relying on the financial statements, and the auditor derives it from a percentage of a benchmark like revenue, total assets, or pre-tax income.2PCAOB. AS 2105: Consideration of Materiality in Planning and Performing an Audit Misstatements below materiality get tracked. Misstatements above it must be corrected before a clean opinion can be issued.

Planning also includes analytical procedures. The auditor compares current-year balances to prior-year figures, budgets, and industry benchmarks. A revenue account that jumped 30 percent while the industry grew 5 percent draws scrutiny. An expense line that dropped without a clear operational change gets flagged. These comparisons steer attention toward the accounts most likely to contain errors, and they shape the rest of the audit program.

Assess Internal Controls and Segregation of Duties

Before performing detailed transaction testing, the auditor evaluates the company’s control environment. Weak controls mean larger samples, more substantive testing, and higher fees. Strong controls let the auditor reduce sample sizes and rely more on the system itself.

Segregation of duties in the journal entry process gets the closest look. The person who enters an entry should not be the same person who approves it. Someone with authority to create vendor payment vouchers should not also have authority to approve journal entries, because that combination could push fabricated expenses through without challenge. In smaller organizations where full segregation is impractical, compensating controls like mandatory management review of entries above a dollar threshold can fill the gap, and the auditor tests whether those reviews actually occur.

Control testing extends to the accounting system itself. The auditor examines the user access matrix showing who can do what, segregation-of-duties reports flagging conflicting permissions, and automated audit trails that record what changed, when, and who approved it. A well-designed approval matrix, consistent enforcement of access restrictions, and timely account reconciliations all reduce audit risk and, by extension, the scope and duration of the fieldwork.

Reconcile Subledgers and Tie Out the Trial Balance

Substantive work rests on a trial balance where total debits equal total credits and every subsidiary ledger ties to its control account in the general ledger. The accounts receivable aging must match the AR control account to the penny. Accounts payable, inventory, fixed assets, and every other subledger have the same requirement. Any difference between a subledger and its control account is a red flag that triggers expanded testing.

High-risk and complex accounts need supporting schedules that walk the auditor from individual transactions to the aggregated balance. A fixed asset schedule should list each asset with acquisition date, original cost, useful life, depreciation method, and current-year depreciation expense. Accrued liability schedules should show the methodology behind each estimate, whether that is accrued payroll based on days worked after the last pay date or a warranty reserve calculated from historical claim rates. The auditor will challenge the assumptions, and undocumented methodologies rarely survive that challenge.

Manual journal entries recorded near period-end need particular attention. Each one should carry a description explaining what it does and why, along with supporting contracts, invoices, or calculation worksheets. Entries without clear explanations are the first ones pulled for detailed testing.

Select Transactions Through Sampling

No auditor can examine every transaction in a general ledger, so sampling is how conclusions about the whole population get drawn from a subset. Two broad approaches apply. Statistical methods like Monetary Unit Sampling weight the selection toward higher-dollar items, so a $500,000 invoice is far more likely to be pulled than a $500 one. Non-statistical approaches, like random selection or testing all transactions inside a specific time block, are common for lower-risk accounts and control testing.

Sample size follows the risk assessment. Higher assessed risk of material misstatement means larger samples. The auditor also considers tolerable misstatement, which is the maximum error in the population that would still be acceptable. When an account balance sits close to materiality, expect a bigger sample.

Modern audit teams pair manual sampling with computer-assisted audit techniques, known as CAATs, which analyze the full population of general ledger entries rather than a subset. These tools flag entries posted on weekends or holidays, entries made by users whose access level should not allow posting, round-dollar entries without supporting invoices, and duplicate amounts across different accounts. The exceptions CAATs surface become the starting point for targeted substantive testing.

Test Journal Entries for Fraud Risk

Auditing standards require the auditor to presume that management override of controls is a fraud risk in every engagement. Testing journal entries for signs of manipulation is not optional.3PCAOB. AS 2401: Consideration of Fraud in a Financial Statement Audit The auditor must understand the financial reporting process, identify and select entries for testing, and inquire of the people involved in the process about unusual activity.

Period-end entries carry the highest fraud risk and receive the most attention. A company trying to inflate revenue or hide expenses is most likely to do it through adjusting entries recorded just before the books close. The auditor traces selected entries back to source documents like shipping records, vendor invoices, and contracts to verify the date, amount, and economic substance of the transaction. Entries that lack adequate support, bypass the normal approval workflow, or hit unusual account combinations get escalated for deeper investigation.4PCAOB. Audit Focus: Journal Entries

The fraud risk work also requires the auditor to review accounting estimates for bias and evaluate whether significant unusual transactions have a legitimate business purpose.3PCAOB. AS 2401: Consideration of Fraud in a Financial Statement Audit A retrospective review compares prior-year estimates to actual outcomes. If management’s estimates consistently lean in the direction that flatters earnings, the pattern itself is evidence of potential bias, even when each individual estimate looked reasonable in isolation.

Perform Substantive Testing of Key Account Areas

Once planning and control assessment are done, the audit moves into substantive testing of specific account balances and transaction classes. Depth varies by risk, but several areas consistently demand the most attention.

Revenue Recognition

Revenue is the account most prone to manipulation, and auditing standards create a presumption that improper revenue recognition is a fraud risk. The auditor tests whether the company correctly applies the five-step model under ASC 606: identify the contract, identify performance obligations, determine the transaction price, allocate that price, and recognize revenue as obligations are satisfied. For service contracts, that often means verifying revenue is spread over the service period rather than booked entirely upfront.

Cut-off testing follows. The auditor selects sales transactions near period-end to confirm revenue and the related cost of goods sold land in the same fiscal period. Non-operating items like surplus equipment sales get checked to make sure they are not mixed into operating revenue. For contracts with return rights, the auditor tests whether the company has recorded a reasonable return liability based on historical experience.

Expense Classification and Capitalization

The line between capital expenditure and operating expense is one of the more consequential judgment calls in accounting. Capitalizing a cost puts it on the balance sheet and spreads its impact through depreciation. Expensing it hits the income statement immediately. Misclassification in either direction distorts both current earnings and asset values.

The auditor pulls a sample of fixed asset additions and traces each one to the original vendor invoice and work order, verifying the cost genuinely provides a future economic benefit. The auditor also works the other direction, reviewing large repair and maintenance charges to confirm capital-eligible costs are not being buried in operating expenses, which would understate assets and current income.

Estimates, Accruals, and Reserves

Accounting estimates are inherently subjective, which makes them both hard to audit and attractive targets for manipulation.5PCAOB. AS 2501: Auditing Accounting Estimates The allowance for doubtful accounts is a classic case. The auditor analyzes the receivables aging schedule, evaluates the historical write-off rate, and tests whether changes to the allowance are supported by actual changes in economic conditions. A company that suddenly reduces its allowance without a corresponding improvement in customer payment behavior is waving a red flag.

Warranty reserves follow the same logic. The auditor recalculates the liability using historical claims data and contractual obligations, then checks whether the methodology is consistent with prior years. Accrued income taxes require reconciling book income to taxable income and verifying the calculation of deferred tax assets and liabilities. In every estimate area, the auditor looks for both mathematical accuracy and whether the underlying assumptions pass a reasonableness test.

Inventory

Inventory testing combines physical verification with valuation work. The auditor attends and observes the company’s physical inventory count, independently counting a sample of items and comparing them to recorded quantities. Discrepancies trigger investigation. On valuation, the auditor reviews purchase invoices to verify unit costs, confirms the company applies its chosen cost method consistently (FIFO, LIFO, or weighted average), and tests that inventory is recorded at the lower of cost or net realizable value. Obsolete or slow-moving items that should be written down are a frequent audit finding.

Lease Accounting

Under ASC 842, most leases appear on the balance sheet as a right-of-use asset and a corresponding lease liability. The auditor verifies the lease liability was initially measured at the present value of remaining lease payments using the appropriate discount rate, typically the rate implicit in the lease or the company’s incremental borrowing rate. The right-of-use asset should equal the initial lease liability plus any prepayments and direct costs, minus any incentives received. For operating leases, the auditor checks that a single lease cost is recognized on a straight-line basis over the lease term. For finance leases, the amortization of the asset and the interest on the liability are tested separately.

Intercompany Transactions

For consolidated entities, the auditor confirms that intercompany transactions (loans, sales, or management fees between a parent and its subsidiaries) are properly eliminated in consolidation. Intercompany balances must offset exactly. When they do not, one side recorded something the other did not, and the auditor tracks down the difference. These transactions must also be documented at arm’s-length values, meaning they reflect what unrelated parties would agree to in the same circumstances.

Send External Confirmations

Some audit evidence only becomes reliable when it comes from outside the company. External confirmations involve the auditor contacting third parties directly to verify balances or terms.6PCAOB. AS 2310: The Confirmation Process The most common targets are banks (to verify cash balances, loan amounts, and credit lines), customers (to confirm outstanding receivable balances), and attorneys (to identify pending or threatened litigation affecting the financial statements).

The auditor controls the confirmation process from start to finish. The company prepares the letters, but the audit team mails them and receives the responses directly. That sequence prevents anyone at the company from intercepting or altering a response. When a bank confirms a loan balance that does not match the general ledger, or a customer disputes a receivable, the auditor investigates the difference before clearing the account.

Review Subsequent Events and Going Concern

The audit does not end at the balance sheet date. Auditors are required to evaluate events that occur between the balance sheet date and the date they sign the audit report.7PCAOB. AS 2801: Subsequent Events Some events, like the resolution of a lawsuit that was pending at year-end, require adjusting the financial statements. Others, like a major acquisition that closed in January, do not change the numbers but must be disclosed in the notes.

To catch these events, the auditor reads the latest available interim financial statements, inquires of management about significant changes in debt, capital, or working capital since year-end, and asks whether any unusual adjustments have been made. The auditor also checks for changes in related-party relationships and the current status of items that were based on preliminary data at year-end.7PCAOB. AS 2801: Subsequent Events

Separately, the auditor evaluates whether the company can continue operating as a going concern, meaning it has the financial capacity to meet its obligations for a reasonable period after the financial statements are issued.8PCAOB. AS 2415: Consideration of an Entity’s Ability to Continue as a Going Concern Indicators of going concern doubt include recurring losses, negative cash flows, loan defaults, and loss of a major customer. When substantial doubt exists, the auditor assesses management’s plans to address the situation and determines whether the financial statement disclosures are adequate. A going concern modification is one of the most consequential findings an auditor can issue.

Obtain the Management Representation Letter

Before issuing the opinion, the auditor obtains a written representation letter signed by management.9PCAOB. AS 2805: Management Representations The letter is not a formality. In it, management formally confirms that the financial statements are fairly presented, that all material transactions have been recorded, that all known or suspected fraud has been disclosed, and that all subsequent events requiring disclosure have been identified. If management refuses to sign, the auditor cannot issue an opinion.

The letter also covers specific items the auditor flagged during the engagement, such as the completeness of related-party disclosures and the reasonableness of significant estimates. Signing creates a documented commitment that can have legal consequences if the statements later prove materially misleading.

Evaluate Results and Issue the Opinion

After substantive testing wraps up, the auditor aggregates all identified misstatements, both corrected and uncorrected, and evaluates whether the financial statements as a whole are materially misstated.10PCAOB. AS 2810: Evaluating Audit Results The evaluation weighs both the dollar amount and the nature of each misstatement. An error that turns a profit into a loss can be material even if it falls below the quantitative threshold.

Findings get communicated to management through a schedule of proposed adjustments and a management letter outlining control deficiencies and recommendations. Material misstatements must be corrected through adjusting journal entries before a clean opinion can be issued. The management letter might identify issues like inadequate segregation of duties, missing documentation for revenue contracts, or inconsistent application of the capitalization policy.

The auditor then issues one of four opinions:

  • Unqualified (clean): The financial statements are free from material misstatement.
  • Qualified: The statements are fairly presented except for a specific identified issue.
  • Adverse: The financial statements are materially misstated and should not be relied upon. This can crater investor confidence and trigger loan covenant violations.
  • Disclaimer: The auditor could not obtain enough evidence to form an opinion. In practice, this is as damaging as an adverse opinion.

Additional Requirements for Public Companies

The steps above describe a financial statement audit that applies to companies of any size. Public companies carry an additional layer under Section 404 of the Sarbanes-Oxley Act. Management must include a report in its annual filing assessing the effectiveness of internal controls over financial reporting.11GovInfo. Sarbanes-Oxley Act of 2002 For large accelerated and accelerated filers, the external auditor must also attest to and report on that assessment, producing a separate opinion on internal controls that is integrated with the financial statement audit.12PCAOB. AS 2201: An Audit of Internal Control Over Financial Reporting

Smaller reporting companies that do not qualify as accelerated filers are exempt from the auditor attestation requirement under SOX 404(b), though they still must perform management’s own assessment under 404(a).11GovInfo. Sarbanes-Oxley Act of 2002 Emerging growth companies are also exempt from the auditor attestation. When management or the auditor identifies a material weakness, that finding goes into the annual report and becomes public. It does not automatically mean the financial statements are wrong, but it signals that the control environment has a gap serious enough that a material misstatement could slip through undetected.