The audit technique used to test the completeness assertion is tracing. An auditor selects source documents that represent real economic events—shipping records, receiving reports, vendor invoices, remittance advices—and follows each one forward into the journals, subsidiary ledgers, and general ledger. If the trail goes cold before the transaction reaches the books, an unrecorded item has been found. That forward direction is what makes tracing the right tool: completeness is about detecting what’s missing, and you can only detect an omission by starting outside the accounting records and working in.
What the Completeness Assertion Covers
When management issues financial statements, they make several implicit claims about the numbers. Auditing standards group these into assertions: existence or occurrence, completeness, valuation, rights and obligations, and presentation and disclosure.1Public Company Accounting Oversight Board. PCAOB Auditing Standards – AS 1105 Audit Evidence
Completeness addresses a specific risk: that transactions, accounts, or disclosures that should appear in the financial statements were left out.1Public Company Accounting Oversight Board. PCAOB Auditing Standards – AS 1105 Audit Evidence The concern is understatement. If a company received goods before year-end but never booked the payable, liabilities are too low. If shipments went out the door but nobody recorded the sale, revenue is understated. Every other assertion looks at what’s already in the records and asks whether it’s right. Completeness flips the question: is anything missing? That difference drives how the testing has to be designed.
Tracing Versus Vouching
Auditors use two directional testing methods, and they are easy to confuse because they touch the same documents. The direction is what separates them.
Vouching starts with an entry already sitting in the general ledger and works backward to the underlying source document. The goal is to confirm that a recorded transaction actually happened, which tests existence or occurrence. If you pick a journal entry and can’t find a shipping document, invoice, or contract behind it, you may have a fictitious transaction.
Tracing works in the opposite direction. It starts with a source document created outside the accounting system and follows it forward into the ledger. If a receiving report proves goods arrived, there should be a matching entry in accounts payable. If a shipping document proves goods left the warehouse, a sale should appear in revenue.1Public Company Accounting Oversight Board. PCAOB Auditing Standards – AS 1105 Audit Evidence
The reason this works for completeness is that source documents exist independently of the accounting records. A receiving report gets created when goods physically arrive. A bill of lading gets generated when a carrier picks up a shipment. These documents capture economic reality. By starting from that reality and testing whether it made it into the books, the auditor can detect omissions that would be invisible if only the recorded entries were examined.
Tracing in the Revenue Cycle
The revenue cycle is where completeness and occurrence risks pull in opposite directions. Occurrence risk is about whether recorded sales really happened, which vouching handles. Completeness risk is about whether real sales went unrecorded, and tracing is the tool to find them.
The auditor selects a sample of shipping documents or bills of lading generated near year-end. Each document is traced forward to the corresponding sales invoice, then to the sales journal, and finally to the accounts receivable subsidiary ledger. If a shipping document has no matching entry anywhere in the revenue records, an unrecorded sale has been identified, understating both revenue and receivables.
Reviewing the numerical sequence of pre-numbered shipping documents adds another layer. Every number in the sequence should either tie to a recorded sale or be properly voided. A gap could represent an unbilled shipment sitting between the warehouse and the accounting department.
Near the period end, this testing overlaps with cutoff concerns. A shipment that left on December 30th but wasn’t invoiced until January 3rd creates a completeness problem in the year under audit. Auditors pay close attention to the last shipping documents before year-end and the first ones after, to make sure each transaction landed in the correct period.
Tracing for Liabilities and Expenses
Liabilities and expenses are where completeness testing earns its keep. Management has a natural incentive to understate these accounts: lower liabilities make the balance sheet look stronger, and lower expenses inflate reported income. Auditors are most skeptical about what might be missing here.
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 fundamentally 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 a simple question about each payment: was this for something the company received before the balance sheet date?
If a check written on January 15th pays for supplies delivered in November, the liability should have appeared on the December 31st balance sheet. The auditor traces that payment backward to pinpoint when the obligation was actually incurred. When the answer is “before year-end,” the company needs to record an adjustment.
The same review covers vendor invoices that arrived after year-end. Auditors check the dates on the invoices 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. Invoices sitting in someone’s in-tray that haven’t been entered into any system yet get particular attention, because those are the most easily overlooked liabilities.
Vendor Confirmations
Confirming accounts payable balances directly with vendors provides independent evidence of completeness. External confirmations are generally more reliable than internal records alone, and auditing standards specifically 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 telling 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 can surface invoices the company never recorded. A vendor who responds with “actually, you owe us $85,000” has just revealed a completeness failure that internal testing alone might have missed. When vendors don’t 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 Testing
Tracing and confirmations are direct, transaction-level tests. Analytical procedures work from a higher altitude, scanning for patterns that suggest something is missing. Auditors develop expectations about account balances based on prior years, industry data, budgets, and relationships between financial and non-financial information, then investigate where reality doesn’t match.3Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
A significant unexplained drop in operating expenses compared to the prior year, for instance, could mean the company failed to record costs it actually incurred. The same logic applies to accrued liabilities that shrank without an obvious business reason. These anomalies don’t prove a completeness problem by themselves, but they tell the auditor where to aim the detailed tracing work. When an explanation can’t be obtained, additional procedures are required to determine whether the difference represents a misstatement.3Public Company Accounting Oversight Board. AS 2305 – Substantive Analytical Procedures
Cutoff testing zeroes in on timing. The auditor examines the last several sequentially numbered receiving reports and shipping documents generated before year-end, along with the first several after, to verify that each transaction landed in the correct period. Goods received on December 31st belong in year-end inventory and accounts payable. Goods shipped on December 31st should appear in revenue and cost of goods sold. Pushing a receipt into January or pulling a January shipment into December creates a cutoff error that directly affects completeness of the period under audit.
What Sample Size Depends On
Auditors do not trace the same number of documents in every engagement. The scope depends on the assessed risk of material misstatement for the completeness assertion in each significant account.4Public Company Accounting Oversight Board. AS 2301 – The Auditor’s Responses to the Risks of Material Misstatement When internal controls over the recording process are weak or an account is particularly susceptible to misstatement, the auditor needs more persuasive evidence, which usually means tracing a larger sample.
An account with heavy transaction volume processed through manual entry carries more completeness risk than one fed by automated matching systems.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 statements as a whole and a lower tolerable misstatement amount for individual accounts.6Public Company Accounting Oversight Board. AS 2105 – Consideration of Materiality in Planning and Performing an Audit Small omissions below that threshold don’t automatically trigger more testing, though qualitative red flags can still push the auditor to dig deeper.
Consequences of Completeness Failures
When tracing reveals that a company’s controls failed to capture real transactions, the consequences reach beyond a few adjusting entries. When the external auditor identifies a material weakness in internal control, auditing standards require an adverse opinion on the company’s internal controls. The auditor’s report must define what a material weakness is, identify it specifically, and describe its actual and potential effect on the financial statements. The auditor must then determine whether the adverse internal control opinion also 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 also requires management to disclose the weakness and lay out a remediation plan in the annual filing.8U.S. Securities and Exchange Commission. Sarbanes-Oxley Section 404 Costs and Remediation of Deficiencies