The first lesson from T+1 was that the market could move faster than many people expected.
When the U.S. securities market moved from T+2 to T+1 in May 2024, the obvious fear was trade failure. A shorter settlement cycle meant less time to correct allocations, match instructions, fund trades, and deal with bad reference data. If anything broke, investors would feel it in failed trades, funding pressure, and operational noise.
That is not what happened at scale. The U.S. transition was smoother than many had feared. DTCC said 94.55% of transactions were affirmed by DTC’s 9 p.m. ET cutoff on May 29, 2024, up from 73% at the end of January. Its first-day T+1 fail rates were also lower than the May average under T+2 for both CNS and DTC non-CNS activity. SIFMA, ICI, and DTCC later said July fail rates stayed broadly consistent with T+2 levels.
The pressure showed up later.
T+1 did not expose order routing as the main weakness. Most front-office systems were already built to send orders, manage execution logic, and connect to venues quickly. The real pressure moved into the middle and back office, where records from brokers, custodians, managers, venues, and counterparties had to agree before settlement day arrived.
That is why financial firms are now spending more time with engineering teams working on complex builds. The new problem is clean data, exception handling, reconciliation, audit trails, and systems that can catch bad information before it becomes a settlement issue.
T+1 Made the Back Office More Visible
For years, post-trade work sat behind the more visible parts of the market. Traders cared about execution quality, liquidity, routing, and price. Investors cared about fills, performance, and fees.
The SEC’s rule shortened the standard settlement cycle for most broker-dealer transactions from two business days after the trade date to one business day. It also added processing and recordkeeping requirements for broker-dealers and registered investment advisers, and created a straight-through processing requirement for central matching service providers.
That matters because a one-day settlement cycle leaves less room for late allocation, missing standing settlement instructions, wrong account data, FX timing issues, and small mismatches. Under T+1, a flawed record becomes a timing problem almost immediately.
That is why the important work lives in matching engines, reference data controls, exception queues, and workflow tools that show where the break started.
Routing Got Faster Before Reconciliation Did
Order routing has had years of attention. Equity markets, options markets, fixed income venues, algorithmic trading platforms, and execution management systems all pushed firms to invest in speed, connectivity, and routing logic.
Better routing can affect execution quality, transaction costs, and client outcomes. It is also easy to understand because it sits close to revenue.
Reconciliation was easier to ignore. In plenty of firms, the work still runs through older platforms, spreadsheet checks, file drops, email chains, and manual sign-offs. That can hold together when settlement teams have more time. Under T+1, the cracks show faster. It becomes fragile when confirmation, funding, settlement instruction, and exception repair all sit inside the same compressed cycle.
The industry already knows this. DTCC’s T+1 materials for global markets point to data flows, enrichment gaps, reconciliation, and automation as areas firms need to assess as more jurisdictions move to shorter cycles. Europe, the U.K., and Switzerland are preparing for their own T+1 changes, which means cross-border firms will have to manage different calendars, currencies, custodians, and settlement practices.
The front office had already spent years solving speed. Post-trade teams are now dealing with agreement, proof, and timing.
Reconciliation Is Where Operational Risk Hides
Reconciliation is often described as matching records. That sounds simple until the trade touches five or six systems.
A manager may have one version of the trade. A broker may have another. A custodian may use a different security identifier, account field, or settlement location. A fund administrator may need the data for NAV. Compliance may need proof of who changed what and when.
If every system agrees, nobody talks about reconciliation. If one field is wrong, the issue can move through the chain quietly until it becomes a break.
Reconciliation now acts more like a risk control than a purely administrative task. It tells firms whether their view of the market matches the records held by everyone else in the trade lifecycle.
Coalition Greenwich’s 2025 research found about one in 10 buy-side firms reported using outsourced trading for U.S. equities. Trading and reconciliation are different functions, but the lesson is relevant: buy-side firms are more open to outside specialists when infrastructure, staffing, or scale becomes too expensive to carry alone.
Post-trade is heading in a similar direction. Once settlement windows shrink, firms have to choose between more staff, better systems, or external support.
Software Spend Is Moving Toward the Breaks
The software market is already reacting. Gresham’s 2025 research with WBR spoke to more than 100 senior data, operations, and technology leaders across buy- and sell-side firms. The concerns were not abstract: cleaner data, fewer manual checks, better controls, and reconciliation tools that can keep up with shorter settlement windows.
Market forecasts tell a similar story.
Precedence Research expects the reconciliation software market to grow from $4.01 billion in 2025 to $15.52 billion by 2035. Forecasts are never perfect, but the direction makes sense. Under T+1, firms have less patience for manual checks that only work because someone stays late to chase breaks.
The job is fairly unglamorous. The same trade rarely arrives in one tidy format. It may come through a broker feed, a custodian record, an administrator file, and an internal platform, with each one telling a slightly different version of the same event. The system then needs to show what does not match, who owns the issue, and what changed before settlement. That is the plumbing firms used to overlook. Under T+1, it is harder to ignore because teams have less time to find where an error started.
The next round of post-trade investment is likely to look different from earlier trading technology spend. It will be less about building the fastest route to market and more about connecting the messy parts around the trade.
Investors Hangout has already covered how trading infrastructure providers are trying to deal with fragmentation across order, execution, and post-trade systems. The same fragmentation is now the daily problem for reconciliation teams.
Hiring Alone Will Not Fix It
Post-trade systems need engineers who understand financial workflows, data lineage, controls, APIs, reporting, and operational risk. They also need operations people who can explain why a break matters and what a good repair workflow looks like.
That mix is hard to find. Front-office systems usually get attention first because they are closer to trading revenue. Post-trade systems often get attention later, usually when something has already gone wrong. That could be a failed settlement, an audit question, or a client asking why a break was not fixed sooner.
More engineers can help, but they cannot clean up a poor process on their own. The problem might be old account data, files arriving in different formats, rules stored in spreadsheets, or exception queues with unclear ownership. In that setup, adding people only reduces the pressure for a while.
What firms need is more basic: cleaner data, fewer handoffs, clearer ownership, and systems that let operations teams fix common breaks without turning every small change into a technology request.
The Next Test Is Cross-Border
The U.S. move to T+1 proved that a large market can shorten settlement without widespread disruption. It did not prove that every firm has solved the harder operating model questions.
Cross-border trading will make those questions sharper. A U.S. security may settle on one cycle, a European security on another, and the related FX or fund transaction may follow a different timeline. Holidays, custodians, time zones, and cutoffs all add pressure.
That is where reconciliation moves from back-office hygiene to market infrastructure.
If the same institution trades across markets, it needs a reliable view of cash, positions, settlement status, fails, and exceptions. A weak reconciliation process can distort that view. It can also force teams to make funding and risk decisions with incomplete information.
A firm may have strong execution tools and still carry hidden operational risk. It may show healthy trading volumes while relying on fragile manual checks. It may win business on front-end experience while the settlement process behind it is held together by people working late to clear breaks.
T+1 made the market faster. It also made weak post-trade processes harder to ignore.
Order routing still matters. Execution quality still matters. But after T+1, firms have a more basic question to answer: do the books agree before the deadline arrives?
