Approved beneficiaries
Normally you may only pay a destination that belongs to the account’s owner. That rule stops a payment going to a stranger’s bank account by mistake.
Some destinations are not strangers. The revenue service, a municipality, an insurer — every account in the organisation pays them, and nobody should have to capture their bank details to do it.
An approved beneficiary is a destination your organisation has vouched for. It belongs to no customer and no operating entity. Any account may pay it.
Who a payment may go to
Every outbound payment is checked against one rule, on the server, on every path.
| Destination | May you pay it |
|---|---|
| An account belonging to the paying account’s owner | Yes |
| An approved beneficiary | Yes |
| Anything else | No |
If a destination fails the rule, the payment is refused when you capture it, and the message tells you both ways to fix it: capture the destination against the owner, or have it approved.
Add an approved beneficiary
You add a beneficiary on the settings page, not on a customer’s record.
- Select Settings, then Payments, then Approved Beneficiaries.
- Select Add beneficiary.
- Enter a description, such as “City of Cape Town”.
- Choose the bank and enter the account number.
- Select Add.
Adding a beneficiary approves it in the same step. You may also set the payment references and the notification contacts at the same time, or leave them for later.
A bank account appears in the directory once. If the account is already there, the addition is refused and the message names the entry that holds it.
If your organisation needs a second pair of eyes on additions, the entry shows as awaiting authorisation and is not payable until someone else approves it.
Change an entry
Open the row’s menu on the same page.
| Action | What it does |
|---|---|
| Change description | Renames the entry |
| Change account number | Moves the entry to a corrected number. It stays approved |
| Payment references | Sets what a payment to this beneficiary is called, on both sides |
| Notification contacts | Sets where proof of payment goes when a payment settles |
Paying an approved beneficiary
Nothing special. Open the account, select Pay Out Balance, and the destination list shows two labelled groups: the owner’s own accounts first, then the approved beneficiaries.
The list shows only what the rule permits, so you are never offered a destination the system then refuses.
Revoking and approving again
Select Revoke from the row’s menu. The entry stays in the list and shows as Revoked.
Revoking does not cancel anything already agreed. What happens next depends on how far each payment had got.
stateDiagram-v2
[*] --> Captured
Captured --> Approved: approved while the beneficiary stood
Approved --> Sent
Captured --> Refused: beneficiary revoked first
Refused --> [*]
Sent --> [*]
| The payment was | What revoking does |
|---|---|
| Already approved | Nothing — it goes out, and the trail shows it was approved while the designation stood |
| Captured but not approved | It is refused at approval, naming the revocation |
So a mistaken approval is closed off immediately for everything still in your hands, and nothing already committed is quietly reversed.
To restore a revoked entry, select Approve again from its menu. That approves the same entry. It never creates a second one.
Seeing the whole directory
The page lists every entry, approved or revoked, with its account, currency and the reference a payment to it carries. An entry that has been closed or transferred shows that status and offers no actions.
The external account’s own screen no longer approves or revokes. It shows whether the account is an approved beneficiary, and still sets references and contacts.
Seeing who you can pay from the client portal
If you use the client portal, select Payments, then Beneficiaries. The list sits beside Payments and Schedules.
Each row shows the name, the masked account number, the date you last paid it, and its source. The date is blank if you have never paid that beneficiary.
| Source | What it means |
|---|---|
| Yours | Your organisation added this beneficiary. |
| Bank approved | The bank approved this destination for every customer. |
The list holds everyone your organisation may pay: the beneficiaries you added, see adding your beneficiaries, and the ones the bank approved.
You cannot remove a bank-approved entry from this list. Nothing on this list can be removed.
For example, a list holding “Kapstadt Logistics” (added by the client) and
“Revenue Service” (approved by the bank) shows Yours on the first row and
Bank approved on the second. The names come from the test fixtures in
client-beneficiaries-screen.test.tsx.
What your organisation configures
- Which destinations are approved. This is a running list, maintained by whoever is trusted to vouch for a destination.
- Whether adding, approving and revoking need a second pair of eyes.
- What reference a payment to each beneficiary must carry — see payment references. The reference rules follow the remittance-information line in the standards register.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.