Minimum Commitment Revenue Recognition Under ASC 606

Most contracts with minimum commitments look straightforward on paper. A customer commits to $120,000 for the year. They use $80,000 worth of services. The contract ends with $40,000 unused.

The billing question is simple. The customer owes the $120,000 regardless. The revenue recognition question is not simple at all. When do you recognize the $40,000 they never consumed? All at once at contract end? Ratably over the year? Only the portion you're confident they'll never claim? Under ASC 606, all three approaches have valid accounting rationale. And all three produce different income statement outcomes.

What follows is a practical guide to the three recognition methods for unused capacity under ASC 606, a sensitivity analysis showing exactly how each method affects your income statement, and a decision framework for choosing the right one for your contract structure.

What is a minimum commitment contract under ASC 606?

A minimum commitment contract is an agreement where the customer commits to purchasing a minimum dollar value or volume of goods or services over a defined period, regardless of actual consumption. If the customer uses less than the committed amount, they still owe the full commitment. If they use more, overages are billed separately.

💡In tech, this looks like a customer committing to $120,000 of API calls or platform usage for the year. They consume $80,000. The invoice is still $120,000. The question ASC 606 forces you to answer is what you do with the $40,000 they never used.

What's the performance obligation for unused capacity?

Before choosing a recognition method, your team needs to answer: does the unused capacity represent a satisfied performance obligation, an unsatisfied one, or an obligation that will never be satisfied?

The answer depends entirely on your contract terms.

1. If the contract is strictly take-or-pay with no carry-forward

The customer committed to paying for capacity whether they used it or not. Your job was to keep that capacity available to them throughout the contract period, not to ensure they consumed it. You fulfilled that obligation every month, so you can recognize revenue every month. 

2. If the customer has a contractual right to carry forward unused capacity

The customer can still consume the unused credits in a future period, which means you have not fully delivered on your promise yet. Until those credits are consumed or expire, you cannot recognize the unused amount as revenue. Recognition must be deferred until that obligation is met or expires.

3. If historical data shows a consistent pattern of unused capacity

ASC 606-10-55-28 allows you to apply a breakage estimate. ASC 606-10-55-28 is the specific rule within ASC 606 that allows companies to recognize breakage, meaning revenue from amounts customers are unlikely to ever use.  You recognize only the portion of unused capacity you expect will never be claimed, based on documented historical patterns.

These three scenarios map directly to the three recognition methods. Getting the foundational question right is what determines which method applies to your contracts.

Method 1: Recognize straight-line over the contract period

Straight-line recognition treats the minimum commitment as a single performance obligation satisfied ratably over the contract term. You recognize the full $120,000 evenly across 12 months, regardless of how much the customer actually consumes.

• Monthly recognition: $10,000 
• Year-end total: $120,000 
• Unused capacity treatment: Fully recognized by contract end

This method is the simplest to implement and the easiest to defend to auditors, provided your contract supports it. The accounting rationale is that your obligation was to make capacity available, not to ensure consumption. If the customer had continuous access to the platform throughout the year, that obligation was satisfied ratably.

When does method 1 apply?

Method 1 is appropriate when the contract is strictly take-or-pay with no carry-forward rights, and when the customer's access to the platform is continuous and uninterrupted. If the customer can argue they were unable to consume capacity due to a service issue or contractual failure on your part, straight-line recognition of the unused portion becomes harder to defend.

However, method 1 threatens customer relationships. Recognizing $40,000 in revenue the customer never consumed can create friction at renewal if the customer feels they paid for something they didn't receive.

Method 2: Recognize on consumption, recognize remainder at contract end

Method 2 tracks actual usage and recognizes revenue as the customer consumes capacity. The unused portion is deferred until the contract end date, at which point it is recognized in full as the take-or-pay obligation crystallizes.

• Monthly recognition: Variable, based on actual consumption 
• Year-end total: $120,000 
• Unused capacity treatment: Deferred throughout the year, recognized at contract end

Using the $120,000 scenario, you recognize $80,000 ratably as the customer consumes services across the year. The remaining $40,000 sits in deferred revenue until the final month of the contract, when it is recognized in full.

When does method 2 apply?

Method 2 is appropriate when your contract has no carry-forward rights but you want recognition to more closely reflect actual delivery of services. It requires reliable usage tracking throughout the contract period, since recognition is tied directly to consumption data.

The challenge with method 2 is the revenue spike at contract end. Recognizing $40,000 in the final month alongside regular consumption revenue can create lumpiness in your income statement that auditors and investors will ask about. You need a clear, documented rationale for why the end-of-period recognition reflects the economics of the contract.

Method 3: Recognize on consumption, defer remainder as breakage

Method 3 also tracks consumption but handles the unused portion differently. Rather than recognizing the full unused amount at contract end, you apply a breakage estimate to determine how much of the unused capacity you expect will never be claimed, and recognize only that portion.

• Monthly recognition: Variable, based on actual consumption 
• Year-end total: Less than $120,000 unless breakage estimate absorbs full unused amount 
• Unused capacity treatment: Partially recognized as breakage, remainder deferred until claimed or expired

