From 2027 onwards, ETF businesses in the UK, EU and Switzerland will be judged less on their product line‑up and more on whether their operating model can actually run at trade‑date speed.
The move from T+2 to T+1 sounds like a technical change; in practice it is a hard audit of how quickly you can go from execution to a settled, reconciled, booked position without depending on overnight batch jobs and spreadsheets.
If you issue ETFs, manage global UCITS or run multi‑asset strategies off a stitched‑together stack, this transition is not just a regulatory milestone. It is a competitive filter. ESMA’s T+1 roadmap
What T+1 really changes for ETF Managers
The joint migration date of 11 October 2027 for the EU, UK and Switzerland aligns European markets with the US and compresses the trade lifecycle into roughly 12–14 hours for allocation, confirmation and instruction submission. Regulators and industry committees are clear: allocations and confirmations must be completed on trade date, with settlement instructions submitted to securities settlement systems by late evening.
That removes the one business day that ETF operations have historically relied on to catch errors, enrich files, reconcile positions and fix funding gaps. Activities that used to be sequential – trading, allocation, FX, funding, settlement – now have to run in parallel, intraday. If your workflows still assume “we’ll tidy this up tomorrow”, T+1 simply exposes those assumptions as settlement fails and cash‑breach risk.
ETFs also carry structural FX complications that traditional mutual funds can often avoid. When ETF shares settle on T+1 but underlying securities or FX legs remain on T+2, authorised participants face funding gaps that must be bridged with collateral, increasing the cost and complexity of primary activity. ESMA has already flagged ETFs as having lower settlement efficiency than other instruments and explicitly called for the industry to fix primary/secondary misalignment ahead of the T+1 go‑live.
Add FX cut‑offs, (longer) APAC exposures, securities lending and UCITS constraints, and the picture is simple: ETFs will feel T+1 more acutely than many other asset classes. The firms that come out ahead will be those that treat T+1 as an operating‑model project, not just a compliance exercise. ECB’s T+1 settlement paper
Why traditional setups struggle
Most ETF and multi‑asset managers still run on stacks that grew incrementally: OMS from one vendor, risk from another, reconciliation somewhere else, accounting on a legacy platform, all held together by bespoke work-arounds and Excel. That architecture was built for T+2. It relies on time to provide the buffer it needs to function properly.
Under T+1, those buffers disappear. Back offices that once had 12 hours to process post‑trade work in European equities will have, it is expected, to cope with only two hours. Industry surveys show large infrastructures and custodians broadly ready, while asset managers and smaller firms are materially behind and heavily dependent on service providers and intermediaries.
This creates three operational pressure points:
- Data and workflow fragmentation. Separate systems for trading, confirmation, settlement and accounting mean multiple versions of the truth and latency between each step. In a T+1 world, every hand‑off is a risk.
- Manual buffers and exception queues. Many teams still rely on overnight enrichment, manual affirmation and spreadsheet‑driven reconciliations. Compression of the cycle moves those manual tasks into the trading day, where they compete with new trade flow.
- Funding and FX visibility. When cash movements, FX trades and collateral requirements are not visible in real time across funds, T+1 exacerbates funding gaps and increases the risk of CSDR penalties and liquidity stress.
The firms that are already running integrated, exception‑based operating models will absorb T+1 as a non‑event. Everyone else will be trying to jury‑rig a T+1 regime onto a T+2 stack. EU T+1 industry survey
How TrussEdge helps you run T+1 As Normal
TrussEdge was built as a single front‑to‑back application for investment firms: our proprietary software (Safari) starts at order management and runs through execution, settlement and accounting, delivering a fully reconciled, consolidated view of trading and cash positions, risk and the investment GL in one place.
For ETF issuers and multi‑asset managers, that architecture directly addresses the core pressure points T+1 creates.
Below are three specific ways it supports the transition.
1. One Operating Layer from Trade to Ledger
In a T+1 environment, you can’t afford to have different systems owning different fragments of the lifecycle. Safari treats ETF PMS, risk, compliance and accounting as one connected stack rather than four projects.
- Orders, executions, allocations, treasury and cash management all live in the same application, with live PnL, exposure and iNAV sitting on top of the same data that feeds the general ledger.
- Multi‑asset coverage spans fixed income, futures, equities, options, repos, commodities and crypto, so you don’t maintain parallel processes or workarounds for different instruments.
For T+1, the practical outcome is simple: allocations, confirmations and settlement instructions draw from a single, real‑time source of truth. There is no overnight export from OMS to reconciliation, then to accounting. You are already operating at trade‑date speed because the stack was designed to do so.
2. Native T0/T+1 Reconciliation with Exception‑Based Control
Regulators and industry committees emphasise automation and straight‑through processing as non‑negotiables for T+1, with instructions expected to be processed continuously throughout the trading day and submitted by late evening. TrussEdge’s middle‑office layer was built on that premise.
- Safari provides automated and integrated confirmations and T0/T+1 reconciliations for trades and cash, with automated settlement operations managed through dashboards.
- Operations teams use exception‑based workflows: the system handles standard flows and surfaces only the breaks that genuinely require judgment, rather than forcing staff to chase every recon line item.
This lets you shift from “big overnight reconciliation” to continuous intraday exception management, which is exactly what T+1 guidance from ESMA, the EU T+1 Handbook and market infrastructure groups recommend. It also means your team is working on the 20% of issues that matter, not the 80% the system can safely resolve.
3. Multi‑Asset ETF + FX coverage without spreadsheet workarounds
FX, APAC baskets and cross‑currency cash flows are where many T+1 plans quietly fail. Under compressed cycles, the lack of real‑time visibility over positions, cash, FX and exposures is not just inconvenient; it becomes a source of settlement fails and funding gaps.
TrussEdge’s consolidated data model and multi‑asset coverage give ETF issuers and asset managers a single view of positions, cash and FX across funds, with integrated FIX,API & sFTP connectivity to counterparties.
- For “T‑1” ETFs with APAC components, you can model and execute indicative creations/redemptions and their funding flows inside the platform, then track true‑ups when baskets trade the following day, without resorting to spreadsheets and emails.
- For cross‑currency portfolios, you can move from T+2‑assumption processes to T+1 or pre‑funding logic with a clear picture of downstream cash movements and settlement obligations across the stack.
The practical benefit: you stop treating FX and complex ETF primary activity as offline problems to fix later and start treating them as first‑class objects in your operating model. That is precisely the direction regulators and market infrastructures are signalling when they talk about increasing settlement efficiency in ETFs.
Turning T+1 into an Operating‑Model Advantage
T+1 will create a quiet divide in Europe. On one side will be firms that treat it as a compliance checklist and hope their service providers absorb the complexity. On the other will be firms that use it as a forcing function to retire fragmented architecture and prove to investors, APs and allocators that their operating model is as modern as their products.
If you run your ETF or multi‑asset business on Safari, you already have the building blocks: a single application from trade to ledger, native T0/T+1 reconciliations, exception‑based operations, multi‑asset coverage and real‑time views across positions, cash and FX. T+1 becomes an external validation of how you operate today, not a scramble to fix weaknesses at the last minute.
If you’re revisiting your stack ahead of T+1, it’s worth comparing what your current architecture can realistically do inside a 12‑hour trade lifecycle with what a single‑application operating model looks like in practice.
www.trussedge.com I sales@trussedge.com
About Thomas Byrne
Thomas Byrne is Business Development Manager at TrussEdge, with over 20 years of experience across buy- and sell-side firms in sales, trading, and middle- and back-office roles. Since joining TrussEdge in 2018, he has focused on helping investment managers develop practical, tailored solutions across their technology and operational needs.
