Real-time gross settlement (RTGS) is a funds-transfer system in which banks settle individual transactions instantly and on a one-by-one basis through a central bank’s books. “Real time” means settlement occurs immediately when a payment is received; “gross settlement” means each payment is processed and settled individually rather than being accumulated and netted against other payments. Because settlements are final and irrevocable at the moment they post, RTGS is the primary mechanism for high‑value, time‑sensitive interbank payments (e.g., large corporate payments, bank-to-bank settlements, urgent cross-border transfers) (Investopedia).
Key takeaways
– RTGS processes individual payments immediately and makes them final once settled.
– It is typically run by a country’s central bank and used for high‑value transfers.
– RTGS reduces settlement (counterparty) risk but can be more expensive per transfer than net‑settlement systems.
– Well-known RTGS systems include Fedwire (U.S.), CHAPS (U.K.), and TARGET2 (Euro area) (Investopedia; Federal Reserve; ECB).
How RTGS works — the mechanics
– Participants: commercial banks and financial institutions hold accounts (reserves) at the central bank and submit payment messages to the RTGS infrastructure.
– Processing: each payment message is processed immediately and funds are transferred by debiting the sender’s central bank account and crediting the receiver’s account.
– Finality: once the entry posts, it is final and cannot be reversed (except in extraordinary legal/court-ordered situations).
– Liquidity management: banks must have sufficient central bank balances or access to intraday credit to make RTGS payments. Central banks often provide intraday credit or liquidity‑saving mechanisms to keep the system functioning smoothly.
– Settlement does not require physical cash; it is an electronic change to central‑bank ledger balances (Investopedia; Bank for International Settlements).
Why central banks use RTGS
– Minimize settlement risk (delivery risk) for large-value payments by eliminating multihour or end-of-day exposure.
– Reduce systemic risk, because failure to settle a large transaction does not cascade through netting cycles.
– Improve speed and certainty for critical payments (e.g., interbank borrowing, securities settlement, emergency liquidity operations).
RTGS vs net settlement (e.g., BACS)
– RTGS: each payment processed individually, in real time, final on posting. Best for high-value, urgent transfers.
– Net settlement (ACH/BACS): payments are accumulated throughout the day and settled as a net position at preset times (often end of day). This is more cost-efficient for high volumes of low‑value transactions but exposes participants to end‑of‑day settlement risk (Investopedia; BIS).
– Tradeoff: RTGS reduces counterparty risk but typically has higher per-transaction costs and requires more intraday liquidity.
Examples of RTGS systems
– Fedwire Funds Service — U.S. RTGS-like system that evolved from earlier telegraph-based transfers (Federal Reserve).
– CHAPS — U.K. high-value sterling payments system run by the Bank of England.
– TARGET2 — RTGS for euro‑area payments operated by the Eurosystem (European Central Bank).
– Many other countries operate their own RTGS platforms (Investopedia; ECB; BIS).
Advantages of RTGS
– Immediate finality and irrevocability.
– Lower systemic and settlement risk for high-value payments.
– Shorter exposure time for transactional data — smaller window for some cybersecurity threats.
– Supports time-critical liquidity operations and settlement of financial markets (Investopedia).
Limitations and risks
– Higher transaction costs per payment relative to netting-based systems.
– Requires sufficient intraday liquidity; participants may need access to central bank credit or collateralized intraday loans.
– Operational and cyber risk — although RTGS shortens exposure windows, it still depends on robust, resilient infrastructure and controls (SBA; BIS).
– Potential for liquidity gridlock if multiple participants run low balances simultaneously.
Real-time gross settlement fees
– No universal fee — fees depend on the country, the central bank or operator, the sending institution’s pricing, and the value of the transfer.
– Fees may be flat per transaction, tiered by value, or sometimes waived for certain client segments or internal transfers.
– Because RTGS is costlier to run, many banks pass some of this cost to customers. Corporate clients can often negotiate or use specialized banking arrangements to reduce per‑transfer costs (Investopedia).
Practical steps — For individuals who need instant, high‑value transfers
1. Confirm whether your bank offers RTGS/express high-value transfers and the operating hours. Some RTGS systems operate only on business days and limited hours.
2. Check fees and thresholds (minimum/maximum amounts that trigger RTGS vs ACH). Ask whether fees can be waived for one-off or urgent transfers.
3. Provide exact beneficiary details (bank name, account number/IBAN, sort code/BIC/SWIFT) to avoid delays or recall requests.
4. Use RTGS only when speed and irrevocability are required; for routine, low-value payments, consider ACH/batch options which are cheaper.
5. Keep proof of payment and confirmation messages in case of inquiries.
Practical steps — For businesses that handle frequent high‑value payments
1. Analyze your payment flows: separate urgent/high-value items for RTGS from bulk payroll/supplier payments manageable by net systems.
2. Negotiate treasury services and volume‑based pricing with banks; consider a dedicated banking channel for RTGS.
3. Consolidate accounts where feasible to reduce the number of RTGS transactions and aggregate value.
4. Use same‑bank transfers where possible (often internal and cheaper), or employ payment service providers that can route payments optimally.
5. Maintain a liquidity buffer in your primary banking account to avoid failed RTGS payments and related costs.
Practical steps — For banks and payment operators
1. Integrate robust RTGS connectivity and allocate liquidity management tools (real-time monitoring, forecasting).
2. Use liquidity-saving mechanisms (LSMs), queuing, or bilateral netting where permitted to reduce intraday liquidity needs.
3. Ensure strong operational resilience and cyber‑security: redundant systems, formatted message validation, two‑factor authentication, staff training against social engineering.
4. Coordinate with the central bank for intraday credit lines and contingency procedures.
5. Offer clear client communications and fee structures for corporate and retail customers.
Practical steps — For central banks and regulators
1. Design RTGS with liquidity-saving features and risk controls (e.g., queuing and prioritization, collateralized intraday credit).
2. Set operating hours that reflect market needs while balancing systemic risk.
3. Require regular operational resilience and cyber‑risk testing; publish contingency plans and recovery procedures.
4. Encourage interoperability and messaging standards to support cross‑border settlement efficiency (e.g., ISO 20022 migration).
When to choose RTGS vs other systems
– Choose RTGS when:
• The transfer is large or time sensitive (e.g., securities settlement, urgent interbank funding).
• Finality and irrevocability are required.
– Choose net/ACH or batch systems when:
• Payments are low value and non‑urgent (e.g., payroll, routine supplier payments).
• Cost efficiency is more important than immediate finality.
The bottom line
RTGS is the backbone of high‑value payment infrastructure — a system that provides immediate, final settlement of individual transactions and greatly reduces settlement risk. It is indispensable for central banks and financial markets, though it requires robust liquidity management and can be more costly per transaction than netting systems. For ordinary users and businesses, RTGS should be used when speed and certainty justify the cost; for banks and policymakers, the focus is on operational resilience and efficient liquidity arrangements (Investopedia; Fed; ECB; BIS).
Sources and further reading
– Investopedia, “Real-Time Gross Settlement (RTGS)” — (Theresa Chiechi)
– Federal Reserve Bank of New York, “Creating an Integrated Payment System: The Evolution of Fedwire”
– European Central Bank, “What is TARGET2?”
– Bank for International Settlements, “Payment Systems in the United Kingdom” and related BIS publications
– U.S. Small Business Administration, “Stay Safe from Cybersecurity Threats”
Editor’s note: The following topics are reserved for upcoming updates and will be expanded with detailed examples and datasets.