Independent Singapore VCC guidance

By Variable Capital Companies Actchecklist

Direct answer

Refresh the VCC bank mandate whenever a director, manager, authorised signatory, payment approver or service-provider user changes. Freeze new authority until the board record, current VCC particulars, bank forms, online roles and payment matrix agree. Remove obsolete access, activate the approved replacement through maker-checker control, and test a low-risk instruction before normal payments resume. Keep one dated cutover file showing exactly who could act before and after the change.

At a glance

  • Treat the mandate as a complete authority system, not a signature card alone.
  • Match every bank user to an approved role, account and payment limit.
  • Remove obsolete access before relying on a replacement control.
  • Test the new arrangement without creating an unnecessary live transfer.
  • Close the change only when bank evidence and internal records agree.

Who this is for

  • Standalone and umbrella VCCs changing directors, managers, signatories, bank users or outsourced payment roles.

Important exclusions

  • Instructions to bypass bank onboarding, legal advice on disputed authority, or permission to make a real payment solely for testing.

Open one controlled authority change

Start a single change record when the event becomes known. Capture the affected VCC, sub-funds, bank accounts, currencies, payment channels, cards, tokens, file-transfer routes and emergency authorities. Record the effective time of the organisational change separately from the bank cutover time. ACRA identifies directors and the permissible fund manager as formal VCC roles, while bank authority is created through separate contractual and system records. One change does not update the other automatically.

Sources: Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority · DBS Bank
  • Identify every account, payment channel, token, card, file interface and bank portal role affected by the change.
  • Preserve the board resolution, resignation or appointment evidence and the accepted regulatory filing where relevant.
  • List current makers, checkers, signatories, viewers, administrators and emergency users directly from bank evidence.
  • Place a controlled hold on unsafe authority while preserving payroll, tax and investor-payment escalation routes.
  • Assign one owner to reconcile the bank response with internal approvals and the administrator payment matrix.
Sources: Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority · DBS Bank

Reconcile five authority records

A reliable cutover compares five records: the VCC decision, current filed particulars, the bank mandate, online banking roles and the operating payment matrix. Differences are not harmless administration. A departed person may remain able to approve online, or a newly appointed director may appear in company records without bank authority. Record each mismatch, its risk, temporary containment and accountable resolver. Do not let a spreadsheet become the source of authority when the bank or governing approval says something different.

Sources: Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority · DBS Bank
Authority reconciliation before activation
RecordQuestion to proveEvidence to retainFailure response
VCC approvalWho was approved for which capacity and scope?Signed resolution or delegated approvalPause activation and clarify the decision
Filed particularsDo formal officer and manager records reflect the event?Accepted filing or current official extractRoute the discrepancy to the company secretary
Bank mandateWhich persons may bind or instruct the account?Bank-accepted mandate and account listRestrict the affected account authority
Online rolesWho can create, approve, administer or view?Bank-generated user and entitlement reportDisable obsolete or unexplained access
Payment matrixDo operational limits match approved bank authority?Versioned process matrix and provider acknowledgementBlock release until records agree
Sources: Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority · DBS Bank

Rebuild maker-checker without hidden gaps

Do not replace one named person with another while leaving the wider workflow unchanged. Reassess who prepares instructions, verifies supporting documents, releases payments, administers users and reviews daily activity. A user who can both maintain beneficiaries and approve payments may defeat the intended separation even if two names appear on the mandate. For an umbrella VCC, scope authority to the correct account and paying pool so a shared provider role does not conceal sub-fund ownership.

Sources: Accounting and Corporate Regulatory Authority · DBS Bank · Accounting and Corporate Regulatory Authority
  1. Only a viewer changesConfirm no approval or administration entitlement is bundled with the viewing role before completing a limited update.
  2. A maker or checker changesReperform separation-of-duties testing and confirm the remaining approval path can operate without self-approval.
  3. An administrator changesReview user creation, token issuance, beneficiary maintenance and audit-log access before granting the powerful role.
  4. A sole approver leaves suddenlyUse only a documented contingency route and obtain replacement authority before normal payment processing resumes.
Sources: DBS Bank · Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority

Cut over access in a controlled sequence

Sequence removal and activation so the VCC is not left with both excessive authority and no workable payment route. Confirm the bank has accepted the mandate, then disable obsolete online roles and recover or invalidate physical credentials. Activate replacement users only after their identity, scope and device delivery are independently confirmed. ACRA states that changes to officers and managers also require formal updates, so the company-secretarial workstream and banking workstream should be tracked together even though they finish through different systems.

Sources: Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority · DBS Bank
  1. ContainRestrict obsolete or uncertain authority and communicate a temporary escalation route to affected operators.
  2. ApproveComplete the VCC decision, formal filing review, bank forms and precise entitlement specification.
  3. RemoveObtain bank evidence that departed users, tokens, cards and delegated permissions are no longer active.
  4. ActivateIssue replacement access through independently verified delivery and record the actual activation time.
  5. ProveRun a non-monetary or low-risk workflow test and reconcile the bank audit trail to the approved design.
Sources: Accounting and Corporate Regulatory Authority · DBS Bank · Accounting and Corporate Regulatory Authority

Test and close the mandate change

A test should prove role boundaries without creating a payment merely for evidence. Use a saved draft, cancelled instruction, bank-provided test environment or another safe method where available. Confirm the maker cannot approve, the checker sees the right account and limits, obsolete users cannot authenticate, alerts reach the approved contacts, and the audit log identifies each action. After the first genuine payment made for a real purpose, perform a heightened review against the invoice, paying pool, beneficiary and approval trail.

Sources: DBS Bank · Accounting and Corporate Regulatory Authority · Accounting and Corporate Regulatory Authority

Frequently asked questions

Does an ACRA officer update also change the bank mandate?

No. The formal VCC update and the bank mandate are separate records and processes. Track both in the same change file, but obtain independent evidence that each has been accepted before treating the new authority as fully effective.

Should access be removed before a replacement user is ready?

Unsafe or obsolete access should be contained promptly. At the same time, use only a documented contingency route for necessary payments. Do not preserve excessive authority simply to avoid planning an interim control.

Can a fund administrator remain a bank maker?

That depends on the approved operating model and bank setup. The key control is whether preparation, verification, approval and user administration remain appropriately separated and traceable for the relevant VCC or sub-fund account.

How can the VCC test without sending money?

Use bank-supported test functions, a draft that is cancelled before release, entitlement reports and audit-log review where available. A real payment should occur only for a genuine authorised purpose, not to manufacture validation evidence.

What evidence closes a bank mandate refresh?

Retain the decision, affected-account inventory, filing evidence where applicable, bank acceptance, old and new entitlement reports, credential removal confirmation, updated payment matrix, test record and heightened review of the first genuine instruction.

Official sources and further reading

Discuss a Singapore VCC structure

For help coordinating a Singapore VCC setup or corporate administration, contact Raffles Corporate Services.

General information only. This article is not legal, tax, regulatory or investment advice and does not imply affiliation with or endorsement by ACRA, MAS or IRAS.

An independent website by Raffles Corporate Services Pte Ltd. Not affiliated with or endorsed by ACRA, MAS or IRAS. General information only.