Intangibles, R&D, software, and goodwill

Linden Peak's digital-investment folder contains a purchased license, patent work, laboratory spending, internal automation, a hosted platform, a customer software product, and an acquired business. The word “technology” describes all of them and decides none of their accounting.

Sequence logic

The module begins with rights and transaction identity, then useful life and amortization. That gives learners an acquired-intangible baseline before the harder internally generated routes. R&D follows because it exposes why expected future benefit is not a general capitalization rule.

The software sequence uses three separate clocks. Internal-use software first requires current-versus-pending standards control. Hosting arrangements first require license-versus-service scope. Software marketed externally uses a stipulated technological-feasibility window. Only after those distinctions are stable does the module enter acquisition-date identifiable assets, residual goodwill, entity alternatives, impairment, rollforwards, and release.

Name the right, purpose, transaction, entity, and period
├─ Acquired identifiable right → finite/indefinite life → subsequent accounting
├─ Internal activity → ordinary R&D or internal-use software clock
├─ Hosted arrangement → license/service gate → implementation activity
├─ Marketed software → feasibility-to-availability window
└─ Business combination → identifiable net assets → residual goodwill
       ↓
Select asset-level, asset-group, or reporting-unit impairment lane
       ↓
Reconcile class, cash/noncash, expense, impairment, and ending balance

Accounting and finance lenses

Accounting learners build scope memos, cost ledgers, amortization schedules, acquisition allocations, impairment workpapers, entries, and disclosures. Finance learners examine expense timing, acquired versus organic investment, capital intensity, recurring service costs, product-development economics, and why recognized intangible balances are not a valuation of the firm's ideas, people, network, or brand.

Cumulative work

The Linden Peak case requires a standards-clock cover sheet, rights and scope matrix, R&D and software cost ledger, finite-life schedule, cloud-service implementation rollforward, marketed-software window, acquisition allocation, goodwill and impairment workpapers, class rollforward, cash/noncash bridge, and release memo. The two canonical examples have readable Python and formula- visible Excel companions; their checks verify only supplied routes and amounts.

Boundaries and handoffs

The module uses bounded US-GAAP facts. Tax amortization, valuation techniques, complex consideration and combinations, website detail beyond the declared software model, crypto assets, film and other industry guidance, legal/IP advice, and full IFRS application stay outside the core. IAS 38 appears only as a labeled comparison showing why US-GAAP R&D and software conclusions cannot be exported to another reporting basis.