Replace account signers without confusing an approved request with authority already in force. Track the bank mandate, signing rules and related access changes to separate completion gates.
A finance director leaves on Friday. Their replacement has internal approval to sign, but the bank has not finished the mandate change. A payment is due that afternoon. The problem is not simply a missing name on a form: the team must establish who can act now, under which signing rules, and what evidence will show the change is complete.
A bank signatory change workflow controls additions, removals and changes to the people recognized under a business account mandate. This guide is for finance and treasury teams coordinating ordinary operating accounts. It supplies a reusable change record and evidence gates, not a bank form or a legal resolution template. Disputed authority, deceased signers, insolvency and restricted accounts need the bank’s appropriate specialist route.
Separate three kinds of authority
Do not use “approver” as a single field. Track these independently:
- Internal authority: who the organization has approved to perform a role, subject to its governing documents and delegation rules.
- Bank-recognized mandate: the signatories, account scope and signing arrangements the bank has accepted.
- Service access: the portal permissions, payment entitlements, cards and other facilities actually available to a person.
One does not prove the others. NatWest’s signatory guidance, for example, says that adding a mandate signatory does not automatically give them online banking access; that requires a separate application after its mandate process. Apply your own bank’s instructions rather than copying another institution’s sequence.
The workflow below is a recommended company control. Applicable law, the organization’s authority documents, account agreement and bank instructions determine the actual requirements. There is no universal two-signature rule, processing time or document checklist in this guide.
Capture the intended change before collecting signatures
Open a case when a departure, appointment, role change or revised signing arrangement affects bank authority. Name a finance owner and a reviewer able to compare the requested change with the approved scope. Bring in the company secretary or legal adviser where corporate authority needs confirmation.
Use one row for each affected account and signing arrangement. “All bank accounts” is not enough unless the bank and reviewer can identify that population. Include dormant accounts and currency accounts where they are genuinely in scope; do not assume a single request covers every relationship.
| Field | What to record |
|---|---|
| Case and scope | Case ID, legal entity, bank, masked account reference, currency, account purpose and bank contact source. |
| Current authority | Evidence date, current signatories, signing groups/combinations and any applicable account or amount restrictions. |
| Requested authority | Names to add/remove, roles, proposed signing rules, affected services and intended effective date. |
| Authority to request | Internal approval reference, bank-required authorizers, applicable mandate/resolution and required signing method. |
| Implementation evidence | Submitted version, channel, submission date, bank case reference, outstanding document requests and next follow-up owner/date. |
| Verified outcome | Bank-confirmed effective date and resulting arrangement, reviewer comparison, related access-case references and remaining exceptions. |
Keep identity documents, signatures and full account details in approved restricted storage. A coordination queue can contain masked identifiers and controlled references instead of copies of sensitive documents accessible to everyone.
Use evidence gates, not a single completed checkbox
Use a state path such as Requested → Scope verified → Internally authorized → Bank packet ready → Submitted → Bank confirmed → Dependencies verified → Closed. A returned packet moves back to preparation; a materially changed request moves back to authorization. Submission alone never advances a case to bank confirmed.
| Stage and owner | Evidence and control | Block and resume condition |
|---|---|---|
| Scope verified — treasury | Compare current bank evidence with the requested additions, removals and signing rules for each account. | Unknown current mandate: obtain bank clarification before defining the final packet. |
| Internally authorized — designated authority owner | Confirm the decision follows the organization’s authority framework; retain the approved before/after scope. | Missing or disputed authority: specialist review and valid authorization, not requester self-approval. |
| Bank packet ready — bank relationship owner | Check the current bank route, authorized submitters, forms, identification and signature method. | Wrong form or unavailable authorizer: obtain the bank-supported route and complete its requirements. |
| Submitted — authorized submitter | Retain the exact submitted version, bank reference and outstanding items. Set the next follow-up date. | Rejected or incomplete: correct the identified issue; reapprove material scope changes before resubmission. |
| Bank confirmed — independent reviewer | Compare the bank’s accepted signatories and rules with the approved request, including account scope and effective timing. | Only receipt acknowledged, or mismatch: case stays open until implementation evidence resolves the uncertainty. |
| Dependencies verified — service owners | Verify separately authorized portal, card and payment-service changes against actual resulting access. | Old entitlement remains or new access missing: retain a linked exception with owner and due date. |
| Closed — finance control owner | Accept the final mandate evidence and dependency outcomes; update the internal authority register. | Unresolved material authority difference: do not close as successful. |
The distinction between receipt and implementation is observable in Bank of Ireland’s mandate-change process: it describes an initial receipt email, authorization and signature steps, then a further email confirming the new mandate is in place after checks. It also distinguishes basic online signing arrangements from complex arrangements that require a different route. That is an institution-specific example, not a promise about your bank’s process.
Plan the transition before the outgoing signer leaves
Check both removal and addition timing
Ask the bank how the removal and addition will take effect and whether the requested signing combination will remain usable during the transition. Document its answer. Do not retain a departed person’s authority merely to avoid operational inconvenience; escalate timing and interim arrangements through authorized company and bank channels.
Check upcoming payment deadlines against the authority actually in force. An internal appointment, a signed packet or a desired effective date does not by itself show that the bank recognizes the replacement signer. Never share the outgoing person’s login, token or signature to bridge the gap.
Treat service changes as linked work, not implied work
Assign separate owners for portal rights, cards and relevant payment services. The bank portal access review checklist explains how to compare actual entitlements with current roles. Link the resulting access evidence to the mandate case, but do not mistake a portal screenshot for proof that the bank mandate changed.
Check the bank’s required execution method before circulating documents. CommBank’s business authority instructions call for the current form and specify pen signatures rather than digital or cropped signatures for that process. Other banks use different channels. A method accepted for an internal approval is not automatically acceptable for a bank instruction.
Recover exceptions without inventing signing authority
- Required authorizer unavailable: the bank relationship owner obtains the bank’s alternative or specialist instructions. Keep the case blocked until valid authority and documents exist; another employee cannot simply substitute.
- Only some accounts updated: mark each account’s actual outcome. Ask the bank to resolve the omitted scope; do not mark the entire case effective from one confirmation.
- Accepted rules differ from the request: retain both versions, escalate to the authority owner and bank, and determine a valid corrective instruction. Internal policy approval does not rewrite the bank’s current arrangement.
- Unexpected activity or suspected misuse: contact the bank through established trusted channels and invoke the organization’s incident process. A routine mandate queue is not an emergency response channel.
- Urgent payment during the gap: establish whether an already valid signing combination can authorize it under company policy and bank rules. If not, escalate the obligation and timing; do not label an unauthorized workaround an exception approval.
Worked example: the payment deadline arrives first
Illustrative scenario: a service company owes a supplier $18,000. Its current arrangement requires two signers from an approved group. One signer is leaving, and a replacement has internal approval, but treasury has only the bank’s acknowledgement of the submitted amendment.
The reviewer keeps the amendment at Submitted. Treasury asks the bank to confirm the effective mandate and checks whether a valid existing combination remains available. If that combination exists and the payment is authorized under both company and bank rules, the payment follows the normal release process. Otherwise, the finance owner escalates the due obligation and arranges a legitimate resolution rather than using the replacement’s unconfirmed authority.
Later, the bank confirms the replacement and removal for two accounts but not a third currency account. The first two rows can be verified; the third remains open with the bank relationship owner. The payment’s status is reconciled separately before anyone considers reissuing it.
A mandate change alone is not a payment or an accounting entry. Accounting continues to record actual authorized transactions and investigate differences under the applicable accounting policy. Changing the signer does not settle the $18,000 liability, and a delay does not justify removing it from the records.
Where Workhint fits
Workhint’s Workflow Engine supports defining request steps, routing approvals to named roles and requiring details, files or notes before work progresses. Those capabilities can support the surrounding mandate-change coordination: a scoped request, an internal review and a requirement for bank confirmation before the case advances.
The Finance Leaders solution describes finance review, payment approval and connected payment-related records. The relevant connection here is organizing finance decisions and handoffs—not evidence that Workhint submits mandate forms, changes bank signers, verifies identity for the bank or automatically synchronizes bank permissions. Keep bank execution and the authoritative mandate evidence with the bank’s supported process.
Frequently asked questions
Is a bank signatory the same as an online banking user?
Do not assume so. Check the bank’s definitions and actual arrangements. A mandate amendment and a portal-access change may be separate processes with separate completion evidence.
When is the change complete?
When the bank-supported evidence confirms the intended authority and account scope are effective, the reviewer has resolved discrepancies, and required linked service changes have been verified. A submission reference is evidence of a request, not necessarily implementation.
Must every business use two signers?
No universal rule is prescribed here. The bank’s available arrangements, accepted mandate, company authority framework and applicable requirements determine the permitted combination.
What should finance retain?
Retain the authorized request, before/after scope, exact submitted packet reference, bank confirmation, reviewer decision and linked access outcomes under your approved retention and access policies. Keep unresolved accounts and exceptions visible rather than hiding them in a completed case.

Leave a Reply