If you're a US-based SaaS founder selling only in the US, you can probably stop reading. Your accounting framework is US GAAP, full stop.
But the moment your business does any of the following, the GAAP vs. IFRS question becomes real:
- You sign customers in Europe, the UK, Australia, or most of Asia
- You set up a foreign subsidiary or hire an international team
- You take investment from a non-US fund that needs IFRS reporting
- You're preparing for an exit involving an international acquirer
Here's the short version of what the two frameworks are, where they differ for SaaS companies, and what it means practically.
What each framework is
US GAAP (Generally Accepted Accounting Principles) is the standard used by US companies and required for any business filing with the SEC. It's rules-based — detailed, prescriptive, and specific.
IFRS (International Financial Reporting Standards) is used in 140+ countries including the EU, UK, Australia, Canada, and most of Asia. It's principles-based — broader guidelines that require more judgment in application.
Neither is "better." They're different operating systems for the same outputs.
The differences that actually matter for SaaS companies
Revenue recognition
Both frameworks now have similar rules under ASC 606 (GAAP) and IFRS 15 — they were intentionally converged. For a typical SaaS subscription, you'll recognize revenue ratably over the contract period under either.
Where it gets messy: multi-element contracts (software + implementation + support), variable consideration (usage-based pricing, refunds), and customer-specific modifications. The frameworks treat these similarly in principle but can produce different answers in edge cases.
Capitalized software development costs
This one trips up almost every SaaS company expanding internationally.
- GAAP has very specific rules for when internal-use software development costs can be capitalized (ASC 350-40). Generally: planning costs are expensed, application development costs may be capitalized, post-implementation costs are expensed.
- IFRS is broader (IAS 38). Development costs are capitalized when six specific criteria are met — including technical feasibility and intent to complete and use.
In practice, IFRS often allows more capitalization than GAAP. This means a company's reported expenses, EBITDA, and capitalized asset values can differ meaningfully between the two.
Lease accounting
Both ASC 842 (GAAP) and IFRS 16 brought leases onto the balance sheet, but they classify and present them differently:
- GAAP keeps the operating vs. finance lease distinction
- IFRS treats almost all leases as finance leases
For SaaS companies with office leases or significant equipment leases, this affects how the P&L looks — though cash impact is identical.
Foreign currency translation
If you have international entities, both frameworks require translating foreign subsidiary financials into the parent's reporting currency, but the methods and disclosures differ. Material differences usually show up in cumulative translation adjustments.
What this means practically
If you operate in both worlds, you have three options:
- Keep one set of books, reconcile to the other. Most common for US companies with a small international footprint. You maintain GAAP books and produce IFRS-equivalent reports for the foreign entity's local statutory filings.
- Maintain dual books. Necessary if you have significant operations under both frameworks or if investors require both sets of statements. More expensive but cleaner.
- Pick one and stick with it. If you're predominantly international and have no US reporting obligation, IFRS may make more sense as your primary framework.
When to bring in real help
The frameworks themselves aren't the hard part — the judgment calls are. Revenue recognition on a complex contract, deciding what dev costs qualify for capitalization, structuring intercompany transactions across borders — these are areas where a wrong answer compounds quietly until you're in due diligence and a deal team is asking questions you can't cleanly answer.
If you're operating across borders and your books haven't been pressure-tested by someone who knows both frameworks, that's exactly the kind of work I do.