Chapter 12.2 — US GAAP Compliance

1. Purpose

For partners reporting under US GAAP (Generally Accepted Accounting Principles), this chapter maps travoBooks' accounting model to the relevant FASB Accounting Standards Codification (ASC) sections. The platform's design follows IFRS as the primary standard (Chapter 12.1) and US GAAP shares the same core mechanics for most travel-industry-relevant areas, with documented differences.

2. Standards in scope

ASC	Topic	Relevance
ASC 606	Revenue from Contracts with Customers	Core — substantially equivalent to IFRS 15
ASC 326	Financial Instruments — Credit Losses (CECL)	AR impairment
ASC 830	Foreign Currency Matters	Multi-currency
ASC 842	Leases	Office leases (out of platform scope)
ASC 740	Income Taxes	Out of platform scope Phase 1
ASC 250	Accounting Changes and Error Corrections	Restatements
ASC 220	Income Statement Presentation	Reporting layout
ASC 230	Statement of Cash Flows	Cash flow reporting
ASC 450	Contingencies	Provisions
ASC 350-40	Internal-Use Software	Out of platform scope

3. ASC 606 — Revenue Recognition

ASC 606 is substantially identical to IFRS 15 in core requirements: - Five-step model: identify contract, identify performance obligations, determine price, allocate price, recognise. - Principal vs agent considerations. - Variable consideration constraint. - Contract balances disclosure.

3.1 Same as IFRS 15

• Service-date-driven recognition.
• Deferred revenue mechanism (Chapter 5.7).
• Commission as variable consideration with constraint.

3.2 Differences worth noting

• ASC 606 §606-10-32-29: variable consideration "expected value" or "most likely amount" methods — same as IFRS 15 §53.
• Disclosure granularity: ASC 606 requires more disaggregation in some industries; the platform's revenue_disaggregation report provides per-product-type-per-supplier-type-per-jurisdiction granularity that satisfies both.
• Practical expedients: ASC 606 offers some practical expedients (e.g., for contracts with original duration ≤ 1 year not requiring disclosure of unsatisfied obligations) — travoBooks provides the data either way; partner finance teams elect the expedient at the disclosure-pack level.

3.3 Platform configuration

A partner's gaap_framework field on the partner record drives default behaviours: - IFRS (default) — IFRS 15 terminology in reports. - US_GAAP — ASC 606 terminology; ASC disclosure formatting.

The underlying accounting mechanics are identical; only labelling differs in Phase 1.

4. ASC 326 — CECL (Current Expected Credit Losses)

US GAAP's CECL model (effective FY2020+ for SEC filers, FY2023+ for others) requires lifetime expected credit losses at origination, similar but not identical to IFRS 9's expected-credit-loss model.

Aspect	IFRS 9	ASC 326 (CECL)
Initial recognition	12-month ECL	Lifetime ECL
Stage transitions	3 stages (1, 2, 3) based on credit risk	No staging; always lifetime ECL
Calculation methods	Probability-weighted	Probability-weighted; allows simpler approaches for trade receivables (loss-rate method)
Reversal	Yes, if conditions improve	Yes

For trade receivables specifically, both frameworks permit simplified loss-rate / aging-bucket approaches. The platform's ECL implementation (per Chapter 12.1 §5) supports both under the same calculation engine; selection per partner.gaap_framework.

5. ASC 830 — Foreign Currency

Substantially aligned with IAS 21: - Functional currency designation. - Spot rate at transaction; closing rate for monetary balances. - FX gain/loss in P&L. - Translation of foreign-operation statements for consolidation.

Differences are minor and not material for travel-agency accounting in Phase 1.

6. ASC 220 — Income Statement Presentation

US GAAP presentation differences from IFRS: - "Operating income" defined more rigidly under US GAAP. - Comprehensive income disclosure (OCI items) — for travel agency Phase 1, OCI items are nil; statement of comprehensive income equals net income.

The platform's P&L generation handles both layouts; the configured gaap_framework drives template selection.

7. ASC 230 — Cash Flow

