Who Can Move Your Money, and Who Can Stop Them?

Map who can initiate, approve, change and stop payments, including automated access, named owners and safe testing.
Payment authority map: initiate, approve, change and stop. For each, record the identity, permission, owner, evidence and gap.

Hypothetical scenario: A treasury analyst prepares a supplier payment. A second person approves it, just as policy requires. But the account used by the accounting integration can change the supplier’s bank details, and an administrator can raise the payment limit. When someone spots a problem, nobody is certain who can stop the transfer before it leaves.

The approval policy looks sound. The actual authority is harder to explain.

For CFOs and treasury leaders, the useful question is not simply who signs off. It is who can initiate, approve, change and stop a transaction across the whole payment path. A payment authority map makes those answers visible.

Map what the systems allow

Start with one important payment flow: payroll, supplier payments or customer disbursements. Trace it from the source record through accounting software, integrations, banking portals and any payment provider. Include both the normal route and the exception process used when a deadline is close.

List every human and automated identity that can affect that flow. Employees are only part of the picture. Include shared accounts, service accounts, third-party support access and integrations that submit files or call payment APIs. Give each identity a named business owner, even when no person signs in with it.

Compare the written policy with current permissions in each system. Ask for an access export or a supervised screen review, not a verbal assurance. Record the date and who checked it. A role called “read only” in one application does not establish what the same person can do elsewhere.

The FFIEC’s 2021 authentication guidance addresses employees, third parties and system-to-system access. Its examples include transaction limits, dual control and oversight of privileged accounts. These are useful reference points for the review, not proof that any particular company’s controls are sufficient.

Build a four-part payment authority map

For each payment flow, use four rows. Record the relevant identities, effective permissions, business owner, evidence and any gap.

  • Initiate: Who can create a payment, upload a batch or trigger an automated instruction? Note the account, payment type, amount limits and any route that bypasses the normal queue.
  • Approve: Who can release the payment? Identify whether a different person must approve, what information they see and whether the system actually enforces separation.
  • Change: Who can edit recipients, bank details, approval rules or limits? Include administrators who can grant themselves or someone else these powers. Check whether a material change invalidates an earlier approval.
  • Stop: Who can pause a batch, disable an integration or contact the provider’s urgent support team? Record the cutoff, authorized contact, backup and route for escalation.

Read the four rows together. Two approvers do not provide meaningful separation if one person can change the destination after approval. Equally, removing access without understanding an integration can interrupt legitimate payments.

NIST SP 800-53 Rev. 5 distinguishes separation of duties in AC-5 from least privilege in AC-6. The practical leadership task is to make both visible: separate incompatible responsibilities and limit each identity to the access its work requires.

Test the stop without disrupting the business

A contact list is not evidence that a payment can be stopped. Arrange a controlled exercise with treasury, the process owner and the relevant technology or banking contact. Agree on the scope, safety conditions and recovery steps before testing anything.

Use a tabletop walkthrough or a provider-supported test environment first. Do not interrupt live payroll or attempt an unapproved production transfer. Walk through who notices the problem, who has authority to act, how the backup is reached and which confirmation proves that the instruction was paused.

Distinguish stopping an instruction that has not been released from requesting a recall after release. The available options and deadlines depend on the provider and payment method. Have the owner verify them directly rather than promise that money can always be recovered.

Give the next step one owner

This week, ask the treasury lead to map one critical payment flow with the technology owner and return a reviewed version within five business days. Require one prioritized gap, a named decision-maker and a date for the next safe test.

For the wider leadership discussion, use our five questions about financial authority and resilience. Where responsibility crosses teams or suppliers, independent technology leadership can help turn the map into clear decisions and follow-through.

Search Leadership Insights

Type a keyword or question to scan our library of CEO-level articles and guides so you can movefaster on your next technology or security decision.

Request Personalized Insights

Share with us the decision, risk, or growth challenge you are facing, and we will use it to shape upcoming articles and, where possible, point you to existing resources that speak directly to your situation.