The deal was done. The money took three weeks. That's the problem.
The handshakes were done. The documents were signed. The client had transferred the money. By every measure that matters in a deal-making business — qualification, negotiation, close — the work was finished. What followed had nothing to do with the deal itself. It was three weeks of administrative friction, sequential wire transfers, manual reconciliation, and the quiet, compounding cost of money that had been earned but not yet received. Nobody stole it. Nobody disputed it. The system simply moved it at its own pace, through its own channels, on its own schedule. And the people on the other end of that system — a broker, a co-agent, and a referring consultant — absorbed the full cost of that design without anyone calling it a problem.
This is that story.
The Setup: A Clean Three-Way Deal
The deal involved a commercial property introduction. A consultant based in one city — call him M — had a relationship with a motivated seller. He didn't have the infrastructure to run the transaction himself, so he brought in a licensed broker — call her D — who handled the full process: listing, qualifying buyers, negotiating terms, managing due diligence. D worked with a co-agent in the buyer's market — call him R — who sourced the eventual buyer and managed that side of the relationship through to close.
The commission split was agreed before the deal opened: D took the largest share for running the transaction, R took a percentage for sourcing and managing the buyer, and M received a referral fee for the introduction. Three parties. One transaction. A clean structure, agreed in writing, never disputed. The buyer paid. The deal closed. And then the waiting began.
This is not a story about a dispute. There was no dispute. It is a story about what happens to money — and to the people who depend on it — when a closed deal meets a payment infrastructure that was never designed for speed or simultaneity.
Week One: The Money Arrives Somewhere That Is Not Your Account
When a commercial transaction closes, the funds do not travel in a straight line from buyer to recipient. In traditional deal structures, commission doesn't just land in your account. It has to pass through multiple internal checkpoints — from the agent to the team leader, then to the broker, and finally through administrative staff before a check is cut or a deposit is initiated. For D, this meant the full commission amount arrived at her brokerage's account. For R and M, it meant the clock had started, but they had no visibility into it.
This multi-step process introduces delays — and not just a day or two. The brokerage's internal compliance review — standard practice, not adversarial — required that the transaction file be complete before disbursement could proceed. The brokerage reviewed closing documents, contracts, disclosures, and settlement statements for compliance. If anything was missing or incorrect, payment got paused. Incomplete documents are the primary reason agents don't get paid promptly.
In this case, a co-agent agreement between D and R — executed in a slightly different format than the brokerage's internal template — needed to be re-executed and re-submitted before the compliance team would approve disbursement. That took three days of back-and-forth emails. Three days in which the money sat in an account that belonged to none of the parties who had earned it.
Large brokerages often route payments through centralised hubs, where a transaction becomes just another file in a queue. This can easily add five to seven unnecessary days to what should be a simple payout. D's brokerage was not large by industry standards, but it operated on a weekly payment cycle. The compliance clearance arrived on a Thursday. Payment runs were on Tuesdays. The next disbursement to D would happen in six days.
This is Week One: the deal has closed, the money exists, and no one is receiving it.
Week Two: The Cascade Begins
D received her share on a Tuesday, ten days after close. It arrived as expected — her portion of the commission, deposited by ACH, arriving in her business account two days after the payment run triggered. The one-to-three day settlement window is standard for ACH, and predictable enough for cash flow forecasting on its own. But D's portion was only one part of the equation. R and M were still waiting.
The structure of this deal — a co-agent share and a referral fee paid separately, from D's received funds — meant that D now became a payment intermediary. She was not keeping R's or M's money. She had every intention of paying them immediately. But "immediately" in this context meant: log in to her business banking platform, initiate two separate wire transfers to two separate accounts, verify the banking details she had on file, confirm with R that the international routing number hadn't changed since they last worked together, and then wait.
International payments take longer because they pass through multiple institutions, time zones, and compliance checks. A transfer initiated late in the US workday may not begin processing in Asia until the next business day. These delays complicate cash flow forecasting and vendor coordination. R was in a different country. His wire landed four days after D initiated it. M's domestic wire arrived in two days.
By the time both parties had received their funds, twenty-two days had passed since the deal closed. No fraud. No dispute. No malicious delay. Just the system operating exactly as it was designed.
The Costs Nobody Puts on the Invoice
The true cost of delayed payments is not just the invoice amount sitting in accounts receivable. It is the combination of missed opportunity, higher borrowing costs, delayed hiring, tighter margins, operational stress, and slower growth that happens while a business waits to get paid.
For M, the consultant, the referral fee was earmarked. He had a subcontractor — someone who had helped him cultivate the seller relationship over eighteen months — to whom he owed a portion of his referral upon receipt. That subcontractor had been waiting since the day of close. Twenty-two days later, M finally had the funds to pay him. The subcontractor had covered his own expenses for that period on the assumption that the money was coming. That assumption was correct. But assumptions are not cash flow.
Late payments and outstanding invoices disrupt the cash flow cycle of a business. When payments are delayed, it hampers the ability to meet financial obligations. This can lead to a domino effect, where the business struggles to pay suppliers, meet payroll, or invest in growth opportunities.
For R, the co-agent, the twenty-two day gap fell across a month-end. He had a small operation — himself and one part-time assistant — with fixed monthly costs that did not care about deal close timing. He had modelled the commission receipt into his cash position for the prior month. When it arrived in Week Three instead, he drew down on a short-term credit facility for eleven days to cover the gap. The interest on that draw was negligible in absolute terms. But it was money paid to a bank for a problem that had nothing to do with R's creditworthiness or the deal's legitimacy. The deal was done. The money was coming. He paid interest anyway.
Waiting to get paid creates a cash flow gap that forces businesses to fund operations without access to revenue they have already earned. They often bridge that gap by taking on debt.
For D, the broker who ran the transaction, the cost was different — and subtler. By the time she had received her share and initiated the outgoing wires to R and M, she had spent approximately four hours across the twenty-two day period on payment-related tasks: confirming banking details, initiating transfers, following up on the compliance re-submission, responding to messages from R and M asking for updates. Four hours is not a catastrophic figure. But she closed roughly thirty transactions a year. If even half of them involved multi-party splits of this kind, that is sixty hours annually spent not on deals but on the administration of payments for deals already closed. That is the equivalent of a full working week — every year — spent chasing money that was already earned.
The cost is not always visible as a line item. The business may not "lose" the invoice, but it loses time, flexibility, and momentum. A company can be profitable on paper while still being unable to move quickly when opportunities appear.
The Architecture of Delay
None of this was caused by incompetence or bad faith. It was caused by architecture — the specific design of the payment system these three professionals were operating inside.
Commission workflows sound simple on paper: a deal closes, a producer gets paid. But the actual workflow is a chain of dependencies that breaks under pressure — multi-party splits, override structures, compliance rules, and a reconciliation process most operations still run through spreadsheets. The result, as in this case, is that producers chase payments while the deal they executed sits finished behind them.
The delay in this story has five distinct structural causes, each of which compounded the others.
The compliance queue. Every brokerage that handles client funds operates under regulatory requirements that mandate internal review before disbursement. This is appropriate. Even after funding, a broker must process compliance paperwork. Missing initialed disclosures, expired signatures, or holidays can push payment to the next business day. The compliance function exists for sound reasons. But its cadence — weekly payment runs, document re-submission cycles, manual review — was not designed with the downstream parties in mind.
The payment cycle. Inconsistent settlement timing destroys cash flow predictability. Transactions processed Monday settle Thursday. Transactions processed Friday settle the following Wednesday. Holiday weeks add another two to three days. D's Tuesday payment run was not unusual. It was standard. But it meant that a compliance clearance arriving on Thursday became an eight-day wait, not because anything was wrong, but because the calendar said so.
The sequential structure. In this deal, R and M could only receive payment after D had received payment and then initiated separate outbound transfers. There was no mechanism for the three payments to move simultaneously. The structure required D to act as a hub — to receive, calculate, and redistribute — before anyone else could receive. Commission doesn't just land in accounts directly. It has to pass through multiple internal checkpoints before a deposit is initiated. Each handoff introduced its own processing window.
The international wire. R's cross-border receipt added days that were entirely outside anyone's control. SWIFT wires are widely accepted and reliable for large invoices. However, they typically take two to five business days and often involve origination fees, intermediary bank deductions, and FX markups that increase total cost. R received less than the amount D sent. The difference was absorbed by an intermediary bank neither of them had chosen and neither could identify.
The human bottleneck. If the broker is the bottleneck and happens to be out of town, on vacation, or just slow to respond, everyone is stuck waiting. D was none of these things — she was attentive and professional throughout. But the payment initiation still required her to act. It required her login, her verification, her time. The system had no capacity to move without her.
Taken together, these five causes produced a twenty-two day gap between deal close and final receipt. Each cause was individually defensible. Collectively, they imposed a cost on every party to the transaction — a cost that never appeared on any invoice and was never charged to the buyer, but was paid nonetheless.
What Three Weeks Actually Costs
Delayed receivables cost businesses one to two percent of annual revenue through interest, lost discounts, and missed opportunities. For a broker operating at D's volume, that is a meaningful number — particularly because the cost is not linear. It does not scale neatly with deal size. A twenty-two day delay on a small commission and a twenty-two day delay on a large one impose the same operational friction: the same compliance re-submission, the same banking initiation, the same wait. The cost of the system is fixed; only the underlying transaction varies.
Delayed receivables create a cash flow gap that forces businesses to either delay payments to suppliers, take on expensive short-term debt, or postpone growth investments. For most B2B companies, approximately half of invoices become overdue at some point. For brokers and consultants operating in deal-flow businesses — where revenue is lumpy, project-based, and often dependent on multi-party structures — this is not an abstract observation. It is the operating reality.
The opportunity cost is immediate and measurable. More than a quarter of small businesses report delaying a planned expansion or being unable to capitalise on an opportunity, while twenty-two percent have reduced staffing due to cash flow challenges. M's subcontractor had been informally promised payment within days of close. Twenty-two days later, the relationship had absorbed a friction it didn't need. The payment eventually arrived. But the expectation had been set, and reality had diverged from it, and that divergence — however small — is the kind of thing that accumulates across a professional relationship.
Delayed payments create a ripple effect across a business. A late invoice may begin as a collections issue, but it can quickly turn into a working capital problem that affects day-to-day decisions and long-term growth. The ripple from this deal was not catastrophic. But it was real. And it was entirely preventable.
The Question the System Never Asks
The system that produced this twenty-two day delay was not failing. It was functioning. Every step — compliance review, weekly payment runs, sequential disbursement, SWIFT processing, human initiation — was operating according to its own logic. The brokerage was not negligent. The banks were not misbehaving. D was not slow. The system was doing what systems do when they were built for control and documentation rather than for speed and simultaneity.
The question the system never asks is: what does it cost the people waiting?
A processor holds money for three to five business days before settlement. Nobody tracks that cost. Nobody negotiates it. Nobody even calculates it. The same is true for the twelve days the compliance queue added, the six days the payment cycle added, and the four days the international wire added. Each of these costs is invisible on the transaction record. The buyer paid one number. The broker, co-agent, and consultant received their shares. The delta — in time, in interest, in opportunity, in administrative hours — is simply absorbed.
This is the architecture of the normal. And the normal is expensive.
For professionals who live inside deal timelines — who quote turnaround times to clients, who manage subcontractors who depend on prompt payment, who fund operating expenses between closings — the twenty-two day gap is not a bad experience. It is a structural feature. It was always going to take this long. The only question was whether anyone was measuring the cost.
Delayed payments are not isolated accounting issues. Recent data shows they are closely tied to cash flow strain, unpaid invoices, operating expense pressure, and funding needs. For D, R, and M, each of those categories had a specific manifestation — a compliance re-submission, a credit facility draw, a subcontractor waiting on a payment that was a week overdue. The abstractions had names and faces and real numbers behind them.
A Different Architecture Is Possible
The twenty-two day gap in this story was not the result of anyone doing something wrong. It was the result of a payment structure that required money to travel sequentially through multiple intermediaries, each with their own processing windows, before reaching the people it was owed to.
The alternative is a payment architecture in which all parties to a deal are paid simultaneously, from a single buyer payment, with no sequential redistribution required. A structure in which the split is defined before the deal opens, the buyer pays once, and the contract executes the distribution — to all parties, at the same moment, without any one of them acting as the hub.
This is what Shaka makes possible. The deal creator configures the payment split, generates a link, the buyer pays, and the smart contract distributes to every party simultaneously — no one holds the funds, no one redistributes, no payment cycle or compliance queue delays one recipient because of another's processing window. For brokers, co-agents, and consultants operating in multi-party deal structures, it is not a marginal improvement. It is a structural change.
The Last Thing
M's subcontractor received his payment on day twenty-two. He acknowledged it professionally. He said nothing about the wait. But M noticed, as professionals always do, that the acknowledgement was noticeably cooler than it would have been on day three.
That is not a data point. It is not measurable. It will not appear in any cash flow analysis or opportunity cost calculation. But it is real, and anyone who has managed a professional relationship built on trust and reliability will recognise it immediately.
The deal was done. The money took three weeks. The work was finished the day it closed. Everything after that was the cost of a system that was never designed to pay attention to the people waiting at the end of it.
