Feature catalogue

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. Anyone may pay it without capturing it first.

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, in scope for the paying account 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.

Approve a destination

You approve a destination from the destination itself, because that is where the record lives.

  1. Open the external account you want to approve.
  2. Select Approve as beneficiary.
  3. Choose who may pay it.
  4. Select Save.

Choosing who may pay it is the whole decision:

Scope Who may pay it
Whole tenant Every account in the organisation
This operating entity only Accounts of the operating entity that captured it

Use Whole tenant for the revenue service. Use This operating entity only for a division’s own supplier, so another division’s clerk is never offered it.

Widening a beneficiary from one division to the whole organisation is a real decision, so it can be set to need a second pair of eyes.

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 you may pay.

The list shows only what the rule permits, so you are never offered a destination the system then refuses.

Revoking an approval

Select Revoke approval on the external account.

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.

Seeing the whole directory

Settings → Payments → Approved Beneficiaries lists every approved destination, who may pay it, who captured it, and what reference a payment to it carries.

The verbs are not on that page. Approve, re-scope, and revoke live on each external account, where the record is.

What your organisation configures