Thoroughbred LLC — Board Pre-Engagement Advisory Notice

SWIFT SR2026 — Network Readiness Assessment as of November 14, 2026

Issued by the Board of Directors of Thoroughbred LLC — Pre-Engagement Due Diligence

This document is issued prior to any engagement with an institution operating on the SWIFT/CBPR+ network. Our Board of Directors has mandated the conduct of a readiness assessment before proceeding with any cross-border transaction relationship — not as a compliance test, but as part of due diligence in anticipation of a long-term partnership.

SWIFT has established a firm mandatory application date: after November 14, 2026, payments that do not comply with SR2026 requirements for structured address and transaction data will be rejected at the network level. This is a network-level change that affects all participants equally.

The majority of institutions have addressed the postal address requirement. This assessment also covers the second domain: transaction data fields related to assets and their linkage to the underlying electronic asset record — the foundation of UCC Article 12 processing and HQLA treatment under Basel III.

We are seeking a long-term relationship. The purpose of this document is to ensure that both parties understand the requirements and that the institution has the tools and readiness necessary to meet them.

Domain 1 — SWIFT/CBPR+ Message Readiness

Structured postal address and mandatory transaction fields. Network-level enforcement takes effect on November 14, 2026.

Domain 2 — Asset Evidence Readiness (Y26NAK)

The underlying electronic asset record must be identifiable, traceable, and reconcilable. This assessment confirms that capability.


Are You Getting Paid After November 14, 2026?

Every payment has to travel somewhere. After November 14, 2026, the SWIFT network applies new validation rules to every cross-border payment message. If the message does not conform, it does not pass. This is not a future risk — it is a published, documented enforcement mechanism with a fixed date and no contingency. Follow the trail. Show the evidence. Get paid.

Who Is Following This Trail?

Social Security

Military Pay

Veterans Benefits

Pension & 401(k)

Payroll

Unemployment

Securities / Investments

Contractors & Vendors

Every one of these payments travels through the financial system as a structured message. After November 14, 2026, that message must meet the SR2026 requirements — or it will be returned at the network level. You do not need to understand 70 fields. You need to follow your payment through 8 checkpoints.

The 8-Step Treasure Hunt — One Path. Your Payment.

Step 1 — Find Your Payment

UETR / Instruction ID / End-to-End ID. Can the payment be uniquely identified? This is the transaction spine. SWIFT requires the UETR to be present and pass unchanged through every institution in the chain.

Step 2 — What Value Is Moving?

Settlement Amount + Currency. What amount is being transferred and in what denomination? This is mandatory in every CBPR+ payment message.

Step 3 — When Does It Settle?

Settlement Date. When is the payment scheduled to settle? Mandatory in every applicable CBPR+ message.

Step 4 — Can the Message Pass the Address Gate?

(SWIFT MESSAGE GATE — November 14, 2026): Structured Address — Town Name + Country in the required structured or hybrid format. From November 14, 2026, CBPR+ payments containing fully unstructured addresses will be NAK'd at the network level. This is the gate SWIFT enforces directly. Source: https://www.swift.com/standards/iso-20022/removal-unstructured-address

Step 5 — What Does the Payment Point To?

(Y26NAK ASSET GATE): Applicable remittance / underlying reference. Can the payment be deterministically reconciled to the underlying asset or obligation being claimed? If NO: Payment Event = PROVEN. Underlying Asset = UNPROVEN. This is not automatically a SWIFT NAK — it is a separate evidence gate tested by Y26NAK.

Step 6 — Article 12: Show Control

(Y26NAK ASSET-EVIDENCE GATE): If the identified electronic asset is claimed to be a Controllable Electronic Record (CER): Benefit → Exclusion → Transfer → Identification. Is the asset a CER under §12-102? Does the claimant hold control under §12-105? Was it acquired for value, in good faith, without notice?

Step 7 — Show the Control Transition

Prior controller → New controller → Effective time → Provenance → Authenticated record. The transfer of control must be documented and verifiable. The record must exist. The record must be produced.

Step 8 — Basel III: Prove the Claimed Treatment

If qualifying prudential treatment or HQLA status is claimed: Classification → Encumbrance → Liquidity → Eligibility → Risk Weight / Haircut → HQLA Treatment. A stablecoin is not automatically HQLA. A digital token is not automatically a CER. The asset must be tested against the published Basel III LCR framework.

— VISUAL BRIDGE — THE PAYMENT EXISTS. NOW SHOW WHAT IT REPRESENTS. —

SWIFT Message Gate (What the Network Tests)

