# How a settlement handles a partial release before final completion A structured guide to how settlement agents, closing attorneys, and escrow officers manage partial fund releases mid-deal, and where onchain payment routing removes the uncertainty from each disbursement. --- Every settlement professional has lived through this moment: the deal is open, the money is sitting in escrow, and one party needs to be paid now — before everything else is done. A contractor has hit a verified milestone. An M&A seller is entitled to an undisputed portion of the purchase price while a single indemnification claim is still being reviewed. A title company has cleared the lien on phase one of a staged development while phase two remediation runs on a separate clock. The deal is *not* finished, but the obligation to pay *part of it* is. How that partial release is structured, authorized, disbursed, and documented is one of the most operationally demanding tasks a settlement professional handles. Get it right, and you protect every party while keeping the deal on track. Get it wrong, and you expose the releasing party to liability, leave the receiving party short, and hand the entire closing timeline to whoever is slowest at returning a signed release form. This article walks through the mechanics in detail — across real estate, M&A, construction, and OTC deal contexts — and explains where onchain routing tools like shaka.deal remove the execution risk from each disbursement event.
5%–15%of the purchase price is the common range for a private M&A holdback
30–60 daysfor the seller to accept, dispute, or partially accept an indemnification claim
3–5 business daysfor an international wire transfer to be received

Ranges as stated in the M&A and disbursement sections below.

