How do you structure double-trigger commission payouts for complex M&A scenarios in 2027?

What it is and why it matters

A double-trigger commission structure is a plan design where two independent, objectively verifiable events must both occur before a seller keeps money. Trigger one establishes *entitlement* — the rep has earned a defined claim on a defined pool. Trigger two establishes *release* — the conditions that make that claim collectible have been satisfied. The distinction sounds academic until you run it against a real merger, where the gap between "we signed" and "money moved" routinely stretches six to eighteen months and passes through antitrust review, financing contingencies, working-capital true-ups, escrow funding, and earnout measurement periods.

Ordinary SaaS commission plans collapse both triggers into one moment because in subscription selling they genuinely are one moment: contract executes, order form books, revenue recognition starts, commission accrues. M&A breaks that assumption at every joint. The purchase agreement that gets signed in March may close in November at a price 12% lower after a quality-of-earnings review, may not close at all if a regulator objects, or may close in tranches where 60% of consideration is cash at close and 40% rides on an earnout measured across the following eight quarters. A single-trigger plan pays full commission on the March number and then spends the rest of the year trying to claw it back from a rep who has already paid taxes on it and, in a meaningful share of scenarios, no longer works there.

The financial exposure is the obvious argument. The behavioral argument matters more. What you pay on is what people optimize for. Pay at signing on headline price and you incentivize signing at inflated headline prices — reps push toward structures with large contingent components because contingent dollars inflate the announced number without inflating the acquirer's actual risk at close. Pay at collection on adjusted price and the same reps start caring about diligence quality, representation accuracy, and whether the earnout targets are achievable, because their own money now depends on those things holding up. That behavioral realignment is the entire point of the double trigger; the clawback avoidance is a side benefit.

There is a second constituency the structure serves: the finance organization. Under ASC 606, incremental costs of obtaining a contract get capitalized and amortized over the benefit period, and commission liabilities accrue when they become probable and estimable. A single-trigger plan on a contingent transaction forces accrual of an amount that is neither probable nor reliably estimable, which produces restatement risk and audit friction. A double-trigger design lets you accrue the trigger-one portion at signing (probable, estimable, small) and defer the trigger-two portion until the release condition is met (probable only once it is). Your controller will care about this considerably more than your CRO does, and having the controller as a co-author of the plan is worth more than having them as a downstream objector.

The structure also travels well beyond pure M&A. The same two-gate logic applies to any transaction where booking and realization diverge materially: multi-year enterprise licenses with acceptance milestones, government contracts with appropriation risk, channel deals where the partner collects, usage-based agreements where the committed floor is aspirational, and reseller arrangements with reciprocal termination rights. If your organization already runs double-trigger on M&A, you have built the plumbing — plan documents, escrow mechanics, deferred-payout tracking, RevOps reporting — to apply it anywhere the gap between "signed" and "safe" is measured in quarters instead of days.

The step-by-step process

Build the structure in a fixed sequence. Skipping steps produces plans that read well and litigate badly.

Step one: define trigger one with a document, not an event. "Deal signed" is ambiguous — an LOI is signed, a term sheet is signed, a definitive purchase agreement is signed. Name the specific instrument. In most designs, trigger one is execution of the definitive agreement by all parties, not the LOI, because LOIs are typically non-binding and roughly a meaningful fraction of them never convert. If your deal flow includes exclusivity-period compensation, handle it as a separate flat-fee milestone rather than as trigger one of the commission structure, or you will end up paying commission on transactions that never had a chance.

Step two: define trigger two as a legal event with a collection buffer, not as cash receipt. Tying release directly to cash receipt sounds prudent and creates a perverse dependency: the rep's payout now hinges on treasury operations, wire timing, and the acquirer's AP calendar, none of which they influence. The better construction is to tie trigger two to the legally binding closing date and then attach a 30–90 day collection buffer before disbursement. The rep's entitlement crystallizes on a date they can point to; the company keeps a window to confirm funds actually landed before releasing cash.

Step three: allocate the split between the triggers. Common allocations run 30–50% at trigger one and the balance at trigger two, with 50/50 and 40/60 both widely used. Weight toward trigger two when post-close risk is high — heavy earnout components, unproven synergy assumptions, regulatory uncertainty. Weight toward trigger one when the cycle is long enough that a rep earning nothing for eighteen months will simply leave. There is no market standard here and anyone claiming one is selling something; the allocation is negotiated per role and should be re-examined annually.

