Variable consideration under ASC 606: when bonuses shift revenue

Variable consideration under ASC 606 is the part of a contract price that depends on a future event, such as a bonus for early completion. The common mistake is to book only the fixed fee and treat the bonus as a windfall when it arrives. It moves revenue into the wrong period, and the error often surfaces in a board review or diligence.

Spotting the variable terms before you sign

Start with the contract, not the accounting entry. Before you can answer any question about variable consideration, you need a complete list of every term that could change the price. Read the statement of work, the order form, and any side letter or addendum. Bonuses, milestone-based payments, volume rebates, and penalties for late delivery all belong on that list. Many finance teams miss the ones buried in an addendum that sales wrote after the main deal was signed.

A useful first question is what the customer would pay if everything went as planned, and what could move that number. The answer is rarely a single figure. A fixed fee may come with a bonus if the project finishes early, a credit if it slips, or a rebate once annual purchases pass a threshold. Each of these is a claim on the price that depends on events outside a fixed amount, and each one needs its own line in your review.

Look at the trade-offs in how the terms are written. A bonus that depends on a date the customer controls is harder to predict than one that depends on your own delivery. The first can be pushed around by the other party. The second gives you more control, but it can tempt the team to rush work through the door, which affects quality and cost. Note both points in your review file, not only in the contract summary that sales circulates.

Take a hypothetical software implementation contract with a fixed fee of $60,000 and a $15,000 bonus if go-live happens before a set date. The fixed part is easy to record. The bonus is not yet known, and the real question is whether any part of it can be recorded now. That question leads straight into estimation, which the sections below cover in detail. Until someone answers it in writing, the bonus is an open item, not a number.

The practical output of this step is a short schedule. For each term, list the trigger, who controls the trigger, the expected resolution date, and the person responsible for updating it. Keep the schedule in a shared file that the controller, the outside accountant, and the person who negotiates deals can all read. When a term changes during renegotiation, update the schedule the same day. In my view, stale schedules cause more trouble than complicated formulas do.

Other variable terms that look harmless: returns, concessions, and royalties

Bonuses get most of the attention, but other features create variable consideration too. A right of return is one. If a customer can send back product within a set window, the revenue you can expect to keep is not the full invoice. Implicit price concessions are another. When a company regularly grants discounts beyond what the written contract says, a pattern can make the expected price lower than the stated price, even though no one wrote that down.

similar way. If a rebate applies retroactively to all purchases once a threshold is crossed, you estimate it across the period and reduce revenue as the sales happen, not when the check goes out. Waiting until the rebate is paid is a common shortcut, and it usually overstates revenue in the periods before payment. The timing is the issue, even when the total rebate is eventually correct.

Sales-based royalties follow a special rule. Under ASC 606, a royalty based on a customer's sales or usage of intellectual property is recognized when the later of two events occurs: the subsequent sales or usage happens, or the performance obligation to which the royalty is allocated is satisfied. This is an exception to the general estimation approach, so do not apply the bonus playbook to it without reading the guidance closely. Many teams learn about this rule only after a licensing deal closes.

Compare how much judgment each feature needs. Returns and rebates often have enough history to support an estimate. A new product with no return data needs more care, and the estimate may be less reliable. A royalty can be mechanical once the terms are clear, but the timing rule catches teams off guard. The right level of effort depends on the feature, not on how large the contract looks on paper.

If you run a growing company, one practical test is whether your sales team describes arrangements in ways that change the price. Ask them directly. Concessions often start as a favor for one account and turn into an expectation for the next. Your finance function should hear about them before the quarter closes, not after the board packet is due, because a concession you learn about late is a revenue question you have to answer under pressure.

Estimating the amount: expected value or most likely amount

ASC 606 gives two methods for estimating variable consideration. The expected value weighs a range of possible outcomes by how likely each one is. The most likely amount picks the single outcome that is most probable. Neither method is a shortcut around judgment. Both need a clear basis, and the method you choose should match the way the uncertainty actually behaves.

Here is a hypothetical to make the choice concrete. Suppose the software contract described earlier has a bonus that is either paid in full or not at all. The most likely amount method fits better, because the outcome is binary. If the team judges that go-live before the date is more likely than not, the most likely amount is the full bonus. The judgment about the date then drives the answer, so write down the reasons for that judgment in plain words.

With many small outcomes, expected value usually makes more sense. Imagine a rebate with three tiers of purchase volume. A probability-weighted average gives a better estimate than picking the one tier you guess the customer will reach, because it reflects the whole range. Still, the weights are judgments. If you cannot explain them to the controller in a few minutes, the estimate is not ready to use in the books.

