When the U.S. moved to T+1 settlement in May 2024, most of the industry treated it as a deadline to clear. Get the systems ready. Get the teams trained. Get through the first few settlement cycles without a spike in fails. Once the transition held, attention moved on.
The bigger story is only becoming clear now, and it has nothing to do with whether your trades settled on time last quarter. T+1 quietly exposed a structural weakness in how a decade of offshoring decisions were made — and it's forcing asset managers to rethink where their most sensitive operational work actually belongs.
If you built your middle office around large offshore teams sitting ten or more time zones from your trading desks, this is your problem whether you've named it yet or not.
For more than ten years, the offshoring logic was simple and hard to argue with: if a process could be performed reliably somewhere cheaper, move it. Cost came down, efficiency went up, and the numbers looked good on every review.
That logic worked partly because the settlement cycle was hiding its own weakness. Under T+2, you had time. Time to catch an exception, investigate a break, chase a mismatch, and coordinate across teams before anything had to settle. A day of geographic separation didn't hurt you, because the settlement window absorbed it. The cycle was doing quiet work as a shock absorber, and most operating models were leaning on it without realizing it.
T+1 removed the absorber. Trades now finalize one business day after execution, and the margin for error that used to cover a handoff across ten time zones is largely gone. A break that surfaces at the end of your offshore team's day can now land squarely on the settlement deadline instead of comfortably ahead of it.
And geography isn't the only challenge. Over the last two decades, post-trade operations have also become increasingly specialized. Many firms no longer manage the lifecycle of a trade within a single team. Instead, responsibilities are segmented across allocation and matching teams, settlement instruction teams, settlement operations teams, fail management groups, and dedicated account maintenance or SSI teams.
That structure can work well when there is sufficient time in the settlement cycle. Under T+2, an exception could move through multiple teams over the course of a day or two and still settle on time. Under T+1, every handoff matters. A mismatched allocation may require one team to investigate, another team to correct instructions, and a third team to coordinate with a broker or custodian before settlement can occur. What was once a routine operational workflow can quickly become a race against the clock.
The challenge isn't simply where the work is performed. It's how many touchpoints exist between the exception and its resolution. Time-zone separation amplifies the risk, but so does organizational fragmentation. The more teams involved in resolving a trade issue, the more valuable real-time communication, shared ownership, and proximity to the investment process become.
It would be easy to read the recent headlines — asset managers standing up new operations hubs in lower-cost U.S. locations — as a simple reversal. Offshore was the answer yesterday; nearshore is the answer today.
That's too blunt, and firms that treat it that way will overspend correcting a problem they only half understand.
The real shift is more precise. T+1 didn't prove that offshoring was a mistake. It proved that applying one operating logic across every function was a mistake. Some work is genuinely time-agnostic and belongs wherever it's most cost-effective. Other work is trade-sensitive, exception-heavy, and dependent on tight coordination with the desk — and that work now carries real risk when it's separated from the investment process by half a day.
The question is no longer "onshore or offshore." It's "which functions can tolerate distance, and which ones can't anymore?"
Before you move a single seat, it's worth putting your operating model through three questions:
How close to settlement does this function sit?
Exception management, trade breaks, and time-critical reconciliation now live inside a window that punishes delay. Functions that touch settlement directly—or serve as the primary escalation point for trade exceptions—are often the strongest candidates to move closer to the desk. The value isn't just physical proximity; it's the ability to collapse communication loops and reduce the number of handoffs required to resolve an issue before settlement.
Reporting, reference data upkeep, and other work that isn't racing a same-day clock often has no reason to move at all.
How much does this function depend on real-time coordination?
If resolving an issue requires a live conversation with the trading desk, portfolio management team, broker, custodian, or another operational group, a ten-hour gap isn't a cost saving — it's a latent failure waiting for a volatile day to expose it. In many organizations, exception resolution now requires coordination across several specialized teams. Every escalation, queue transfer, and handoff consumes precious time within an already compressed settlement cycle.
What does a single bad day actually cost?
Averages hide the risk. The offshore model looks fine until a spike in exceptions collides with a time-zone gap and a same-day deadline. Price the tail, not the mean, and the trade-offs look very different.
Answer those honestly and the map almost draws itself. You end up with a deliberate split — some work nearshore and close to the desk, some work offshore and cost-optimized — instead of one blanket policy stretched across functions that no longer share the same risk profile.
T+1 is settled reality, and the U.S. won't be the last market to compress its cycle. The firms that come out ahead won't be the ones that reacted fastest to the 2024 deadline. They'll be the ones that use this moment to rebuild their operating model on purpose — matching each function to the location its risk profile actually calls for, rather than the one last decade's cost model assigned it.
That's a hard exercise to run from the inside, because the current setup always feels normal until someone asks the right questions about it.
That's the conversation we have with clients every week. If you're weighing what to move, what to keep, and how to redesign your operating model for a T+1 world without overcorrecting, [let's set up a short call]. We'll pressure-test your current map and show you where the real exposure sits — before a volatile day does it for you.