Key takeaways
What this article covers, in order:
- How the standards group the assertions
- Assertions about transactions and events for the period
- Assertions about account balances at the period end
- Direction matters: existence versus completeness
- Worked example: testing a coffee roaster's year-end balances
- What to have ready for each assertion
Financial statement assertions are the claims management implicitly makes when it presents a set of accounts: that the transactions recorded happened, that nothing is missing, that amounts are right, that items fall in the correct period and accounts, and that the business owns its assets and owes its liabilities. Auditors design their tests around these assertions, so knowing them tells you exactly what evidence your auditor will ask for.
When you sign off a balance sheet showing receivables of 275,000, you are not saying only "this is the number". You are saying the customers exist, they owe the business that much, every amount owed is included, and the balance is stated at what you expect to collect. Each of those is a separate assertion, and each needs different evidence.
How the standards group the assertions
Three sets of auditing standards are in common use, and they slice the same ideas slightly differently.
- International Standards on Auditing (ISA 315, Revised 2019) — used in many countries. Two groups: assertions about classes of transactions and events for the period, and assertions about account balances at the period end, each with related disclosures.
- AICPA standards for US private companies (AU-C 315) — the same structure and essentially the same list as the ISA.
- PCAOB standards for US public companies (AS 1105) — five broader categories: existence or occurrence; completeness; valuation or allocation; rights and obligations; and presentation and disclosure. Accuracy and cut-off are not listed separately but are covered within those categories.
The auditing standards also allow auditors to express the assertions differently, as long as every aspect is covered. What matters is the question each one asks.
Assertions about transactions and events for the period
These apply to the income statement and to flows such as sales, purchases, payroll and cash receipts.
- Occurrence — the transactions recorded actually happened and relate to the business. Risk: fictitious sales, invented expenses.
- Completeness — every transaction that should have been recorded has been. Risk: unrecorded purchases or expenses.
- Accuracy — amounts and other data are recorded correctly. Risk: wrong prices, quantities or calculations.
- Cut-off — transactions are recorded in the correct accounting period. Risk: January sales booked in December.
- Classification — transactions are recorded in the proper accounts. Risk: a capital purchase posted to repairs, or the reverse.
- Presentation — transactions are appropriately aggregated or disaggregated and clearly described, and related disclosures are understandable.
Assertions about account balances at the period end
These apply to the balance sheet.
- Existence — the assets, liabilities and equity interests exist. Risk: receivables from customers who do not exist, inventory that is not there.
- Rights and obligations — the business holds or controls the rights to its assets, and its liabilities are its own obligations. Risk: goods held on consignment for someone else counted as your stock.
- Completeness — all assets, liabilities and equity interests that should be recorded are recorded. Risk: unrecorded supplier invoices, missing accruals, an omitted loan.
- Accuracy, valuation and allocation — balances are included at appropriate amounts, and valuation or allocation adjustments are properly recorded. Risk: no allowance for doubtful receivables, obsolete stock at full cost, wrong depreciation.
- Classification — balances are in the proper accounts, for example current versus non-current.
- Presentation — balances are suitably grouped and described, with the required disclosures.
Direction matters: existence versus completeness
The two assertions most often confused point in opposite directions. Existence and occurrence deal with overstatement: is something in the accounts that should not be? Completeness deals with understatement: is something missing?
That changes how auditors test. For existence, they start from the accounts and trace back to evidence: pick a receivable on the ledger and confirm it with the customer. For completeness, they start from outside evidence and trace into the accounts: take supplier invoices received or payments made after year end and check that the related liability was recorded. Because management is usually under pressure to show more assets and income, existence and occurrence are the main risks for assets and revenue, while completeness is the main risk for liabilities and expenses.
Worked example: testing a coffee roaster's year-end balances
A coffee roaster supplying cafés and grocery chains has a 31 December year end. Its draft balance sheet shows trade receivables of 275,000 and inventory of 410,000. Here is how its auditor maps assertions to tests, and what turns up.
Receivables: existence
The auditor sends confirmation requests to a sample of customers covering 190,000 of the 275,000 balance. All reply and agree, except one café chain that disputes an invoice for 4,200 for a delivery it says was never made. The roaster's own delivery records cannot show proof of delivery, so the invoice is reversed. Receivables fall to 270,800.
Revenue: cut-off
The auditor examines dispatch notes for the last five days of December and the first five days of January. One shipment worth 18,000 left the warehouse on 2 January but was invoiced and recorded as revenue on 30 December. Under the roaster's terms, the customer gains control on delivery, so the sale belongs to the new year. Revenue and receivables are both reduced by 18,000, and the coffee returns to inventory at its cost of 11,500. Receivables are now 252,800.
Receivables: valuation
The aged receivables listing shows 22,000 more than 90 days overdue, mostly from one grocery chain in financial difficulty. Management had made no allowance. After discussion, it records an allowance of 50% of that amount, or 11,000, based on the chain's payment plan. Net receivables are 252,800 − 11,000 = 241,800.
Inventory: rights and obligations, and valuation
The stock count found 9,000 of green beans that the roaster is storing for another roaster under a warehousing arrangement. Those beans are not the roaster's assets, so they come out. Separately, 6,500 of a seasonal blend past its best-before date is written down to an estimated net realisable value of 1,500, a reduction of 5,000. Inventory becomes 410,000 + 11,500 − 9,000 − 5,000 = 407,500.
Liabilities: completeness
The auditor reviews supplier invoices received and payments made in January. A freight bill of 3,400 for December deliveries was not recorded until January. It is accrued at year end, increasing liabilities and expenses for the year.
Every adjustment traced back to a specific assertion. That is the practical value of the framework: it tells the auditor where to look and tells you which records to have ready.
What to have ready for each assertion
- Existence and occurrence — signed delivery notes, customer contracts, bank statements, stock count sheets, fixed asset tags.
- Completeness — a list of supplier invoices received after year end, accruals workings, loan statements, a clean bank reconciliation.
- Accuracy and valuation — price lists, aged receivables and payables, depreciation schedules, stock valuation and obsolescence reviews.
- Cut-off — dispatch and receiving records around the year end, sequential invoice numbers.
- Rights and obligations — purchase invoices and title documents for major assets, consignment and warehousing agreements, loan and lease agreements.
- Classification and presentation — your chart of accounts mapping and the workings for current versus non-current splits.
hellobooks< / a > -helps-you-support-the-assertions">How HelloBooks helps you support the assertions
HelloBooks keeps the records auditors use as evidence in one place. Sales invoices, bills, purchase orders and goods receipt notes are linked, so occurrence and cut-off can be checked against dispatch and receipt dates. AR and AP aging reports support valuation reviews, bank reconciliation supports existence of cash and completeness of payments, and the fixed assets register calculates straight-line or WDV depreciation for each asset.
Period-end closing tools help you post accruals, prepayments and depreciation; journal entries can require approval; period locking prevents changes after close; and the audit trail shows who recorded or edited each entry and when. The auditor still forms their own view, but you spend less time searching for documents.