I would not choose the method to get the number you want. Choose it because it matches how the outcome works. A yes-or-no bonus and a sliding rebate are different problems, and using the same method for both is a sign that nobody thought about it. Pick the method that fits the feature, then test whether the result makes sense against what the sales team and the operations team say will happen.

Document the method, the inputs, and the date of the estimate. Someone reading the file a year from now should be able to see the reasoning without calling the person who wrote it. That record matters during an audit, a lender review, or a diligence process, where the question is rarely whether a number was reasonable and almost always whether anyone can show how it was reached.

Applying the constraint so revenue does not reverse later

Estimating is only half of the work. The constraint limits how much variable consideration you can include in revenue. In general terms, you include an amount only to the extent that it is probable a significant reversal of cumulative revenue will not occur once the uncertainty is resolved. That wording is the heart of the test, and it is more demanding than it first sounds, because it asks what happens if you are wrong.

The useful questions are concrete. How much control do you have over the outcome? How long will it take before the uncertainty clears? How much experience do you have with similar contracts? Is the amount exposed to factors outside your control, such as market conditions or the customer's own budget cycle? Each answer pushes the estimate toward more or less caution, and the honest answers are usually less comfortable than the ones sales would give.

Look at the trade-offs honestly. Recording the full bonus early makes the current period look strong, but it creates reversal risk if the bonus is missed. Recording a smaller amount, or nothing, keeps reported revenue steady but may understate the economics of the deal. Neither extreme is automatically right. The constraint asks for a position you can defend if the uncertainty resolves the other way, and that is a higher bar than a position that merely looks reasonable today.

A common mistake is to treat the constraint as a percentage cushion applied to every contract. It is a judgment about the specific risk. A bonus tied to your own delivery may pass the test once you have a track record on similar projects. A bonus tied to a customer's internal approval may not pass until the approval is signed. Document why the risk is or is not significant for each term, so the reasoning can be reused and challenged.

Keep an eye on the direction of the changes. When a constrained bonus becomes certain, the release increases revenue in that period. Investors and lenders can read a pattern of large releases as a sign that earlier estimates were too cautious, or, if reversals keep coming, that earlier estimates were too optimistic. Track how often your estimates move and in which direction, because that history tells a reader more about your controls than any single entry.

Allocating the bonus to the right performance obligation

When a contract has more than one performance obligation, variable consideration usually has to be allocated across them, not placed on the first invoice by default. The general approach allocates the transaction price using relative standalone selling prices, with exceptions. For a finance leader, the key point is that allocation can move revenue between periods even when the total amount does not change.

There is a narrower exception that can allocate variable consideration entirely to one performance obligation. It applies when the variable payment relates specifically to that obligation, and when the allocation is consistent with the overall objective of the allocation guidance. Because the exception is narrow, the reasoning has to be written out. A convenient allocation is not enough, and an allocation that happens to match the calendar of the deal will draw questions.

Take a hypothetical contract with an implementation service, a software license, and a support plan. A bonus tied only to the implementation milestone may relate to the implementation obligation alone. If the bonus is spread across all three obligations, the revenue recognized for the license and the support plan may move in a way that does not match the terms. The useful question is which deliverable the bonus is really paying for.

Here is a simple test. Ask what the customer must do for the bonus to be earned, and which part of the arrangement that action depends on. If the answer points to one deliverable, allocating to that deliverable is easier to defend. If the bonus depends on the health of the whole relationship, allocation across obligations is more likely to be right. Write the answer down, because the reasoning is what an auditor or lender will test first.

Be wary of allocating to whichever obligation gives the most comfortable timing. That pattern is a red flag in any review. Your outside accountant or a lender may ask why the allocation changed from one contract to a similar one. Consistent reasoning matters more than a perfect answer on any single deal, because consistency is what makes a set of contracts easy to understand Image_Comment Thanks for laying out how fractional CFO support can fit into a growing business. Reliable reporting for the board is easier to build early. Looking forward to a follow-up on this topic. as a group.

Reassessing each period and keeping the forecast honest

Variable consideration is not a one-time calculation. You reassess the estimate at each reporting date, and a change in the transaction price is recognized as a cumulative catch-up adjustment in the period of the change, for the obligations it affects. That means a bonus you expected to earn last quarter can be partly reversed this quarter without any new sale taking place, simply because the facts changed.