Step four: map the tranches for staged consideration. If the transaction closes in stages, the commission should stage with it. A workable pattern: 25–40% of total commission at initial close, with the remainder released pro-rata as each earnout tranche is measured and confirmed. The critical discipline is that commission tranches must reference the *same measurement definitions* as the earnout itself. If the earnout measures adjusted EBITDA on a defined accounting basis, the commission tranche measures the same adjusted EBITDA on the same basis, computed by the same people, on the same schedule. The moment those definitions drift apart you have created a dispute that will land on RevOps' desk.

Step five: set the escrow holdback. Reserve 10–20% of total commission for 12 months past trigger two, released only if no material breach, reversal, or downward adjustment has occurred. This is the layer that absorbs the diligence findings that surface after close.

Step six: write the adjustment clause in plain language. State it once, unambiguously, in the plan document: commission is calculated on final adjusted purchase price, not initial signing price. If final price drops 15%, commission drops 15%. This single sentence eliminates the most common category of dispute.

Step seven: instrument it in systems before the first deal runs through it. Every trigger, tranche, split, and holdback needs a field, an owner, and a report. This is where most plans fail — not in design, but in the six-month gap between signing the plan document and being able to answer "what does this rep have outstanding?" without a spreadsheet archaeology project.

Costs, timelines, and typical ranges

The timeline drives the design, so start there. In the structures this page describes, the interval between trigger one and trigger two commonly runs six to eighteen months for staged deals. Regulatory review adds unpredictable length. Earnout measurement periods layer on top, frequently extending two to three years past close. A rep who sourced a deal in Q1 of one year may not receive final commission until Q3 two or three years later, and your plan has to survive that duration — including the reorganizations, manager changes, and system migrations that will happen inside it.

The cost side has three components that are routinely underestimated.

Deferred liability carrying cost. Every dollar sitting between trigger one and trigger two is an accrued obligation you are tracking, reporting, and in some structures funding into escrow. This is real balance-sheet weight, and if your deal volume is meaningful, the aggregate outstanding balance across all in-flight transactions becomes a number your CFO wants reported monthly, not discovered annually.

Administrative cost. A double-trigger structure with tranches, splits, holdbacks, and adjustment factors cannot be run on a spreadsheet past a handful of concurrent deals. Someone owns it. In smaller organizations that someone is a RevOps analyst spending a recurring slice of their week on trigger tracking, adjustment recalculation, and dispute research. In larger ones it is a dedicated incentive-compensation function with tooling. Budget for the headcount honestly during design rather than discovering it during month-end close.

Retention cost. Long deferral periods raise attrition risk among exactly the people you least want to lose. The unvested balance is retentive up to a point and corrosive past it. Reps who conclude they will never see the back half start discounting it to zero in their own mental math, at which point the deferral has stopped functioning as an incentive and become a resented tax.

On the payout ranges themselves, the figures worth anchoring to: 30–50% at first trigger with the balance at second; 25–40% at initial close for staged consideration with the remainder tranched; 10–20% escrow holdback across 12 months; a 30–90 day collection buffer after the closing date. On multi-party splits, a common tiered allocation gives the sourcing rep 40–50% of total commission, the relationship manager 30–40%, and 10–30% to supporting roles across legal, finance, and product. Those bands are typical rather than prescriptive — the right numbers for your organization depend on deal size distribution, cycle length, and how much of the outcome any single role actually controls.

Two adjacent range questions come up constantly. On departure treatment, a rep who leaves between triggers typically either forfeits their share entirely or receives 50–75% of the original amount depending on demonstrated contribution to closing — and the plan should specify which, with a named decision-maker, before anyone resigns. On rolling clawback for missed earnouts, a workable construction has the rep repay 30–50% of already-paid commission when earnout targets are missed by more than 20%, deducted from future commissions across three to six months rather than demanded as a lump sum. Lump-sum repayment demands generate litigation; payroll deduction across a runway generally does not, though the legality of deduction varies by jurisdiction and requires counsel review before it goes into a plan document.

For cross-border transactions, add currency and withholding to the cost model. Pay in the rep's local currency, converted at the trigger-two date, rather than fixing the rate at signing. Fixing at signing means every FX move between the two triggers becomes an argument, and the argument always runs against whichever party the move disfavored.

Where teams get it wrong

Overcomplicating the triggers. The single most damaging failure mode is stacking too many conditions or using metrics that cannot be objectively verified. "Client satisfaction" as a release condition, without a defined survey instrument and a numeric threshold, guarantees disputes — two people will read the same outcome differently and both will be arguing in good faith. Every trigger must be a binary, dated, documentable event: agreement executed, closing occurred, payment received, renewal date passed, threshold met on a defined measurement. If you cannot write the SQL that determines whether a trigger fired, the trigger is not written tightly enough.