SWIFT validates that the payment message is structurally compliant: UETR present and unchanged, settlement amount and date populated, structured address in the required format. If a mandatory element fails: MESSAGE → NAK. This gate is enforced by SWIFT beginning November 14, 2026.

Y26NAK Asset-Evidence Gate (What the Asset Must Prove)

Y26NAK tests what the payment represents: Can it be reconciled to an underlying asset or obligation? If so, does that asset satisfy UCC Article 12 control requirements? Does it qualify for the claimed Basel III HQLA treatment? These are separate gates. Passing the SWIFT message gate does not prove the asset. The asset must be independently demonstrated.

What Ceases to Function on November 14, 2026 — and the Documented Basis for Every Assertion

This section establishes, with full source citations, why fiat currency-of-account transactions, standard wire transfers, and stablecoin payments routed via the SWIFT/CBPR+ network will be subject to network-level rejection as of November 14, 2026 — if the sending institution has not implemented SR2026 requirements. Every assertion below is drawn from a document published by SWIFT. URLs are provided in full for independent verification.

The Framework — How SWIFT Constructed the Enforcement Mechanism

SWIFT did not issue a single announcement. It constructed a framework: a sequence of published requirements, technical specifications, testing environments, and enforcement declarations that together establish an unambiguous obligation for every CBPR+ participant. The framework is as follows:

  1. SWIFT defined the requirement. From November 14, 2026, postal address information in CBPR+ payment messages must be provided in a fully structured or hybrid format. At minimum, town name and country must appear in designated fields for all agents and parties. Unstructured address data will not be accepted.
    Source: https://www.swift.com/standards/iso-20022/removal-unstructured-address
  1. SWIFT published the scale of the problem. According to SWIFT's most recent measurement, 61.2% of payments included unstructured debtor postal addresses and 62.9% included unstructured creditor information. The majority of cross-border payments currently in circulation do not meet the November 14 standard.
    Source: https://www.swift.com/standards/iso-20022/iso-20022-bytes/call-action-november-2026
  1. SWIFT directed technology providers to modify their systems. SWIFT specifically directed technology and solution providers to enhance applications to capture and validate correctly structured data, to implement controls to reject or correct non-compliant submissions prior to payment processing, and to align development and testing ahead of November 2026.
    Source: https://www.swift.com/standards/iso-20022/iso-20022-cbpr-compliance-partners
  1. SWIFT directed financial institutions to prepare, test, and inform their clients. Financial institutions were directed to conduct end-to-end impact assessments, coordinate operations and technology, enhance systems, provide clients with specifications mandating required data, establish testing environments, and validate client data prior to initiating payments.
    Source: https://www.swift.com/standards/iso-20022/iso-20022-bytes/call-action-november-2026
  1. SWIFT published the enforcement mechanism. Interfaces applying schema validation will reject invalid payment instructions prior to network submission. Payments containing unstructured addresses will receive a NAK (negative acknowledgement) at the network level under CBPR+ as of November 14, 2026.
    Source: https://www.swift.com/standards/iso-20022/removal-unstructured-address
  1. SWIFT closed the workaround path. SWIFT expressly stated: "Address information must come from the source, so SWIFT cannot provide a contingency solution to financial institutions experiencing readiness delays." There is no workaround. There is no fallback processing path.
    Source: https://www.swift.com/standards/iso-20022/removal-unstructured-address
  1. SWIFT confirmed the scope. The requirement applies to corporate payments, securities, trade, foreign exchange, and funds. It applies regardless of the channel used — MT101, pain.001 SCORE+, or the bank's proprietary channel. The channel creates no exemption.
    Source: https://www.swift.com/standards/iso-20022/removal-unstructured-address
  1. SWIFT confirmed the timeline. The SR2026 production environment goes live on November 14, 2026. The vendor test system opened May 8, 2026. The pilot system with SR2026 validation rules opened July 18, 2026. Specifications were available from February 20, 2026. Institutions have had the full specification, test environment, and pilot environment available. The deadline is not a surprise.
    Source: https://www.swift.com/standards/iso-20022/standards-releases

What This Means for Each Payment Type

Fiat Currency of Account

A USD wire or EUR correspondent banking payment is a CBPR+ message. It is subject to SR2026 validation. If the message contains an unstructured postal address — as the majority currently do — it will be returned at the network level as of November 14, 2026. The fiat denomination does not exempt the message from the structured address requirement. The correspondent banking relationship does not exempt the message. The message must be compliant.

Standard Wire Transfers (MT 103 / pacs.008)

MT 103 and pacs.008 are the primary message types affected. Address fields for the debtor, creditor, and agents must be structured. A message submitted in the format that has constituted standard practice for decades — with a free-text address block — will not pass SR2026 validation. The institution must have modified its systems, channels, and client data prior to November 14.

