Revenue Recognition for Multi-Element Arrangements

A few quarters ago, I worked with the finance team of a SaaS company that had just closed its largest enterprise deal worth USD 1.2M over three years. It looked like a clear win on paper. But in practice, it bundled a custom implementation, a recurring subscription, and ongoing support, all of these recorded as a single line item in their ERP. 

The problem is ASC 606 doesn’t see “one deal”, it sees multiple performance obligations, each with its own timing for revenue recognition. The result was days of manual allocations, back-and-forth with auditors, and a real risk of misstating revenue. This isn’t a rare situation. Any growing software or services business will eventually run into multi-element arrangements (MEAs).

In this guide, we’ll break down how to recognize revenue for MEAs step-by-step, keep your accounting compliant, and avoid turning month end close difficult. 

What is a multi-element arrangement (MEA)?

A multi-element arrangement is a single contract that includes more than one promised product or service. For finance teams, the complexity lies in the fact that each element may have its own delivery schedule, cost structure, and revenue recognition rules under ASC 606 or IFRS 15. 

We see this often in scaling software companies, sales closes a one deal package, but accounting must unbundle it into separate performance obligations. Doing this right ensures revenue is recognized when each part is delivered, not just when the invoice hits the books.

Example of multi-element arrangement

You probably encounter multi-element arrangements more often than you think, even outside of the finance world. Here’s how they look in real life:

SaaS

Zoom could sign an enterprise deal that includes a $50K onboarding and training package plus a $100K/year video conferencing subscription. The onboarding is recognized when delivered, while the subscription is recognized evenly over the year.

Hardware + software license + support

Apple might sell a MacBook bundled with a one-year AppleCare plan and pre-installed pro software. The MacBook revenue is recognized at delivery, while the AppleCare portion is spread over the coverage period.

Construction with design + build phases

A company like Turner Construction might contract to design and build a corporate headquarters, recognizing design revenue as the plans are completed and build revenue as the structure is constructed.

Step-by-step revenue recognition for MEAs

1. Identify the contract with a customer

This is literally opening the document and confirming:

• Who signed it and when
• What they agreed to deliver or receive
• The commercial terms, price, payment schedule, currency, renewal clauses
• Whether the customer is legally bound to pay

It sounds obvious, but we’ve seen situations where Sales celebrated a closed deal only for Finance to find there was no final signature, or the payment terms were buried in an email thread. If it’s not enforceable, you can’t recognize revenue, period.

2. Identify the performance obligations in the contract

Performance obligations are just a formal way of saying: what exactly are we on the hook to deliver, and what exactly is the customer on the hook to receive?

You go line by line:

• Is the onboarding work separate from the subscription, or is it necessary to use the product?
• Is that free hardware actually part of the subscription value, or a standalone deliverable?
• Does support mean 24/7 helpdesk, periodic updates, or both?

If each part delivers value on its own, it’s distinct. If the customer can’t use it without the other parts, it’s bundled. Get this wrong and you either pull revenue forward (audit nightmare) or push it out unnecessarily (forecasting mess).

3. Determine the transaction price 

Now you nail down the real price, not just what’s printed on page one. You look for:

• Fixed fees
• Variable amounts like usage charges, rebates, or penalties
• Discounts that apply to the whole deal or just certain parts
• Clauses about refunds or credits

Example: That $500K annual subscription might actually be $450K after the first-year discount and $50K in potential usage overages. If you don’t read the fine print, your allocation will be off from day one.

4. Allocate the transaction price to performance obligations in contract

Here’s where the SSP (standalone selling price) conversation becomes real. You ask: If we sold each piece separately, what would it cost? Then you split the total contract value accordingly.

• If you have actual standalone prices in your catalog, use them.
• If not, look at similar deals from competitors.
• If that’s not possible, estimate it based on costs plus margin.

Example: If an iPhone sells for $1,000 and AppleCare for $200, and you bundle both for $1,100, you still allocate $916.67 to the iPhone and $183.33 to AppleCare based on relative SSP, not $1,000 for the phone and $100 for the warranty.

5. Recognize revenue when the entity satisfies performance obligation

Finally, you decide when to move amounts from deferred revenue to earned revenue. This step states when the entity will book the revenue, the timing, and the period. 

• Physical goods? When the customer takes control.
• Subscriptions? Evenly over the service period.
• Implementation or training? When the work is complete and accepted.
• Licenses? Depends if it’s “right to use” (point in time) or “right to access” (over time).

Example: Zoom sells onboarding + annual subscription. The onboarding fee is recognized once the training is delivered. The subscription fee is recognized monthly. If you try to recognize it all up front, you’ll have an auditor in your inbox.

Example of allocating revenue in a multi-element SaaS arrangement

Let’s say TechWave Solutions, a mid-market SaaS provider, signs a $5 million contract with GlobalMart Inc. for a bundled package that includes:

• A three-year enterprise subscription to its supply chain management platform
• A one-time custom implementation project
• Annual support and upgrades
• On-site training for GlobalMart’s operations team

Here’s what’s in the signed contract:

• Total contract value: $5,000,000 (billed at contract start)
• TechWave sells the subscription separately for $3.2M and support for $600K per year.
• Implementation and training aren’t sold separately, but GlobalMart gathered quotes from other vendors during procurement, $800K for similar implementation work and $200K for training.

