A trustee resigns. A long-serving finance officer retires. A signatory moves on to a new role. On paper, these are routine changes — the kind of thing that happens in every organisation, every year.
At the bank, they trigger something else entirely: a payment to an overseas partner, sitting mid-process, suddenly frozen while the mandate gets re-verified. No one told the programme team in Nairobi or Lagos why the transfer hasn't landed. No one budgeted for the delay. It just happens, quietly, and it happens more often than most finance teams expect.
A bigger problem than it looks
According to the Charity Finance Group's 2026 banking report, 53% of UK charities name mandate and signatory changes as their single biggest banking challenge — ahead of fraud, ahead of fees, ahead of almost everything else finance teams usually worry about.
That figure is worth sitting with. It means the most common banking problem in the charity sector isn't a security issue or a cost issue. It's a basic administrative one: proving, quickly and cleanly, who is currently allowed to move money on the organisation's behalf.
For domestic payments, that's an inconvenience. A delayed supplier invoice, an awkward phone call, a few days lost. For payments crossing a border, it's a different scale of problem.
Why overseas payments make it worse
Cross-border payments already carry more friction than domestic ones — correspondent banking delays, FX timing, and compliance checks that get re-triggered more easily than most finance teams realise. Layer a mandate change on top of that, and a payment that should take a day can take weeks.
There's a second layer most organisations don't discover until it's tested: HMRC's expectation that charities take "reasonable steps" to verify overseas grants and payments. This isn't a niche technicality — it applies to any charity sending funds to partners, suppliers, or programmes outside the UK. The problem is that most finance teams only learn what "reasonable steps" actually requires when they're asked to produce evidence of it, usually during an audit or a funder review, by which point it's too late to go back and reconstruct a clean record.
What "reasonable steps" actually means in practice
Stripped of legal language, auditors and HMRC tend to look for the same handful of things:
- A traceable record for each payment — not just that money left an account, but why, and tied to what.
- Clear verification of who the counterparty actually is, done once, properly, rather than re-checked informally each time someone new picks up the file.
- A reference or audit trail that survives staff turnover — so the record doesn't depend on one person's memory or one person's continued employment.
None of this is exotic. It's closer to good bookkeeping than compliance theatre. But it has to exist before it's needed, not assembled retrospectively when a funder or auditor asks for it.
Where this leaves finance teams
The honest answer is that most of this friction isn't caused by any one bank being difficult — it's structural. Mandate management, overseas verification, and audit-trail record-keeping all sit in slightly different places, and when a staffing change hits, they all need re-syncing at once. That's what causes the delay.
This is the specific gap NectPay was built to close. Every payout carries its own reference number from the moment it's initiated — visible on the dashboard, on the receipt, and in exported records — so the trail doesn't disappear when a signatory changes. Compliance verification happens once, at onboarding, rather than being re-triggered every time internal staffing shifts. Settlement runs through a UK FCA-authorised Electronic Money Institution, so the regulatory backbone is handled without the charity needing to manage a second banking relationship.
It won't stop trustees from moving on or finance officers from changing roles — that's normal organisational life. What it changes is what happens next: instead of a payment stalling while a mandate gets rebuilt from scratch, the record already exists, independent of any one person's sign-off.
If your organisation sends regular payments to partners, suppliers, or programmes in Nigeria, Kenya, or Ghana, and a staffing or signatory change has ever slowed a payment down, it's worth asking whether the record-keeping is doing its job — or whether it's quietly relying on one person remembering the details.
See who NectPay serves