Stablecoins and Digital Asset Payments

A stablecoin or digital asset payment routed via the SWIFT/CBPR+ network is a CBPR+ message. It is subject to the same SR2026 structured address obligation as any other payment. It is also subject to the second obligation: the underlying electronic asset record must be identifiable, its control status must be provable under UCC Article 12, and its prudential classification must be established under Basel III. A stablecoin is not automatically HQLA. A digital token is not automatically a controllable electronic record. Asset type creates no exemption from either condition.

Full Reference Links — All Assertions Are Independently Verifiable

SWIFT — Removal of Unstructured Addresses (primary enforcement page):
https://www.swift.com/standards/iso-20022/removal-unstructured-address

SWIFT — Call to Action, November 2026 (scale of non-compliance + instructions to institutions):
https://www.swift.com/standards/iso-20022/iso-20022-bytes/call-action-november-2026

SWIFT — CBPR+ Compliance for Technology Partners (instructions to technology providers):
https://www.swift.com/standards/iso-20022/iso-20022-cbpr-compliance-partners

SWIFT — November 2026 Milestone (structured address removal confirmed):
https://www.swift.com/standards/iso-20022/iso-20022-milestone-november-2026-unstructured-addresses-removed

SWIFT — Standards Release Schedule (test and production system dates):
https://www.swift.com/standards/iso-20022/standards-releases

SWIFT — AI Address Structuring Model (mandatory transition to structured formats):
https://www.swift.com/standards/iso-20022/iso-20022-swift-ai-address-structuring-model

SWIFT — ISO 20022 in Brief: The Journey Continues (minimum town and country requirement):
https://www.swift.com/standards/iso-20022/iso-20022-bytes/journey-continues

The Three-Tier Architecture

Three entirely distinct conditions must be satisfied — and satisfying one does not satisfy the others. Each tier has its own governing authority, its own mandatory requirements, and its own standard of proof. Conflating them produces an unproven condition and a failed compliance test. This is the architecture that governs every cross-border transaction after 14 November 2026.

Tier 1 — SWIFT / ISO 20022 Message Validation

SWIFT validates CBPR+ messages against the applicable usage guideline. When a mandatory element is defective or absent, FINplus returns a NAK. Mandatory fields are mandatory for every participant sending that message type — not because of the identity of the sender, but because the applicable usage guideline requires it. No institution is exempt. SWIFT has stated that no contingency solution exists for non-compliant messages.

Tier 2 — UCC Article 12 (CER / Control)

UCC Article 12 governs Controllable Electronic Records. It asks the following questions: Does the asset constitute a CER? Does the institution exercise control within the meaning of §12-105? Was the CER acquired for value, in good faith, without prior knowledge? If all conditions are met, the qualifying purchaser takes the asset free of any competing claim under §12-104(e). These conditions are proven by the underlying asset registry — not by the payment message alone.

Tier 3 — Basel III HQLA (Prudential)

Basel III asks distinct questions concerning the actual asset-object: What is its classification (Level 1, Level 2A, Level 2B, or non-HQLA)? Is it unencumbered — free of any legal, regulatory, contractual, or other restriction? Is it operationally available? Does it have a proven liquidity history? These are prudential conditions, independent of message compliance.

SWIFT SR2026 — Documented Preparation and Enforcement Chain

SWIFT did not simply announce a deadline and leave each party to discover what was required. It issued instructions across the entire delivery chain — to technology vendors, financial institutions, payment market infrastructures, and corporate clients. Direction flows in both directions: SWIFT → technology vendors/banks → clients. This is the documented notification chain. The performance observation point is November 14, 2026.

1. SWIFT publishes requirements

SWIFT defines the SR2026 requirements for structured addresses and transaction data, and publishes the applicable Usage Guidelines.

2. SWIFT → Technology Vendors: bring your systems into compliance

SWIFT specifically instructs technology/solution vendors to: communicate requirements to financial institutions and corporates; enhance applications to capture and validate correctly structured data; implement controls to reject or correct non-compliant submissions prior to payment processing; and align development and testing ahead of November 2026.

Source: https://www.swift.com/standards/iso-20022/iso-20022-cbpr-compliance-partners

3. Final publication of CBPR+ Usage Guidelines (20 Feb. 2026)

Financial institutions and technology vendors receive the definitive specifications.

4. Message Definition Reports and Schemas (20 Mar. 2026)

Publication of technical implementation specifications.

5. Vendor Test System opens (8 May 2026)

Technology vendors may test SR2026 validation rules.

