# Supplier onboarding and bank-detail changes: approval controls for SMEs

> Control new suppliers and bank-detail changes with separate verification, restricted fields and a block on payment until the approved record is published.

Source: https://www.fyadvisers.com/blog/supplier-onboarding-bank-detail-change-workflow/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

Supplier onboarding should make a verified record easier to create. It should not make an unverified bank account easier to pay. Keep capture, independent verification and approval apart. A request from a familiar address is still a request.

Once the supplier exists, committing spend is the [purchase order](/blog/purchase-order-approval-workflow-singapore/) path. Accepting their bill is [invoice approval](/blog/invoice-approval-workflow-automation-singapore/). This page stops at the master record.

## Fields, and nothing you do not need

Collect what procurement and finance will actually use: legal name, the identifier you use to recognise the entity, country, authorised contacts, the terms you agreed, the documents those terms require, and payment details. Extra identity documents “just in case” are personal data you then have to protect and later justify keeping. The PDPC’s [Key Concepts guidelines](https://www.pdpc.gov.sg/-/media/Files/PDPC/PDF-Files/Advisory-Guidelines/AG-on-Key-Concepts/Advisory-Guidelines-on-Key-Concepts-in-the-PDPA-17-May-2022.pdf) (17 May 2022) describe both protection duties and a retention limitation: stop holding personal data, or remove the link to an identifiable person, when the purpose is over and retention is no longer necessary for a legal or business purpose. There is no single statutory number of days in that obligation.

Business contact information is not automatically outside the PDPA. The guidelines say the Data Protection Provisions generally do not apply to business contact information, and that this depends on purpose and context. A bank account, a personal mobile on a sole proprietor, or a passport scan is not “just a supplier form”.

## States

| State | What users may do |
|---|---|
| Pending | See the request. Cannot pay against it |
| Verification required | A named verifier works from an independent channel |
| Approved | The published record may be used by purchasing and payment |
| Suspended | No new orders or payments until a named role lifts it |
| Superseded | The previous bank values remain restricted history, not the payable account |

Restrict who can see bank fields. Log the old value, the new value, the actor and the time. A general “supplier edited” event is not enough.

## Bank changes

For a change to a payable account:

1. Open a change record. Do not edit the live account in place.
2. Contact the supplier using details already on the master file. Do not call only the number in the email that asked for the change.
3. A second person approves, where you have decided the risk warrants dual control. That split is a recommendation for payment fraud risk. It is not a statement that every Singapore SME has one prescribed statutory workflow.
4. Publish with a change reference. Push that reference to purchasing and to the accounting system. If one downstream system rejects the update, the change stays partially applied and visible. It does not show as finished.
5. Keep the previous account retrievable for a period finance agrees, in storage that payment runs do not read.

Microsoft’s [sequential approval](https://learn.microsoft.com/en-us/power-automate/set-up-sequential-approvals) pattern can express “verify, then approve”. It does not choose your verifier. If the approval step fails or times out, [error handling](https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/error-handling) should leave the record pending. A retry must not publish twice and must not fall back to the unverified value.

## Duplicates, mergers, dormant files

A second supplier with a slightly different spelling is a duplicate case, not a new payable account. Match on the identifier you trust, then on tax or registration numbers you are allowed to hold, then ask a person. Merging two records needs a survivor and a redirect from the old id, or purchase orders will point at a dead supplier.

Expired insurance or certification documents, if you collect them, move the supplier to verification required or suspended for new orders. They should not delete the history of invoices already posted. Dormant suppliers can be blocked from selection without being erased.

The acceptance tests are: an approver changes the account number after verification; a near-duplicate name; one downstream system rejects the approved update. Ask who may create, who may verify and who may approve, how the independent check is stored, and whether a pending account can appear on a payment screen. Also ask for a rollback you have witnessed: the previous account restored, with the failed change still in the history.

Illustrative scenario, not a client engagement: accounts receives a PDF asking for a new bank account. The workflow stores it as pending, alerts a verifier and does not publish the new number. Nobody pays the supplier from the PDF. The verifier uses the phone number already on the supplier record. Only the approved value is what the next payment run can select.

This is an operational design guide. It is not legal advice, and FYAdvisers is not a law firm. To map how a bank detail reaches a payment run today, use the contact form or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Who should be allowed to create, verify and approve a supplier?

Three different roles where the amount at risk justifies it. The person who keys the request should not be the only person who verifies the bank account. Dual control is a design choice for that risk, not a rule that every SME is legally required to adopt in one particular form.

### How should independent verification be evidenced?

Record the channel you used and that it was a channel you already held, such as a phone number on the existing master file or a known supplier contact. A phone number printed on the change request is not independent. Store the verifier’s name and the time, not a vague “called the supplier”.

### Can a pending bank change appear on a payment screen?

It should not. Payment runs read the published account only. The pending value lives on the change record until approval. After approval, downstream systems update with a change reference, and a failed update stays visible.

### What if the approver edits the account number after verification?

That edit invalidates the verification. The new value goes back to pending. The acceptance test is an approver who “corrects” a digit on the way through.
