T+1 settlement: solving the client interface problem

Ahead of the October 2027 go-live for T+1 settlement in the UK, EU and Switzerland, the supervisory expectations are clear: mobilization and planning today, core build complete and key operational enablers in place by end of 2026, followed by participation in industry testing through 2027.

While many banks are already well into the implementation phase, those that cannot demonstrate a credible trajectory are already drawing regulatory attention – and with good reason. Eliminating one processing day from the settlement cycle means a substantial portion of tasks currently completed on T+1 must now be executed on trade date (T+0) itself. Allocations, confirmations, instructions, inventory decisions, collateral calls, funding – all must happen faster and with far less tolerance for error.

The challenge is not speed alone, however. It is the transformation of the entire trade lifecycle to a near-real-time chain. In the event of a breakdown at any point – a failed match, a late instruction, a margin discrepancy – there is no longer the buffer of an extra day to absorb it. It becomes a failed trade, an exception, a query.

The European transition is structurally complex: multiple currencies, time zones and dozens of central securities depositories across different jurisdictions. Banks operating cross-border cannot simply replicate what worked in the US – a single currency, a single market reference time and a single settlement venue – when it transitioned to T+1 in 2024.

Foreign exchange further compounds this: the correct currency has to be in place to fund settlement within a window further compressed by time zone differences, sometimes significantly so.

The client interface problem

T+1 requires solving a set of well-understood technical challenges: getting settlement instructions to central securities depositories on time, aligning cutoffs across jurisdictions, meeting margin reporting requirements at central counterparties, and reengineering batch processing windows. These are genuine problems requiring significant investment.

That said, technical infrastructure is only part of the picture. Every exception that occurs – a failed trade, a margin call, an unmatched instruction – triggers a chain of communication between operations teams, counterparty banks and custodians that requires handling. Under T+1 this has to be managed in hours, not days. Banks that have invested in the technical layer but have not enhanced how they handle these exceptions will find that gap difficult once under the pressure of a live T+1 environment.

ServiceIQ: AI-enabled acceleration

A suite of accelerators developed and refined across tier-1 banks and capital markets firms, Capco’s AI-enabled ServiceIQ transforms how exceptions and client-facing communications are managed. ServiceIQ is not a single fixed solution but rather is implemented dynamically in tandem with an assessment of a bank's existing technology landscape. This identifies which tools and data infrastructure should be leveraged and where additional capability is needed. The objective is to build on what already works rather than replace it, provided the underlying data is accurate and supported by the right data contracts.

For T+1 settlement, a single-layer response to query management will not suffice. The compressed environment creates pressure at multiple points simultaneously. Inbound volume increases, risk prioritization becomes time critical and there is less time to catch and correct the upstream breakdowns that generate queries in the first place. ServiceIQ is structured to address all three of these challenges.

The reactive layer handles inbound communication intelligently across all channels.

• The AI reads incoming communications in context, extracting key data points such as trade references, amounts, counterparties and deadlines. 
• It identifies urgency and prioritizes accordingly, driving intelligent routing and ensuring cases reach the right team based on content, priority and capacity. 
• Where a query follows a known and repeatable pattern, resolution is automated entirely. Every interaction is logged with a full audit trail.

To illustrate what this looks like in practice: a counterparty operations team emails a settlements desk flagging a EUR 50 million trade that has not settled, expressing frustration at the lack of response to a previous chase. Without ServiceIQ, that communication enters a manual triage process where it waits until someone identifies it, pulls the trade details and drafts a reply.

In a high-volume environment that can take hours. With ServiceIQ, the same communication is read and understood by AI, the urgency identified, the trade data retrieved and a draft response generated, all within ten seconds. The handler's role shifts from assembling information to making decisions.

The proactive layer operates before queries arrive.

• ServiceIQ interrogates internal settlement systems directly, identifying high-value trades, current fails and positions yet to settle, and prioritizing the response accordingly. 
• Cases can be ordered by client tier, currency and settlement instruction deadline, ensuring the highest-risk exposures are addressed first rather than managed in the order they happen to arrive.

Where a security has an upcoming corporate action, ServiceIQ identifies and escalates it as a distinct risk category, surfacing it for intraday resolution rather than allowing it to become part of the general exception queue.

The preventative layer addresses the upstream causes of query volumes.

• Many of the inbound communications that settlements teams receive, fails, margin discrepancies, originate from breakdowns in the confirmation and matching process: late allocations, unmatched instructions, manual interventions that introduce delay or error. In some cases banks are still receiving confirmations by telephone or fax. 
• ServiceIQ connects into automated confirmation and matching platforms, identifying these breakdowns earlier in the process and reducing the volume of exceptions that reach the client-facing layer at all.

The result is not just better query management; it is a reduction in the conditions that generate queries in the first place.

Across ServiceIQ deployments at three global banks, outcomes have been consistent: a 40% improvement in productivity across operations teams through digitized query workflows; a 20% improvement in right-first-time resolution through accurate AI-driven routing; and a 15% reduction in query volumes through improved handling and prevention controls.

Three key imperatives for T+1 readiness

Calibration. T+1 changes not just the volume of exceptions but the urgency profile. A query management function built around today's settlement cycle, where exceptions can be managed across two days, will be subject to a materially different volume and urgency profile from October 2027. Banks that are not capturing and analyzing query data systematically are also missing one of the clearest signals of where their settlement process is under stress. Both the capacity to respond and the intelligence to improve need to be calibrated against the demands of a compressed T+1 environment.

Audit trail. In the months following October 2027, the FCA and ESMA will be monitoring settlement performance closely. Banks will need to demonstrate not just that they settled, but how they handled exceptions and communicated with counterparties when they did not. Manual processes do not produce that evidence reliably at scale. Automating the audit trail is not an administrative improvement – it is a regulatory focus.

Query data. Queries are a signal and direct measure of where the settlement process is breaking down. Banks that treat query management purely as a resolution function – without analyzing what the volume and type of queries are telling them about upstream weaknesses – are managing consequences rather than causes. That distinction becomes harder to sustain under T+1 conditions.

In summary, T+1 is rightly concentrating the industry's attention on technical infrastructure – but the banks that will perform optimally through this transition will have devoted the same degree of attention and investment to the operational layer. How exceptions are identified before they escalate, how counterparties are communicated in the event of escalation, and how the data those interactions generate is used to drive improvements.

The client interface is not a secondary concern. It is where the quality of everything upstream becomes visible and as such is a critical consideration as you plan for T+1 readiness.