A completeness audit tests whether every transaction, asset, liability, and disclosure that belongs in the financial statements actually made it in. Auditors do this by working outside-in: they start with evidence of real-world activity (a receiving report, a signed contract, a bank statement, a lawyer’s letter) and trace it forward into the books, because that is the only direction that can catch what isn’t there. The procedures are targeted, not exhaustive, and they concentrate on the accounts where omission is most tempting or most likely: liabilities, expenses, accruals, cutoffs, and footnote disclosures.
What Management Is Claiming
When management issues financial statements, it implicitly claims that everything belonging in those statements has been recorded.1PCAOB. AS 1105: Audit Evidence That claim is the completeness assertion, and it runs across all three assertion categories: classes of transactions during the period, account balances at period end, and presentation and disclosure in the notes.
The core risk is omission. A vendor invoice received on December 28 but never entered in the system understates accounts payable, understates cost of goods sold, and inflates reported profit. A pending lawsuit left out of the footnotes hides a contingent obligation from investors. Both are completeness failures, and both make the picture look better than reality. Because management sometimes has an incentive to omit unfavorable items, auditors treat completeness as a high-risk assertion for liabilities and expenses in particular.
Not every gap becomes an audit finding. Auditors evaluate omissions against a materiality threshold: the dollar amount below which a misstatement would not change a reasonable investor’s decision. The PCAOB requires the auditor to consider both quantitative size and qualitative factors when setting that threshold, and small omissions can still be material if the circumstances are sensitive (a related-party transaction, for example).2PCAOB. AS 2105: Consideration of Materiality in Planning and Performing an Audit
Why the Direction of Testing Matters
Completeness and existence are mirror-image assertions. Existence asks whether recorded items are real; completeness asks whether real items are recorded. One guards against overstatement, the other against understatement. The distinction dictates which way the auditor’s testing physically runs.
To test existence, auditors use vouching: pick an entry from the ledger, trace it backward to the source document, and confirm it is supported. To test completeness, auditors reverse that direction and use tracing: pick a source document that represents a real economic event, and follow it forward into the journals and general ledger.1PCAOB. AS 1105: Audit Evidence Starting from the ledger can only confirm what is already there. Starting from real-world evidence is the only way to catch what isn’t.
The design principle follows from this. The starting population for a completeness test must be independent of the accounting records being tested. If you want to know whether all purchases were recorded, you don’t start from the purchases journal, because anything missing from that journal is invisible to it. You start from the receiving dock, the vendor files, or the purchase orders.
The Core Procedures
Tracing From Source Documents
Tracing is the workhorse. The auditor pulls a sample of source documents (receiving reports, shipping documents, signed contracts, time cards) and follows each one through the accounting system to confirm it was recorded in the right account, in the right amount, in the right period. For purchases, that means confirming each receiving report has a matching entry in inventory and accounts payable. For payroll, it means confirming that hours worked or salaried employment translated into payroll register entries.
Sequence Checks on Pre-Numbered Documents
Many accounting systems use pre-numbered checks, invoices, shipping documents, and receiving reports. The auditor reviews these sequences for gaps. If shipping documents run 4501 through 4600 but 4573 is missing, the auditor investigates whether a shipment occurred without a corresponding revenue entry. This only works when the company actually maintains disciplined control over its numbering, which is itself a control the auditor evaluates.
Analytical Procedures
Analytical procedures compare current-period balances and ratios against prior periods, budgets, or industry benchmarks to flag unexpected relationships. If revenue grew 20% but cost of goods sold barely moved, something is probably missing from inventory costs. The PCAOB recognizes that expected figures can also be developed from non-financial data (production statistics, selling square footage) and compared against recorded amounts, with any shortfall pointing to a completeness problem.1PCAOB. AS 1105: Audit Evidence Analytics rarely prove an omission on their own, but they are effective at pointing the auditor toward the accounts worth digging into.
Cutoff Testing
Cutoff testing targets transactions right around the balance sheet date, where the risk of recording activity in the wrong period is highest. The auditor selects shipping documents, receiving reports, and invoices from the last days of the reporting period and the first days of the next, then confirms each transaction landed in the correct period. A shipment that left the warehouse on December 30 should appear as December revenue; one that left on January 2 belongs in January.
Sample size depends on the auditor’s risk assessment, the tolerable misstatement for the population, and the expected frequency of errors.3PCAOB. AS 2315: Audit Sampling A company with weak controls over its closing process, or a history of cutoff errors, warrants more testing than one with a documented, consistent process.
Errors can go either direction. Recording next-period revenue early overstates current income. Deferring current-period expenses into the next period achieves the same result. Auditors examine both sides because either manipulation produces a better-looking current period at the expense of an accurate one.
The Search for Unrecorded Liabilities
This is the single most important completeness procedure on most audits. The search for unrecorded liabilities targets obligations that existed at the balance sheet date but never made it into the books. The technique works by examining cash disbursements made after year-end and tracing each payment back to determine when the underlying obligation actually arose. If a check issued in January pays for goods received in December, the liability and expense belong in the prior year and need an adjusting entry.
The auditor also reviews vendor statements and files of unpaid invoices, comparing them against the accounts payable ledger to identify anything absent. Invoices arriving in the first few weeks after year-end deserve particular scrutiny, because they often relate to goods or services delivered before the cutoff date. Sampling from subsequent cash disbursements is the standard scope, because that population is where omitted obligations most reliably surface.
Omitting liabilities cascades through the statements. It understates total debt, which makes leverage ratios look healthier than they are. It also understates expenses, inflating net income. For any lender or investor relying on those numbers, the distortion can be significant, which is why auditors spend a disproportionate share of their completeness effort here.
Accrued Expenses and Unbilled Revenue
Accrued expenses are costs incurred but not yet invoiced or paid: payroll earned by employees in the final days of December, interest accumulating on outstanding debt, professional fees for ongoing engagements. Because no invoice triggers the recording process, these items depend on management deliberately estimating and booking them. The auditor independently recalculates the accruals from the underlying contracts, pay rates, and time periods to confirm the full obligation was captured.
Revenue completeness runs the other direction. If a service provider finishes a project phase before year-end but doesn’t issue the invoice until January, the earned revenue still belongs in the current period. Failing to record it understates both revenue and the corresponding receivable (sometimes called a contract asset or unbilled revenue). The auditor reviews contracts and project documentation to confirm earned-but-unbilled amounts are recognized at period end.
Inventory: Floor to Sheet
During a physical inventory count, auditors apply the same directional principle. Floor-to-sheet testing means selecting items from the physical warehouse floor and confirming each appears on the count sheets. Anything physical that never made the sheet is an unrecorded asset. The companion procedure, sheet-to-floor, works in reverse and tests existence. Floor-to-sheet should generally come first, because an auditor who has already handled and located items during sheet-to-floor may inadvertently double-count when switching direction.
Completeness of Disclosures and Attorney Letters
Completeness extends past the numbers on the face of the statements to the footnotes. Contingent liabilities from pending lawsuits, debt covenants, related-party transactions, and financial guarantees all require disclosure under GAAP, and an auditor who confirms every dollar amount on the balance sheet can still miss a material omission in the notes.
For litigation and claims, the primary tool is the attorney inquiry letter. The auditor asks the company to send a letter to its outside counsel requesting a description of all pending or threatened litigation, an assessment of the likelihood and potential amount of loss, and confirmation of any unasserted claims the lawyer believes are probable of being asserted.4PCAOB. AS 2505: Inquiry of a Client’s Lawyer Concerning Litigation, Claims, and Assessments The lawyer’s response should cover a date as close as possible to the date of the auditor’s report, and auditing interpretations suggest a two-week window between the effective date of the lawyer’s review and the date the response is due.5PCAOB. AI 17: Inquiry of a Client’s Lawyer Concerning Litigation, Claims, and Assessments: Auditing Interpretations of AS 2505
The attorney letter is one of the few places where a third party independently corroborates what management says about completeness. Any limitation on the lawyer’s response, or a refusal to respond at all, is a red flag the auditor cannot ignore.
Management Representation Letters
Near the end of every audit, management signs a formal representation letter to the auditor. It includes explicit statements about completeness: that all financial records and related data have been made available, that all minutes of stockholder and director meetings are complete and accessible, and that there are no material unrecorded transactions or undisclosed side agreements.6PCAOB. AS 2805: Management Representations
The letter does not substitute for testing. An auditor who relies on management’s written assurance that everything has been recorded has not performed an audit. The letter pins management to specific claims that create accountability if omissions are later discovered. If management refuses to sign, or qualifies a representation, that is a scope limitation that may prevent an unqualified opinion.
Completeness in IT Systems
Most companies process transactions through interconnected software rather than paper journals, and data can be lost or excluded during input, processing, or transfer between systems. Auditors address this by testing both the IT application controls that govern data flow and the reliability of reports produced by those systems.
When an auditor uses a report generated by the company’s own systems as audit evidence, the report is called information produced by the entity, or IPE. Before relying on any IPE, the auditor must test its accuracy and completeness, or test the controls that ensure both.1PCAOB. AS 1105: Audit Evidence An accounts payable aging report that quietly omits a subsidiary’s transactions is worse than useless; it actively hides the problem the auditor is looking for.
Application controls supporting completeness include batch totals that sum numerical data before and after processing to catch dropped transactions, sequential numbering controls that flag gaps in automated document sequences, and reconciliation procedures that match data between systems or against source records. For electronic transfers between trading partners, interface controls verify that orders, invoices, and payments transmitted electronically arrive complete and unaltered. The auditor evaluates whether these controls were designed effectively and tests whether they operated consistently during the period.
How Materiality Drives Sample Sizes
Auditors do not test every transaction. They concentrate effort where omissions are most likely to exceed materiality and where the consequences of a missed omission would be most significant. The PCAOB requires auditors to consider whether certain accounts or disclosures could be materially misstated at amounts lower than overall materiality, especially where qualitative factors heighten investor sensitivity.2PCAOB. AS 2105: Consideration of Materiality in Planning and Performing an Audit
Sample sizes flow from these judgments. Tolerable misstatement for a given population, assessed risk of material misstatement, and expected frequency of errors all factor in.3PCAOB. AS 2315: Audit Sampling A high-risk account with weak controls gets a larger sample. A low-risk account with strong automated controls and clean prior-year results may need only targeted testing. New information mid-audit (a regulatory change, a significant contract, a lawsuit filed after planning) can force the auditor to revisit these levels and expand completeness testing in areas that initially looked low-risk.
Consequences of Getting It Wrong
Inadequate completeness testing has real consequences. The PCAOB regularly sanctions auditors who fail to obtain sufficient evidence. In a 2024 enforcement action, the Board censured three auditors for failures relating to audit evidence and professional skepticism, imposing civil penalties totaling $130,000 and barring two engagement partners from practice with a right to petition for reinstatement after two years.7Public Company Accounting Oversight Board. PCAOB Sanctions Three Auditors for Failures Relating to Audit Evidence, Skepticism, and Other Violations
Companies face parallel exposure. In fiscal year 2024, the SEC obtained $8.2 billion in total financial remedies, including $2.1 billion in civil penalties, with particular focus on material misstatements and gatekeeper failures. In one case, the managing partner of an audit firm was permanently barred from practicing before the Commission and agreed to pay a $2 million civil penalty.8U.S. Securities and Exchange Commission. SEC Announces Enforcement Results for Fiscal Year 2024 The financial and reputational damage from a missed completeness failure typically dwarfs the cost of doing the work correctly the first time.