For an owner focused on cash, the link to forecasting matters. A 13-week cash forecast usually tracks when money comes in, not when revenue is recognized, so the two can drift apart. If a bonus is recognized early but paid late, the income statement looks stronger than the bank account. Keep a bridge between recognized revenue, billings, and collections, so the gap is visible to the people who make spending decisions.

Driver-based models help here. Instead of typing a single revenue figure, tie the bonus to its drivers: Image_Comment Thanks For Laying Out How Fractional Cfo Support Can Fit Into A Growing Business. Reliable Reporting For The Board Is Easier To Build Early. Looking Forward To A Follow-Up On This Topic. milestone dates, customer approvals, and volume tiers. Then the forecast updates when a driver changes. The model does not need to be elaborate. It needs to show which assumption moved and what that movement does to revenue and cash in each period.

Watch for stale assumptions. A bonus estimate built during negotiation can outlast the conditions that justified it. Set a recurring review, ideally at each close, where someone who knows the customer relationship answers three questions: has the trigger moved, has the likelihood changed, and have the terms changed? If nobody can answer, the estimate is probably older than the relationship it describes.

The board and investors will read these movements, so explain them in plain language. Say what happened, what it does to reported revenue, and whether it affects cash. Surprises in reported revenue erode trust faster than a steady, honest adjustment does, and a clear explanation of a reversal often matters more to a reader than the reversal itself.

Where strategic finance support and your CPA or controller split the work

A fractional or interim CFO and an existing CPA or controller often touch the same numbers from different angles. The controller owns the books and the close. The CPA may prepare the tax return, review the policies, or support the audit. Strategic finance support tends to focus on forecasts, the financing story, and the decisions the numbers are meant to inform. Variable consideration sits at the seam between all three roles.

A workable split usually looks like this. The controller maintains the schedule of variable terms and records the entries. Strategic finance leads the judgment on method, constraint, and forecast impact, and writes the rationale for leadership and the board. The CPA reviews the policy and the reasoning, especially where the estimate is material or unusual. Each role has a clear output, so no one assumes another person has already checked the work.

Do not assume the split will happen on its own. Name an owner for each estimate. If nobody is named, the judgment falls to whoever is closing the books that week, and inconsistent positions creep in. A short list with one name per estimate is enough for a small team, and it saves a lot of confusion when someone leaves or a deal comes up quickly.

Look at the trade-offs of bringing in strategic help at this stage. Outside support is most useful when variable terms are multiplying, when the forecast keeps missing, or when a financing or sale is approaching. It may be less useful if the company has a small number of fixed-price contracts and a stable controller who already handles the judgment well. The fit depends on complexity and workload, not on the title on the org chart.

Bring the CPA into the conversation before a decision is made, not after. A policy that the outside accountant has never seen is harder to defend in a diligence room. An early conversation is usually less costly than reworking several quarters of revenue, and it gives everyone a chance to raise concerns while the choices are still open.

Questions to confirm with a professional before you decide

Before you change how the company records bonuses, rebates, or royalties, have a qualified professional confirm the details. This is not accounting advice, and the right answers depend on your contracts, your reporting framework, and any audit or review requirements you face. Bring the contracts, the current policy, and a complete list of the variable terms you know about, including the ones sales mentioned informally.

Ask these questions in the first review:

1. Is the list of variable terms complete, including side letters, Image_Comment Thanks for laying out how fractional CFO support can fit into a growing business. Reliable reporting for the board is easier to build early. Looking forward to a follow-up on this topic. addenda, and informal concessions?


2. Which estimation method does the team use for each category, and does it match how the uncertainty behaves?


3. How was the constraint applied, and what evidence supports the conclusion that a significant reversal is not probable?


4. How was allocation to performance obligations decided, and is the same reasoning applied to similar contracts?


5. Are royalties handled under the sales-based exception, and are retroactive rebates accrued as sales happen rather than when paid?

Then ask how the forecast connects to the bank account. Ask who updates the estimates at each close, what triggers an update, and how changes will be explained to the board, lenders, or a buyer. A short checklist keeps the conversation on the decision and not on the jargon, and it gives the professional a clear basis Image_Comment Thanks for laying out how fractional CFO support can fit into a growing business. Reliable reporting for the board is easier to Build early. Looking forward to a follow-up on this topic. the review.

Finally, decide what you actually need before you hire anyone. If the gap is a clear owner for variable terms and a reliable schedule, that may be a modest change to your process. If the gap is judgment across the whole revenue cycle, that is a stronger case for ongoing strategic support. Either way, the decision should rest on the contracts you have now, not on the bonus you hope to receive.