Adjustments Implementation Guidelines SPS 2026

[dkoeni]

Contact Details

dkoeni

Issue category

Enhancement

Issue description

Changes with regard to adjustments to Swiss Payment Standards Implementation in Guidelines Cash Management, Credit Transfer and Status Report, valid from 14. November 2026. Details to the changes will be published on Monday, 17.11.2025 in the SPS consultation procedure.

Issue reasoning

Compliance with Swiss Payment Standards as per release.

Request

Status Report

4.3 Change status condition "NbOfTxsPerSts"

• Status changed from ND to O, with definition " Kann zur Sammlung von Rückmeldungen verwendet werden"
• Attribute is mainly used by Finnova.
• Indicates the number of transactions reflected by the respective status.

Cash Management

5.1 Changes to structured RemittanceInformation (TxDtls - RmtInf - Strd)

• With the Swift CBPR+ 2026 release, the previous restriction on using Structured Remittance Information will be removed.
• Swift CBPR+ now allows multiple structured remittance elements per transaction (D-Level).
• This results in a change to the cardinality of CdtrRefInf, affecting fields such as "Type" and "Reference" related attributes like "Referred Document Information" (RfrdDocInf) and "Referred Document Amount" (RfrdDocAmt)
  • Example: A single transaction can include multiple structured "RemittanceInformation" objects with different SCOR + Reference combinations.
• Current "remittenceReference" schema allows only one occurence of "reference" and "type" .
  • The schema therefore needs to be updated to support multiple entries (array) and include at least the additional attributes "RfrdDocInf" and "RfrdDocAmt"

--> To decide:

• Should the "RemittanceInformation" schema be adjusted and if so, with v6 or v7?
• Which additional attributes for structured Remittance Information should be included?

Other changes
Which do not have an impact on the current specification according to my estimation.

2 Discontinuation euroSIC

• QR-bills in EUR will only be supported with IBAN using a Creditor Reference (ISO 11649) or IBAN with an unstructured message, while the use of QR-IBAN with QR Reference will no longer be permitted.
• Payment in EUR to a CH or LI-IBAN must be processed according to payment type X requirements (SEPA / non-SEPA)

4.2 Tracker Data pain.002

• Status of "TrckrData" attributes changed, which are used in context of instant payments

Affected endpoints and components

No response

Proposed change

<<<<<<< Section As-Is

========

>>>>>>> Section To-Be

Affected API's

Both

Code of Conduct

• I agree to follow this project's Contribution Guidelines

[claude]

I implemented the part of this issue that was concrete enough to build without further input, and left the rest open for the working group. Draft PR: #8

Implemented — Status Report 4.3 (NbOfTxsPerSts)
Added an optional field to the payment/standing-order status responses that lets a bank report, for a status, how many of the underlying transactions were given that status — without having to list every transaction individually. Existing integrations are unaffected since it's a new optional field.

Not implemented — Cash Management 5.1 (structured remittance information)
This section itself poses it as an open decision ("To decide: ... Which additional attributes ... should be included?") and only gives examples (referred document info/amount) rather than a definitive list. For someone using the API, the choice here determines exactly which extra reference fields a payment can carry — e.g. whether we support one extra reference field per transaction or several. Since the issue leaves that choice open, I did not guess a specific set of fields. To move forward I'd need the working group to confirm the exact list of additional attributes to expose (release timing is not something I need — that's handled separately).

Not implemented — item 2 (discontinuation of euroSIC) and item 4.2 (pain.002 Tracker Data)
The issue states these have no impact on the current specification, so I left them untouched. Flagging here in case that assessment changes once the SPS 2026 consultation details are published.