6. Pilot System opens with SR2026 validation rules (18 Jul. 2026)

Full pilot environment with live NAK conditions for non-compliant messages.

7. SWIFT → Financial Institutions: prepare, test, inform your clients

SWIFT calls on financial institutions to conduct end-to-end impact assessments, coordinate operations and technology, enhance their systems, provide clients with specifications detailing required data, offer test environments, and validate client data before initiating payments.

Source: https://www.swift.com/standards/iso-20022/iso-20022-bytes/call-action-november-2026

8. SWIFT → Banks: inform your clients

SWIFT expressly calls on financial institutions to "mobilise clients and partners to communicate requirements" and to raise awareness among corporate clients of the data required. SWIFT has published Quick Guides and encouraged institutions to disseminate them.

9. SWIFT → Corporate Clients: get your source data in order

Corporates must collect the necessary information themselves, store it in their ERP/treasury systems, and provide it to the bank at payment initiation. This requirement applies regardless of channel — MT101, pain.001 SCORE+, or proprietary banking channel.

Full Reference Links

SWIFT — Removal of Unstructured Address: https://www.swift.com/standards/iso-20022/removal-unstructured-address

SWIFT — CBPR+ Compliance for Technology Partners: https://www.swift.com/standards/iso-20022/iso-20022-cbpr-compliance-partners

SWIFT — Call to Action, November 2026: https://www.swift.com/standards/iso-20022/iso-20022-bytes/call-action-november-2026

SWIFT — Standards Release Timeline: https://www.swift.com/standards/iso-20022/standards-releases

SWIFT — November 2026 Milestone: https://www.swift.com/standards/iso-20022/iso-20022-milestone-november-2026-unstructured-addresses-removed

SWIFT — AI Address Structuring Model: https://www.swift.com/standards/iso-20022/iso-20022-swift-ai-address-structuring-model

SWIFT — ISO 20022 in Numbers Archive: https://www.swift.com/standards/iso-20022/iso-20022-bytes/archive

SWIFT — TRD Proof of Concept (prior UETR/ISO 20022): https://www.swift.com/news-events/press-releases/swift-completes-landmark-dlt-poc

Clearstream — CBPR+ pacs.008 Mandatory Fields: https://www.clearstream.com (CBPR+ mandatory fields page)

November 14, 2026 — What Changes and Why It Concerns Fiduciary Account Currency

Most institutions have addressed the postal address requirement. That is Gate 1. But there is a second, deeper consequence that most institutions have not yet confronted: after November 14, 2026, the fiduciary account currency system as it has operated to date will no longer function in the same way for cross-border payments. The structured address mandate is the visible change. The asset proof requirement is the structural change.

What Changes — SR2026 (Structured Address)

From November 14, 2026, when postal address information is provided in a CBPR+ payment message, it must be in a fully structured or hybrid format. City and country information must be provided in designated fields, at minimum, for all agents and parties. Unstructured address data will no longer be accepted at the network level.

Affected messages: MT 103 and pacs.008, including the debtor/creditor and agent fields in both.

SWIFT has confirmed: 61.2% of payments contained unstructured debtor postal addresses, and 62.9% contained unstructured creditor information at the last measurement. The scale of non-compliance is significant.

What This Means for Fiduciary Account Currency

Until November 13, 2026, institutions may continue doing what they do today. After November 14, they cannot — not without structured data compliance.

But the deeper problem is this: the fiduciary account currency system depends on the payment message as a complete record. After SR2026, the payment message must also point to — and be reconcilable with — the underlying electronic asset record.

Amount + Currency + Date are not sufficient. The institution must be able to demonstrate:

  • → WHICH asset is being transacted
  • → WHO controls it
  • → Whether it is eligible under UCC Article 12
  • → Whether it qualifies as HQLA under Basel III

If the institution cannot demonstrate these elements, the transaction record is incomplete — and the fiduciary account currency relationship cannot be maintained over the long term.

Official SWIFT Sources — SR2026 Structured Address

  • Removal of Unstructured Address — https://www.swift.com/standards/iso-20022/removal-unstructured-address
  • CBPR+ Compliance for Partners — https://www.swift.com/standards/iso-20022/iso-20022-cbpr-compliance-partners
  • November 2026 Milestone — https://www.swift.com/standards/iso-20022/iso-20022-milestone-november-2026-unstructured-addresses-removed
  • SWIFT AI Address Structuring Model — https://www.swift.com/standards/iso-20022/iso-20022-swift-ai-address-structuring-model
  • ISO 20022 in Brief — The Journey Continues — https://www.swift.com/standards/iso-20022/iso-20022-bytes/journey-continues
  • Call to Action — November 2026 — https://www.swift.com/standards/iso-20022/iso-20022-bytes/call-action-november-2026
  • Standards Release Calendar — https://www.swift.com/standards/iso-20022/standards-releases