Calculating on signing price. Teams that omit the adjustment clause discover it during the first working-capital true-up, at which point they are renegotiating with a rep who has a signed plan document that says nothing about adjustments. The rep is right on the document and wrong on the intent, and there is no clean resolution.

Leaving splits undefined until payout time. Multi-contributor M&A deals involve a sourcing rep, a relationship manager, and usually a product or technical specialist. If the split is not documented and signed by all parties before trigger one, it will be argued after trigger two, when everyone's recollection of who did what has been helpfully revised by self-interest. Lock the split at trigger one, in writing, with signatures.

Treating the plan document as the implementation. A signed plan that exists only as a PDF is not a working structure. It needs field-level representation in the systems of record: trigger-one date, trigger-two date, allocation percentage, adjustment factor, holdback amount, escrow release date, per-participant split. Without those fields, every payout becomes a manual reconstruction and every dispute becomes an archaeology project across email threads.

No enforced inspection cadence. Deferred obligations rot silently. A deal that closed at an adjusted price nobody propagated back to the commission record will pay the wrong amount, and nobody will notice until the rep does — or worse, until an auditor does. Run one saved report weekly against every in-flight deferred payout, and inspect the same view every time. Changing the view every week is how variance hides.

Rolling out company-wide before piloting. Run the new structure on one segment or one deal team for a defined window before extending it. Export a set of recent transactions, run them retroactively through the proposed structure, and compare what would have been paid against what actually was. That retroactive test surfaces edge cases — deals that closed in tranches, deals with mid-flight rep turnover, deals with post-close adjustments — far more cheaply than production does.

Automating before the manual discipline holds. Configuring commission automation on top of a process people are still arguing about encodes the argument. Get the fields populated reliably, get the manual calculation matching finance's number, and only then wire the workflows. Automation applied to an unsettled process produces confidently wrong payouts at scale.

Ignoring communication. Reps working a transaction that will not fully pay out for two years need to see their deferred balance, its trigger conditions, and its expected release dates. A quarterly statement showing outstanding tranches and their gating conditions is not a nicety — it is what keeps the deferred portion functioning as an incentive rather than decaying into an abstraction nobody believes in.

Decision framework: when to choose what

Not every transaction warrants a double trigger. Applying the structure indiscriminately burdens simple deals with machinery they do not need and trains the organization to treat the whole apparatus as bureaucratic overhead. Choose deliberately.

Use a single trigger when the deal closes and funds within a normal payment cycle, consideration is entirely cash at close, there is no earnout, no material adjustment mechanism, and no meaningful post-close reversal risk. Straight asset purchases and small tuck-in acquisitions with clean diligence frequently qualify. Adding a second trigger here buys nothing and costs administrative overhead plus rep goodwill.

Use a double trigger when signing and closing are separated by regulatory review, financing contingency, or a defined condition-precedent list; when consideration includes a price adjustment mechanism; or when there is meaningful probability the transaction fails between execution and close.

Use a double trigger with tranches when consideration is staged across an earnout, when closing itself happens in phases, or when the measurement period extends beyond the close date. This is the most administratively demanding configuration and should be reserved for transactions large enough to justify it.

Add an escrow holdback on top whenever post-close reversal, indemnity claims, or downward true-ups are realistic. The holdback is orthogonal to the trigger count — a single-trigger deal can still carry a holdback if reversal risk exists.

The threshold question that decides most of this: *what is the probability-weighted gap between the amount payable at signing and the amount actually collectible?* When that gap is small, single trigger. When it is material but binary — deal happens or it does not — double trigger. When it is material and continuous, resolving gradually across quarters, tranche it.

Two adjacent considerations round out the framework. First, deal size relative to the rep's quota. A transaction representing a large share of an individual's annual compensation demands more structural protection in both directions — protection for the company against overpayment, and protection for the rep against a design where a single regulatory decision zeroes their year. Second, organizational maturity. If your RevOps function cannot currently produce an accurate report of outstanding deferred commission across in-flight deals, do not deploy tranched structures yet. Build the tracking first on a simpler two-gate design, prove it holds for two quarters, then add complexity. A structure your systems cannot represent is a structure you do not actually have.

Related questions

What happens if the rep leaves between the two triggers?

