AuditingBusiness

Supplier Master Data and Payment Controls: 10 Ways to Reduce Vendor Fraud Risk

A practical guide for US and Canadian controllers to protect supplier onboarding, bank-detail changes and payment runs with independent verification, SAP dual control, segregation of duties and audit-ready evidence.

A supplier’s bank-account change can look like routine housekeeping: a new remittance form, a revised invoice footer or a short email from a familiar contact. But if the request is fraudulent—or if a legitimate request is entered incorrectly—the next payment may go to the wrong account. Once a wire or electronic payment has been released, recovery can be difficult.

For financial controllers, supplier master data is therefore part of the payment control environment, not merely an accounts-payable administration task. The objective is to make every new supplier and every sensitive change independently verifiable, authorized, traceable and reflected correctly in the payment process. The same principles apply whether the organization pays through ACH in the United States, EFT in Canada, wires, checks or cross-border transfers.

Why supplier changes deserve a separate control

Business email compromise (BEC) can involve compromised legitimate email accounts, impersonation or social engineering to redirect a payment. The FBI’s Internet Crime Complaint Center specifically recommends using a secondary channel or two-factor authentication to verify requests to change account information. Its BEC guidance also advises organizations to contact their financial institution quickly if a fraudulent transfer is discovered.

The Government of Canada’s Competition Bureau describes scams in which a purported supplier requests new banking details and warns businesses to verify supplier identity and use clear procedures for verification, payment and invoice management. Its guidance on common scams targeting Canadian businesses is useful for training AP teams, purchasing staff and budget owners.

1. Establish a controlled supplier onboarding process

Require a standard onboarding package before a supplier becomes eligible for payment. Depending on the organization and jurisdiction, that may include legal name, address, tax and registration information, business purpose, approved purchasing contact, payment terms, remittance contact and bank details. Collect only the information needed for the relationship and store sensitive information in approved systems rather than shared mailboxes or uncontrolled spreadsheets.

Validate the supplier’s business identity independently using trusted records and contact details obtained outside the onboarding request. A tax form, invoice or professional-looking website can be part of the evidence, but none should be treated as conclusive proof by itself. Define enhanced review for high-value, one-time, overseas or otherwise higher-risk suppliers.

2. Verify bank-account changes through a known channel

Never rely solely on the email, phone number, attachment or link supplied in a bank-change request. Contact the supplier using a phone number or other channel already held in the approved supplier record or independently obtained from a trusted source. Ask an authorized supplier contact to confirm the change and record who confirmed it, when, how and which account details were validated.

For higher-risk changes, require a second independent verification step, such as confirmation by a separately established supplier contact. A reply to the original email thread is not independent verification if that mailbox may be compromised. Do not use a callback number included in the change request until it has been independently validated.

3. Separate request, approval and master-data maintenance

The person requesting a supplier or bank-detail change should not be the sole approver and should not be able to implement and release the change without independent review. Separate the duties of procurement, supplier master-data maintenance, invoice processing and payment release wherever practical.

Where staffing is limited, use compensating controls: documented review by a controller or manager, restricted access to the master-data function, and a recurring report of changes reviewed by someone who did not make them. A policy that says “two people are involved” is not enough; the evidence should show which person performed each step.

4. Put sensitive changes behind dual control and a payment hold

Identify fields that could redirect funds or change the party receiving payment. These commonly include bank account and routing information, beneficiary name, alternative payee, payment method and remittance details. Determine which fields are available and configurable in your ERP and master-data governance process.

SAP S/4HANA Cloud Public Edition documentation for release 2608 describes the Confirm Supplier List app. When fields have been configured as sensitive for dual control, a second authorized user can confirm or reject the change. SAP notes that a relevant supplier account is blocked for the payment run after a sensitive-field change and remains blocked if the second user has not confirmed it. This behavior depends on the system configuration and selected fields; controllers should verify it in their own release and process design.

For SAP S/4HANA on-premise and private-edition environments, SAP’s 2025 FPS01 payment-block documentation explains how a vendor payment block can be applied at company-code level. Confirm how your configuration treats automatic payment runs, manual payments and alternative payees; do not assume one block setting covers every payment route.

5. Use a documented change request with evidence

Capture the old and new values, reason for change, supplier identity, requestor, verification method, verifier, approver, effective date and supporting documents. Keep bank details masked in general workflow notifications and reports wherever possible. Restrict access to full account information to staff who need it to perform their role.

Make the process reject incomplete requests rather than allowing AP staff to fill gaps from an email conversation. If the change is urgent, use an approved expedited route with the same independent verification and approval requirements—not an informal override.

