Contract Combination Under ASC 606: When to Treat Multiple Contracts as One

When a customer signs more than one contract with the same vendor, contract combination under ASC 606 merges them into a single accounting arrangement if three criteria are met: they were negotiated together, one serves as a performance condition for the other, or the price of one depends on the other. Combining contracts changes the timing and amount of recognized revenue, often deferring it until the entire bundle is satisfied.

The Core Problem: Revenue Splitting

Imagine a software vendor signs a contract for a $500,000 license and a separate contract (on the same day, with the same customer) for a $200,000 implementation service. If the vendor accounts for them separately, it might recognize the $500,000 upfront and defer the $200,000 over time, front-loading revenue.

But the economic reality is that the customer agreed to both for a single reason: the implementation is essential to the software being usable. The vendor cannot ethically claim the license revenue before the software works. Under ASC 606, the two contracts should be combined and treated as a single $700,000 performance obligation, with revenue deferred until both the license and implementation are delivered.

Contract combination prevents vendors from fragmenting deals into pieces, recognizing favorable pieces early and deferring unfavorable ones. It enforces unity of economic substance.

Criterion 1: Negotiated Together

The first test is straightforward: were the contracts negotiated as part of a single transaction?

“Negotiated together” typically means:

• The contracts are signed on the same day or in a closely linked sequence.
• The customer agreed to one contract only on the condition of the other.
• The vendor’s pricing in one contract reflects the assumption that the other contract will also be signed.

Example 1: A construction company signs a main contract for $2 million to build an office building and, on the same day, a separate contract for $300,000 of design services. The customer (a developer) negotiated them together as part of one project. They must be combined.

Example 2: A cloud services provider sells a three-year managed IT service to a customer. Due to contract renewal cycles, they split it into three one-year contracts signed on consecutive dates. If the second and third contracts were conditioned on the customer committing upfront (verbally or in writing), they were negotiated together and must be combined into one three-year obligation.

Non-example: A customer signs a service contract in January; six months later, they buy an unrelated product from the same vendor. Even though they are the same customer, the contracts were not negotiated together, so they are separate.

The key word is together, not “at the same time.” A customer could sign contract #2 months after contract #1, but if they negotiated terms for both contracts in a single negotiation, the contracts are negotiated together.

Criterion 2: Single Performance Obligation or Condition Precedent

The second test examines the substance of what is being sold: does one contract serve as a condition or component of the other?

This criterion applies when:

• One contract’s goods or services are a requirement for the other to be useful or binding.
• The customer’s commitment to one is explicitly or implicitly contingent on the other.

Example 1: A software vendor sells a license for $400,000 and a separate maintenance contract for $50,000 per year. The license contract clause states, “Maintenance is mandatory and must be purchased for the license to be in effect.” The maintenance contract is a performance obligation tied to the license; they combine.

Example 2: A consulting firm signs a contract for a one-month diagnostic engagement ($100,000) and a separate contract for implementation based on recommendations ($500,000). If the diagnostic report is a prerequisite for the implementation contract to be enforceable (the client cannot proceed with implementation until the diagnostic is complete), the contracts are linked and combine.

Example 3: A leasing company structures an equipment lease and a separate guarantee/buy-back contract with a customer. If the buy-back guarantee is essential to the economics of the lease (the lessor’s return depends on it), they are interdependent and combine.

The question is not whether the contracts are related in a business sense, but whether satisfying one is truly conditional on the other. If the customer could (in theory) walk away from one contract and still have a viable arrangement under the other, they are separate.

Criterion 3: Pricing Interdependence

The third test focuses on economics: is the price of one contract contingent on the performance or outcome of the other?

This criterion captures pricing structures where:

• The price of contract B varies based on the completion or performance of contract A.
• One contract explicitly references the other’s price or terms for adjustment.
• The vendor’s cost to perform one contract depends on the scope confirmed in another.

Example 1: A systems integrator signs a contract for network design and architecture at a fixed $150,000 and a separate implementation contract priced at $50 per configured device. The $50 per device price was set in negotiation on the assumption that design would proceed in parallel. The final implementation cost depends on design decisions made in the architecture contract. The contracts are priced together; they combine.

Example 2: A real estate developer signs a contract for land acquisition from one party and a separate contract for development rights, with the development fee structured as a percentage of the acquisition price. The price of the development contract is directly tied to the other contract’s cost. They combine.

Example 3: A SaaS vendor sells a platform license at a flat $100,000 annually and a separate managed services contract that caps fees at 50% of the license cost. The managed services price is capped based on the license cost; they are economically linked and combine.

Non-example: A construction firm sells a main contract for $2M and a separate material supply contract for $300K at a pre-negotiated, fixed unit price. The supply price does not vary based on project completion; it is simply a fixed-price supply agreement. If the unit pricing was quoted independently and is not contingent on other contract terms, they need not combine—though the first criterion (negotiated together) might still apply.

What Happens When Contracts Are Combined

Once combined, the arrangements are treated as a single contract with one or more performance obligations. The combined revenue and performance obligations are then assessed under the rest of ASC 606:

• Identify the combined performance obligations (which goods or services are included and whether they are separate performance obligations or bundled).
• Determine the transaction price (sum the prices from all contracts, adjusted for any discounts or variable terms).
• Allocate that price to each distinct performance obligation using the standalone selling price method.
• Recognize revenue as each performance obligation is satisfied (over time or at a point in time).

Typically, combining defers revenue recognition. A vendor cannot claim upfront revenue from a favorable contract if unfavorable terms in a combined contract have not been satisfied.

Common Pitfall: Failing to Identify Separate vs. Combined

A frequent error is treating contracts as separate when combination is required, or vice versa. Here are the key missteps:

Documentation and Evidence

When combination is questionable, the company should document:

• The date each contract was signed and the timing of negotiations.
• Email or meeting notes showing whether terms were discussed together.
• Any written clauses in the contracts that explicitly link them or make one conditional on the other.
• The pricing history: were the prices quoted independently, or did the vendor present a bundle price?

This documentation supports the accountant’s judgment and provides audit evidence if questioned.

See also