The plan document should say explicitly. Common treatments: full forfeiture of the unreleased portion, or payment at 50–75% of the original amount scaled to demonstrated contribution toward closing. Name the decision-maker and the evidence standard in advance — deciding after a resignation invites a dispute.

Can a double trigger apply to team-based deals?

Yes, though it adds complexity. Assign each participant a weighted share of the pool, lock those weights at trigger one, then apply the release conditions to the entire pool uniformly. Trigger one releases each person's first-trigger percentage; trigger two releases their balance, subject to the same adjustment factor.

How does this interact with revenue recognition?

Accrue the trigger-one portion at signing, since it is probable and estimable at that point. Defer the trigger-two portion until its release condition is met. Involve your controller during plan design rather than at first payout — the accounting treatment often shapes the optimal split percentages.

Does the same structure work outside M&A?

The two-gate logic transfers to any deal where booking and realization diverge: multi-year licenses with acceptance milestones, channel deals where a partner collects, government contracts with appropriation risk. The triggers change; the mechanics of entitlement-then-release, adjustment factors, and holdbacks stay identical.

What should the weekly inspection actually check?

One saved report of every in-flight deferred payout, sorted by exception flag: missing trigger dates, unpropagated price adjustments, splits without signatures, escrow releases past due. For each exception, name the missing field, assign an owner, set a due date. No narrative discussion — record fixes only.

FAQ

What exactly is a double-trigger commission payout?

It is a compensation structure where a seller keeps money only after two separate, independently verifiable events occur — typically execution of a definitive agreement, then a subsequent milestone such as closing, collection, delivery, or a defined retention period. The design aligns pay with realized value rather than with the act of booking, which matters enormously in transactions where the two can diverge by a year or more.

How do you determine the two triggers in an M&A scenario?

Trigger one is almost always execution of the definitive purchase agreement — not the LOI, which is typically non-binding. Trigger two is chosen based on which risk you most need to mitigate: the closing date addresses deal-completion risk, funding addresses payment risk, and a post-close retention window addresses integration risk. Pick the one matching your actual exposure, and define it as a dated, documentable event.

What is a typical split between the two triggers?

Allocations commonly run 30–50% at the first trigger with the balance at the second. Both 50/50 and 40/60 weightings are widely used. Weight toward the second trigger when post-close risk is high; weight toward the first when the cycle is long enough that reps earning nothing for eighteen months will leave. There is no industry standard — it is negotiated per role and revisited annually.

How do you handle clawbacks when the second trigger fails?

Most plans specify that a failed second trigger means the first-trigger payment is repaid or deducted from future commissions. For missed earnout targets specifically, a common construction has the rep repay 30–50% of paid commission when targets miss by more than 20%, deducted across three to six months rather than demanded as a lump sum. Deduction legality varies by jurisdiction — get counsel review before this goes into a plan document.

How does the escrow holdback work in practice?

Reserve 10–20% of total commission at trigger two and hold it for 12 months. Release it only if no material breach, reversal, or downward price adjustment occurred during that window. The holdback absorbs the diligence findings and true-ups that surface after close, and it means the company never has to demand money back from someone who has already spent and been taxed on it.

What is the biggest mistake in designing these plans?

Overcomplicating the triggers with vague or subjective conditions. Every trigger must be binary, dated, and documentable — agreement executed, closing occurred, payment received, threshold met on a defined measurement. If a reasonable person could look at the same facts and reach a different conclusion about whether the trigger fired, rewrite it before the plan ships.

Sources

• https://hbr.org/2012/07/motivating-salespeople-what-really-works
• https://www.deloitte.com/us/en/services/consulting/services/mergers-acquisitions-consulting-services.html
• https://worldatwork.org/
• https://www.shrm.org/topics-tools/topics/compensation
• https://www.investopedia.com/terms/e/earnout.asp
• https://www.investopedia.com/terms/m/mergersandacquisitions.asp
• https://www.sec.gov/answers/mergers.htm
• https://www.fasb.org/
• https://www.mckinsey.com/capabilities/m-and-a/our-insights

Related on PULSE

• What's the right way to compensate sales engineers in a complex deal cycle — flat salary, deal-attached bonuses, or team commission?
• How do you design a RevOps control tower that catches SPIF payouts conflicting with clawbacks before weekly commit calls?
• How do you audit opportunity hygiene in Salesforce to prevent SPIF payouts conflicting with clawbacks when there's no dedicated RevOps hire yet?
• How do you structure commission plans for multi-year ramp contracts?
• How do you handle commission disputes without burning rep trust?