Series of Distinct Goods and Services in Revenue Recognition

A cable company delivers internet to a customer every month. A software firm provides cloud storage access continuously. Are these one revenue obligation or twelve separate ones? ASC 606 allows companies to treat certain recurring offerings as a series—a single bundled performance obligation—provided they meet specific conditions. This simplifies accounting and can accelerate revenue recognition.

The series concept

Imagine a homeowner buys a one-year cable subscription: internet access every month for $60/month. Technically, the cable company is performing a distinct service each month—delivering bandwidth. Without the series rule, the company would record 12 separate performance obligations, each recognized when monthly access is delivered.

Under the series guidance, the company can instead treat the entire 12-month agreement as one performance obligation. Revenue is then recognized evenly over the year as the series is satisfied. The logic: the customer contracted for a single “thing”—reliable annual internet access—even though satisfaction happens monthly.

This simplification is powerful. It reduces accounting complexity, aligns revenue recognition with customer intent, and matches how management typically views and prices such contracts.

The two-part series test

ASC 606 specifies that a series qualifies if:

1. The company has the right to consider the items a series. The contract must permit treating the repetitions as a bundle, not as standalone items. Often this is implicit: a 12-month service agreement inherently bundles the monthly deliveries.

2. The nature of the promised service and the basis for pricing remain substantially the same throughout the period. This is the hard requirement. Each monthly delivery must be:

   • Functionally identical (or nearly so).
   • Priced on the same basis (e.g., $60 every month, not $60 then $70).
   • Subject to the same terms and conditions.

If these two conditions are met, the entire series is a single performance obligation. If the pricing or nature of deliverables changes mid-term, the series may split into two or more obligations at the change point.

When the series rule applies

Subscription services: Monthly SaaS subscription (software as a service), where the customer receives the same cloud-based tool each month. Single series obligation.

Recurring access: Annual gym membership with monthly access. Single series obligation, provided the gym doesn’t change the scope of access mid-year.

Maintenance and support contracts: A manufacturer provides quarterly equipment maintenance for 24 months at a fixed fee. Single series obligation.

Utility billing: A power company delivers electricity to a residential customer over 12 months. The monthly volumes may vary, but the service nature and rate structure are the same. Series treatment is appropriate.

Exception: If pricing or scope changes mid-stream. A company signs a 2-year software contract: Year 1 at $100/month, Year 2 at $120/month. The pricing change means this is two separate series or obligations, not one. Revenue is split accordingly, with the Year 1 portion recognized over 12 months at the Year 1 rate, and Year 2 over the next 12 months at the higher rate.

Series versus individual obligations: a worked example

Scenario: A pest control company offers a quarterly treatment plan at $200 per quarter. The customer commits to 4 quarters ($800 total).

Without series treatment (if conditions were not met):

• Four separate performance obligations.
• Q1 revenue = $200 (upon completion of Q1 service).
• Q2 revenue = $200 (upon completion of Q2 service).
• Q3 revenue = $200 (upon completion of Q3 service).
• Q4 revenue = $200 (upon completion of Q4 service).

Accounting is granular; revenue follows each delivery.

With series treatment (conditions are met):

• One performance obligation: the “4-quarter pest control series.”
• Revenue recognition = $800 total divided by 4 quarters = $200 per quarter.

The outcome looks the same in this case, but the accounting approach differs. Under series treatment, the company might recognize revenue upfront for the full series (if it’s a performance obligation satisfied over time), or systematically over the period. The key benefit: the company can recognize all $800 upfront if conditions for over-time recognition are met (customer gets benefit as delivered, company cannot redirect services, etc.), rather than waiting for each delivery.

Pricing and scope changes

A series breaks if pricing or scope materially changes. Example:

• Contract: Year 1 cloud storage at $50/month (12 months = $600), Year 2 at $60/month (12 months = $720).
• This is two separate series (or possibly two obligations if series treatment doesn’t apply to the year-2 portion).
• Year 1: Recognize $50/month over 12 months.
• Year 2: Recognize $60/month over the next 12 months.

If scope changes (e.g., storage allocation doubles in Year 2), the substance is the same: two distinct obligations.

Interaction with performance obligations and revenue timing

Series treatment affects when revenue is recognized, contingent on how the series is satisfied:

• Over time: If the company satisfies the series over time (customer consumes benefit gradually, or company has enforceable right to payment), revenue is recognized ratably over the contract term.
• At a point in time: If the series is satisfied at a single moment (rare for recurring services, but possible), revenue is recognized in that period.

Most subscription and recurring services are “over-time” obligations, so series treatment locks in gradual revenue recognition aligned with delivery.

Practical audit and disclosure implications

Auditors closely examine whether companies correctly apply series guidance, because the classification can materially accelerate revenue. For example:

• A company treats a software subscription as a series and recognizes annual revenue upfront.
• Auditor scrutinizes whether pricing is truly “substantially the same” across the year, and whether the service scope is identical.
• If evidence shows the company customized deliverables or prices mid-stream, the series treatment may be invalidated, forcing re-recognition over time.

Companies must disclose in notes:

• The nature of series obligations.
• How revenue is recognized (upfront, ratably, etc.).
• Any significant changes to series terms during the period.

See also