Using the $120,000 scenario, you recognize $80,000 as consumed. Historical data shows that 60% of unused capacity across your customer base is never claimed. You apply that estimate to the $40,000 unused balance and recognize $24,000 as breakage. The remaining $16,000 stays in deferred revenue until the carry-forward period expires or the customer consumes it.

When does method 3 apply?

Method 3 applies when your contracts allow carry-forward of unused capacity and you have sufficient historical data to support a defensible breakage estimate. ASC 606-10-55-28 requires that breakage estimates be based on a large pool of similar contracts and updated regularly as new data becomes available.

The strength of method 3 is that it most closely reflects the economic reality of your contract portfolio. The risk is the documentation burden. Your auditors will want to see the historical data, the estimation methodology, and evidence that the estimate is reviewed and updated each period.

Sensitivity analysis: How each method affects your income statement

Before looking at the numbers, here is the key difference between the three methods in plain terms:

Method 1 ignores actual usage entirely. You recognize $10,000 every month no matter what the customer consumed.

Method 2 follows actual usage month by month, but holds the unused $40,000 in deferred revenue and releases it all in month 12 when the contract ends. Same total as Method 1, very different timing.

Method 3 also follows actual usage month by month, but instead of releasing the full $40,000 at contract end, it only recognizes the portion history says the customer will never use. The rest stays deferred. This is why Method 3's year-end total is $104,000, not $120,000.

The simplest way to think about it: Method 1 and 2 always get to $120,000. Method 3 may not, depending on your breakage estimate.

Assumptions: $120,000 minimum commitment, $80,000 consumed evenly across 12 months, 60% breakage estimate applied to $40,000 unused balance under Method 3.

The year-end totals tell the most important part of the story. Methods 1 and 2 both recognize the full $120,000, but the timing differs significantly. Method 1 is flat and predictable. Method 2 creates a $46,667 spike in month 12. Method 3 recognizes $104,000, with the remaining $16,000 deferred until the carry-forward period expires.

For a single contract, the difference is manageable. Across a portfolio of 50 or 100 minimum commitment contracts, the method you choose has a material impact on your quarterly revenue figures, your deferred revenue balance, and the questions your auditors ask at year-end.

In a webinar where we hosted Jill Hauck, she framed the stakes plainly: 

"There is no universally correct method for recognizing unused capacity under ASC 606. There is only the method you can defend with a documented policy."

Which method should you choose? The 4-factor decision framework

The right choice depends on your contract economics, your historical data, and your auditor's comfort level.

Which recognition method fits your minimum commitment contract?

Choosing the right method comes down to four factors. Work through them in order.

Step 1: Check your carry-forward rights

If customers can roll unused capacity into a future period, Method 1 is off the table. Straight-line recognition assumes the performance obligation is fully satisfied each month, which isn't true if the customer can still consume those credits later.

Step 2: Assess your usage tracking capability

If there is no carry-forward, check whether your billing system meters usage at the contract level. Both Method 2 and Method 3 require reliable consumption data. If your system cannot track usage accurately, Method 1 is your only defensible option.

Step 3: Evaluate your historical data

If you have reliable usage tracking, the final question is whether you have enough historical data to support a breakage estimate. Without a documented pattern across a large pool of similar contracts, Method 2 is the correct choice over Method 3.

Step 4: Document your policy

The one factor that overrides all others is documentation. According to Audit Analytics (2024), companies with undocumented recognition policies face 2.3x higher audit questioning rates. Pick any of the three methods, document why it fits your contract economics, and review it annually.

Automate minimum commitment revenue recognition with Zenskar

Manual recognition for minimum commitment contracts requires your team to track usage data per contract, apply the correct method to each one, calculate deferred revenue balances, and adjust when usage patterns change mid-period. At ten contracts, that's manageable. At a hundred, it's a close bottleneck.

Zenskar's revenue recognition solution supports all three recognition methods for minimum commitment contracts. 

Here is how Zenskar handles it end to end.

Step 1: Configure your recognition policy

Select your method once per contract type: straight-line, consumption-based with end recognition, or consumption-based with breakage. Every new contract of the same type inherits the policy automatically.

Step 2: Connect your usage data

Zenskar ingests usage data from your billing and metering layer in real time, tracking consumption at the contract level and updating the recognition schedule with each usage event.

Step 3: Deferred revenue is calculated automatically

As usage is tracked, Zenskar updates the deferred revenue balance for each contract in real time. No manual journal entry input required.

Step 4: Edge cases are flagged for review

When a contract has unusual terms, such as a mid-period tier change or an early termination, Zenskar flags it for controller review rather than applying a default treatment.

Step 5: Recognition entries are generated with a full audit trail

At period end, Zenskar generates journal entries for every minimum commitment contract, each traceable back to the contract terms, usage data, and recognition policy that drove it.

Book a demo today to see how Zenskar can automate your revenue engine.

‍