The audit technique used to test completeness is tracing. The auditor starts with a source document generated outside the accounting system — a shipping log, a receiving report, a vendor invoice — and follows it forward into the journals, subsidiary ledgers, and general ledger to confirm the transaction was actually recorded. Completeness is about what might be missing from the books, so the test has to begin with evidence that an economic event happened and then check whether the accounting caught it.1Public Company Accounting Oversight Board. PCAOB Auditing Standards – AS 1105 Audit Evidence
Why Completeness Needs Its Own Technique
Management’s financial statements carry several implicit assertions, and completeness addresses one specific risk: that transactions, accounts, or disclosures that belong in the statements were left out.1Public Company Accounting Oversight Board. PCAOB Auditing Standards – AS 1105 Audit Evidence The concern is understatement. Goods received before year-end but never booked as a payable understate liabilities. Shipments that went out the door without a corresponding sale entry understate revenue. These errors can make a company look less indebted or less profitable than it really is.
Every other assertion examines something already sitting in the records and asks whether it is right. Completeness flips that question and asks whether anything is missing. That reversal is what drives the choice of technique.
Tracing vs. Vouching: Direction Is Everything
Auditors rely on two directional procedures, and they are not interchangeable.
Vouching begins with an entry already in the general ledger and works backward to the supporting document. It confirms that a recorded transaction really happened, which tests the existence or occurrence assertion. If a journal entry has no shipping record, invoice, or contract behind it, the entry may be fictitious.
Tracing runs the other direction. The auditor picks a source document created outside the accounting system and follows it forward into the books. A receiving report proves goods arrived, so an accounts payable entry should exist. A bill of lading proves goods left the warehouse, so a sale should be recorded. When the trail stops before reaching the ledger, the auditor has found an unrecorded transaction — a completeness failure.1Public Company Accounting Oversight Board. PCAOB Auditing Standards – AS 1105 Audit Evidence
Tracing works for completeness because source documents exist independently of the accounting records. A receiving report is created when goods physically arrive. A bill of lading is generated when a carrier picks up a shipment. These documents capture economic reality, and that is the only starting point from which an omission can be detected.
Tracing in the Revenue Cycle
In the revenue cycle, completeness and occurrence risks run in opposite directions. Occurrence asks whether recorded sales really happened; vouching tests that. Completeness asks whether real sales went unrecorded, and tracing is how auditors look.
The auditor selects a sample of shipping documents or bills of lading from around year-end. Because those documents prove goods physically left the company’s control, a sale should have been recognized. Each selected document is traced forward to the matching sales invoice, then to the sales journal, and finally to the accounts receivable subsidiary ledger. A shipping record with no matching entry in the revenue stream points to an unrecorded sale, which understates both revenue and receivables.
Reviewing the numerical sequence of pre-numbered shipping documents reinforces the test. Each number in the sequence should either tie to a recorded sale or be properly voided. A gap can represent an unbilled shipment caught somewhere between the warehouse and the accounting department.
Timing overlaps with cutoff testing near period end. A shipment that left on December 30 but was not invoiced until January 3 is a completeness problem for the year under audit. Auditors look closely at the last shipping documents before year-end and the first after, confirming each transaction landed in the correct period.
Tracing in Liabilities and Expenses
Liabilities and expenses are where completeness testing earns most of its attention. Management has an incentive to understate both: lower liabilities strengthen the balance sheet, and lower expenses inflate reported income.
The Search for Unrecorded Liabilities
The search for unrecorded liabilities is one of the most widely applied procedures in financial statement audits, and it is a tracing exercise focused on the period after the balance sheet date. The auditor reviews cash disbursements made in the weeks following year-end and asks, for each payment, whether it was for something the company received before the balance sheet date.
If a check written on January 15 pays for supplies delivered in November, the liability belonged on the December 31 balance sheet. The auditor traces the payment backward to the point the obligation was incurred. When that point falls before year-end, an adjustment is needed.
The same work covers vendor invoices arriving after year-end. The auditor checks the invoice dates and the related receiving reports. If the goods were in the warehouse before the books closed, a payable belongs in the prior year regardless of when the invoice showed up. Auditors also look for invoices sitting unopened or unentered on someone’s desk, because those are the most easily overlooked liabilities.
Vendor Confirmations
Confirming accounts payable balances directly with vendors adds independent evidence. External confirmations are generally more reliable than internal records alone, and auditing standards identify accounts payable as an area where confirmation procedures can test completeness.2Public Company Accounting Oversight Board. AS 2310 – The Auditor’s Use of Confirmation
The most useful confirmations target vendors showing a zero or unusually small balance. If a company regularly buys from a supplier but shows nothing owed at year-end, asking the vendor to confirm that balance can surface invoices the company never recorded. When vendors do not respond, auditors turn to alternative procedures: examining subsequent cash disbursements to that vendor, reviewing correspondence, or inspecting other supporting documentation.2Public Company Accounting Oversight Board. AS 2310 – The Auditor’s Use of Confirmation
Analytical Procedures and Cutoff Tests
Tracing and confirmations work at the transaction level. Analytical procedures work from a higher vantage point, scanning for patterns that suggest something is missing. Auditors develop expectations about what account balances should look like based on prior years, industry data, budgets, and relationships between financial and non-financial information, then investigate where the actual figures do not match.3Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
A significant unexplained drop in operating expenses versus the prior year could mean the company failed to record costs it actually incurred. The same logic applies to accrued liabilities that shrank without a business reason. These anomalies do not prove a completeness problem on their own, but they tell the auditor where to aim the detailed tracing work. When an explanation cannot be obtained, additional procedures are required to determine whether the difference is a misstatement.3Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
Cutoff testing targets timing directly. The auditor examines the last sequentially numbered receiving reports and shipping documents generated before year-end, along with the first after, to verify that each transaction fell in the correct period. Goods received on December 31 belong in year-end inventory and accounts payable. Goods shipped on December 31 belong in revenue and cost of goods sold. Pushing a receipt into January or pulling a January shipment back into December is a cutoff error that distorts completeness of the period under audit.
How Much Tracing Is Enough
Auditors do not trace the same number of documents in every engagement. Scope depends on the assessed risk of material misstatement for completeness in each significant account.4Public Company Accounting Oversight Board. AS 2301 – The Auditor’s Responses to the Risks of Material Misstatement Weak controls over recording, high transaction volume, manual entry, or problems in prior audits all push the sample size up.5Public Company Accounting Oversight Board. AS 2110 – Identifying and Assessing Risks of Material Misstatement
Materiality shapes the work too. Auditors set a materiality threshold for the financial statements as a whole, then determine a lower tolerable misstatement for individual accounts.6Public Company Accounting Oversight Board. AS 2105 – Consideration of Materiality in Planning and Performing an Audit A missing transaction below the tolerable misstatement is unlikely to prompt additional testing on its own, but qualitative red flags still matter. A small omission can matter if it masks a pattern or affects a sensitive line item.
When Completeness Testing Finds a Problem
Findings from tracing feed into the audit’s conclusions on both the financial statements and internal controls. If the external auditor identifies a material weakness in internal control, auditing standards require an adverse opinion on the company’s internal controls. The report must define what a material weakness is, identify it specifically, and describe its actual and potential effect on the financial statements. The auditor then determines whether the adverse opinion on internal controls affects the opinion on the financial statements themselves.7Public Company Accounting Oversight Board. AS 2201 – An Audit of Internal Control Over Financial Reporting
For public companies, Sarbanes-Oxley Section 404 requires management to assess the effectiveness of internal controls over financial reporting in the annual filing. A material weakness in the controls designed to ensure complete recording must be disclosed along with a remediation plan.8U.S. Securities and Exchange Commission. Sarbanes-Oxley Section 404 Costs and Remediation of Deficiencies That is why the tracing procedure, modest as it looks from the outside, carries so much weight in the audit file.