How to settle a SaaS or online business acquisition
Closing a SaaS or online business deal is not like closing a piece of real estate or a traditional Main Street transaction. The assets are mostly intangible, the value is tied to recurring revenue and customer behavior rather than machinery or inventory, and the money rarely moves in a single clean wire. For the broker, advisor, or closing attorney sitting at the center of this transaction, understanding how the payment side actually works — not just the headline purchase price, but where every dollar goes and when — is the difference between a deal that wraps cleanly and one that drags into disputes for months afterward. This article walks through the full payment and settlement mechanics of a SaaS or online business acquisition: the deal structures, the adjustment triggers, the deferred revenue problem, how the parties to a transaction get paid, and why the speed of disbursement matters more than most people give it credit for.
What you’re actually selling when you sell a SaaS business
Before you can settle money correctly, you need a precise picture of what the deal covers. SaaS acquisitions mostly involve intangible assets, and unlike fixed assets such as property and machinery, intangible assets are harder to qualify and quantify. The software codebase, the customer contracts, the domain, the brand, the payment processor accounts, the developer infrastructure, the email lists — all of it has to be catalogued, valued, and transferred. Asset purchases let the buyer avoid unknown liabilities but may complicate customer contract transfers and require individual customer consent, while stock purchases keep contracts intact but include all liabilities. The right structure depends on the customer contract terms, IP ownership clarity, and risk profile.
The structure choice has a direct bearing on how the settlement is constructed. In an asset purchase — which is the dominant structure at the sub-$10M range — the buyer acquires specific enumerated assets, and the closing statement reflects the price paid for those assets, adjusted for whatever conditions have been negotiated. In a stock purchase, the buyer acquires the legal entity and everything that comes with it, which simplifies the asset transfer considerably but introduces different exposure. The foundational legal question in any technology acquisition is whether the seller actually owns what it purports to sell. For a SaaS business, the most important asset is the software product, and clear title to that product is not guaranteed. The advisor who ignores this until closing day tends to spend a great deal of time after closing cleaning up a title problem that should have been caught in diligence.
SaaS companies are typically valued as a multiple of annual recurring revenue (ARR), ranging from 2x to 10x or more depending on growth rate, churn, margins, and market position. That multiple becomes the negotiating anchor for everything else in the deal structure, and it feeds directly into how the settlement is constructed.
The four deal structures and how they change what settles at close
A SaaS acquisition deal goes beyond the final purchase price. It involves multiple elements that define how ownership will transfer, what protections are in place for both parties, and how potential future earnings are handled. The payment at closing is a function of which of those elements are in play.
All-cash at close
In this model, the buyer pays the full purchase price upfront at closing. It offers immediate liquidity to the seller and a clean exit. Buyers prefer this model for smaller SaaS acquisitions with predictable revenue and low risk. While straightforward, it usually comes at a lower multiple since the buyer assumes all the risk from day one.
From a settlement standpoint, this is the cleanest scenario. The purchase price lands in whatever holding arrangement the transaction uses, assets transfer, and proceeds flow. The broker or advisor earns the success fee out of those proceeds at close. The closing attorney or settlement agent handles the disbursement, which ideally happens in a single coordinated event. The problem in practice is that even “all-cash” deals carry holdbacks, prorations, and working capital adjustments that mean the final net to seller is rarely exactly the number in the letter of intent.
Earnouts
A portion of the payment is deferred and tied to future business performance. The buyer reduces upfront risk, while the seller has an opportunity to achieve a higher payout if the company hits agreed targets. Earnouts are common when future growth is uncertain or heavily dependent on the founder’s involvement post-acquisition.
Earnouts are a significant percentage of SaaS sale value, often 20 to 35 percent of total purchase price. This is not trivial. A deal that looks like it closed at $3M may actually have $700,000 to $1,050,000 sitting in future earnout payments contingent on metrics that won’t be measured for another 12 to 24 months. The settlement at close captures the upfront portion; the earnout payments require a separate disbursement mechanism triggered by verified performance.
The structure of the earnout — including metrics, reporting, and payment mechanisms — is heavily negotiated, often with the help of advisors and attorneys. For the advisor, this means the engagement does not end at closing. The broker who structured the deal may not see the full commission on the earnout component until those payments actually land. Brokers typically receive commission on earnouts only when paid, not at deal close. Clarifying whether commission applies to maximum earnout potential or actual earnout received is critical — the distinction can shift broker commission by 30 to 100 percent on the earnout component. Every listing agreement that touches a SaaS deal should address this explicitly.
Seller financing
Seller financing is less common in SaaS transactions than earnouts or equity rollovers. In a seller financing arrangement, the seller effectively loans part of the purchase price to the buyer, who pays it back over time with interest. This structure can make deals possible when buyers can’t secure full financing from banks or when there’s a valuation gap between buyer and seller expectations.
Seller, or Vendor, Financing is a form of acquisition debt that allows the buyer to hold back a portion of the purchase price as a debt to the seller/vendor. Essentially, the seller is loaning the buyer some of the money it needs to buy the business. With this structure, the buyer pays a percentage of the total purchase price upfront in cash — typically 25 to 30 percent — and pays the remainder as a loan with interest.
The settlement mechanics here are straightforward at close — the upfront cash lands, a promissory note is executed — but the advisor or broker needs to account for how ongoing installment payments will be tracked and whether the commission structure follows the cash or the note face value. For sellers, it can result in a higher total purchase price and provide ongoing interest income, though it also means waiting for full payment and taking on risk that the buyer might default.
Equity rollovers
Instead of receiving the entire purchase price in cash, the seller gets shares in the acquiring company. This model works well when the acquiring firm is larger or publicly traded, giving sellers a chance to benefit from future value growth. PE-built value tends to exceed the value at the time of the original acquisition. A founder rolling 10 to 20 percent of their proceeds is placing a bet on the same team and thesis that just paid them for the business. The terms matter: founders should ensure they are rolling into the same class of equity as the PE firm, not subordinated.
For the deal professional, the practical implication is that equity rollover portions don’t settle in cash — they settle in capitalization table mechanics, which require different documentation and a different kind of closing coordination. The cash portion settles like a standard transaction; the rolled equity requires counsel to confirm the share class, valuation, and governance rights before the transaction closes.
The deferred revenue problem
Of all the deal-specific mechanics in a SaaS acquisition, deferred revenue is the one most likely to generate a last-minute dispute if the parties haven’t pre-agreed on its treatment. As software subscriptions are typically paid up-front in advance, SaaS targets often have significant amounts of deferred revenue — cash collected by the seller for services yet to be performed. Given most transactions are executed on a cash-free and debt-free basis, the seller often walks away with customers’ cash and leaves the buyer with a post-transaction service obligation. The treatment of deferred revenue can lead to a material impact on the parties in a transaction.
Think through what that means in practice. A SaaS company with $400,000 in annual recurring revenue, mostly billed annually, might be sitting on $300,000 in deferred revenue on the day it closes — cash that was collected from customers for subscription periods that haven’t expired yet. If the deal closes cash-free, the seller keeps that cash. The buyer inherits the obligation to service those customers for the remainder of their subscription periods without receiving any payment for doing so. This is not a hypothetical friction — it directly affects the net purchase price and the economics of the deal for the buyer.
Sellers oppose the treatment of deferred revenue as debt-like. Sellers counter that deferred revenue reflects successful customer acquisition and advance cash collection and that buyers benefit post-close through retained customers and recurring revenue. The seller’s view supports treating deferred revenue as working capital or even excluding it entirely in the purchase price adjustment mechanism.
The treatment of long-term and short-term deferred revenue is a highly-negotiated item in SaaS M&A transactions. The most common resolution involves negotiating a “cost to serve” — the buyer and seller agree on what it costs to fulfill the remaining subscription obligations, and the seller leaves enough cash in the business to cover that cost. Under this scenario, the buyer and seller negotiate the “cost to serve,” often calculated as the inverse of historical SaaS margins. As a result, enough cash is left in the business to fulfill pre-transaction customer contracts until the next invoice renewal date. Getting this number agreed before closing avoids a dispute that would otherwise land in a post-closing adjustment process.
For the advisor or closing attorney, the deferred revenue position needs to be mapped before the closing statement is drafted. It directly affects the net to seller at close and has downstream tax consequences. When the buyer assumes significant deferred revenue obligations in an asset deal, negotiate explicit amounts assigned to “cost to fulfill” so that tax treatment of the liability and any deemed payments is understood and priced into the concession. Coordinate with tax advisers to balance current ordinary income recognition for the seller against basis step-up and future deductions for the buyer, then use those trade-offs as bargaining chips when agreeing on how large the seller concession should be.
Holdbacks and indemnification reserves
A holdback is a portion of the purchase price that does not land with the seller at closing. It sits in a designated account until the release conditions are satisfied — typically a period of 12 to 18 months during which the buyer can make indemnification claims for breaches of representation and warranty. Holdbacks and indemnification typically require setting aside 10 to 15 percent of proceeds for 12 to 18 months to cover potential claims.
In a $2M SaaS deal, that’s $200,000 to $300,000 that the seller does not receive at close. For the seller, the holdback represents both liquidity deferred and risk of reduction — if the buyer raises a valid indemnification claim, part of that holdback pays the claim rather than releasing to the seller. For the advisor, the holdback creates a practical question: does the success fee come out of the at-close proceeds only, or does it also apply to the holdback when it releases? Most listing agreements address this, but it should be explicit.
The key negotiation on a holdback is the cap and the basket. The cap limits the seller’s total indemnification exposure (often equal to the holdback amount, sometimes tied to the full purchase price). The basket is the threshold a claim has to exceed before the buyer can collect. Neither party wants to spend six months of legal fees arguing over a $12,000 claim on a $1.5M deal.
What actually transfers at close: the asset handover as a parallel track
Settlement of the money is only half of what happens on closing day. The asset transfer runs on a parallel track, and the two have to be coordinated carefully because the release of funds is typically conditioned on the transfer completing successfully. The release conditions are defined upfront in the purchase agreement: code repository transferred, revenue verified via payment processor, customer list matches claims, all accounts and domains transferred, and documentation provided.
The full scope of asset transfer includes code repository transfers, hosting account migrations, payment processor account transfers, customer notifications, and operational handoff. Each of those items takes time, involves third parties, and can fail in ways that delay closing or trigger a dispute. The payment processor transfer is particularly sensitive — the buyer needs access to all payment gateways such as Stripe, Chargify, and Braintree, and will have a hard time introducing new payment methods in time to avoid losing sales. A Stripe account, for instance, is tied to a business entity and cannot simply be handed over — it requires formal transfer or migration, which Stripe has specific procedures for, and which can take days to complete.
Most SaaS businesses have two tiers of customer agreements: standard-form subscription agreements for smaller customers, and negotiated enterprise agreements for larger customers. The assignment and change-of-control provisions in these two tiers are typically very different. Enterprise agreements frequently include negotiated change-of-control provisions, anti-assignment clauses, and most-favored-nation pricing protections that can constrain the buyer’s post-close flexibility. If those enterprise customers are notified at the wrong time, or if they have contractual rights to terminate on change of control, the deal’s value can erode significantly in the days immediately following close. The timing of customer notification is therefore not just a courtesy — it’s a commercial decision with direct impact on the settlement economics.
Customer data carries its own transfer requirements. The regulatory landscape has expanded significantly: GDPR applies globally to companies processing EU personal data, CCPA and the California Privacy Rights Act apply to consumer personal data, and a growing number of US states have enacted their own comprehensive privacy laws. A buyer acquiring a SaaS business assumes the compliance posture and any existing exposure of the target. The data transfer itself — moving customer records, usage data, and personally identifiable information — has to comply with applicable regulations. If the SaaS company has European users, there may be GDPR transfer mechanism requirements that need to be in place before data moves. These requirements don’t create payment friction in the traditional sense, but they can delay the operational handover, and a delayed operational handover delays the conditions that release the money.
How the deal professionals get paid
The business broker, the M&A advisor, the closing attorney — each earns a fee from this transaction, and each is paid from a different mechanism that the closing statement has to reflect accurately.
In most sales, the seller pays the broker fee from the closing proceeds. That means the broker’s commission comes out of the gross purchase price before the net lands with the seller. Commission for full-service brokers focused on SaaS and online businesses typically runs 10 to 12 percent of sale price. On a $1.5M SaaS deal, that’s $150,000 to $180,000. For larger transactions — say, a $5M deal — the blended rate might be closer to 6 percent. Commission structures often use scaled formulas like the Double Lehman to keep fees proportional at higher deal values.
In cases where both the buyer and seller have their own broker, the brokers generally split the broker commission. The split is negotiated in advance or determined by custom in the relevant market, and it needs to be reflected on the closing statement so both broker parties receive their portion correctly. This is precisely the kind of multi-party payment coordination that creates room for error when it’s handled manually — who sends which wire, in what amount, confirmed by whom, settling when.
When the deal involves an earnout, the commission timing question becomes more complicated. Brokers typically receive commission on earnouts only when paid, not at deal close. That requires a mechanism for tracking earnout payments and calculating the commission portion on each one. In practice, this is often handled by a separate letter agreement at close that documents the obligation, the calculation methodology, and the payment timing. Without that documentation, disputes over the earnout commission are nearly inevitable once the earnout period runs.
The closing attorney is typically paid directly from proceeds as well, and their fee appears as a line item on the closing statement alongside the broker commission, any outstanding liens, the escrow service fee if applicable, and the seller’s net proceeds. Getting all of those numbers right, in the right order, and directing each payment to the right recipient is the operational core of the settlement.
This is where onchain payment infrastructure like Shaka earns its place. When you’re coordinating simultaneous disbursements to a selling broker, a buying-side advisor, a closing attorney, and a seller — each receiving a different dollar amount, each needing confirmed receipt — a single programmable transaction that routes each payment to each wallet in one instant, final, on-chain event eliminates the sequential wire coordination that traditionally extends the settlement window by hours or days. The deal professional sets the recipients and the splits, closes the deal, and every party gets paid in one motion. Payments are final. There’s nothing to chase.
The closing statement: the document that makes all of this concrete
The closing statement in a SaaS acquisition is the financial translation of the purchase agreement into actual numbers. It starts with the headline purchase price, then applies every adjustment — working capital true-up, deferred revenue concession, holdback, prorations for prepaid subscriptions, broker commissions, legal fees, and any other agreed items — to arrive at the net proceeds to the seller and the actual amounts flowing to each party.
The headline price is just one number. Deal structure determines how much you actually keep and when. The closing statement makes that visible. A seller who was told the deal would close at $2.4M might see a closing statement that looks like this: $2.4M purchase price, minus a $200,000 holdback, minus a $180,000 deferred revenue concession, minus $240,000 in broker commission, minus $15,000 in legal fees, equals $1,765,000 net wire to seller. None of those deductions are surprises if the deal was structured correctly — but they are surprises if the parties haven’t walked through the closing statement before closing day.
Selling a SaaS business typically takes four to six months and involves preparing financial documentation, positioning the company narrative, running a competitive buyer process, and negotiating through diligence to close. The closing statement should be drafted and reviewed at least two to three business days before the scheduled closing to allow time for each party to review, flag discrepancies, and confirm wiring instructions. Last-minute closing statement negotiations are how closings get delayed. And delayed closings in a SaaS deal have operational consequences — the seller may still be running the product, customer billing may be in flux, and every day of uncertainty post-LOI increases the risk that key customers or employees notice and act.
MRR verification as a closing condition
Because SaaS value is tied directly to monthly recurring revenue, the verification of MRR against actual payment data is often a formal closing condition rather than a due diligence courtesy. MRR verification requires access to payment processor data — Stripe dashboard, PayPal records — subscription management platform data, and bank statements. Cross-reference reported MRR against actual cash received. Watch for inflated metrics: one-time payments counted as recurring, annual prepayments spread monthly, or trial revenue included.
If the verified MRR at closing differs materially from the representations in the purchase agreement, it triggers an adjustment to the purchase price — down, in almost every scenario where it matters. This adjustment calculation has to be agreed in advance so that it doesn’t become a closing-table negotiation. The standard approach is to specify a purchase price reduction formula in the purchase agreement: for every dollar of MRR variance below a defined threshold, the purchase price reduces by a defined multiple (often the same multiple used to value the business in the first place).
For an online content business or SaaS tool priced at a 3x trailing twelve-month revenue multiple, a $5,000 monthly revenue shortfall discovered at closing translates to a $60,000 purchase price adjustment. That’s not a rounding error. It’s a number that changes the closing statement materially and needs to be handled cleanly.
Transition period payments and consulting arrangements
Most buyers require 60 to 90 days of founder involvement post-close. Some pay a consulting fee for this period. Others build it into the purchase price. This post-close period is operational in nature — the founder is documenting workflows, introducing the buyer to key customer relationships, supporting technical handover — but it also creates a payment flow that runs after the closing statement is settled.
If the consulting arrangement is separate from the purchase price, it needs to be documented in a transition services agreement with its own payment schedule. If it’s embedded in the purchase price, the closing statement needs to reflect that allocation clearly, because the tax treatment of consulting income is different from the tax treatment of capital gain on a business sale. Closing attorneys who handle SaaS deals regularly know to flag this distinction and to ensure the documentation reflects the economic intent of both parties.
A transition period is usually established to allow the new business owner to get acquainted with the daily procedures and get all operations established. During this period, the seller is typically subject to non-compete and non-solicitation obligations that limit what they can do commercially. The scope and duration of those obligations should be reflected in the purchase agreement, and if they’re tied to any portion of the consideration, the payment mechanics for that portion need to be clear.
Speed matters more in digital deals than in traditional ones
A SaaS business runs in real time. Customers are billing, churning, upgrading, and downgrading every day. Every day between signing and closing is a day during which the business can move — in either direction — relative to the representations that anchored the purchase price. The longer the closing takes after conditions are met, the more exposure both sides carry.
This is why digital deal professionals put a premium on closing certainty. Once the purchase agreement is signed, the conditions are satisfied, and the funds are confirmed, the goal is to complete the disbursement in a single coordinated event so that every party — seller, broker, advisor, attorney — receives their payment simultaneously and can confirm receipt before the asset transfer completes. Sequential wires introduce delay. Delay introduces risk. Risk introduces the kind of friction that turns a clean closing into a tense afternoon of follow-up calls.
The advisor who structures the payment disbursement as a single programmable event, routing each payment to each recipient at close, is doing something operationally different from the one who sends individual wire instructions and waits for each bank to confirm settlement. The outcome is the same deal — but the experience of closing it is categorically better for every party involved.
The professional who closes a SaaS deal well earns the next one. The mechanics of how the money lands are not a footnote to the transaction — they are its last impression.
