The 2025 SEPA rulebooks published by the European Payments Council (EPC) on November 28, 2024 are entering into force on October 5, 2025. This date aligns with the Instant Payments Regulation (Regulation (EU) 2024/886) and the SEPA Regulation (amending Regulation (EU) 260/2012)

SEPA rulebooks apply to all direct and indirect participants to SEPA schemes.

This guide details the changes introduced by the 2025 SEPA rulebooks as well as the impacts on your Numeral integration.

Rulebook updates

Hybrid postal address

Rulebook updates

The SEPA 2025 rulebooks introduce a new hybrid address format alongside the existing structured format. The existing unstructured address format will no longer be authorised starting from November 22, 2026.

The differences between structured, hybrid, and unstructured Address formats are as follows:

Numeral integration changes

• Incoming payments: no change required, as Numeral already supports structured and hybrid addresses
• Payment orders: customers have until November 22, 2026 to migrate to structured or hybrid addresses

Organization identification structure

Rulebook updates

The SEPA 2025 rulebooks now allow LEI, anyBIC, and / or one occurrence of Othr as organization identification.

In case an organization has multiple identifiers,default_other_identifier should be used to specify the identifier to be used by default.

Numeral integration changes

• Incoming payment: no change required
• Payment order
  • No change required for originating_account and receiving_account
  • Breaking change for ultimate_originator

ultimate_originator breaking change

ultimate_originator.organization_identification is currently defined with bank_code and other (string) attributes.

There will be a migration phase where these 2 attributes will still be allowed in the new definition of organization_identification but will be deprecated later on.

"organization_identification": {
  "bank_code": string | null,
  "other": string | null
}

"organization_identification": {
  "bank_code": string | null,
  "other": string | null,
  "legal_entity_identifier": string | null,  
  "business_identification_code": string | null,  
  "default_other_identifier_type": string | null,  
  "others": [  
    {  
       "type": string,  
        "value": string  
     }  
   ]  
}

"organization_identification": {  
	"legal_entity_identifier": string | null,  
  "business_identification_code": string | null,  
  "default_other_identifier_type": string | null,  
  "others": [  
    {  
       "type": string,  
        "value": string  
     }  
   ]  
}

During the migration phase, the rules will be:

1. If business_identification_code is defined, then it will take precedence over bank_code. Otherwise, if only bank_code is defined, its value will be copied to business_identification_code
2. If others array has at least one element, then it will take precedence over other as a string. Otherwise, if only other as a string is defined, then it will be copied to the value attribute of an element of the others array with type = unknown

Single return request allowed for SCT and SCT Inst payments

Rulebook updates

The SEPA 2025 rulebooks now allow only one return request per SCT and SCT Inst payment.

Numeral integration changes

• Incoming payments: Numeral support team will contact if you are receiving more than one return request
• Payment orders: the Numeral API will return a 409 - Conflict status code if a return request already exists

SCT Inst processing time

Rulebook updates

The SEPA 2025 rulebooks defines the execution timeline of SCT Inst payments as follows:

Numeral integration changes

• Incoming payments: incoming payments and related events now include initiated_at for SCT Inst payments. Customers must use initiated_at to compute target maximum execution time target and reject payments that have been received more than 7 seconds from initiation. Numeral does not calculate target maximum execution time target and does not automatically reject payments
• Payment orders
  • Created from the API: customer must include initiated_at and set auto_approval to true
  • Created from the dashboard or through file ingestion: Numeral will automatically set initiated_at

SCT Inst maximum amount

Rulebook updates

The SEPA 2025 rulebooks defines maximum amount for an SCT Inst payment as €999,999,999.99 instead of €100,000.00.

Numeral integration changes

Numeral already supports amounts up to 999,999,999.99.

Obligation to notify SCT Inst debtor

Rulebook updates

The SEPA 2025 rulebooks mandate the debtor PSP to notify its customer that that the funds have been credited on the beneficiary's account.

Numeral integration changes

Customers can already use the payment_order:executed event as a confirmation that the funds have been credited on the beneficiary's account.