The same business, the same year, the same transactions — and two different profit figures, both prepared correctly. That is what happens when one set of books follows US GAAP and the other follows IFRS. If you ever take on a foreign investor, open a subsidiary abroad, get acquired by an overseas buyer, or list on a foreign exchange, someone will ask you to translate your numbers from one rulebook to the other. The differences below are where that translation hurts most, and knowing them now saves you from restating years of history later.
GAAP and IFRS in One Paragraph
US GAAP (Generally Accepted Accounting Principles) is the rulebook for financial reporting in the United States, set by the Financial Accounting Standards Board (FASB). Every US public company must use it, and most lenders and investors expect it from private companies too. IFRS (International Financial Reporting Standards) is set by the International Accounting Standards Board (IASB) and is required or permitted in more than 140 jurisdictions, including the EU, UK, Canada, Australia, and Japan. The US is the notable holdout: the SEC lets foreign companies listed in the US file in IFRS, but domestic US companies must stick with GAAP.
The two frameworks share the same goal — financial statements investors can trust — but different philosophies. GAAP is rules-based: detailed guidance for specific situations, with bright lines and industry-specific rules. IFRS is principles-based: broader standards that leave more to professional judgment. That philosophical gap is why convergence efforts narrowed the differences but never closed them.
Why Two Rulebooks Still Exist
The FASB and IASB spent most of the 2000s trying to merge the frameworks. The 2002 Norwalk Agreement launched joint projects that genuinely converged two of the biggest standards — revenue recognition (ASC 606 and IFRS 15, both effective 2018) and, to a lesser degree, lease accounting (ASC 842 and IFRS 16). For a while, full US adoption of IFRS looked plausible; the SEC even published a roadmap for it in 2008.
Then momentum died. The SEC never pulled the trigger, the financial crisis redirected everyone's attention, and the boards quietly went back to setting standards separately. Today convergence is best described as frozen: revenue is largely aligned, leases are superficially similar but mechanically different, and topics like inventory, R&D, and asset revaluation were never converged at all. Plan as if both frameworks are permanent.
Revenue: Mostly Converged, Details Differ
Revenue recognition is the success story. ASC 606 and IFRS 15 share the same five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate the price to obligations, and recognize revenue as each obligation is satisfied. If your business sells straightforward products and services, your revenue number will be the same under either framework.
The remaining differences live in edge cases, but edge cases are where audits happen:
- Collectibility threshold. Both standards require it to be "probable" you will collect before you recognize revenue — but "probable" means different things. Under IFRS it means more likely than not (over 50 percent). Under GAAP it carries its traditional US meaning of likely to occur, a notably higher bar. A shaky contract that clears the IFRS threshold can fail the GAAP one.
- Licenses and intellectual property. The guidance on whether a license grants a right to use IP (recognize at a point in time) or a right to access it (recognize over time) differs in emphasis, and GAAP adds industry-specific implementation guidance IFRS lacks.
- Practical expedients. GAAP offers relief valves IFRS does not, such as the policy election to treat shipping and handling as a fulfillment cost rather than a separate performance obligation.
For most small businesses, the practical takeaway is simple: if you recognize revenue correctly under ASC 606, an IFRS reader will follow your numbers without serious adjustment.
Inventory: LIFO Is the Big One
Inventory is where the two frameworks openly contradict each other, and the contradiction has real tax consequences.
LIFO is allowed under GAAP and banned under IFRS. Last-in, first-out lets a US company assume its newest, most expensive inventory sold first, which raises cost of goods sold and lowers taxable income when prices rise. IAS 2 permits only FIFO and weighted-average cost. A US manufacturer using LIFO that gets acquired by a European group must unwind years of LIFO layers and restate to FIFO — a conversion that typically increases reported inventory and creates a deferred tax adjustment, all computed from records you hopefully kept.
Write-down reversals go opposite ways too. Both frameworks require writing inventory down when it loses value. But if the market recovers, IFRS lets you reverse the write-down back up (never above original cost), while GAAP treats the written-down value as the new cost basis permanently. Under GAAP, the recovery shows up only when you sell the goods; under IFRS, it can flow back into profit earlier.
The rule of thumb: GAAP is more conservative on inventory recoveries and more permissive on cost-flow assumptions. If there is any chance your company will one day report under IFRS, track FIFO-equivalent inventory values alongside your LIFO books from the start.
Leases: One Model vs Two
Both frameworks now put leases on the balance sheet — the old days of hiding operating leases in footnotes ended with ASC 842 and IFRS 16. But they disagree on what happens after that.
GAAP keeps two models for lessees. Every lease is classified as either a finance lease or an operating lease. Both create a right-of-use asset and a lease liability, but an operating lease produces a single straight-line lease expense in operating costs, while a finance lease splits into depreciation plus interest, front-loading the total expense into the early years.
IFRS uses a single model. With narrow exemptions for short-term leases (12 months or less) and low-value assets, every lease is accounted for like a finance lease: depreciation plus interest, front-loaded expense, period.
Three consequences follow:
- EBITDA looks higher under IFRS. Depreciation and interest sit below the EBITDA line, while GAAP's straight-line operating lease expense sits above it. Two identical companies with identical leases report different EBITDA purely because of the framework.
- Cash flow statements classify differently. Under GAAP, operating lease payments are operating cash outflows. Under IFRS, the interest portion can go to operating or financing and the principal portion to financing, which flatters operating cash flow.
- Exemptions differ. IFRS explicitly exempts low-value assets (laptops, small office equipment); GAAP has no equivalent low-value exemption, only the short-term lease policy election by asset class.
If you sign multi-year office or equipment leases, keep a lease schedule detailed enough to run both calculations — payment streams, renewal options, discount rates — rather than whatever single number your current framework asks for.
Development Costs: Expense vs Asset
This is the difference that most changes how a technology or product company looks on paper.
Under GAAP, research and development is generally expensed as incurred (ASC 730). The money you spend building a product hits the income statement immediately and never appears as an asset, with narrow exceptions — most notably software development costs once technological feasibility is established (ASC 985-20) and certain internal-use software costs (ASC 350-40).
Under IFRS, development costs are capitalized once six criteria are met (IAS 38): technical feasibility, intent to complete, ability to use or sell, a demonstration of future economic benefit, adequate resources to finish, and reliable measurement of the spending. Research-phase spending is still expensed under both frameworks; the split happens at the research-development boundary.
The effect is dramatic. A startup that spends $2 million developing a product shows $2 million of expense and no asset under GAAP. Under IFRS, much of that $2 million can sit on the balance sheet as an intangible asset, amortized over future years — higher current profit, higher assets, and a completely different story for lenders. Neither treatment is wrong; they reflect different judgments about when uncertain spending becomes a probable future benefit. But if you report under one framework and pitch investors accustomed to the other, expect hard questions, and document exactly where your research phase ended and development began.
The Differences That Bite in Practice
Beyond the big four, a handful of smaller gaps regularly surprise companies the first time they cross frameworks:
- Revaluing property and equipment. IFRS (IAS 16) lets you carry fixed assets at fair value, with increases going to other comprehensive income. GAAP requires historical cost less depreciation, full stop. An IFRS balance sheet can show a factory worth far more than it cost; a GAAP one never will.
- Impairment reversals. IFRS permits reversing most asset impairments (except goodwill) when conditions improve. GAAP prohibits reversals for assets held and used. Like inventory write-downs, GAAP locks in bad news permanently.
- Contingencies. Both frameworks book a liability when a loss is probable and estimable, but "probable" again means more-likely-than-not under IFRS and likely-to-occur under GAAP — so IFRS books uncertain liabilities earlier.
- Debt classification. Under GAAP, long-term debt that violates a covenant becomes current unless you obtain a waiver. IFRS historically applied a stricter test tied to rights existing at the reporting date (recently clarified by amendments to IAS 1, but the mechanics still differ in edge cases).
None of these will matter to every business, but each of them has forced at least one company into an expensive restatement. When in doubt, ask your CPA which framework your readers expect before you close the year, not after.
What This Means for Your Books
Most US small businesses should simply use GAAP — or, if their lender allows it, an income-tax basis or another simplified framework — and not think about IFRS day to day. But structure your records so a conversion is possible, because the need usually arrives suddenly: a foreign acquirer, an overseas subsidiary, a cross-border loan.
Four habits make you conversion-ready:
- Keep inventory records that support FIFO, even if you use LIFO for US tax purposes. The LIFO reserve — the gap between your LIFO and FIFO values — should be computable every year, not reconstructed from memory.
- Separate research spending from development spending as you incur it, with dated evidence of feasibility milestones. Retroactively drawing that line for IAS 38 is guesswork an auditor will challenge.
- Maintain a real lease register with full payment schedules, renewal and termination options, and the discount rate used. Both frameworks need this data; neither accepts a single annual rent figure as a substitute.
- Document judgments in writing. IFRS runs on professional judgment — why a cost was capitalized, why a liability was probable — and judgment without a paper trail does not survive an audit or a buyer's due diligence.
One more practical note: book-to-tax differences already force you to track two versions of reality (your GAAP books and your tax return). Adding IFRS awareness does not mean keeping three full sets of books — it means keeping source records detailed enough that your accountant can derive the second or third view without asking you what happened three years ago.
