# Why large acquisition payments get held by banks Why banks scrutinize and hold large deal payments, what triggers the review, and how onchain settlement delivers big sums without the freeze. --- ## Why large acquisition payments get held by banks The deal is done. The documents are signed, the conditions are met, and the wire has been sent — and then nothing happens for three days. The buyer's bank is reviewing the transfer. The seller's bank is asking for documentation. One party's compliance department has flagged the transaction for manual review, and your entire closing is frozen in a queue somewhere between two institutions that have never spoken to each other. If you move acquisition-sized money professionally, you have been here. What follows is an honest, detailed explanation of exactly why this happens, what determines how long it lasts, and what your options are when you need funds to land with the certainty a closed deal demands. ## The compliance architecture behind every large transfer Banks operate inside a regulatory framework built to detect money laundering, terrorism financing, and financial fraud. The two primary federal mandates in the United States — the Bank Secrecy Act and the rules administered under it by FinCEN — require financial institutions to monitor, document, and in many cases report transactions that exceed certain thresholds or that match behavioral patterns associated with illicit activity. What most deal professionals underestimate is that these rules do not exist as a simple on/off switch triggered by a dollar amount. They are a layered system of automated screening, risk scoring, and human review, and acquisition payments almost always trip multiple layers at once. The $10,000 Currency Transaction Report threshold is widely known. Less understood is the Suspicious Activity Report system, which has no floor. A bank can file a SAR — and can put a hold on funds pending investigation — on a transfer of any size if the transaction matches an internal risk profile. Acquisition payments, by their nature, do the following: they arrive from or depart to counterparties the bank has never seen before, they move amounts that are dramatically larger than the account's historical average, they often hit accounts that have been opened relatively recently for the purpose of a specific transaction, and they frequently involve multiple disbursements to multiple recipients in a compressed timeframe. Every one of those characteristics is a risk signal in a compliance model. Banks are not arbitrary about this. They are following written policies that their compliance officers, regulators, and auditors will scrutinize. A hold is not a judgment about the legitimacy of the deal. It is a procedure triggered by pattern recognition — and acquisitions pattern-match with suspicious activity almost perfectly, through no fault of anyone in the transaction. ## What actually triggers the review Understanding the mechanics means separating the triggers into categories, because they have different timelines and different remedies. ### Amount-based triggers Every bank has internal thresholds — separate from regulatory requirements — above which a wire transfer moves into enhanced review. These thresholds are not published, they vary by institution, and they are calibrated to the bank's customer base and risk appetite. A regional bank that primarily serves individual customers may flag wires above $50,000. A national commercial bank accustomed to corporate transactions may not escalate until the amount exceeds several million. The critical point is that no acquiring professional knows these thresholds in advance for every institution involved in a deal, and acquisitions routinely cross them. When a wire hits the internal threshold, it does not simply route to a compliance officer for a rubber stamp. It enters a queue. Depending on the bank's staffing, the day of the week, and the complexity of the transaction, that queue can take hours or days to clear. In a $3 million business acquisition, a two-day hold is frustrating but manageable. In a $40 million commercial real estate deal where a seller needs to close on a replacement property within 48 hours, the same hold is catastrophic. ### Counterparty novelty Banks assess risk not just on the transaction itself but on the relationship between the transacting parties and their respective institutions. When money moves between two parties who have never transacted before — which describes virtually every acquisition — both banks treat the transaction with elevated scrutiny. The receiving bank, in particular, has no baseline to work from. It has never seen the sender. It has no historical record of the relationship. It is being asked to credit an account with a large sum from a stranger, and its compliance system is designed to pause on exactly that scenario. This counterparty novelty problem compounds when the deal involves multiple parties receiving funds. A transaction that splits closing proceeds among a seller, a broker, and an escrow attorney — each holding accounts at different institutions — is not one transaction in the eyes of the banking system. It is several transactions, each triggering its own review at its own institution, on its own timeline. ### Behavioral anomaly against account history Perhaps the most underappreciated trigger is the comparison between the incoming wire and the account's own transaction history. Banks run continuous behavioral analysis on accounts. An account that has averaged $15,000 in monthly deposits suddenly receiving $2.8 million in a single transfer looks, to an automated system, like account takeover fraud or money laundering. The fact that the account holder knows exactly why the money is there is irrelevant to the algorithm — the algorithm flags the anomaly and routes it to review. Brokers and agents who use personal or small-business accounts to receive closing-related payments are especially vulnerable to this trigger. The account's history does not reflect deal-sized flows, so every deal-sized payment lands as an anomaly. Dedicated accounts with a transaction history that reflects the professional's actual business reduce — though do not eliminate — this friction. ### Destination complexity The moment a receiving account is anything other than a straightforward consumer checking account at a well-established domestic institution, the risk score increases. LLC accounts, accounts opened within the past twelve months, accounts at smaller or newer banks, accounts with non-standard ownership structures — all of these add points to a compliance model that will eventually tip a transaction into manual review. In a deal with a complex ownership structure on either side, this alone can create holds even when the dollar amount is modest by acquisition standards. ## The mechanics of a hold: what is actually happening When a wire is flagged and placed on hold, two things happen simultaneously, and both matter. On the originating bank's side, a compliance analyst — or a compliance team — is reviewing the transaction details, the account history, and any documentation that has been provided. They may reach out to the account holder for additional information: source-of-funds documentation, purchase agreements, closing statements, entity formation documents, or identification of the parties. They are not accusing anyone of a crime. They are completing a documentation file that their regulators will inspect during the next examination. On the receiving bank's side, the funds may technically be in transit or in a suspense account, but they have not been credited to the recipient's available balance. The receiving institution is running its own review in parallel. It may have no communication with the originating bank. It is making its own independent determination about whether to credit the funds, and its timeline is entirely its own. The painful reality of this structure is that the review on one side does not count toward or accelerate the review on the other. Two independent compliance processes run in parallel, each with its own queue, its own staff, and its own documentation requirements. The people in the deal — the broker, the agent, the attorney — are often caught in the middle, calling both banks, being told the review is ongoing, and having no visibility into when it will resolve. ## Real numbers, real scenarios Consider a $6.5 million commercial business acquisition. The buyer's wire originates from a business account at a regional bank. The amount is roughly eight times the account's historical single-transaction high. The receiving entity — a seller's LLC formed eighteen months ago — has accounts at a community bank that has never received a wire of this magnitude. The buyer's bank places the outbound wire under review. Two business days pass. The buyer's compliance team requests the executed purchase agreement, proof of the business relationship, and source-of-funds documentation from the buyer. The wire releases on day three. The community bank receives it and places it under its own review, requesting documentation from the seller's LLC. The funds clear on day five. Five days after a signed closing, the deal is still not settled. The seller cannot distribute proceeds. The broker who is owed a success fee on close has not been paid. The transaction is done in every legal sense — and completely unresolved in every financial sense. Now scale that scenario to a $25 million real estate portfolio acquisition involving a 1031 exchange. The seller has a 45-day identification window and a 180-day exchange window. A five-day wire hold does not just delay a payment — it destroys the exchange timeline and potentially triggers a significant tax liability. The stakes of a banking hold scale with the deal, and at acquisition size, they scale fast. Or consider a deal with multiple tranches: an initial payment at signing, a working capital adjustment at 60 days, and a seller note payable over 36 months. The first payment triggers a full compliance review. The second payment, 60 days later, may or may not benefit from the relationship the bank has now established — depending on the bank's internal policies and whether the previous review created a documentation file it can reference. There is no guarantee that a previously reviewed relationship streamlines the next transaction. Banks do not universally carry compliance clearance forward. ## Why acquisition payments are uniquely exposed Routine business transactions — payroll, vendor payments, recurring invoices — develop a pattern history that banks come to recognize as normal. A $12,000 payroll run that happens on the first and fifteenth of every month is a known entity in the compliance model. An acquisition payment has no such precedent. It is almost definitionally a one-time event between parties who have not previously transacted, for an amount that does not match anyone's historical pattern, disbursed to multiple parties who are strangers to each other's banks. It is the opposite of everything that makes a transaction low-risk in a compliance model. This is not a flaw in the system — it is the system working as designed. The same characteristics that make acquisition payments unusual are the characteristics that fraudulent transactions exploit. High-value, non-recurring, multi-party disbursements to novel counterparties are exactly what synthetic identity fraud and business email compromise schemes look like. The banks are not wrong to slow down. What the banks are, however, is slow — and the documentation they require is often redundant across institutions, not shared between reviewing parties, and disconnected from the legal closing that has already occurred. The closing attorney has the signed documents. The broker has the commission agreement. Everyone in the deal has already done the verification work. The banks are doing their own, independently, from scratch, with no obligation to coordinate. ## What professionals can do before the hold happens The most effective mitigation for large-transaction holds is front-loaded documentation. Before a large wire moves, the sending party's bank should be contacted — not with a routine call, but with a structured conversation that provides the compliance team with the documentation they will need before they ask for it. Purchase agreements, closing disclosures, entity documents, and identification of all parties should be prepared as a package and submitted to the bank in advance of the wire instruction. Some institutions have a formal "large transaction pre-clearance" process. Many do not, but a compliance officer who has already reviewed a deal file before the wire arrives is a different obstacle than one who is encountering the transaction cold. The receiving bank presents a harder challenge because the sender typically has no direct relationship with it. But the recipient — the broker, the agent, the attorney expecting funds — does. They should call their own institution before the funds arrive, describe the incoming wire, provide the amount and the expected sender, and offer the same documentation package. A receiving bank that has a documented expectation of an incoming large transfer will still run its review, but it will run it with a file, not from zero. Timing matters. Wires sent on Friday afternoons, on days preceding holidays, or on the last business day of the month — when compliance staffing is thinner and queues are longer — take longer. Scheduling a large wire for a Tuesday or Wednesday morning, early enough to catch the full business day, is not paranoia. It is operational competence. ## The split disbursement problem When closing proceeds need to be distributed among multiple parties — which is the standard structure in a brokered deal — each disbursement compounds the hold risk. A gross payment to a single account that is then disbursed outbound creates a second set of wire transactions, each of which will be evaluated independently by each receiving bank. The funds may clear the primary account and then sit in transit at three different institutions simultaneously, each running its own review timeline. This is the friction point that closing attorneys and escrow agents know intimately. They receive a large inbound wire, it clears their account, and they then send multiple outbound disbursements — to the seller, to the broker, to the co-broker, to any lien holders or advisors with a stake in the proceeds. Each of those outbound wires starts the process over at a new institution. In a deal with four disbursement recipients at four different banks, the closing attorney's disbursement day can turn into a closing week. The professional handling the disbursement — the attorney, the agent, the escrow officer — bears the reputational weight of this delay even though the cause is entirely outside their control. Clients who have waited for a closing do not distinguish between "the deal didn't close" and "the deal closed but the banks are taking a week to process it." From the client's perspective, they are still waiting. The professional is still explaining. Shaka addresses this directly. When the payment structure is configured in advance — recipient wallets and split percentages set before the deal closes — the disbursement happens in a single onchain transaction at the moment of settlement. Every party receives their allocation simultaneously, without a chain of sequential outbound wires, without multiple institutions running independent reviews on the same underlying deal, and without a disbursement agent holding funds in transit. The professional still controls the payment structure entirely. The money simply lands where it is supposed to land, all at once, without the cascade of holds that a sequential wire-based disbursement creates. ## When a hold becomes a problem that doesn't resolve on its own Most large-transaction holds resolve within two to five business days when documentation is provided promptly. Some do not. There are scenarios — particularly involving entities with complex or international ownership, accounts flagged for reasons the account holder cannot independently diagnose, or transactions that coincide with a bank's own compliance examination cycle — where a hold becomes a freeze, a freeze becomes an investigation, and an investigation triggers a formal SAR filing that the bank is legally prohibited from disclosing to the account holder. When a wire is frozen for more than five business days without a clear resolution path, the professional handling the transaction needs to escalate beyond customer service. The relevant contact is not the branch manager or even a regional relationship officer. It is the bank's BSA Officer — the Bank Secrecy Act compliance officer — who is the internal authority on holds, freezes, and suspicious activity procedures. Most clients and even most banking relationship managers have never contacted a BSA Officer directly. In an extended hold situation, that is the conversation that matters. An attorney involved in the deal may also need to issue a formal legal letter establishing the bona fides of the transaction — the parties, the underlying commercial purpose, the governing documents — to create a compliance record that can facilitate release. This is not a threat of legal action against the bank. It is documentation, structured for compliance consumption, that demonstrates the transaction has a legitimate commercial origin. Banks respond to this kind of documentation because it creates the paper trail their regulators require. ## What the banking system is not built to do It is worth being clear about this: the banking correspondent infrastructure was not designed for the closing table. It was designed for recurring, relationship-based, pattern-predictable commercial activity. Acquisitions are the opposite of that. They are high-value, non-recurring, multi-party, time-sensitive transactions between parties who may never transact again. The system's design assumptions break down under those conditions, and the result is friction that is structurally built in rather than incidental. Every professional who closes deals for a living eventually develops an intuition for this friction — which banks are slower, which documentation packages move faster, which days of the week are safer for wires, which deal structures create fewer disbursement hops. That intuition is real operational expertise. It does not come from any certification program. It comes from watching money get held and learning why. The professionals who move acquisition-scale money most smoothly are the ones who have internalized the compliance logic well enough to front-run it: building the documentation before it is requested, timing the wire for optimal processing conditions, and structuring disbursements to minimize the number of independent review processes a single deal payment has to pass through. Shaka is one tool in that architecture — the piece that handles simultaneous multi-party disbursement in a single settlement event, eliminating the sequential hold chain entirely for the onchain portion of a transaction. ## The certainty question At the center of every large-deal payment discussion is a question about certainty. The buyer wants to know the money left. The seller wants to know the money arrived. The broker wants to know the commission is in. The attorney wants to know the disbursements went out clean. Under a wire-based settlement, none of these parties has simultaneous, confirmed, irrevocable knowledge. They have confirmations — which can be reversed. They have bank statements — which are updated on bank timelines. They have each other's word — which is not a settlement mechanism. Certainty is not a luxury in acquisition-scale transactions. It is the foundational requirement, and the banking infrastructure delivers it later, with conditions attached, and sometimes not at all without a documentation fight. Understanding why large payments get held is not just academic knowledge. It is the professional baseline for structuring deals in a way that protects your clients, protects your commission, and protects your reputation as someone who closes cleanly. The banks will do what they do. The professionals who navigate it best are the ones who stopped being surprised by it and started building around it.