EPC Rulebooks proposed changes 2026 SCT, SCT Inst, SDD Core, SDD B2B und OCT Inst

Published on

19/11/2026

Updated on

19/11/2026

Reading time

5 min

Last updated: 19 November 2026

On 9 November 2026 the European Payments Council (EPC) published the results of its 2026 change management cycle: five Change Proposal Submission Documents, one per rulebook (EPC099-26 to EPC103-26). They record which of the change requests submitted will go into the next rulebook versions – and which will not. The most important news, however, is not in the decision tables but in the foreword: the next formal rulebook generation will arrive later than usual.

The short version

  • Postponed: the next formal rulebook generation will not appear in November 2026 but in the second quarter of 2027.
  • Name fields: 70 → 140 characters, in all five rulebooks.
  • SCT Inst: a new repayment procedure initiated by the beneficiary, based on the pacs.004.
  • SDD: a new reason code FR01 for (possible) fraudulent collections.
  • ISO 20022: the version change is coming – but only with the 2030 rulebooks.

The changes in detail

The sections below can be opened individually. They cover the rulebooks for SCT, SCT Inst, SDD Core and B2B, and OCT Inst.

The new timeline – and why it has slipped

In September 2026 the EPC decided to postpone the next formal version of all five rulebooks from November 2026 to the second quarter of 2027. Those versions will bring three things together:

  • the accepted business change requests from the 2026 cycle,
  • the regulatory changes arising from the final texts of PSR and PSD3 – expected in December 2026 at the earliest and to take effect in September 2028 at the earliest,
  • the regulatory changes from the EPC action plan addressing the recommendations of the ECB and the Joint Oversight Team under the PISA oversight framework.

Only once PSR and PSD3 have been published will the EPC be able to set the actual publication and effectiveness dates of the so-called 2028 versions, in the first half of 2027. As things stand, they are expected to take effect on the PSR and PSD3 date or close to it.

The next regular change cycle already relates to the rulebook versions entering into effect in November 2030. They will be published by May 2029 – giving the industry 18 months to implement them.

What changes in all five rulebooks alike

Eight items apply to SCT, SCT Inst, SDD Core, SDD B2B and OCT Inst equally:

  • Name fields 70 → 140 characters: the maximum length of the Name elements doubles.
  • ISO 20022 migration not before 2030: the 2030 versions move to the then current ISO 20022 release; rulebook and technical documents appear 18 months before they take effect.
  • Alignment with FTR3: the SEPA Usage Rules on (Ultimate) Creditor/Debtor Organisation and Private Identification are brought into line with the Funds Transfer Regulation (EU) 2023/1113.
  • Structured remittance information: the description and the SEPA Format Rules are reworked where that information is structured.
  • New AOS rules: communities must now submit the characteristics, business rules and technical specifications of an Additional Optional Service to the EPC for review beforehand.
  • The term “Payment Account” is used consistently and in line with applicable EU legislation.
  • US military banking: entities operating strictly under the Military Banking Programme of the US Department of Defense become eligible for scheme participation.
  • Effectiveness dates: from the version after 2028 they are tied to those of the relevant technical standards.
SCT – in addition

20 change requests, input from 29 (communities of) payment service providers. Beyond the common set, two items were accepted:

  • Validation duty for the Creditor Reference: the Originator PSP must validate structured remittance information where it explicitly refers to ISO 11649 – and only that information, and only in the pain.001, not in the subsequent pacs.008.
  • Recall deadline 10 → 15 banking business days for the reasons “Duplicate” and “Technical Reason”.

Rejected were, among others, the optional use of the UETR, address details for the Originator and Beneficiary Reference Party, and an enhanced remittance information attribute.

SCT Inst – in addition

35 change requests, input from 33 (communities of) payment service providers – the largest of the five cycles. The two SCT items above apply here as well, plus two of its own:

  • Beneficiary Initiated Repayment: a formal procedure allowing the Beneficiary to transfer back funds from an SCT Inst transaction that has already settled successfully. It covers all use cases, including payments at the point of interaction, and uses the pacs.004.
  • One reject reason disappears: “Amount exceeds the maximum authorized amount for SCT Inst” is no longer a valid ground for a Reject by the Originator PSP.

Rejected were, among others, the proposal to make OCT Inst mandatory for certain SCT Inst participants, and the Credit Confirmation Inquiry.

SDD Core and SDD B2B – in addition

16 change requests and 28 responses for SDD Core, 14 and 20 for SDD B2B. Both direct debit schemes gain only one change of their own – but a practical one:

  • New reason code FR01 for a (possible) fraudulent collection. In SDD Core it applies to Reject, Return and Refund, in SDD B2B to Reject and Return (see the overview of SEPA reason codes).

Note that the ISO 11649 validation duty and the extended recall deadline do not apply to the direct debit schemes. Rejected were the shortening of the collection cycle from D-1 to D, mandatory use of purpose and category purpose codes, greater transparency on creditors, and the removal of the “Not Specified Reason” codes in R-message processing.

OCT Inst – in addition

16 change requests, 16 responses. The youngest scheme picks up the most changes of its own – mostly alignments with the SEPA schemes:

  • Charges: they may no longer be deducted from the principal amount. For the Euro Leg only the shared cost principle is permitted – incoming and outgoing alike, and irrespective of the charging option chosen in the non-Euro Leg. This brings the charging rules into line with the SCT schemes.
  • Planned non-availability: participants may set maintenance windows for their OCT Inst service, as in SCT Inst. This makes it easier for SCT Inst participants to take up OCT Inst.
  • Validation duty for the Creditor Reference: as in SCT, here performed by the PSP of the Euro Leg-based Payer.

Returning funds after the amount has been credited was already provided for in the scheme; no action was needed.

How the change process works

The cycle follows a fixed sequence, which the five documents trace for every single change request:

Submission by 31 December 2025 → analysis and recommendation by the PSEMWG (for OCT Inst by the OLO Task Force) → a three-month public consultation from 13 March to 11 June 2026 → change proposals based on the responses → decision by the Payment Scheme Management Board, taking into account the position papers of the end-user group (EPC106-26) and the technical player group (EPC107-26).

What this means for institutions

The later date buys room, not a break: the 2028 versions will bundle business and regulatory changes into one package, and their scope depends on PSR and PSD3 – it will not be possible to size it reliably before the course of 2027. What can be planned today is what stands regardless. Doubling the name fields to 140 characters touches data storage, screens, printed output and sanctions screening alike, and should not be dismissed as a field-length change. The new validation duty for structured remittance information under ISO 11649 affects validation at payment initiation. And anyone offering SCT Inst should take the beneficiary-initiated repayment procedure into process planning early – it is the only genuinely new business function in this cycle.

The Instant Payments Regulation is unaffected; its deadlines run independently of the rulebook cycle.

Sources

Suchen Sie nach einer Lösung für den elektronischen Zahlungsverkehr?