SEPA — Single Euro Payments Area

SEPA (Single Euro Payments Area) harmonises euro-denominated bank transfers and direct debits across 36 European countries (EU plus EEA, Switzerland, Monaco, San Marino, Andorra, Vatican City and the UK). Since the SEPA migration deadline of 1 February 2014, all euro-payments within SEPA follow standardised formats (ISO 20022 XML), with cross-border euro-transfers priced the same as domestic. SEPA is foundational to ERP-side payments-and-receivables operations for any DACH-based organisation.

SEPA scheme components

SEPA Credit Transfer (SCT) — standard euro-payment, settlement within 1 banking day. ERP generates pain.001 XML files; bank confirms via pain.002
SEPA Direct Debit Core (SDD Core) — consumer direct debit, B2C, with 8-week refund right for unauthorised debits
SEPA Direct Debit B2B (SDD B2B) — business direct debit with shorter timelines and no refund right after acceptance
SEPA Instant Credit Transfer (SCT Inst) — real-time payments under 100,000 EUR, available 24/7, settles within 10 seconds. Becoming mandatory for all PSPs from 2025 under EU Instant Payments Regulation
SEPA Request-to-Pay (SRTP) — newer scheme for invoice-driven payment requests, increasingly relevant for B2B and consumer billing

ERP integration patterns

Standard ERP payment-run workflow. (1) Selection: AP module selects open invoices matching payment criteria (due date, vendor priority, discount window). (2) Payment proposal: treasury or AP reviewer approves or adjusts the proposed payments. (3) SEPA file generation: ERP generates pain.001.001.x XML file with the structured payment instructions. (4) Bank submission: file uploaded to corporate banking portal (EBICS, SWIFTNet, host-to-host), increasingly via API-based channels (PSD2 Account Information / Payment Initiation Services). (5) Confirmation: bank sends pain.002 acknowledgement and account statement (camt.053) showing the executed payments. (6) Reconciliation: ERP matches bank statement entries to original payment instructions, clearing the open items.

Direct-debit mandate management

SEPA Direct Debit requires a signed mandate from the debtor authorising the creditor to collect. Mandate management is an ERP-side responsibility: store the signed mandate (paper or electronic with qualified signature), generate the mandate reference (UMR — Unique Mandate Reference), populate the SDD XML correctly with mandate details, monitor for mandate-related exceptions (returns, refusals). Pre-notification (mandate-specific or general) to the debtor is required at least 14 calendar days before the debit. Modern DACH ERPs (SAP, Microsoft Dynamics 365, NetSuite, weclapp) handle mandate workflows natively; specialist tools (Bottomline, PPRO, GoCardless) offer additional capabilities for high-volume B2C direct-debit operations.

Instant payments mandate

The EU Instant Payments Regulation (effective 2024) mandates that all EU-area Payment Service Providers (PSPs) must offer SCT Inst as a default service from October 2025 (receiving) and January 2026 (sending), with no premium pricing versus standard SCT. For ERP-bearing organisations, this changes payment economics and customer expectations. Outbound: ad-hoc supplier payments can execute in seconds rather than overnight, supporting tighter cash management and Skonto optimisation. Inbound: customer payments arriving instantly enable just-in-time order release for prepaid e-commerce. ERP-side adaptation: support for SCT Inst as payment method, real-time settlement notifications, AI-driven cash application operating on near-real-time bank statements.

Frequently Asked Questions

Is SEPA only for euro payments?

Yes. SEPA covers only euro-denominated payments. Other-currency payments to or from SEPA countries use traditional cross-border banking channels (SWIFT MT103, multi-currency platforms). For mid-market with multi-currency operations, ERP must handle both SEPA (for euro) and SWIFT-based foreign-currency payments.

Does SEPA replace national payment systems?

For euro payments, yes — national legacy systems (German DTAUS, French Etebac) were retired by 2014. For other-currency domestic payments, national systems persist (Swiss Postfinance, Swiss QR-bill, UK BACS). SEPA does not affect non-euro flows.

How does PSD2 affect SEPA in ERP?

PSD2 enables third-party Payment Initiation Services and Account Information Services through bank APIs. This allows ERP and treasury platforms to integrate directly with banks via standardised APIs rather than through EBICS or host-to-host file transfers. Mid-market in DACH increasingly adopts API-based bank integration; legacy EBICS persists alongside.