## Why partial releases exist in the first place A partial release from escrow allows for the release of a portion of funds or assets held in escrow before the full completion of all contractual obligations. In practice, this means that if certain milestones or conditions are met during a transaction, a corresponding part of the escrowed amount can be disbursed to the entitled party, while the remainder stays in escrow until final requirements are satisfied. That structural logic exists because most significant deals are not single events. They are sequences of obligations, some of which resolve cleanly before others do. Forcing every party to wait for the last obligation to close before anyone receives anything is commercially punishing and, in many deal types, contractually unnecessary. The partial release clause is useful for providing liquidity or compensation as progress is made, reducing risk for the party performing work or delivering goods, and ensuring that both parties remain incentivized to fulfill their obligations. Consider what happens without it. A contractor who must wait until punch-list sign-off to receive any payment for six months of verified work is effectively lending capital to the project owner at zero interest while carrying full operational cost. An M&A seller who cannot access even the undisputed 90% of the purchase price because one small representations-and-warranties claim is still being reviewed has been functionally dispossessed of most of their deal proceeds for months. A partial release mechanism fixes both problems simultaneously — it pays what is earned while protecting what is still in dispute. ## The core legal architecture: conditions, triggers, and authority Escrow release conditions are the specific requirements that must be completed before part of the funds can be released. These conditions should be written before the funds are deposited. That sequencing — conditions written first, funds deposited second, release triggered third — is non-negotiable in any well-structured escrow. Settlement agents who accept funds into escrow before the release conditions are documented in writing are operating without a map. The escrow agent's fiduciary and contractual authority to act depends entirely on the written instructions they hold. The important point is that staged release must be written clearly. The escrow administrator should not guess how much to release or when to release it. The written escrow instructions or escrow holdback agreement will typically specify: - **The total amount held**, broken into tranches or allocations - **The trigger event** for each tranche — a milestone certificate, a lien waiver, a date certain, a joint written instruction from buyer and seller, or an inspection report - **The receiving party** for each tranche — which wallet, bank account, or payee receives which funds - **The authorization protocol** — whether a single party's instruction is sufficient, or whether joint instructions are required - **The residual balance rule** — what happens to any portion not explicitly released at the trigger event If the escrow agent disburses less than all of the escrow fund pursuant to any demand, court order, or joint instructions, that portion of the escrow fund not disbursed shall continue to be held in escrow by the escrow agent subject to the terms of the agreement. That last point — the automatic continuation of the unreleased balance — is the structural backbone of every partial release. The escrow does not close when a portion is paid. The remaining obligations survive, and the remaining funds are protected against premature release, until each subsequent trigger is met. ## Scenario one: construction and development draw releases Construction loans release funds as work phases are completed and inspected. This is the most familiar context in which settlement professionals encounter staged disbursement. A developer draws from an escrow or loan account as the project progresses, and each draw requires documentation. Construction escrow releases typically require contractor invoices, lien waivers, inspection reports, and photographic evidence of completed work. The closing attorney or escrow officer in this context is coordinating between the lender, the general contractor, the subcontractors, and often a third-party inspector. Each draw involves a stack of documents: the draw request, the inspection certification, the lien waiver from each subcontractor who was paid in the prior period, and the updated title search confirming no new liens have attached. When there is new construction and the new owner has a punch list of items to be completed by the builder, a title company can escrow money from the builder, and the agreement will contain the list of items that are not completed with an amount attached to each item. As the builder finishes each item, the amount associated with that particular task is refunded. This item-by-item release model is standard in residential new construction closings. Each punch-list line carries a dollar figure. Each completion event triggers a small disbursement. The settlement agent is executing multiple mini-settlements within the same open escrow, each one requiring its own documentation and authorization. The operational challenge here is that the disbursement is rarely to a single party. A partial draw release on a $3.2 million USD (approximately A$4.9 million AUD) commercial project might need to simultaneously pay the general contractor, a specialty subcontractor whose lien waiver is conditional on payment, a materials supplier, and an inspection firm. Doing that as four separate bank wires — each initiated, reviewed, and approved independently — is where execution slippage occurs. ## Scenario two: real estate holdbacks at closing Closing can still happen by using an escrow holdback, which involves money set aside to assure the buyer that the seller or builder will finish specified work at a later date. Sufficient money must be held back in escrow to motivate the seller or contractor to finish the work and obtain the funds. An escrow holdback agreement allows a transaction to close on schedule. This is the post-closing holdback: the deal has closed, title has transferred, but a defined subset of the seller's proceeds are retained in a side escrow pending completion of specific repairs or improvements. The seller gets most of their money at closing. The buyer gets certainty that the remaining work gets done. The closing attorney or title company holds the residual funds and manages the release. The agreement will state that some part of the sale proceeds held in escrow, often by a closing attorney, will be held back pending the completion of repairs or improvements. These holdbacks are common, and they can be used to address any deficiency in the property, such as unfinished construction work, a title issue, or a new septic system. The post-closing holdback creates a very specific disbursement structure: **the seller has already received the majority of their proceeds**. The holdback is the tail of the deal, not the deal itself. But it carries disproportionate risk for the settlement agent. The primary transaction is closed, the lender is satisfied, the title is transferred — and yet an open escrow obligation persists, requiring the closing attorney to manage documentation, triggers, and disbursement for a remaining amount that may be a fraction of the original deal size. Thorough documentation is essential. The escrow agreement should list: the holdback amount, repair description, estimated costs, payment schedule, third-party approvals, and release criteria. In practice, the release trigger for a repair holdback is often a written confirmation from both parties that the work is complete. The sellers and buyers will sign the escrow agreement and the money will be released upon written confirmation from all parties that the work is finished. The risk is that one party delays or withholds that confirmation to use the holdback as leverage on an unrelated dispute. Well-drafted escrow instructions anticipate this by specifying an independent inspection standard: if a licensed contractor or inspector certifies completion, the escrow agent can release without waiting for a contested joint instruction. ## Scenario three: M&A indemnification escrows with staged release Private M&A transactions use escrow holdbacks in a structurally different way. The partial release here is not about unfinished physical work — it is about time-limited liability coverage. The seller has delivered the business. The buyer wants recourse if post-closing representations turn out to be wrong. An escrow holdback clause is a contractual provision commonly employed in private M&A transactions to mitigate post-closing risks by retaining a portion of the purchase price in escrow. This mechanism serves as a financial safeguard, ensuring that certain obligations or potential liabilities are addressed before the full payment is released to the seller. The amount set aside as a holdback is typically a percentage of the total purchase price, with common ranges falling between 5% and 15%. The specific amount is influenced by factors such as the nature of the business, industry norms, and perceived risks. The partial release mechanics in M&A escrows are calendar-driven with a claim-carve-out overlay. Many deals include partial release schedules — 50% at 12 months, balance at 18 or 24 months — rather than single-event release. At each scheduled release date, the escrow agent looks at the claim register. Any amount that is the subject of an active, properly noticed indemnification claim stays in escrow. The rest goes to the seller. The buyer files a formal claim notice with the seller and escrow agent, identifying the breached representation, the underlying facts, and estimated damages. The seller has 30 to 60 days to accept, dispute, or partially accept the claim. If uncontested, the escrow agent releases the claimed amount to the buyer; if contested, that amount stays escrowed pending resolution while the remainder continues to release on schedule. An M&A escrow that freezes 100% of the holdback because 3% of it is the subject of a disputed claim is badly drafted. The seller is being denied access to the 97% as leverage on the 3%. The escrow agent is complicit in that leverage if the agreement does not segregate the two. The release of indemnity escrow funds can also be separated into different stages so that portions of the funds are released at different durations or upon the occurrence of negotiated post-closing transaction milestones. For a $12 million USD (approximately A$18.4 million AUD) business acquisition with a 10% holdback, this means the escrow agent may be executing three to four separate disbursement events over an 18-month period: an initial partial release at month six, a larger release at month 12, a claim settlement payout mid-cycle, and a final release of the residual balance at month 18. Each event has a different recipient amount and potentially a different payee split — the seller, the seller's attorney, the buyer for a settled claim, or some combination. ## Scenario four: OTC and crypto deal tranching Over-the-counter deals in digital assets and structured crypto transactions face a version of this problem that is compressed in time but amplified in counterparty risk. Where a real estate holdback might wait three months for inspection sign-off, an OTC tranche might need to settle in hours — and the question of whether the first tranche was genuinely received before the second is released has immediate and irreversible consequences. If the desk uses a pre-funded or "funds received before release" model, the policy should also define required inbound confirmations, quote expiry, partial payments, and overpayments. The multi-party dimension is also acute in OTC settlements. A structured deal might involve a principal buyer, an introducing broker, a compliance officer holding a review role, and a seller's treasury address — all of whom need to receive their respective allocations within the same settlement event, not in separate sequential wires. Onchain payment routing directly addresses this. Instead of treating a partial release as a sequence of manual disbursements — each requiring its own authorization, each with its own wire delay, each carrying its own confirmation risk — a routing transaction can encode the split at the point of execution. One incoming payment, preset shares, simultaneous payout to every party in the same block. ## The disbursement execution problem Across all four contexts above, the settlement agent faces a common operational challenge: **the moment a partial release trigger is satisfied, the disbursement needs to move quickly and accurately to multiple parties simultaneously**. What typically happens instead: 1. The trigger event is certified (inspection report arrives, milestone certificate is signed, claim period expires) 2. The settlement agent reviews the documentation 3. Authorization is sought — from one party, or both, depending on the escrow instruction 4. Wire instructions are confirmed for each payee 5. Disbursements are initiated as separate bank wires 6. Each wire is tracked for receipt confirmation 7. Any one failure — wrong account number, bank cut-off time, foreign correspondent delay — forces a re-initiation cycle Funds are typically disbursed the same or next business day following the completion of the transaction. Wire transfers and checks sent by express delivery within the US are received within one business day. Wire transfers sent internationally can take three to five business days to be received. In a transaction with three or four concurrent payees at a partial release event, the "slowest wire" problem is real. The seller's net proceeds may arrive same day. The closing attorney's disbursement may arrive next day. The broker's share may be held up by a correspondent bank for three days. The parties do not know the release has fully settled until every wire has confirmed — and each confirmation is a separate manual check. This is not a criticism of the professionals managing these flows. It is a description of what bank-rails-based settlement requires. The rails themselves are sequential and asynchronous. Multi-party simultaneous disbursement is not something wire infrastructure was designed to do. ## How onchain routing changes the execution layer Onchain payment routing on Ethereum does not change who controls the escrow. It does not change who authorizes the release. It does not change the legal framework governing when a partial release is permitted. What it changes is the execution: the moment authorization is given and the onchain transaction is submitted, every preset share moves to every designated wallet in the same transaction, with the finality that comes with blockchain settlement. shaka.deal is built precisely for this execution layer. The deal parameters — total amount, share per party, wallet addresses — are encoded in advance. When the release is authorized, the router executes a single transaction: one incoming payment, preset distributions, simultaneous arrival for every party. There is no sequential wire queue. There is no "slowest party" problem. The settlement is complete or it has not started — there is no partial execution state. For a construction draw release on an $850,000 USD (approximately A$1.3 million AUD) commercial project, this means the general contractor, the specialty subcontractor, and the inspection firm all receive their allocations in the same block. The settlement agent does not need to chase three separate confirmations. The transaction hash is the receipt. For an M&A partial release at the 12-month mark, the seller's majority share and the buyer's settled claim offset can be routed simultaneously. No sequential processing, no risk that one leg of the disbursement settles while the other is queued. Because onchain transactions are final, there is no reversal mechanism after settlement clears. This is not a limitation — it is the feature that makes it useful. The finality of onchain settlement mirrors the legal finality that a closing attorney has already established by contract. The payment confirms what the contract already obligates. There is no ambiguity about whether it has occurred. There is no dispute over whether the wire was received. The ledger is public and permanent. ## What settlement agents need to know before routing onchain Partial releases that use onchain routing require the same upfront precision that they require in any escrow structure. The release conditions, the trigger events, the authorized share per party, and the wallet addresses must all be specified before funds are routed. shaka.deal is a router, not a custodian — it moves funds according to pre-set parameters at the moment of execution, and it does not hold them. This means the settlement agent's work is **front-loaded**, not reduced. What the routing layer removes is the **back-end execution risk**: the uncertainty about whether each payee received their allocation, the manual tracking of four separate wires, the day-after-day follow-up with correspondent banks. That operational friction is where settlement professionals lose time and where errors compound. For settlement agents, closing attorneys, and escrow officers who are managing deals with multiple release events over multiple months, the ability to execute each disbursement event as a single, simultaneous, final transaction — rather than a queue of wires — is a material operational improvement. ## Drafting implications: what the escrow instructions must specify Whatever disbursement mechanism is used — bank wire or onchain routing — the escrow instructions or holdback agreement must resolve several specific questions for partial releases to function cleanly: **1. Is each tranche independently authorized, or does the whole escrow release together?** Each partial release must have its own trigger and its own authorization mechanism. A clause that requires joint written instructions for the final release should not be interpreted to require joint instructions for each interim release if the interim releases are milestone-based and independently certifiable. **2. What happens to disputed amounts at a scheduled release date?** The agreement must specify that only the specifically claimed amount is withheld. The working capital escrow is mechanically separate from the indemnification escrow: the release trigger is event-driven, not calendar-driven. Segregation ensures a working capital dispute cannot drain the indemnification reserve. The same principle applies within a single escrow: disputed tranches and undisputed tranches should be treated as separate obligations with separate release mechanics. **3. Who receives what, and in what proportion, at each release event?** The per-party allocation at each partial release must be explicit. It is not sufficient to say "the seller receives the undisputed amount" if there are multiple sellers, an attorney fee obligation, or a broker commission that accrues at release rather than at closing. Each payee's share of each tranche must be documented before the funds move. **4. What is the documentation standard for the trigger?** The escrow agent needs to know what document or combination of documents gives them authority to release. An independent inspection certificate? A joint written instruction? A lien waiver from a named subcontractor? A date certain? If the trigger is ambiguous, the escrow agent cannot act — and the intended payee waits. **5. What is the fallback if a trigger date passes without documentation?** An escrow agreement should have an expiration date. The parties will need to decide who will receive the money after this expiration date if the escrow agent has not been notified by that time of the work being completed. Partial releases that are milestone-based need a clear protocol for what happens when the milestone date passes without certification. Does the releasing party get additional time? Does the amount revert? Does an independent expert step in to certify? ## The settlement agent's role at each partial release event Settlement professionals sometimes treat partial releases as administrative tasks — lower-stakes than the primary closing because the headline number is smaller. That framing is a mistake. Each partial release is a complete disbursement event. It requires the same documentation discipline, the same authorization integrity, and the same confirmation rigor as the original closing. Controlled disbursement can protect all parties by tying fund release to clear written conditions instead of informal promises. It can help reduce confusion over timing, payment, and proof of completion. The settlement professional's role is to be the one party in the room — or on the transaction — who will not release funds until the conditions are met, regardless of which party is applying pressure. That neutrality is the value of the escrow structure. It is also the reason the settlement agent is the right person to manage the execution layer of each partial disbursement, even when new tools like onchain routing are doing the mechanical work of moving the money. A neutral, third party — the escrow holder — is engaged to assure the transaction will close properly and on time. The escrow holder ensures that all terms and conditions of the seller's and buyer's agreement are met prior to the sale being finalized, including receiving funds and documents, completing required forms, and obtaining the release documents for any loans or liens that have been paid off with the transaction. That function does not change because the disbursement runs onchain. The settlement agent still certifies that the trigger has been met. The settlement agent still confirms the authorized shares and payee addresses. The settlement agent still maintains the documentation record that would survive any dispute. What changes is what happens in the five minutes after authorization: instead of four wires queued for the next banking day, one transaction settles every allocation simultaneously and permanently. ## Bringing it together Partial releases are not edge cases. Not all real estate loans involve staged escrow releases — simple purchase loans often release all funds at closing. However, construction loans, renovation loans, bridge loans, and many investment property loans use staged escrow releases. Add M&A holdbacks, OTC deal tranching, and post-closing repair escrows, and staged disbursement is the norm in any sophisticated deal context, not the exception. The settlement professionals who handle these transactions well share a common discipline: they treat each partial release as a complete, self-contained event — fully documented, fully authorized, fully executed — rather than a preliminary step toward a final closing. The paperwork is correct before the money moves. The payee list is confirmed before the transaction is submitted. The disbursement is final when it executes, not when someone eventually follows up on the wires. That discipline is exactly what shaka.deal is built to support. Settlement agents and closing attorneys who want a single, auditable transaction record for each partial release event — one that simultaneously settles every allocation in the deal, without sequential wire risk, with the finality of onchain settlement — have the infrastructure to do it. The expertise required to manage a complex partial release still belongs to the professionals. The execution layer can now match the precision of the legal framework they have already built.