Gate 1 vs Gate 2 — What SWIFT Proves vs What Asset Proof Proves

The following table reflects the mandatory/optional/conditional status of the nine fields most relevant to asset proof reconciliation, as established by CBPR+ usage guidelines published by Citi, UBS, Clearstream, and Payments Canada. Mandatory status is determined by the applicable message type and usage guideline — not by the identity of the issuing institution.

Gate 1 — What SWIFT/CBPR+ Validates

SWIFT message validation confirms that the payment message is syntactically and regulatorily compliant. It proves:

→ WHICH PAYMENT (UETR)
→ WHICH INSTRUCTION (Instruction Identifier)
→ WHICH AMOUNT (Settlement Amount)
→ WHEN (Settlement Date)
→ STRUCTURED ADDRESS (from 14 November 2026)

If a mandatory network predicate is missing or invalid: MESSAGE → VALIDATION FAILURE → NAK

Gate 2 — What Asset Proof Must Prove Separately

SWIFT message validation does NOT prove:

→ WHICH ASSET is being transacted
→ WHICH PROPERTY CLASS it belongs to
→ WHO HOLDS CONTROL
→ WHETHER CONTROL HAS BEEN TRANSFERRED
→ WHETHER IT IS HQLA

These predicates require the underlying electronic asset register. The payment message constitutes reconcilable evidence — it is not itself proof of the legal or prudential predicate.

Exact Field Mapping — ISO → UCC Article 12 → Basel III HQLA

Each ISO field serves a distinct evidentiary role at the transactional layer. That evidence is then reconciled against the underlying asset registry to test the predicates of UCC Article 12 and Basel III. The ISO field constitutes evidence capable of being reconciled — it is not in itself proof of the legal or prudential predicate. It is the underlying asset object that proves those predicates.

The Reverse Chain — #70 to the Underlying Asset

The most important architectural principle of this framework: #15 Amount + #16 Currency ≠ Proof of the Underlying Asset. 10,000 USD tells the system an amount and a denomination. It does not answer: WHICH ASSET? WHICH ELECTRONIC RECORD? WHO HOLDS CONTROL? WHICH ASSET CLASS? IS IT ENCUMBERED? IS IT HQLA? That requires #70 → UNDERLYING ASSET RECORD.

UCC Article 12 — What the Asset Record Must Prove