Both IFRS (IAS 7) and US GAAP (ASC 230) permit direct and indirect methods. travoBooks implements indirect-method by default Phase 1, both frameworks aligned.

Classification differences: - Interest paid: IFRS allows operating or financing; US GAAP requires operating. - Interest received: IFRS allows operating or investing; US GAAP requires operating.

Per-partner classification config: cashflow_interest_classification = OPERATING | FINANCING_PAID_INVESTING_RECEIVED.

8. ASC 450 — Contingencies

Provisions and contingent liabilities (disputed ADMs, dispute provisions) treated per IAS 37 in Phase 1; ASC 450's "probable, reasonably possible, remote" threshold framework is functionally similar but with subtle differences in recognition thresholds.

travoBooks' provisions table stores: - Both ifrs_recognition_basis (virtually certain / probable / possible / remote) and gaap_recognition_basis (probable / reasonably possible / remote). - Recognition decision in P&L driven by partner.gaap_framework.

9. ASC 740 — Income Taxes

Out of platform scope Phase 1. Partner finance teams handle current and deferred tax computation outside travoBooks; travoBooks provides: - Pre-tax book income (from P&L). - Permanent and timing differences inferable from JE detail. - Tax-return-data export.

The tax journal entry is booked as a manual JE by partner accountants.

10. ASC 250 — Restatements vs Out-of-Period Adjustments

US GAAP distinguishes: - Restatement (material error in prior period) — restate prior-period financials. - Out-of-period adjustment (immaterial) — book in current period with disclosure.

The platform supports both: - Restatement workflow: period reopen → adjusting JE → re-close → snapshot replacement (with audit-log breadcrumb to original). - Out-of-period adjustment: current-period JE with is_out_of_period = TRUE flag; auto-included in disclosure pack.

Same machinery serves IAS 8 (prior-period error correction).

11. Disclosure pack — GAAP version

When partner.gaap_framework = US_GAAP, the disclosure pack generates: - ASC 606 disaggregated revenue disclosures. - ASC 326 CECL roll-forward. - ASC 830 FX rate disclosures. - ASC 450 contingencies summary. - ASC 220 income statement (with US GAAP classification). - ASC 230 cash flow statement. - Notes formatted per US GAAP convention.

12. Audit considerations

US GAAP audits (under PCAOB or AICPA standards) test the same control environment as IFRS audits with framework-specific assertion checks: - Cut-off — service-date-driven recognition; the platform's nightly recognition run and period-end run provide cut-off evidence. - Existence — booking → ticket → JE chain provides existence evidence. - Completeness — BSP/ARC import + reconciliation provides completeness evidence for issued tickets. - Valuation — fare data captured at issuance + commission rules with version pinning. - Rights & Obligations — principal/agent classification per supplier with rationale.

13. SEC-specific considerations

For partners that are SEC registrants: - SOX 404 internal-control attestation — travoBooks' documentation suite + tested control framework supports this. - 10-Q/10-K disclosure data points — exported from disclosure pack. - XBRL tagging — Phase 2 platform capability.

These are not Phase 1 platform features; partners overlay using existing controls.

14. Configuration summary

partner table fields driving GAAP behaviour:

Field	Values
gaap_framework	IFRS (default) | US_GAAP
cashflow_method	INDIRECT (default) | DIRECT
cashflow_interest_classification	OPERATING (default) | MIXED
ecl_methodology	LIFETIME_LOSS_RATE (default) | MULTI_SCENARIO
revenue_disclosure_disaggregation	array of dimensions

15. Common pitfalls

• ⚠️ Assuming ASC 606 = IFRS 15 in every detail. Disclosure expectations differ; practical expedients differ.
• ⚠️ CECL vs IFRS 9 12-month vs lifetime confusion. Always lifetime under CECL.
• ⚠️ Treating ASC 250 restatement as a routine event. Restatement is reportable; minimise via robust period close.
• ⚠️ Mixing OCI items into US GAAP net income. Phase 1 has no OCI items; if introduced (e.g., hedge accounting), watch the classification.
• 🔒 Framework-mixing — a single legal entity reports under one framework only; ensure partner-level config is correct at onboarding.