T+1 is a static-data deadline

ESMA has proposed amendments to the technical standards on settlement discipline and revised guidelines on allocations and confirmations, moving those steps to trade date and requiring electronic, standardised communication using international messaging standards. References to oral or otherwise non-machine-readable allocations and confirmations are removed except during temporary technical disruption. A step that a person could previously do by telephone at nine the next morning becomes a message that has to be right first time.

It is worth stating plainly that 11 October 2027 is the date the cycle changes, and that nothing settles faster before it. The intervening milestones belong to the rules. ESMA delivered its final report on amendments to the settlement discipline standards in October 2025; the Commission endorsed the delegated act on 6 July 2026; scrutiny by the Parliament and the Council runs into October 2026, with publication in the Official Journal expected in the fourth quarter and the first requirements expected to apply from 7 December 2026.

ESMA consulted separately on revised guidelines for allocations and confirmations, with responses due by 7 July 2026 and final guidelines expected later in the year, aligned to the same December 2026 date. Both instruments are expected and not final as this is written, so an internal plan should record them as expected dates. The one date settled in law is the one in the regulation.

A settlement instruction is a short message resting on a long list of things somebody recorded earlier. The legal name of the account holder. The account and custody details. The standing settlement instructions for that market and currency. The identifier of the entity, and the people authorised to instruct. A trading desk does not maintain any of that; an entity-management or operations team does, usually alongside the bank mandates.

A group running twenty sub-funds and a dozen holding vehicles carries twenty versions of the problem. A sub-fund was renamed at launch and the custodian holds the working title. A vehicle was redomiciled and the old market instructions survive. A signatory left in March and the mandate was never updated. In a two-day cycle these surface as friction that somebody fixes before settlement date. In a one-day cycle the same defects become failures, buy-ins and cash penalties.

Four fields decide whether an instruction matches, and each of them can be reviewed on a cycle. The registered legal name, against the account name held by every custodian and counterparty. The legal entity identifier and its status. The standing settlement instructions per market and currency, with the date each was last confirmed. The current list of authorised signatories, with evidence for each. Give every item an owner and a review date, and treat an unconfirmed instruction as a defect.

What happens when something changes matters as much as the list. A renaming, a redomiciliation, a new custodian, a director or signatory leaving: each should raise the same short list of downstream updates, with a due date. Groups that already know which accounts and mandates belong to which entity can produce that list in an afternoon. Groups that keep account details in a treasury spreadsheet and signatories in an email folder will spend 2027 finding out which is authoritative.

Alethia holds bank accounts and mandates against the entity that holds them, with the authorised signatories, the supporting documents and the KYC requests that produced them. The registered name and identifiers sit on the same entity record, so the name a counterparty holds can be checked against the name the register holds without assembling anything new. Compliance obligations carry due dates, which is the right shape for a periodic reference-data review, and the audit trail shows who changed an account detail or a signatory and when.

Alethia sends no settlement instructions, connects to no custodian and holds no market data. The difference shows on the Monday morning after a signatory leaves: the entities that person could instruct for, the accounts behind them and the mandates that name them come back as one query, and the updates that follow have owners and dates.