6. Detect duplicates, dormant suppliers and suspicious patterns

Run preventive and detective checks for duplicate or near-duplicate suppliers using combinations of legal name, address, tax identifier, phone number, email domain and bank-account identifiers. Flag cases where multiple unrelated suppliers share the same bank account, where a new supplier resembles a blocked supplier, or where a dormant supplier suddenly becomes active. Treat matches as investigation leads, not automatic proof of fraud: legitimate groups, factoring arrangements and shared service providers can create valid exceptions.

Review one-time suppliers, employee/vendor overlaps, alternative payees, unusual payment terms and changes to payment methods. Establish an owner and resolution deadline for every exception. Do not let a duplicate alert become a box-ticking exercise that is routinely overridden without explanation.

7. Match invoices to approved commercial activity

Supplier master controls do not replace invoice controls. Match invoices to approved purchase orders, contracts and evidence of receipt or service completion where applicable. Validate invoice number, amount, currency, tax treatment, payment terms and duplicate-invoice indicators. Route non-PO invoices through a defined approval process with budget-owner confirmation.

Canadian Competition Bureau guidance notes that fraudulent invoices can enter vendor lists and become more likely to be paid if the first questionable payment is not challenged. Train AP staff to question unfamiliar suppliers, unexpected changes in contact or banking details, pressure to pay immediately, and invoices that cannot be linked to a real order or service.

8. Review payment proposals and release files independently

Before payment release, review new or changed beneficiaries, unusual amounts, urgent manual payments, duplicate amounts, changed payment methods and payments outside normal patterns. For a payment run, the reviewer should have access to a report of recent supplier master changes and should confirm that changes affecting the run have completed the required verification and approval.

Separate payment-file creation from bank-portal approval where feasible. Restrict who can edit payment files, change beneficiary details, upload files and release funds. Reconcile the bank confirmation to the approved payment proposal and investigate rejected, returned or redirected payments promptly.

9. Monitor changes and payments after implementation

Generate a recurring report of supplier additions and changes, including bank details, alternative payees, payment methods, addresses and contact information. Review the report for changes made by privileged users, changes outside business hours, repeated reversals, emergency access and unusual concentration of changes before payment runs.

For higher-risk suppliers or changes, consider heightened monitoring of the first payment after the change. Confirm receipt through the established supplier contact where appropriate, and investigate returned payments or requests to resend funds to a different account. Set thresholds and monitoring frequency according to transaction volume, payment risk and the organization’s control framework.

10. Prepare an incident response before a payment goes wrong

Maintain a response playbook with named contacts in treasury, AP, IT security, legal, internal audit, senior finance and the banking relationship team. If a fraudulent payment is suspected, contact the originating bank immediately and request a recall or other available recovery action. Preserve emails, headers, call notes, approval logs, payment files, bank confirmations and system change records. Notify law enforcement and the relevant reporting channel according to the organization’s location and circumstances.

The FBI IC3 advises victims to contact their financial institution as soon as fraud is recognized and to file a complaint with IC3. In Canada, the Government of Canada directs businesses and individuals to report scams to the Canadian Anti-Fraud Centre reporting service. Follow internal incident and legal protocols as well; a report to an external agency does not replace the need to contain access, notify affected parties where required or assess financial-statement implications.

Controller’s supplier-payment control checklist

Control area Evidence to retain
Supplier onboarding Approved onboarding record and independent identity validation
Bank-detail changes Callback or secondary-channel confirmation using trusted contact details
Segregation of duties Request, approval and implementation logs showing different authorized users
Dual control/payment hold ERP workflow approval and evidence that payment block was released by an authorized reviewer
Duplicate and exception review Duplicate-supplier report, investigation notes and approved resolutions
Invoice authorization PO/contract, receipt or service evidence, invoice match and business approval
Payment release Reviewed payment proposal, bank approval and payment confirmation
Ongoing monitoring Supplier-change report, access review and first-payment or exception follow-up

Conclusion

Supplier payment security is strongest when procurement, accounts payable, master data, treasury and IT operate from one controlled process. Independent verification, dual control, payment holds, disciplined invoice matching and timely monitoring make it harder for a fraudulent or erroneous change to move unnoticed from an email into a released payment. For the controller, the key test is simple: can the organization demonstrate who requested the change, how it was independently verified, who approved it, when it became effective and which payments were affected?

Informational only: this article describes general finance and control practices. It is not legal, cybersecurity, banking or accounting advice. Confirm system functionality against your SAP release and configuration, and tailor procedures to applicable laws, payment-network rules, bank agreements and company policy.

Sources and further reading

Shares: