Article
Brochure
Executive Resource
Insight Hub
Video
Ext. PublicationASC 606: What Tech, Media and Telecom Companies Need to Know
Never miss a thing.
Sign up to receive our insights newsletter.
The Financial Accounting Standards Board (FASB) established Accounting Standards Codification 606, Revenue from Contracts with Customers (ASC 606), to create a uniform framework for revenue recognition across industries. This article summarizes key elements of ASC 606 to guide CFOs and controllers of technology, media and telecom companies through common accounting challenges.
The information presented is for informational purposes only; readers should consult with relevant professionals as to specific matters and application.
Background
ASC 606 introduced a consistent framework for revenue recognition but applying it in the tech sector is far from simple. From bundled products and usage-based billing to custom contracts and equity-backed growth expectations, technology companies face unique challenges in every step of the five-step model. This article highlights common pitfalls in identifying performance obligations, allocating transaction price and timing revenue. It offers practical examples and lessons learned along the way.
Technology, media and telecom companies, especially private equity or venture capital-backed firms reporting under U.S. Generally Accepted Accounting Principles (GAAP), face intense scrutiny on financial reporting. Bundled offerings, subscriptions, hardware sales and service contracts can create challenges in the timing of revenue recognition, allocation to different performance obligations, capitalizing costs such as setup fees and commissions, managing contract assets and liabilities, and accounting for deferred revenue.
Accurate revenue recognition under ASC 606 is not merely about compliance; it is essential for investor trust, funding rounds and sustainable growth. The standard requires robust judgments, and systems missteps can trigger restatements or erode confidence.
The Five-Step Model: Core of ASC 606 for Tech Revenue Recognition
The core of ASC 606 is a five-step process:
- Identify the contract
- Identify the performance obligations
- Determine the transaction price
- Allocate the price to the performance obligations
- Recognize revenue when the obligation is satisfied
This model applies universally but manifests differently across sectors. Hardware companies may recognize device sales at a point-in-time. Software and SaaS companies recognize subscription revenue over time. Telecom bundles hardware with service plans. Data processing revenue often resembles service-based recognition. Each has unique timing considerations.
A major challenge is determining whether these costs should be recognized over time (e.g., certain software subscriptions, telecom services) or at a point-in-time (e.g., hardware manufacturing).
Bundled smart devices and cloud services require evaluating whether the hardware stands alone as a distinct performance obligation or forms part of an integrated offering. Telecom faces similar bundling issues when routers and cell phones accompany ongoing service plans. SaaS and data processing often involve variable usage, complicating both determining and allocating the transaction price.
Sector Snapshot
| Sector | Common Issue | Typical Judgment |
|---|---|---|
| Hardware | Bundled device + software | Whether device and service are distinct obligations |
| SaaS | Tiered usage pricing | Transaction price allocation |
| Telecom | Device + monthly plan | Allocation between equipment sales and services |
| Data processing | Consumption-based billing | Determining transaction price and timing |
Capitalizing and Amortizing Customer Setup Costs
Contracts with customers often present challenges in accounting for costs to obtain or fulfill obligations. Tech firms incur upfront costs for customer onboarding, implementation (software/SaaS), installation (telecom/hardware) or system setup (data processing). These direct costs may be capitalized under ASC 340-40 if they create or enhance resources used to satisfy future performance obligations and are recoverable. Amortization generally aligns with the period of customer benefit, often the contract term plus probable renewals or customer life.
Challenges vary: Hardware setups may not qualify if they do not enhance future obligations; telecom installations may qualify if distinct. SaaS/data processing arrangements with high churn require more frequent impairment monitoring. Estimating renewal periods is especially complex given sector volatility.
Commissions and Other Contract Assets
Commission arrangements are common in tech sales. Depending on the specifics of the plan, certain incremental costs to obtain a contract must be capitalized and amortized over a future period. Claw backs for terminations also affect recognition.
Contract assets (e.g., unbilled usage in data processing/telecom) often arise when performance precedes billing. For hardware companies, commissions on bundled sales complicate allocation. Telecom dealer commissions may be capitalized but should be distinguished from discounts. Variable pricing models in software/SaaS and data processing can create earnings volatility.
Deferred Revenue: Cancellable vs. Noncancellable Contracts
Deferred revenue from advance payments is common in tech. Recognition depends partly on contract enforceability. In noncancellable deals (e.g., locked telecom plans), or when substantive termination penalties exist, recognition is typically ratable over the term. Cancellable contracts limit recognition to the enforceable period, and receivables tied to deferred revenue be removed on the gross basis.
Sector nuances include:
Hardware: Deferral related to warranties or bundled services
Telecom: Upfront activation fees are deferred if no material rights exists; recognition accelerates for month-to-month plans.
Software/SaaS and data processing: Uncertainty in renewals affects remaining performance obligations (RPO), a critical metric for VC/PE investors.
Sector Snapshot
| Sector | Common Issue | Typical Judgment |
|---|---|---|
| Hardware | Advance payments, warranties, bundled services | Determine deferral period based on obligations; recognize ratably if noncancellable |
| SaaS | Subscriptions with uncertain renewal | Limit recognition to enforceable periods; reassess RPO |
| Telecom | Activation fees, cancellable plans | Recognize for noncancellable; accelerated for month-to-month |
| Data processing | Variable contracts | Apply ASC 606-10-55-286; recognize as performed |
Key Takeaways for CFOs and Controllers
- Align accounting with your business model.
- Capitalize costs carefully and only when recoverable.
- Monitor renewals and churn; adjust amortization and impairment assumptions.
- Document judgments to build auditor and investor confidence.
- Automate where possible to reduce risk and improve scalability.
Tackling These Challenges
Revenue recognition does not have to be a back-office exercise. With strong documentation, consistent judgments and system support, CFOs can turn ASC 606 into a strategic advantage. Clear application of the standard strengthens valuations, investor transparency and scalable systems.
Weaver’s professionals help technology, media and telecom companies evaluate and refine revenue processes and align them with strategic goals. We support clients across hardware, software, telecom and data processing with tailored U.S. GAAP solutions. Ready to optimize revenue recognition and contract design? Contact us.
Access the full text of ASC 606, Revenue from Contracts with Customers through the FASB Accounting Standards Codification at https://asc.fasb.org (free registration required). After logging in, navigate to Topic 606 for the complete standard.
©2025