From #70 → Electronic Asset Object / Registry Record:

  • WHAT IS THE ASSET? CER / controllable account / controllable payment intangible / electronic money / deposit / investment property / other — UCC Article 12 contains explicit exclusions and classification determines the applicable regime
  • IF CER — §12-105 CONTROL: Power to obtain substantially all benefits; exclusive power to prevent others; exclusive power to transfer control; holder of control readily identifiable
  • ACQUISITION EVENT: Value (#15 Settlement Amount) + good faith (#24 Purpose as context) + lack of knowledge of a competing claim
  • OUTCOME — QUALIFYING PURCHASER: Free acquisition consequence under §12-104 — a qualifying purchaser takes free of any third-party property claim

Basel III HQLA — What the Asset Record Must Prove

From the same underlying asset object:

  • ELIGIBLE ASSET CLASS? Level 1: cash, central bank reserves, sovereign/PSE securities with 0% risk weight (no haircut applied); Level 2A: 15% haircut, ≤40% of total HQLA; Level 2B: higher haircut; or NON-HQLA
  • LIQUID IN STRESS? "Easily and immediately convertible into cash with little or no loss of value in stressed circumstances" — proven track record required
  • UNENCUMBERED? Free from any legal, regulatory, contractual, or other restriction on the ability to liquidate, sell, transfer, or assign
  • LEGALLY AND OPERATIONALLY AVAILABLE? The bank must be genuinely able to monetize the asset within the standard settlement timeframe
  • OUTCOME: LEVEL 1 / LEVEL 2A / LEVEL 2B / NON-HQLA

UCC Article 12 — Complete Legal Framework Reference

UCC Article 12 governs Controllable Electronic Records (CER) — a new category of personal property introduced to provide technologically neutral rules applicable to digital assets. Precise understanding of the statutory definitions is essential to the correct application of the field mapping.

Definition of CER (§12-102)

«A record stored on an electronic medium that can be subject to control.» A CER does not include: controllable accounts, controllable payment intangibles, deposit accounts, electronic copies of commercial paper, electronic titles to property, electronic money, investment property, or transferable records. Classification is mandatory before applying UCC Article 12 — these exclusions are substantive, not technical.

Control (§12-105)

Control requires three distinct and concurrent powers: (1) the power to avail oneself of substantially all the benefits of the electronic record; (2) the power to prevent others from availing themselves of those same benefits; and (3) the power to transfer both of those powers to a third party. Control is technologically neutral — it constitutes the functional equivalent of possession for tangible assets.

Qualifying Purchaser (§12-104)

«A purchaser of a CER or an interest in a CER that obtains control of it for value, in good faith, and without knowledge of a property claim.» All three prerequisites — value, good faith, and lack of knowledge — must be satisfied independently. Satisfaction of the value condition alone (evidenced by #15) does not by itself establish qualifying purchaser status.

Take-Free Rule (§12-104(e))

A qualifying purchaser «acquires rights in the CER free of any property right held by third parties.» This is the commercial consequence of satisfying all conditions set forth under UCC Article 12. Priority: a secured creditor holding control of a CER has priority over creditors who have only filed a financing statement, even if control was obtained after the filing. Perfection by control supersedes perfection by filing.

Published References:
Cleary Gottlieb — UCC Digital Asset Amendments — https://www.clearygottlieb.com/news/ucc-digital-asset-amendments-finalized
UCC §12-102 — Justia — https://law.justia.com/codes/new-york/2023/ucc/article-12/12-102/
UCC §12-104 — Justia — https://law.justia.com/codes/new-york/2023/ucc/article-12/12-104/
UCC §12-105 — Justia — https://law.justia.com/codes/new-york/2023/ucc/article-12/12-105/
Clifford Chance — UCC Digital Asset Amendments — https://www.cliffordchance.com (search «UCC Digital Asset Amendments»)

Basel III HQLA — Complete Regulatory Framework Reference

The Basel III Liquidity Coverage Ratio (LCR) framework requires each bank to maintain an adequate stock of unencumbered high-quality liquid assets (HQLA) that can be converted immediately into cash under a 30-calendar-day stress scenario. HQLA status is determined by the intrinsic nature of the underlying asset — not by the transaction record, amount, or denomination alone.

HQLA Asset Classification

Mandatory HQLA Characteristics

Unencumbered

"Free of any legal, regulatory, contractual or other restriction limiting the bank's ability to liquidate, sell, transfer or assign the asset." Assets pledged, used as collateral or subject to operational restrictions are ineligible. — https://www.bis.org/basel_framework/chapter/LCR/40.htm

Liquid in Stress Periods

"Easily and immediately convertible into cash with little or no loss of value" — must demonstrate a proven track record of liquidity in private markets, even under stress conditions. Assets with no market history cannot satisfy this characteristic.

Operationally Available

The bank must be able to effectively monetize the asset within the standard settlement timeframe. Both legal availability and operational availability are required. A mere accounting entry without operational monetization capacity is insufficient.

Published References:
Basel III LCR Framework — BIS — https://www.bis.org/basel_framework/chapter/LCR/40.htm
Basel III Overview — BIS — https://www.bis.org/bcbs/basel3.htm
Basel III: Definition of Unencumbered Assets — https://www.bis.org (search "Basel III unencumbered definition")
Basel III: A Global Regulatory Framework — https://www.bis.org/bcbs/basel3.htm

Institutional Readiness Confirmation — Pre-Engagement Request

The following confirmation request is addressed to any SWIFT/CBPR+ participant whose November 2026 transaction environment must be verified before we proceed with any engagement. Our Board of Directors has directed us to confirm both conditions — structured address compliance AND asset evidence provision capability — before proceeding with any cross-border transaction relationship.

Structured address implementation (Condition 1) is established separately. This request pertains to Condition 2: the nine asset-related transaction fields and the required linkage to the underlying electronic asset ledger for UCC Article 12 and Basel III HQLA compliance.

Published evidence establishes the implementation of ISO 20022 structured address requirements for the November 2026 Standards Version.

Before proceeding, we must confirm that the November 2026 transaction environment also supports the applicable asset-related transaction data and preserves its relationship to the underlying electronic asset ledger.

Specifically, please confirm the ability to capture, validate, and preserve, to the extent required by the applicable message and usage guideline:

→ #8 — Creation Date/Time: Establishes the transaction timestamp for reconciliation against the effective state of the underlying electronic asset.
→ #13 — Transaction Identifier: Provides the transaction identifier necessary to reconcile the payment transaction with the corresponding underlying asset ledger.
→ #14 — UETR: Provides the unique end-to-end transaction reference necessary for transaction traceability across all participating institutions.
→ #15 — Settlement Amount: Records the amount exchanged and enables reconciliation of the consideration/value associated with the underlying transaction.
→ #16 — Currency: Identifies the denomination of the settlement amount and enables distinction between denomination and the legal and prudential classification of the underlying asset.
→ #17 — Settlement Date: Establishes the date on which settlement occurred so that the event may be reconciled against the effective state of control, ownership, and availability of the underlying asset.
→ #22 — Payment Instrument: Identifies the applicable payment instrument and enables reconciliation with the underlying asset and its classification gateway.
→ #24 — Purpose of Payment: Records the stated economic purpose and enables reconciliation with the underlying transaction and obligation.
→ #70 — Remittance Reference / Underlying Transaction: Provides the critical reference linking the payment transaction to the underlying electronic asset ledger.

Regarding field #70, please also confirm that the referenced underlying electronic asset ledger can remain associated with the transaction throughout processing so that the following evidence may be preserved: CER Identifier → Control State and Transfer Ledger → Provenance/Chain of Ledger → Effective Date and Time → Authenticated/Post-Quantum Signature; and, from the same underlying asset ledger: Asset Classification → Encumbrance/Availability State → Liquidity Characteristics → Central Bank or Market Eligibility → Applicable Risk Weight and Haircut → Resulting HQLA Treatment.

The purpose of this confirmation is straightforward: amount and currency alone do not establish the identity, control state, provenance, or prudential classification of the underlying asset. If this confirmation requires involvement from the relevant Payments, Treasury, Legal, or Prudential Risk function, please forward this request accordingly.

1

ISO 20022 Transaction

#8 → #13 → #14 → #15 → #16 → #17 → #22 → #24 → #70

2

Underlying Reference #70

The bridge — links the message to the electronic asset ledger

3

Electronic Asset Ledger

Control / Provenance / Signature Evidence for Article 12

4

Prudential Asset Evidence

Classification / Encumbrance / Liquidity / Level 1–2/Not HQLA for Basel III

The Eliminatory Test

Breach of a mandatory SWIFT predicate → MESSAGE VALIDATION FAILURE
Inability to produce the underlying object → ASSET PREDICATE NOT ESTABLISHED
Inability to establish Article 12 control → CONTROL PREDICATE NOT ESTABLISHED
Inability to establish Basel characteristics → HQLA PREDICATE NOT ESTABLISHED

NO EVIDENCE. NO TRANSACTION.

Why We Ask Before We Engage

We are not seeking a short-term relationship. We are seeking a long-term relationship. An institution that cannot maintain both conditions after November 14, 2026 cannot maintain a cross-border transaction relationship with us.

This is not a compliance test we invented. SWIFT invented it. SWIFT asked technology vendors to correct it. SWIFT asked banks to correct it. SWIFT asked clients to correct it. We are simply asking: have you done so?

The Transition to the New Asset Class — Why This Moment, Why Now

November 14, 2026 is not simply a technical deadline. It is the inflection point at which the global payments infrastructure formally requires that transaction data be structured, traceable, and reconcilable with an underlying asset record. This is not a coincidence. It is the architecture of the transition away from fiat money of account as the sole record of value, toward a world in which the underlying electronic asset — its identity, control status, provenance, and prudential classification — must accompany the payment.

What the Old System Assumed

  • The payment message IS the record of value
  • Amount + currency + date = complete proof of transaction
  • The bank's accounting entry is the asset
  • Fiat denomination determines asset class
  • No structured link to an underlying object is required
  • Compliance is at the message level: if the message validates, the transaction is complete

What the New System Requires

  • The payment message POINTS TO the record of value
  • Amount + currency + date = transaction proof only — asset proof is distinct
  • The underlying electronic asset record IS the asset
  • Asset class is determined by the object, not by denomination
  • The structured link (#70 → underlying record) is the evidentiary bridge
  • Compliance is three-tiered: message validation + UCC Article 12 control + Basel III HQLA

Through November 13, 2026

Institutions operate within the existing fiat money of account framework. Unstructured addresses are still processed. The link to the underlying asset is not required at the network level.

November 14, 2026

SR2026 takes effect. Unstructured addresses receive a NAK. The network formally requires structured, traceable transaction data.

The New Standard

Every cross-border payment must carry structured address data, traceable transaction identifiers, and — for asset-backed transactions — a verifiable link to the underlying electronic asset record.

The Long-Term Relationship

Institutions capable of satisfying all three tiers — SWIFT message compliance, UCC Article 12 control, Basel III HQLA — are the institutions with which we engage on a long-term basis.

Y26NAK — Readiness Assessment and Remediation Tools

Not every institution will arrive at November 14, 2026 with all fields and records correctly structured. Y26NAK was designed precisely for this transition period — to give institutions a clear, documented picture of their current position and a practical path to remediate areas requiring attention. It is a readiness tool, not a compliance verdict.

Step 1: Complete the Assessment

Y26NAK tests the institution's transactional environment against applicable standards. It identifies supported fields, records present, and areas requiring attention. The assessment is documented and precise.

Step 2: Identify What Is Required

For each area requiring attention, Y26NAK identifies the specific record, field, or link required and the form it must take. The institution receives a clear, actionable picture — not a general recommendation.

Step 3: Apply the Standard

Y26NAK applies the applicable framework to each element: CBPR+ Usage Guidelines for message fields, UCC §12-102/§12-105 for electronic asset control, and the Basel III LCR framework for HQLA classification. Each result maps to one of five documented states: Confirmed, Confirmed Insufficient, Unproven, No Record Found, or Not Applicable.

Step 4: Remediation and Resolution

Where gaps are identified, Y26NAK provides the remediation tools to address them. The institution is not left with a finding and no path to resolution. The objective is readiness — and the record of that readiness is permanent and verifiable.

Why We Built Y26NAK

The payment message has always been the record of the transaction. What changes after November 14, 2026 is that the network begins to require transaction data to be structured and traceable. Y26NAK extends that traceability to the underlying asset — because SWIFT tests the message, and Y26NAK tests the asset.

What This Means for Your Institution

If any area of your transactional environment requires attention — structured address fields, asset-linked data fields, or links to underlying records — Y26NAK can identify it and provide a clear path to resolution. We are looking for institutions committed to the standard. That is the foundation of a long-term relationship.

Y26NAK.com — One Standard. One Engine. One Record.

Y26NAK Evidence Engine — The Solution

The Y26NAK Deterministic Evidence Engine provides institutions with the tools necessary to assess, document, and demonstrate their compliance across the three layers of the SR2026 framework. The Global Accountability Bingo table maps all 25 verified transaction fields across five evidence categories. One standard. One engine. One record.

The Assessment Tool

Y26NAK tests each transaction field against the applicable standard and returns a documented result for each predicate.

The Remediation Tools

When a field or record requires attention, Y26NAK provides the specific tools and guidance necessary to address it — before the transaction is initiated.

The Record

Every assessment, every result, and every resolution is retained in the record. The record is permanent. The record is verifiable.

Y26NAK.com — No Proof. No Validation.

The Y26NAK Referee — A Technology Tool for Measuring Compliance & Identifying Gaps

The Y26NAK Referee is a deterministic technology tool — not a person, not an opinion, not a judgment. It is software that applies published, written standards to transaction data and returns a documented result. It takes no position. It does not interpret. It measures.

What Y26NAK Measures

Y26NAK tests each cross-border payment transaction simultaneously against three published frameworks: (1) SWIFT CBPR+ usage guidelines for field-level message compliance, (2) UCC Article 12 for the identification of Controllable Electronic Records, control status, and qualifying purchaser standing, and (3) the Basel III Liquidity Coverage Ratio framework for HQLA classification and unencumbered status. For each field and each predicate, Y26NAK returns one of five documented outcomes: Confirmed, Confirmed Insufficient, Not Proven, No Record Found, or Not Applicable.

What Y26NAK Does With Gaps

When Y26NAK identifies a missing field, an unlocatable record, or a predicate that cannot be proven from available evidentiary materials, it does not simply flag the issue and stop. It identifies precisely which record is required, what form that record must take, and what the applicable standard demands. The institution is then provided with a clear, documented, and actionable path to remediate the gap — before the transaction is initiated, before November 14, 2026, and before the network returns a negative acknowledgment.

Why This Is Determinative After November 14, 2026

Through November 13, 2026, institutions may continue to operate as they do today. Beginning November 14, the SWIFT network will begin returning non-compliant messages at the network level — without contingency and without workaround. Y26NAK was designed so that institutions do not discover these gaps on November 14. Compliance assessment occurs before engagement, before transaction, and before the deadline — so that the long-term relationship is built on a sound and verified foundation.

If the Assessment Is Compliant

All fields confirmed. All records present. All predicates satisfied. The institution is ready for the new standard. The relationship continues on a verified basis.

If Gaps Exist

Y26NAK identifies each gap precisely. Remediation tools provide the path to resolution. The institution closes the gap before it becomes a network-level problem.

If a Record Cannot Be Produced

Y26NAK documents the result: Not Proven or No Record Found. The institution understands exactly what is missing and what is required. Nothing is left to assumption.

The Record Speaks. The Outcome Is Documented.