Your bank is ready. Your ERP, probably not.
Since 9 October 2025, all banks in the eurozone have been required to both send and receive SEPA Instant Credit Transfers (SCT Inst) at parity with standard transfer fees, under EU Regulation 2024/886. The historical €100,000 per-transaction cap has been lifted — the European Payments Council raised the theoretical maximum to €999,999,999.99. In theory, CFOs and treasurers at mid-market companies can now settle suppliers, intercompany balances, or payroll advances in ten seconds, 24/7, at no extra cost.
In practice, the majority of ERP treasury modules still operate as though it were 2019: end-of-day PAIN.001 payment batches, next-morning MT940 reconciliation, approval workflows calibrated to J+1 transfers. The problem is not in the banking infrastructure — it is in how your ERP is configured.
This guide is written for CFOs, treasurers, and cash managers at mid-market companies running SAP S/4HANA, Dynamics 365 Finance, Sage Intacct, or Odoo. It explains why the gap exists, what it changes operationally, and how to close it.
EU Regulation 2024/886 on Instant Payments: Background
From PSD2 to SCT Inst: The Long Road to Real Time
Europe laid the groundwork for real-time payments with the PSD2 directive (2018) and Open Banking. But PSD2 focused primarily on account data access (AIS) and payment initiation (PIS) — not settlement speed. The SEPA Instant Credit Transfer scheme (SCT Inst) had existed as a voluntary option since November 2017, but adoption remained patchy: under 10% of SEPA transfers in 2020, and additional banking fees that discouraged corporate use.
EU Regulation 2024/886, adopted on 13 March 2024 and in force from April 2024, changed the equation by converting SCT Inst from a commercial option into a regulatory obligation.
What the Regulation Requires of Banks
The compliance calendar is precise and non-negotiable:
- 9 January 2025: eurozone banks were required to be able to receive instant transfers at standard transfer rates.
- 9 October 2025: obligation extended to sending instant transfers. Banks can no longer charge a premium for SCT Inst.
- 9 January 2027: same deadlines for banks in EU countries outside the eurozone.
Three technical constraints apply to every SCT Inst transaction: 24/7 availability, crediting the beneficiary’s account in under ten seconds, and immediate settlement confirmation to the sender. Simultaneously, since October 2025, Verification of Payee (VoP) has been operational — banks verify in real time that the beneficiary name matches the IBAN before executing the transfer.
What the Regulation Does Not Require of Companies — But What They Should Do
The regulation does not compel companies to send their payments via SCT Inst. It simply removes any cost justification for not doing so. This is a shift in leverage: treasurers no longer have an economic excuse to keep running J+1 payment batches when a critical transaction can settle in ten seconds at the same price.
But capturing that opportunity requires reconfiguring the ERP treasury module. Which most companies have not done.
Why ERP Treasury Modules Have Fallen Behind
Legacy Modules Are Built Around J+1 Transfers
ERPs were designed to process payments in batch mode: the treasurer validates a payment run by mid-morning, the PAIN.001 file is generated and sent to the bank via EBICS (Electronic Banking Internet Communication Standard), the bank executes the transfers overnight, and the next morning the MT940 or CAMT.053 statement arrives with confirmations. This cycle is deeply embedded in ERP workflows: payment approvals, treasury controls, and reconciliation are all calibrated to a 24-hour cadence.
SCT Inst breaks that model on three structural points. First, there is no batch: each transfer is initiated, routed, and confirmed individually in real time. Second, the payment confirmation (the credit CAMT.054) arrives within seconds of dispatch — not the following morning. Third, from 15 November 2026, unstructured address formats are banned in EPC messages, including SCT and SCT Inst, which requires updating counterparty master data in the ERP (EPC 2025 SEPA Rulebook Updates, Mambu).
SCT Inst Changes the Model: 10-Second Confirmation, Immediate Reconciliation
The EBICS Time Stamp (EBICS TS) protocol — which lets ERPs transmit payment orders in real time without manual intervention — was updated in October 2025 with new SCT Inst-specific order types in the BTF (Business Transaction Format) parameter. SAP and Dynamics 365 support EBICS TS natively in their payment modules. Sage Intacct and Odoo rely on partner connectors (Ponto, Nordigen, Agicap) that may or may not have integrated these new BTF order types.
Result: Unconfigured ERPs Treat Instant Payments as Deferred
If your ERP has not been configured for SCT Inst, it continues to bundle your payments into a standard PAIN.001 batch, even if your bank is technically ready to process them in ten seconds. The result: you have been paying without a surcharge since January 2025, but you are capturing none of the operational benefits of instant payments. You continue to manage treasury positions on a J-1 basis, wait until the next day to confirm a supplier payment has gone through, and absorb reconciliation gaps that a daily CAMT.053 cannot avoid.
What SCT Inst Actually Changes in Treasury Management
Real-Time Liquidity vs. J-1 Treasury Position
The first shift is the temporal granularity of the treasury position. With standard payment batches, the treasurer knows their position at end of day or the following morning. With SCT Inst, every payment sent or received is immediately reflected in the bank balance. For a mid-market group with accounts across multiple banks, this transforms intraday cash pooling: intercompany transfers that previously took overnight can be executed in seconds to optimise balances throughout the day.
Immediate Automatic Reconciliation with CAMT.054
The CAMT.054 format is the individual debit/credit notification sent by the bank for each transaction. Where CAMT.053 is a daily bank statement summarising the previous day’s transactions, CAMT.054 is a push message triggered transaction by transaction, immediately after execution. For treasurers, this means the end of the morning bank statement download: each SCT Inst payment received generates a CAMT.054 that can feed automatic reconciliation in the ERP in real time.
This architecture requires your ERP or TMS to be configured to receive CAMT.054 push webhooks rather than periodically downloading CAMT.053 files. This is not a minor update — it is a paradigm shift in bank-ERP integration.
Concrete Opportunities: Pay at the Last Moment, Collect Immediately
SCT Inst opens optimisation levers that J+1 transfers simply cannot support:
- DPO management (Days Payable Outstanding): with SCT Inst, you can hold cash until the last moment and pay the supplier exactly at the due date, even on a Saturday evening. A J+1 transfer forces you to anticipate by one or two business days, unnecessarily tying up cash.
- E-commerce collections: real-time payment confirmation allows fulfilment to begin immediately after settlement, without waiting for the next day’s bank validation.
- Instant intercompany: balances between group subsidiaries can be settled in seconds, simplifying consolidation and reducing dormant intercompany cash positions.
How to Reconfigure Your ERP to Leverage SCT Inst
SAP S/4HANA TRM: Enabling SEPA Instant Credit Transfer
In SAP S/4HANA, SCT Inst configuration runs primarily through the DMEE (Data Medium Exchange Engine) and payment parameters. You need to create or adapt a SEPA Instant payment format (distinct from the standard SCT format), configure EBICS TS communication channels with the new BTF order types, and set up CAMT.054 push notifications in the bank integration configuration. Verification of Payee (VoP) requires additional verification on the banking partner side, which SAP is progressively integrating in its 2025–2026 releases. Before starting, confirm with your SAP integrator that your S/4HANA version is compatible and that your banking partner has activated EBICS TS.
Dynamics 365 Finance: SEPA Instant Payment Formats
In Dynamics 365 Finance, configuration happens in the Treasury module: Setup > Methods of Payment > Payment Formats. Select the SEPA Instant Credit Transfer format from GER (Generic Electronic Reporting) configuration files, update EBICS TS parameters in bank accounts, and enable real-time CAMT.054 push notifications via live reconciliation journals. Microsoft is progressively rolling out these features in cloud Dynamics 365 versions — check availability in the Release Plan for your version.
Sage Intacct and Odoo: Depends on the Banking Connector
For Sage Intacct and Odoo, native SCT Inst support depends on the banking connector in use. Aggregators such as Ponto (Isabel Group), Nordigen (GoCardless), or Agicap have generally updated their APIs to support SCT Inst, but ERP-side configuration must be verified with the vendor or partner. For Odoo, the l10n_sepa module supports PAIN.001 format for standard SCT — SCT Inst support requires additional configuration and verification that the banking partner is compatible with EBICS TS or the corresponding API.
Configuring CAMT.054 Push Notifications
Regardless of ERP solution, enabling CAMT.054 push notifications requires three steps:
- Banking side: verify that your EBICS agreement includes CAMT.054 confirmation reports in push mode (not just download). All major European banking groups now support this mode for SCT Inst.
- ERP side: configure the directory or webhook to receive CAMT.054 files, and define automatic matching rules (IBAN, ISO 20022 structured reference) to trigger reconciliation without manual intervention.
- Process side: adapt approval and reconciliation workflows to handle near-real-time notifications rather than daily batch processing.
What to Prepare Before Activating SCT Inst in the ERP
Agreement with Your Bank on EBICS TS Access
The first step is contractual: verify with your banking relationship manager that your EBICS agreement is up to date and includes BTF order types for SCT Inst. Some older EBICS agreements need to be renegotiated to incorporate EBICS TS. This update is free under the regulation (Regulation 2024/886 prohibits surcharges), but it may take a few weeks depending on your bank’s internal processes.
Revision of Internal Approval Workflows
This is the most critical and most commonly overlooked point. Your payment approval workflows were designed for a J+1 cycle: the treasurer validates a batch, the financial controller co-signs, the payment goes out the next day. With SCT Inst, a payment can be executed within ten seconds of the first approval. If your dual-signature workflow is not revised, you risk a fraudulent payment going out before the second approver has had time to react.
Updating workflows must precede activating SCT Inst in the ERP. This means setting amount thresholds below which SCT Inst can run on single signature, and thresholds above which a validation delay is enforced before execution.
ISO 20022 Structured Addresses in Counterparty Master Data
The 15 November 2026 deadline is an immediate concern. From that date, unstructured address formats are banned in EPC messages — SCT and SCT Inst included. If your counterparty master data (suppliers, customers) stores addresses in a free-text field, your payments will be rejected by banks. An audit of counterparty master data and migration to ISO 20022 structured address fields (street, number, postcode, city, country in separate fields) is non-negotiable before end of October 2026.
Business Use Cases That Justify the Migration
SCT Inst is not a technical update: it is an operational competitive lever. Here are the most concrete use cases for a mid-market company.
Suppliers under cash pressure: a supplier with a tight cash position who accepts a commercial discount in exchange for immediate payment can be settled in ten seconds. This negotiation lever does not exist with a J+1 transfer.
Intragroup intercompany: a holding company that needs to balance subsidiary balances at end of day can move liquidity in seconds, without overnight overdraft costs or intraday credit line fees.
Emergency payroll: a salary advance or urgent replacement payment can be executed on a Sunday evening with no banking delay constraint.
Real-time B2B collections: for companies that deliver against payment (distribution, wholesale), SCT Inst confirmation before dispatch eliminates the risk of delivering without a settlement guarantee.
To upgrade your ERP treasury module, start with these three concrete actions: verify your EBICS agreement with your bank, audit your counterparty master data for structured addresses before 15 November 2026, and review your approval workflows before enabling SCT Inst.
To go deeper on bank-ERP integration, see our guide on ERP and Open Banking: connecting your bank accounts for real-time treasury and our analysis on ERP and treasury management: TMS, SWIFT, and real-time cash forecasting.
