What is ASC 606 variable consideration in the context of royalties?

It's the accounting standard's term for revenue, like a sales-based royalty, that depends on a future event rather than being fixed and known in advance. ASC 606 constrains how much of that revenue can be recognized before it's reasonably certain the constraint won't reverse.

Why can't a royalty be recognized when the licensing agreement is signed?

Because the amount depends on the licensee's future sales, which haven't happened yet. Recognizing it too early would mean booking revenue that might not actually materialize.

Does Zietra replace a dedicated royalty accounting tool?

Zietra includes ASC 606 revenue recognition and royalty management as part of the same workspace as CRM, sales, and purchasing, rather than as a separate standalone tool. For a brand that wants that connected to its other operating data instead of managed apart from it, that's the relevant difference.

ERP and NetSuite

How Consumer Brands Handle ASC 606 Royalty Revenue

Jithesh Manoharan, Chief Executive Officer. September 29, 2026. 3 min read

In short

A royalty based on a percentage of a licensee's future sales is variable consideration under ASC 606, and cannot be recognized until it is reasonably certain. Brands with more than one licensing relationship usually need this connected to actual sales data rather than tracked in a spreadsheet, to avoid a slow, manual reconciliation at close.

A brand that licenses its name, or collects a percentage of a partner's sales, runs into a specific accounting problem that a straightforward retailer never has to think about. Royalty income based on someone else's future sales is variable consideration under ASC 606, and recognizing it correctly takes more than a spreadsheet formula.

Why sales-based royalties are harder than a fixed license fee

A fixed annual licensing fee is straightforward to recognize, since the amount and timing are both known in advance. A royalty based on a percentage of a licensee's sales is not known until those sales actually happen, and ASC 606 has a specific constraint on recognizing that kind of variable consideration before it's reasonably certain. In practice, that means the accounting has to wait for actual sales data from the licensee before revenue can be booked, rather than recognizing an estimate up front.

What breaks when this lives in a spreadsheet

This is manageable with one licensing partner and one royalty rate. It stops being manageable once a brand has several licensing relationships, each with a different rate, reporting cadence, or minimum guarantee, because reconciling actual licensee sales reports against what was recognized becomes a manual process with no system of record behind it. The usual failure mode is a quarter-end close that takes longer than it should, because someone has to manually chase down and reconcile each licensee's sales report against the books.

Where a workspace like Zietra fits

Zietra covers CRM, sales, purchasing, item management, product lifecycle, manufacturing execution, quality, and ASC 606 revenue recognition and royalties, in one workspace per brand, with a subdomain and row-level data isolation per tenant. That is the published scope of what it covers, not a separate royalty add-on. Keeping royalty and revenue recognition in the same workspace as sales and purchasing, rather than in a disconnected tool, is the structural approach it takes.

What to ask a platform before trusting it with royalty accounting

A few questions are worth asking directly of any platform being considered for this. Can it handle more than one royalty rate structure at once, since most brands with multiple licensing deals don't have identical terms across all of them. Is royalty and revenue recognition part of the same system as sales and purchasing data, or a separate tool that needs to be reconciled against them by hand. And does it support the timing rules ASC 606 actually requires, rather than just calculating a percentage and calling it done.

More on Zietra, or how we work with consumer brands and beauty companies. For a full ERP instead, see our NetSuite Advanced Revenue Management guide.

Common questions

What is ASC 606 variable consideration in the context of royalties?: It's the accounting standard's term for revenue, like a sales-based royalty, that depends on a future event rather than being fixed and known in advance. ASC 606 constrains how much of that revenue can be recognized before it's reasonably certain the constraint won't reverse.
Why can't a royalty be recognized when the licensing agreement is signed?: Because the amount depends on the licensee's future sales, which haven't happened yet. Recognizing it too early would mean booking revenue that might not actually materialize.
Does Zietra replace a dedicated royalty accounting tool?: Zietra includes ASC 606 revenue recognition and royalty management as part of the same workspace as CRM, sales, and purchasing, rather than as a separate standalone tool. For a brand that wants that connected to its other operating data instead of managed apart from it, that's the relevant difference.

About the author

Jithesh Manoharan, Chief Executive Officer

An IT consultant with experience spanning more than two decades, across startups and the Big 4 alike. Jithesh has worked as a NetSuite ERP consultant, principal advisor and solution architect for companies including Wells Fargo, Hampton Creek, Anastasia Beverly Hills and JUST Inc. He runs several concurrent programmes across industry verticals, and advises boards and executives on enterprise wide technology strategy.

Talk to the team that wrote this

If any of this matches what you are dealing with, a short conversation will get you further than another article.

Book a consultation ERP and NetSuite at TechCloudPro