RM vs RMS: What Is the Difference?
The terms RM and RMS appear throughout South African collections documentation, bank specifications and industry FAQs, and they are often used as if they mean the same thing. Strictly speaking they do not: RM refers to the mandate itself, while RMS refers to the industry service that registers it.
Understanding the distinction helps when you read bank documentation, interpret statuses, or discuss integration options with your sponsoring bank or payment provider.
What is a registered mandate (RM)?
A registered mandate (RM) is the mandate record itself — the agreement between you and your payer that has been registered at the payer's bank. It contains the mandate details you captured: the payer's account, the collection amount or maximum amount, the frequency and the collection date.
Once registered, the RM exists as a record at the payer's bank. Collections you submit reference that record, and the mandate moves through a lifecycle of statuses such as registered, amended, suspended or cancelled. See The Registered Mandate Lifecycle Explained for the full picture.
What is the Registered Mandate Service (RMS)?
The Registered Mandate Service (RMS) is the industry service — part of South Africa's ISO 20022 DebiCheck-era collections system — that carries mandate registrations between banks. It is the rail, not the record.
RMS handles non-authenticated mandates: the mandate details are registered at the payer's bank without the payer electronically approving them. The payer's bank notifies the payer of the registration, and the payer can query or dispute it, but no authentication step takes place. This is what distinguishes RMS from DebiCheck, where the payer must actively authenticate the mandate.
RMS covers the full set of mandate operations:
- Initiation (registering a new mandate)
- Amendments to an existing registered mandate
- Suspension of a mandate
- Cancellation of a mandate
All of these are communicated as ISO 20022 messages between your sponsoring bank and the payer's bank, over either an API or a host-to-host file integration. See API vs Host-to-Host Integration.
Why are RM and RMS used interchangeably?
In practice, most people say "RM" or "registered mandate" to mean the whole capability — registering mandates and collecting against them — and "RMS" when quoting bank or industry documentation. Because every registered mandate exists only through the Registered Mandate Service, the two terms point at the same process from different angles:
| Term | Refers to | Example usage |
|---|---|---|
| RM | The mandate record registered at the payer's bank | "The RM was cancelled by the payer's bank." |
| RMS | The industry service that registers and manages mandates | "We submit RMS registrations via host-to-host files." |
You will see both in bank specifications — for example, Absa publishes a Registered Mandate host-to-host file specification and a Registered Mandate API. Both describe the same underlying RMS capability.
Does the distinction matter operationally?
Rarely. What matters operationally is:
- Whether the mandate registered successfully at the payer's bank.
- What status the mandate currently holds (registered, amended, suspended, cancelled or rejected).
- Whether your collections reference a valid, active registered mandate.
If a bank or provider tells you "the RM was rejected", they mean the mandate record; if they say "RMS is unavailable", they mean the service. Kwik supports registered mandate collections through RMS, so you can register and manage mandates without needing to work with the bank messaging directly.
Related topics
What Is a Registered Mandate?
Learn what a registered mandate is, how registering debit order mandates with the payer's bank reduces disputes, and how it differs from DebiCheck.
RM vs DebiCheck vs EFT
Compare registered mandates, DebiCheck and plain EFT debit orders on authentication, dispute protection, cost and use cases to pick the right collection type.