Real-Time Gross Settlement
Central bank payment system settling large-value transactions individually in real time with immediate finality.
Real-Time Gross Settlement (RTGS) is a payment system operated by central banks in which large-value fund transfers are settled individually (on a gross basis, not netted with other transactions) in real time (immediately upon processing, not at the end of the day). RTGS systems are the backbone of financial system liquidity management, used for high-value interbank transfers, securities settlements, and time-critical payments where irrevocability matters.
Key characteristics: immediate settlement—funds move to the recipient's account instantly with finality (no risk of reversal); gross settlement—each transaction settles separately, requiring the full amount of liquidity; central bank money—settlement occurs in central bank reserves, carrying no credit risk; and irrevocability—once settled, payments cannot be reversed.
Major RTGS systems include Fedwire Funds Service (U.S. Federal Reserve), CHAPS (Bank of England), TARGET2 (European Central Bank, now upgraded to T2), SIC (Swiss National Bank), and equivalent systems in virtually every developed economy. TARGET2 alone processes over 350,000 transactions per day with average values in the millions of euros.
For corporate treasury teams and banks, RTGS access enables intraday liquidity management: banks optimize how much central bank liquidity to maintain throughout the day, anticipating large incoming and outgoing payments. Insufficient intraday liquidity can delay payments, creating systemic risk.
Many RTGS systems have migrated to ISO 20022 messaging standards, enabling richer payment data. The coexistence of RTGS (for large value, irrevocable, same-day settlement) with retail payment systems (ACH for batch, instant payment systems for retail real-time) reflects the layered architecture of modern payment systems.
FAQs
What is the difference between RTGS and netting?
RTGS settles each transaction individually using the full gross amount—if Bank A sends $100M and owes Bank B $80M, these settle as two separate transactions. Netting (or DNS—Deferred Net Settlement) calculates each bank's net position against all other banks throughout the day, then settles only the net differences in a single end-of-day cycle. Netting is liquidity-efficient (requires much less central bank liquidity) but introduces intraday credit risk (payments are provisional until the end-of-day net settlement). RTGS eliminates intraday credit risk but requires more liquidity. Most payment systems use RTGS for large critical payments and DNS for retail batch payments.
Why would a company need to send a Fedwire (RTGS) payment instead of an ACH?
Fedwire (the U.S. RTGS system) is preferred when: immediate, same-day funds availability is critical (real estate closings, securities settlements, margin calls, M&A deal closings); the payment amount is very large (Fedwire handles individual transactions worth millions or billions without concern); payment irrevocability is required (unlike ACH, Fedwire cannot be reversed); or the recipient bank requires RTGS receipt for same-day credit. ACH is slower (1–2 business days for standard transactions) and allows returns/reversals, making it unsuitable for time-critical, high-value, or irrevocability-required payments.
How does intraday liquidity management relate to RTGS?
In RTGS systems, banks must fund each payment in real time from their central bank reserve accounts—they cannot rely on incoming payments to arrive before outgoing payments leave. Banks manage intraday liquidity by monitoring expected incoming and outgoing payment flows, timing large outgoing payments to coincide with expected inflows, using intraday credit facilities from the central bank (Fedwire daylight overdrafts, collateralized repo), and participating in tiered settlement arrangements. Basel III LCR (Liquidity Coverage Ratio) and NSFR (Net Stable Funding Ratio) requirements mandate that banks maintain sufficient liquidity to manage payment obligations even in stressed scenarios.
Related Terms
SEPA
Single Euro Payments Area enabling standardized electronic payments across 36 European countries.
SWIFT Code
Unique identifier (BIC) for financial institutions used in international wire transfers.
ISO 20022
Global financial messaging standard enabling richer, more structured payment data across institutions.
Batch Processing
Grouping payment transactions for processing together at scheduled intervals rather than individually in real time.
