EUR settlement in Europe runs through two largely separate systems, and the distinction matters more for corporate treasury than most textbooks explain. TARGET2, now migrated to the unified T2 platform completed in March 2023, handles real-time gross settlement for large-value interbank transactions. EBA Clearing operates two distinct services: STEP2 for bulk ACH-style credit transfers, and RT1 for instant payments under the SCT Inst scheme. Treasury teams that conflate these systems end up either paying for RTGS speed when STEP2 finality is sufficient, or accepting batch-settlement timing windows that create intraday exposure they have not modeled.
What TARGET2 (T2) Actually Settles
T2 settles central bank money, final and irrevocable, between direct participants, primarily credit institutions. Corporate treasuries do not hold accounts directly in T2. They access the EUR balance their bank maintains at its T2-participating correspondent. A EUR payment from a Miami-based treasury to a European supplier therefore settles when the beneficiary bank's T2 position is credited, not when the payment instruction reaches the wire.
T2 operates on an RTGS model with a settlement window running roughly 07:00 CET to 18:00 CET on TARGET business days. Instructions submitted before cut-off settle the same day. Instructions submitted after 18:00 queue for the next settlement day. The practical implication: same-day EUR settlement requires your payment to be in your correspondent bank's queue well before mid-afternoon Central European time.
The March 2023 T2 migration consolidated the original TARGET2 and TARGET2-Securities platforms and introduced ISO 20022 message formats, specifically pacs.008 and pacs.009, replacing legacy SWIFT MT103 and MT202 structures. For corporate treasury, the main operational change is that correspondent bank interfaces now surface richer payment data and structured remittance fields that map to the ISO 20022 RmtInf block, which improves automated reconciliation matching.
EBA STEP2: Bulk Credit Transfers
STEP2 is a multilateral net settlement system designed for high-volume retail and commercial credit transfers, governed by the SEPA Credit Transfer (SCT) scheme. STEP2 runs in multiple settlement cycles through the business day. Crucially, settlement occurs in T2: STEP2 nets positions across its participants and settles the net in central bank money at designated times.
For corporate treasury, STEP2 is the default rail for routine EUR supplier payments and intercompany transfers within the Eurozone where same-day RTGS timing is not required. Settlement finality in STEP2 is tied to specific cycle cut-offs, not real-time. The practical question for treasury is: which cycle applies to your payment, and does your correspondent's submission cut-off allow you to hit it?
EBA RT1: Instant Payments
RT1 processes SCT Inst transactions, individual credit transfers up to EUR 100,000 that complete within 10 seconds, around the clock including weekends and public holidays. Settlement is in central bank money via T2, though participants must maintain a dedicated liquidity buffer in T2 specifically for RT1 obligations.
The SCT Inst amount limit is a practical constraint for treasury. Most intercompany and large-value supplier payments exceed EUR 100,000. RT1 is therefore most useful for time-sensitive low-value disbursements: urgent vendor corrections, customer refunds in EUR, or FX legs below the threshold on a specific corridor. It is not a substitute for T2-settled large-value payments.
How the Two Systems Interact in a Cross-Border Payment
Consider a USD-to-EUR payment from a US corporate treasury to a Eurozone supplier. The payment arrives in USD, converts at the agreed FX rate, and must settle in EUR. The corridor typically traverses: originating bank, then a US correspondent with EUR capability, then a participating bank in STEP2 or T2, then the beneficiary bank.
Where settlement finality lands depends on whether your correspondent routes via STEP2 or T2 directly. A T2-direct route gives same-day finality if submitted before cut-off. A STEP2 route gives next-cycle finality, which may be same-day or next-morning depending on which cycle is still open when the instruction arrives at the STEP2 participant.
This is not a theoretical distinction. A corporate treasury team managing EUR payables with a Tuesday 17:00 CET deadline needs to know which route their correspondent uses and what submission cut-off applies, not just that the payment is denominated in EUR. We are not saying STEP2 is inferior to T2. For bulk EUR supplier payments in non-time-sensitive corridors, STEP2 is entirely appropriate and cost-effective. The point is that each payment should have an explicit, verified settlement system designation, not an implicit assumption.
What Birch Hill Tracks in This Context
When routing a EUR payment, the reconciliation record Birch Hill generates includes the settlement system actually used (T2 or a STEP2 cycle identifier), the cycle cut-off that applied, the timestamp of settlement finality, and the ISO 20022 end-to-end reference. The break-detection logic flags any payment where the expected settlement cycle did not produce a confirmed credit within the window.
This matters at close. A treasury controller whose EUR payable shows submitted but not settled at 17:30 CET on the last business day of a month has a materially different problem depending on whether the payment is queued in a T2 position that will settle in the 18:00 CET cycle or is sitting unprocessed in a STEP2 queue that cycles next morning. Having that distinction available in the payment record, rather than requiring a call to the correspondent bank to investigate, is where the operational value sits.