ISA 450 · Technology

Misstatement Tracker
for Technology

Accumulate misstatements across SaaS revenue recognition, capitalised development costs, share-based payment accounting, and intangible asset impairment. Configured for the estimate-heavy nature of technology audits.

Materiality thresholds

Enter the materiality levels from your planning documentation. The clearly trivial threshold auto-suggests at 5% of performance materiality.

Misstatements

#1

Export as working paper PDF

Download a formatted ISA 450 evaluation summary. Enter your email to unlock the PDF export. Plus one practical audit insight per week.

No spam. We're auditors, not marketers.

ISA 450.5: The auditor shall accumulate misstatements identified during the audit, other than those that are clearly trivial.

ISA 450.10: The auditor shall communicate on a timely basis all misstatements accumulated during the audit with the appropriate level of management.

ISA 450.11: The auditor shall determine whether uncorrected misstatements are material, individually or in aggregate.

Need production-ready working papers?

Built by a practicing auditor · 14-day money-back guarantee · Free updates when standards change

ISA 450 misstatement evaluation for Technology

Technology company audits are dominated by accounting estimates, and accounting estimates produce judgmental misstatements. Revenue recognition for multi-element SaaS contracts, capitalisation of development costs under IAS 38, impairment testing of intangible assets, and share-based payment valuations under IFRS 2 all involve management assumptions that the auditor needs to evaluate. When the auditor's assessment of a reasonable range for any of these differs from management's selected point, the difference is a misstatement under ISA 450.A1. A single technology audit can produce ten or more judgmental misstatements before you even look at a bank reconciliation. The tracker organises these by financial statement area so you can see whether the aggregate skews in one direction.

ISA 450.8 requires the auditor to communicate misstatements with management and request correction. In technology companies, this communication often becomes a negotiation because management's accounting policies involve genuine judgment calls. Consider capitalised development costs: IAS 38.57 sets six criteria that must all be met before capitalisation begins. Management might argue that a project met the "technical feasibility" criterion in March; the auditor might see evidence that feasibility was only demonstrated in June. The three months of capitalised salary costs between March and June represent a judgmental misstatement. The tracker records both the auditor's position and management's response, which you need for the ISA 450.12 communication with those charged with governance.

Revenue recognition misstatements in technology audits tend to cluster around four areas. First, identifying performance obligations in bundled contracts (software licence, implementation services, post-contract support, hosting). Second, determining the standalone selling price for each obligation when the company does not sell the components separately. Third, applying the correct timing of revenue recognition (over time vs. at a point in time) for implementation services. Fourth, estimating variable consideration for contracts with usage-based pricing or performance bonuses. Each of these involves judgment, and each produces misstatements when the auditor's assessment differs from management's. The tracker lets you map each misstatement to the specific IFRS 15 step where the disagreement arises, which makes the ISA 450.12 communication more precise.

Share-based payment accounting under IFRS 2 creates a particular accumulation challenge because the misstatements are often small in each period but compound over the vesting period. If management uses a Black-Scholes model with a volatility assumption that the auditor considers 3% too low, the resulting understatement of the share-based payment expense affects every period over the vesting term. ISA 450.A4 requires you to consider the carry-forward effect. A €30,000 annual understatement across a four-year vesting period is a €120,000 cumulative misstatement in equity. Record the current-period effect and the estimated cumulative effect separately so your ISA 450.11 evaluation captures the full picture.

Frequently asked questions: Technology

How should I evaluate misstatements in SaaS revenue recognition under IFRS 15?
Map each misstatement to the IFRS 15 five-step model. Step 2 (identifying performance obligations) and Step 4 (allocating the transaction price) produce the most misstatements in SaaS audits. When management bundles software, implementation, and support into a single performance obligation but the auditor identifies them as separate, the reallocation of the transaction price creates misstatements in both the current period and future periods through the deferred revenue balance.
Is an incorrect capitalisation start date for development costs a misstatement?
Yes. If the auditor concludes that management began capitalising costs before all six IAS 38.57 criteria were met, the costs capitalised prematurely should have been expensed. The misstatement equals the capitalised amount for the period between management's start date and the date the auditor considers the criteria were met, less any amortisation already charged.
How do I handle misstatements in share-based payment expense calculations?
Identify whether the misstatement comes from the valuation model inputs (volatility, risk-free rate, expected term) or from the service/performance condition assessment (expected forfeiture rate, probability of performance conditions being met). Track input-related misstatements separately because they affect the fair value of every grant using those inputs, while condition-related misstatements are grant-specific.
What materiality considerations apply to technology companies with losses?
When the entity is loss-making, profit before tax is not a suitable benchmark for materiality. ISA 320.A4 suggests alternative benchmarks including total revenue, total assets, or total expenses. For SaaS companies, recurring revenue is often the most stable benchmark. Set overall materiality as a percentage of recurring revenue (typically 0.5% to 2%) and derive performance materiality and clearly trivial from there.

Related industry guides

General Tracker