Last scan is the most recent recorded cycle of the registered scanner. Sources verified is the most recent substantive verification, which may be manual and may reach beyond the scanner perimeter. The two are never merged.
SR2026 · Implementation Control Room
Swift deferred “all payments changes.”
Its own pages still say November.
An independent desk on Swift Standards Release 2026 — what the controlling publisher has actually published, what has moved, and what is still unresolved.
Open case
Current position
Where SR2026 stands today.
What moved
Every dated movement, newest first.
Movements marked with a capability identifier were caught by source-change detection: registered sources are retrieved and compared against their previous state by plain code. A failed retrieval is recorded as a failure, never as “no change”.
Implementation questions · Front 001 · structured & hybrid postal addresses
What a participant may still need to establish about address data.
Scope. These questions cover the structured and hybrid postal address requirement only. They were drafted against Implementation Front 001 and none of them addresses the open MT 101 case above, which has no drafted questions at this date.
An address is captured, stored, carried, mapped, generated, validated, repaired, screened and tested before it leaves an institution. Each question below names a surface, what should be checked there, how it could be tested and what evidence would support a conclusion.
Evidence · Tier 1
Every published fact is attributable.
Each row records a single assertion, its publisher and its publication date. Two further dates are kept apart deliberately: assertion verified is when the assertion was last checked against retrieved content, retrieved is when the source was last successfully fetched. Fetching a page is not verifying what rests on it. Superseded rows are kept, not deleted. Open a row for its full text and provenance.
Index-only retrievals. Where a row is marked index only, the publisher's own index page was re-fetched on 15 September 2026 (HTTP 200) but the underlying document carrying that row's assertion was not re-retrieved on that date, so its verification date is unchanged. This applies identically to every index-only row and is stated here once rather than repeated on each. Direct document references are added only once verified against the publisher.
Evidence · Tier 2
Authoritative for themselves, and for nothing else.
Banks, central banks, infrastructures and scheme bodies publish their own implementation guidance. Each is authoritative for its own position and actions. Where one describes another organisation's position, the row is an attributed account and names the document it rests on.
Evidence · Tier 3Corroborating references — not authority
How this is produced
Registered sources are checked on a cycle. Change is detected by plain code. Machine assistance is used only where there is something to judge, every quotation is checked word for word against the captured source, and nothing is published without human review.
Read the methodStanding of this page
This is an independent implementation analysis desk. It publishes no compliance verdict, no readiness score and no assessment of any named institution. It does not state whether any requirement applies to a given firm; that determination rests with the firm.
Intelplexis publishes no replacement enforcement date and does not infer one. Nothing here is legal, regulatory or compliance advice. SWIFT remains authoritative for the standard. Intelplexis is independent and is not affiliated with or endorsed by SWIFT. Trade marks referenced belong to their owners.
Monitored sources
The registered scanner perimeter is published in full, with the authority tier of every source and the date each was last successfully checked.
See the source registry