Contemporary financial-district architecture in daylight
Financial-market infrastructure change

Know what the published record supports — and what it doesn't.

Intelplexis reconstructs the dated evidence position behind an implementation requirement: which public source supports it, what each source said and when, where official sources disagree, and what the record does not establish.

Current research front · How structured postal address changes are handled in practice · Swift CBPR+, SEPA, T2

01 · The record moves

Published sources move.

A provider amends a page, annotates it, supersedes it — or leaves an old one standing. How institutions carry that movement into their own requirements is an open research question.

What was published

On 27 August 2026 Swift deferred all SR2026 payments changes, naming only the structured address requirement.

What still stood three weeks later

When retrieved on 15 September 2026, Swift's own call-to-action page and corporates FAQ still carried the November 2026 MT 101 position, unannotated. A programme holding that date could not cite a public source that settled it.

02 · What we do publicly

We reconstruct the record before anyone acts on it.

Retained source states, with dates. Which position superseded which, where two official sources disagree, what carries authority, and what the evidence does not establish at all.

A requirement rests on published evidence. That evidence can change.

  1. 01

    Requirement

    What you are relying on.

  2. 02

    Supporting source

    The published evidence underneath it.

  3. 03

    Intelplexis records the evidence

    Dated source states retained.

  4. 04

    Evidence moves

    The record shows what each source said, and when.

    v5 v6 Illustration · wording differs Clarification required
  5. 05

    You decide

    Intelplexis informs. Decision authority stays with you.

03 · Current front · Swift SR2026

Work already performed, not work promised.

Recorded movement · reviewed 16 September 2026

Swift annotated its CBPR+ roadmap to say its dates may no longer be accurate, and left the MT 101 content beneath that note unchanged. Detected by comparison against the retained earlier version.

Open case · MT 101

Does the November 2026 end of coexistence still stand? Swift now publishes 12 June 2027 for its deferred SR2026 release, but that release excludes Category 1, and some Swift pages still carry the November 2026 MT 101 statements. Review 2, 25 September 2026; Review 1 retained. Open the case →

The record is dated and attributable. In the ledger: 20 Tier 1 entries (dated source states) · 10 institutional accounts · 7 corroborating references · 2 documents recorded as evidence gaps because they cannot be read. Registered retrieval sources: 7.

Published analysis: Swift defers “all payments changes” in SR2026 — and names only one of them, Finextra, 14 September 2026. The full source record is in the Implementation Control Room.

04 · Requirement Desk

The first Requirement Desk round has closed.

The first Requirement Desk round ran 22–27 September 2026 and has closed.

05 · Boundaries

External evidence only.

The scope is narrow on purpose.

Never required

  • System or production access
  • Credentials of any kind
  • Personal data
  • Confidential architecture or configuration

Never concluded

  • Whether the institution complies
  • Whether a requirement applies to a given firm
  • Whether an implementation is adequate
  • Legal, regulatory or compliance advice
  • Any replacement date the source record does not establish

Decision authority remains with the institution.

Current front

The SR2026 record, dated and attributable.

Every assertion carries its publisher, its publication date, when it was last verified, when it was last retrieved, and its reviewed evidence state. Swift remains authoritative for its own standards. Intelplexis is independent and is not affiliated with or endorsed by Swift.