The existence and occurrence assertion is management’s claim that everything reported in the financial statements is real: assets and liabilities on the balance sheet actually exist at the reporting date, and transactions on the income statement actually happened during the period. Auditors group these two ideas together because they answer the same question from opposite sides of the ledger. Did the company record something that isn’t there?
Existence and Occurrence Are Two Halves of One Idea
Existence applies to balance sheet items. When management reports $2 million in cash, $800,000 in inventory, and $3 million in accounts receivable, existence means each of those balances corresponds to a real economic resource sitting in an identifiable place on the reporting date. Liabilities work the same way: a reported bank loan must trace back to an actual lending agreement with a real financial institution.1PCAOB. Auditing Standard No. 15 – Audit Evidence
Occurrence applies to transactions and events. Every recorded sale, expense, and journal entry should reflect something that genuinely took place and belongs to the reporting entity. If the company booked a $50,000 sale, occurrence means goods actually shipped or services were actually delivered to a real customer who agreed to the transaction.1PCAOB. Auditing Standard No. 15 – Audit Evidence
Existence and occurrence sit alongside four other assertion categories in professional auditing standards: completeness, valuation or allocation, rights and obligations, and presentation and disclosure. Each points the auditor in a different direction. Existence and occurrence handle one specific risk, and it is a big one.
Why the Assertion Is About Overstatement
Existence and occurrence exist to catch overstatement. The question is always whether something is in the records that shouldn’t be. That makes them the mirror image of completeness, which asks whether something is missing.
Companies under financial pressure have clear incentives to inflate what they own and what they earn. Inventory is a classic target because it sits in warehouses where outsiders rarely look, and the numbers can be large enough to move the picture of financial health. Cash balances can be fabricated through fictitious bank accounts. Receivables can be inflated by recording sales to customers who never agreed to buy anything. On the income statement, revenue is where the risk concentrates most heavily, because management teams facing earnings targets have historically found creative ways to book sales that don’t represent real economic activity. Expenses carry the opposite version of the same risk: fictitious payroll to funnel cash to insiders, or fabricated vendor payments that circle back to related parties.
Occurrence also has a timing dimension. A sale that genuinely happened on January 3 cannot be pulled back into December’s numbers. Recording transactions in the wrong period is called a cutoff error, and auditors watch closely around the end of each reporting period to catch it.
The testing technique that matches this overstatement direction is called vouching. The auditor starts with an entry already in the accounting records and works backward to the source documents that should support it. Pick a revenue entry from the sales journal, trace it back to a shipping document, a customer purchase order, and an invoice, and you have vouched. Finding all three confirms the transaction occurred. Finding nothing behind the entry is a red flag that it might be fictitious. Tracing runs the opposite way, following a source document forward into the books to catch things that happened but never got recorded, which tests completeness rather than occurrence. Vouching catches phantom entries. Tracing catches missing ones.
How Auditors Test Existence
Testing existence relies on evidence that comes from outside the company’s own records whenever possible. External evidence is harder to fabricate, which makes it more reliable.
Bank and Receivable Confirmations
For cash, auditors send confirmation requests directly to the company’s banks, asking the financial institution to verify account balances as of the balance sheet date. The auditor sends the request and receives the reply without the client handling either end of the communication.2PCAOB. AS 2310 – The Auditors Use of Confirmation
Accounts receivable follow a similar approach. The auditor contacts customers directly to ask whether they actually owe the amounts the company’s books say they owe. A positive confirmation asks the customer to respond regardless of whether they agree or disagree with the stated balance. A negative confirmation asks the customer to respond only if they disagree. Positive confirmations provide stronger evidence, because silence from a negative confirmation could mean the customer agrees, or it could mean the letter was never opened.2PCAOB. AS 2310 – The Auditors Use of Confirmation
Inventory Observation
Inventory is the one major asset class where auditors get physical. The standard approach requires the auditor to attend the company’s year-end inventory count, observe the counting procedures, and perform independent test counts of selected items. The auditor picks items from the warehouse floor and checks them against the count sheets, then picks items from the count sheets and locates them on the floor. This two-directional testing catches both phantom inventory (items on the list but not in the warehouse) and unrecorded inventory (items in the warehouse but not on the list).3PCAOB. Briefing Paper – Auditing Inventory
Document Inspection
For assets that cannot be confirmed externally or counted physically, auditors inspect the underlying legal documents. Property ownership is verified through deeds and title records. Debt obligations are confirmed by reviewing executed loan agreements. Investment holdings are traced to brokerage statements or custody confirmations. Intangibles such as patents, trademarks, and acquired goodwill get the same treatment through registration documents, licensing agreements, and original acquisition records.4PCAOB. AU Section 328 – Auditing Fair Value Measurements and Disclosures Evidence quality depends heavily on whether the documents originate outside the company.
How Auditors Test Occurrence
Occurrence testing centers on vouching: selecting recorded transactions and digging for the paperwork that proves they happened.
Vouching Transactions to Source Documents
The auditor pulls a sample of sales entries from the journal and traces each one back to supporting documents. For a product sale, the chain typically includes a customer purchase order, an internal shipping record proving the goods left the warehouse, and the sales invoice. If any link in that chain is missing or doesn’t match, the auditor investigates further. Revenue near the end of the reporting period gets extra scrutiny because that is where cutoff manipulation tends to cluster.
Sampling and Data Analytics
Auditors cannot test every transaction, so they rely on sampling. Statistical sampling gives every item in the population a known probability of selection and lets results be projected mathematically. Nonstatistical sampling uses professional judgment to pick items. Higher-risk accounts like revenue typically warrant larger sample sizes.
Technology has expanded the toolkit. Data analytics can scan an entire population of transactions for anomalies: journal entries posted on holidays or after the cutoff date, round-dollar amounts that suggest estimation rather than actual activity, or entries that bypass normal approval workflows. These flags do not prove a transaction is fictitious, but they help auditors focus detailed testing on entries most likely to be problematic. Many companies also run continuous monitoring systems that flag unusual activity in real time, which auditors can evaluate when assessing the control environment.
What It Looks Like When These Assertions Fail
The consequences are not abstract. Some of the largest corporate frauds in history were fundamentally about recording things that were not real.
- Wirecard (2020): The German payments company reported billions in cash balances held in trust accounts across Asia. When auditors finally demanded direct confirmation from the banks, the accounts did not exist. Wirecard had fabricated revenue streams through fake third-party partners and created backdated contracts to paper over the fiction. The company collapsed within days of the disclosure.
- Satyam Computer Services (2009): India’s fourth-largest IT company carried roughly $1 billion in cash on its balance sheet that simply was not there. The founder also created thousands of fictitious employees and pocketed their salaries, a scheme that violated both existence (the employees were not real) and occurrence (the payroll transactions never happened as described).
- Bristol-Myers Squibb (2004): The pharmaceutical company inflated sales by stuffing its distribution channels with excess inventory near the end of each quarter, booking about $1.5 billion in revenue from what the SEC alleged were essentially consignment arrangements that did not meet revenue recognition criteria. Bristol-Myers paid a $100 million civil penalty and funded a $50 million shareholder restitution fund.5SEC. Bristol-Myers Squibb Company Litigation Release
The common thread is entries with nothing behind them. Existence and occurrence testing is designed to catch exactly this problem before it reaches investors.
Management’s Legal Responsibility
These assertions are not just an auditing concept. Company executives bear direct legal responsibility for what their financial statements report.
Before the audit is finalized, management signs a formal representation letter confirming that the financial statements are fairly presented, that all financial records have been made available to the auditor, and that no material transactions were left unrecorded. The letter typically includes a specific representation that recorded receivables represent valid claims against actual customers. Those representations give the auditor a written record of management’s claims and create legal exposure if the claims turn out to be false.6PCAOB. AS 2805 – Management Representations
For public companies, the Sarbanes-Oxley Act requires the CEO and CFO to personally certify each quarterly and annual report, affirming that the statements fairly present the company’s financial condition and that the report contains no untrue statement of material fact. Knowingly certifying a false report carries criminal penalties of up to $1 million in fines and 10 years in prison; willful certification raises the maximum to $5 million and 20 years. The SEC also routinely bars executives from serving as officers or directors of public companies in fraud cases. Existence and occurrence are not just technical labels auditors use to organize their work. They are personal promises from the people running the company, backed by real legal consequences when those promises turn out to be lies.