Step 1: Determine standalone selling prices (SSP)

(*Rounded for simplicity.)

The standalone prices total $4.8M, but the contract is actually worth $5M. Under ASC 606/IFRS 15, you don’t just use the standalone prices as-is, you use them to figure out each element’s share of the total. For example, the subscription’s standalone price ($3.2M) is about 53% of the total standalone value ($4.8M). That 53% is then applied to the actual contract price ($5M), which bumps the allocated amount to $2.65M. This ensures the full $5M is allocated across all elements in proportion to their relative value.

Step 2: Apply the right revenue recognition approach for each

• Subscription: Recognize evenly over the 36-month term.
• Support & upgrades: Recognize evenly over each 12-month period.
• Implementation: Recognize as the project milestones are completed and accepted.
• Training: Recognize when delivered.

Because the subscription and support are service-based, their revenue is deferred and recognized over time. Implementation and training are recognized sooner, but only as the actual work is completed.

Handled this way, TechWave keeps the book's audit ready, avoids front-loading revenue incorrectly, and accounting mismatches.

Common complexities in MEA accounting

Multi-element arrangements sound straightforward until you start working through a live contract. That’s when the small details turn into accounting reconciliation headaches and audit red flags. Here are the scenarios that trip finance teams most often, and why they’re so tricky in practice.

Non-refundable upfront fees

ASC 606 doesn’t care what your invoice says, it cares if the customer gets standalone value. If your $50K onboarding fee only makes sense with the subscription, you can’t book it on day one. You must defer and recognize it over the contract term. That means recalculating schedules, adjusting commission payouts, and often walking sales through why the P&L won’t reflect the deal they sold.

Customer options for additional goods/services 

A discount or voucher buried in the contract might actually be a separate performance obligation. If the customer can buy more at a significant discount, part of the original contract value has to be held back for something that hasn’t even been delivered yet. You’re effectively booking revenue for a future, and that messes with forecasting and allocation.

Renewals and contract modifications

Add-ons mid-contract aren’t just extra line items. You have to decide if they’re a new contract, a true-up of the old one, or a hybrid. Each path changes how you allocate revenue and how much you restate prior periods. Without a clear process, this turns into a manual rebuild of revenue schedules, sometimes months after the change happened.

Termination clauses and partial delivery

If a customer can walk away from part of a deal, say, maintenance after year three of a five-year term, you can’t keep recognizing revenue for the undelivered portion. The real headache is when your ERP doesn’t handle conditional obligations well, forcing manual adjustments and reversals when the termination happens.

Usage-based pricing tied to one obligation in a bundle

Usage fees are not predictable ARR. If usage based pricing is linked to one specific performance obligation in your bundle, you can only recognize them when usage occurs. This creates volatile revenue lines and complicates period-end close if usage data is delayed or incomplete.

Operationalizing ASC 606 for MEAs

Getting ASC 606 right for MEAs isn’t about knowing the rules, it’s about configuring your revenue recognition software so the rules actually work in practice. Four areas that make or break the process are:

ERP setup

Your system must split one contract into multiple performance obligations (POBs) with separate allocations, schedules, and recognition logic. If it can’t, you’ll be stuck with workarounds that fail on every contract change.

Deferred revenue per POB

Track deferred balances at the obligation level. Without it, you can’t tie GL numbers to contract schedules, and making books audit ready turns into guesswork.

Revenue schedules & waterfall

Each performance obligation may have a different recognition pattern. If the ERP can’t generate an accurate consolidated waterfall, you’ll end up reconciling Excel models instead of closing.

SSP library maintenance

SSPs change with pricing models and discounts. Without a controlled update process, allocations drift and prior-period adjustments pile up.

If these four are locked in early, MEA revenue recognition runs on rails. If not, every new deal becomes a manual rebuild.

How to recognise revenue for MEAs with Zenskar

Zenskar automates ASC 606/IFRS 15 revenue recognition for multi-element arrangements by removing the manual allocation work that slows finance teams down.

The platform’s AI-powered contract ingestion reads uploaded agreements, extracts transaction prices, products, and terms, and determines the standalone selling price (SSP) for each component in a bundle. It then creates performance obligations, allocates the total transaction price across them using relative SSP ratios, and recognises revenue based on when each obligation is fulfilled, whether at a point in time or over the contract term.

Key capabilities

• Automated bundle management: Configure multiple products and pricing models within a single contract.
• Intelligent price allocation: Automatically split transaction prices using calculated SSP ratios.
• Flexible revenue scheduling: Manage deferred, unbilled, and unearned revenue with custom timing rules.
• Compliant journal entries: Generate audit-ready records without disrupting existing ledgers.

The result: up to 75% less manual revenue work, zero spreadsheet allocations, real-time visibility into revenue across complex arrangements, and a complete audit trail from contract to cash.

If your B2B business runs hybrid pricing models, usage-based elements, or large contracts with multiple deliverables, Zenskar ensures every dollar is recognised accurately, without the month-end scramble. Take an interactive product tour or book a custom demo today to explore our RevRec offerings. 

‍