How to Set Up a Business Bank Account in Singapore as a Foreigner

You're not "opening a bank account" - you're building a reliable get-paid rail in Singapore#

Treat this as an operations system - compliance, receiving rails, and reconciliation, not a one-time application form. It's part of your money ops stack. The real win is predictable cashflow: clients can pay you cleanly, you can explain every inflow, and you avoid unnecessary compliance back-and-forth.

When you operate across borders, your main risk is friction, not "eligibility." Banks in Singapore must run due diligence on customers and beneficial owners, and that shows up as KYC, KYB, and AML checks.

KYC (Know Your Customer) verifies identity. KYB (Know Your Business) verifies the business itself. AML (anti-money laundering) refers to laws, rules, and procedures designed to stop illicit funds from being disguised as legitimate income. That should not scare you. It should shape how you prepare.

Step 1: Define the "get-paid rail" you actually need (before you apply)#

Start by separating labels from capabilities. Many people ask for "a Singapore bank account" when they really need SGD receiving and clean documentation for reconciliation.

Reality check: OCBC markets online application for foreign-owned companies ("Apply online today, no branch visit needed"). DBS states foreign incorporated or foreign-owned companies can open an account in Singapore. Online does not mean zero verification steps. Plan accordingly.

Step 2: Use a risk-first playbook (so money moves, not just paperwork)#

Run this like an operator. Choose the setup based on rails: do you need domestic transfer features, or just SGD receiving plus conversion and withdrawal?

Build a bank-ready packet early so you answer KYB/KYC questions once, cleanly, with consistent entity names and supporting documents. Then design a repeatable "get paid" workflow: invoice naming, payer instructions, and a reconciliation trail you can defend if you're asked about it under AML controls.

Hypothetical scenario: you invoice a Singapore client from a non-resident setup. If your invoice name, payer name, and receiving details do not match cleanly, you create questions. Align them from day one and you move faster.

What kind of Singapore account do you actually need?#

Pick the account type based on your entity and payment rails, not what sounds "official."

Your goal is the smallest, safest setup that still gives you the rails you need. Then you stop reapplying in circles.

Step 1: Run the 10-minute decision tree (don't skip this)#

• Confirm your entity reality.

• If you have a Singapore entity: verify it's registered with ACRA, Singapore's national regulator for business registration and related oversight. Common structures include Private company limited by shares (Pte Ltd) and LLP (ACRA describes an LLP as partnership-flexible but with a separate legal identity). - If you operate from the United States, United Kingdom, Indonesia, etc. with no Singapore entity: "open a corporate bank account in Singapore" may be an optional project, not your default starting point.

• Choose your rails.

• Need local transfers? You likely care about FAST and GIRO. OCBC describes FAST as instant transfers between participating banks and some non-bank financial institutions in Singapore. DBS describes GIRO as a convenient, paperless, cashless payment method. - Need to get paid in SGD? You may only need SGD receiving via account details. Wise says: "This isn't a bank account, but you can receive money in the same way."

Step 2: Map your scenario to a safe default#

Use this as a baseline:

Hypothetical scenario: you run a solo consultancy and invoice Singapore clients monthly. If you do not need GIRO collections or domestic vendor payments, optimize for clean SGD receiving plus reconciliation exports first. Upgrade later if your ops footprint grows.

Rank your decision criteria in this order:

• Speed to usable funds
• Operational controls (statements, references, exports for reconciliation)
• Review risk (how often you trigger AML follow-ups based on your flows)
• Fee exposure (FX spread, outbound transfer fees, and any account maintenance rules you must consistently meet)

Quick reality check: if your ownership chain runs through multiple entities or layered holding companies, expect deeper KYB questions about Ultimate Beneficial Owners. ISCA defines a beneficial owner as "the natural person(s) who in the end owns or controls a client, or the natural person on whose behalf a transaction is being conducted." Build your UBO map early to avoid rework.

If you operate a Pte Ltd, also see A Guide to Singapore's Corporate Tax System for Foreign Entrepreneurs.

Do you even need a Singapore bank account to get paid in SGD?#

No, you do not need a traditional Singapore bank account to get paid in SGD if your real goal is "SGD receiving plus clean reconciliation."

Decide whether you need domestic banking rails, or just a reliable way to accept SGD and keep your books clean.

Step 1: Decide based on payment rails, not labels#

Optimize for: "Can my client pay me smoothly, and can I match every incoming SGD to an invoice?" The label matters less than whether the setup fits your workflow.

Step 2: Implement the "tell clients exactly how to pay" workflow#

Step 1: If you choose a bank account, invoice like a Singapore operator.

• Use your exact registered legal entity name on the invoice.
• Share SGD bank details exactly as your bank provides them for FAST/GIRO-style payments, when relevant.

Step 2: If you choose a receiving account, standardize payer instructions. Wise sets expectations clearly: "This isn't a bank account, but you can receive money in the same way." Wise also states payers "can pay you locally from their Singaporean bank, or internationally by Swift." That gives you one set of instructions you can reuse.

Step 3: Run a reconciliation discipline your future self will thank you for.

• Require an invoice number reference in the payment notes.
• Keep a simple mapping: Invoice ID ↔ transfer reference ↔ payer name.
• If you want to automate that mapping, use Automating Your Freelance Finances: A Zapier Workflow for Connecting Stripe.

Hypothetical scenario: a Singapore client insists on paying SGD, but you do not need GIRO collections. Take the receiving route first, if available. Prove the pay-in workflow works, then upgrade later only if local payables or collections become real needs.

Prerequisites: what to prepare before you apply (so you don't get bounced)#

Most delays come from missing access, unclear authority, or inconsistent entity details.

Once you've decided whether you need a full Singapore corporate bank account or another setup for receiving funds, remove avoidable friction before anyone reviews you.

Step 1: Lock your identity and signatory plan (expect gates)#

Start by confirming who the authorised signatory is, and whether that person can complete any required signing steps.

Singapore's GoBusiness guidance says banks generally require "account signatories and majority directors be physically present in Singapore for paperwork signing at the time of opening the company bank account." GoBusiness also notes some banks may accept signing "at one of their overseas branches or in front of a Notary Public."

Treat this as an ops decision, not a surprise.

• Singpass is "Singapore citizens' and residents' trusted digital identity." If you do not have it, plan around manual steps.
• CorpPass is "the authorisation system for entities to manage digital service access of employees." If your entity uses it, decide who controls it early so you do not bottleneck submissions and follow-ups.

Step 2: Make your entity and compliance story easy to verify#

Banks run KYC for people and KYB for company ownership and legitimacy. You help yourself by sending consistent, readable information the first time.

Use this readiness grid:

Finally, draft a one-paragraph business description in plain language: what you sell, who pays you, and where your clients sit. You cannot control every AML question, but you can answer fast with clean contracts, invoices, and a consistent narrative across your application, website, and invoicing.

Build your "Application Packet" (KYB/KYC-ready) to avoid back-and-forth#

Build one cohesive, clearly labeled Application Packet that proves entity legitimacy, control (UBO), and business activity in a single pass.

This is where many applications stall. Founders drip-feed documents, then lose the thread in KYB and KYC follow-ups.

Step 1: Package documents in four folders (send as one set, not a drip feed)#

Create one zip or one shared folder, then keep filenames boring and consistent.

Use the folders like this:

• 01_Entity: if you have a Singapore entity, include a certified true copy of your company's business profile from ACRA and a certified true copy of your company constitution.
• 02_Ownership-Control: include a board resolution that sanctions opening the account and names signatories, plus any bank forms signed by the authorised signatories under that resolution.
• 03_ID-Verification: include certified true copies of passport (or Singapore IC) and proof of residential address for directors, signatories, and Ultimate Beneficial Owners.
• 04_Business-Proof: include a tight proof set that matches your stated model - website, proposals, signed scopes, and invoices. Keep names and descriptions consistent across everything.

Verification point: when you open any file, the legal entity name and the people names should match exactly, character-for-character.

Step 2: Add a UBO and control map (banks think in control, not vibes)#

DBS explicitly asks you to provide "independent and reliable documentary proof" showing who the beneficial owner is and how they exercise control. It gives an example of control via holding 25% or more shares. Put your control story into one table and reuse it.

Use the term Ultimate Beneficial Owner (UBO) consistently, and align it with your ACRA business profile or equivalent official company extract, where applicable.

Also include a one-page funds and activity memo (your KYB "cover letter"). KYB verifies ownership and legitimacy before a business relationship. Give reviewers a simple narrative: what you sell, how you bill, who pays, client types and geographies, and why money moves cross-border. For example, Singapore clients pay SGD, you convert and withdraw for operating expenses.

Verification point: DBS states "all documents must be in English," and banks can request extra documents depending on your setup. Translate non-English materials into English before you submit so you control the timeline.

Can you open remotely in 2026-or do you need to show up?#

You might complete the application online, but a Singapore bank can still require physical signing or verification before activation.

Choose a path that will not collapse midstream because you assumed "online" means "no humans, no branches."

Step 1: Treat "online opening" as conditional, then pre-decide your fallback#

Start with the conservative baseline. GoBusiness states that most banks require account signatories and majority directors to be physically present in Singapore for paperwork signing at the time of opening. It also notes that some banks may accept signing at an overseas branch or in front of a Notary Public.

Then read product pages like an operator:

Verification point: OCBC's own application forms state that specified signatories must be present with their NRIC or passports at an OCBC branch at the point of account opening. That one line should shape your timeline assumptions.

Step 2: Watch for the failure modes that break remote, then switch tracks early#

Remote usually breaks down when the bank asks for (1) physical presence at a branch to verify signatories, (2) signing via an overseas branch or in front of a notary, or (3) additional documents based on your company setup. Banks may also ask directors or authorised signatories to attend a short video or in-person verification meeting.

Also, do not confuse digital identity rails with bank onboarding. Singpass is Singapore's national digital identity, and CorpPass authorises corporate access to government digital services. Banks might advertise smoother flows that assume local access. If you do not have Singpass or CorpPass, ask what alternate route is supported.

Operational workaround (timeline protection): if travel to Singapore will not happen soon, pre-decide your fallback. You can pursue a bank that accepts overseas branch or notary signing, case by case, or plan for an in-person signing or verification step early so it does not surprise your launch timeline.

If you just need a quick next step while sorting out invoicing, try the free invoice generator.

Step-by-step: submit, verify, and get to "usable funds" (with checks at each step)#

Execute a five-step workflow that keeps your KYB story consistent, your documents reviewable, and your first real payment boring.

Step 1: Pick the target setup and lock your "account purpose" story#

Decide what rail you truly need, then write one plain-English account purpose statement you can repeat everywhere.

• Choose traditional Singapore banking if you need local rails like FAST (Fast And Secure Transfers), which lets customers transfer SGD funds almost immediately between participating banks in Singapore, and GIRO (General Interbank Recurring Order), an automated electronic payment service where billing organisations can request deductions from your bank account.
• Choose a receiving or multi-currency setup, where available, if you mainly need to receive and reconcile incoming payments, not GIRO.

Check: your story must match your proof. Your ACRA business profile - an electronic report that snapshots your entity at a point in time - should align with your website description, contracts, and invoices. Consistency helps reduce KYB back-and-forth, since KYB verifies ownership and legitimacy before the bank enters a business relationship.

Step 2: Do pre-submit hygiene (the fastest way to avoid avoidable questions)#

Run a name-matching audit across every surface area:

• Legal entity name, including "Pte Ltd," in: ACRA profile, bank application, invoice header, contract signature block.
• Individual names in: passport, bank forms, and your UBO table. UBO means the natural person who in the end owns or controls the company.

Check: confirm the payer name your client will use matches your registered entity. If your client pays under a personal name or a trading name, you may get follow-up questions.

Step 3: Submit your Application Packet as a complete set#

Send a complete package with clear structure:

• Entity (ACRA profile, constitution if requested)
• Ownership and control (UBO map, director and signatory details)
• IDs (passport scans, address proof as requested)
• Business proof (contracts, invoices, website)

Include a one-page source-of-funds memo up front. If you involve a foreign entity in the chain, keep relevant foreign registry extracts ready. If the bank asks for officer authority confirmation, a Certificate of Incumbency can verify the identity and current authority of officers and directors.

Check: plan for signing. GoBusiness notes account signatories and majority directors are generally required to be physically present in Singapore for paperwork signing at the time of opening, though some banks may accept signing at an overseas branch or in front of a Notary Public.

Step 4: Respond to follow-ups like an operator#

Reply in one thread. Package documents as one combined PDF per category - Entity, Ownership, IDs, Business Proof. Restate each question, answer it directly, then point to the exact page in your attachments.

Check: reuse the same identifiers every time: contract title, invoice number, client legal name. Do not improvise labels midstream.

Step 5: Activate and validate "usable funds"#

After approval, verify that your digital banking shows the features you planned around, such as FAST or GIRO. Then run a controlled end-to-end payment workflow - receive, reconcile, and transfer out - so you can spot friction early.

Check: read the product terms for operational constraints, for example minimum balance rules where applicable. Confirm the payer uses your exact entity name. Also confirm inbound details and transfer rails before you send the invoice, not after the money hits.

The first 90 days: your "get paid" system to reduce delays, disputes, and holds#

Build a paper-trail-first invoicing and reconciliation system that lets you explain every payment clearly when a bank or fintech asks questions.

Banks and payment providers keep monitoring after onboarding. One Singapore government guidance document defines ongoing monitoring as "the continuous process of assessing the clients and their transactions to detect and mitigate the ML/TF/PF risks." MAS Notice 626 states: "No bank shall rely on an intermediary to conduct ongoing monitoring of customers."

Client onboarding controls + invoice defaults (make AP processing easy)#

Step 1: Capture payer identity and route before work starts. Add three required fields to your onboarding form: payer legal name, payer country, and payment method (bank transfer via FAST, card, etc.). Copy the payer legal name into your invoice "Bill To" exactly as the client's AP team will send it.

Step 2: Lock document consistency across your company records, contract, and invoices. Store your signed MSA/SOW and make sure the contracting entity name matches what you use on your invoice template.

Step 3: Standardise your payment reference so you can reconcile FAST transfers. FAST moves SGD almost instantly between participating banks in Singapore, but references carry limits. UOB's FAST guide shows these constraints, so design your invoice number to fit.

Add a line on every invoice: "Payment reference required: [invoice number]."

Proof-of-delivery pack + reconciliation habits (stay audit-ready)#

Step 4: Keep "supporting documents" ready, even after verification. Wise explicitly says it may request ownership documents. It also says it may ask for bank statements plus invoices from the last 6 months in some cases. Build a folder per invoice number that includes the invoice PDF, the signed scope, and any delivery confirmation trail you have, for example emails or sign-off notes.

Step 5: Reconcile like an operator, not a historian. Bank reconciliation means matching your cash account records to the bank statement. Maintain a mapping: invoice number ↔ incoming transfer reference ↔ payer name ↔ bank fees ↔ FX conversions, when relevant. The goal is simple: you can explain what the money was for, who paid, and why amounts differ, such as fees or FX, using one tidy folder.

Common mistakes that cause delays or freezes (and how to recover fast)#

Most delays come down to risk-based onboarding and missing or inconsistent KYB information. Treat it as a documentation and consistency problem you can solve with one clean packet and one clear story.

This matters most in non-resident banking, where banks may request extra proof about your directors, shareholders, or local presence.

Step 1: Diagnose which "gap" you created (then fix the gap, not the symptom)#

Start with the bank's lens. Banks licensed under the Banking Act (Cap. 19) are required by MAS to apply a risk-based approach to every new corporate relationship. When your information looks inconsistent or incomplete, the perceived risk rises and the back-and-forth starts.

Use this operator table to spot the gap quickly:

Rule of thumb: if two documents describe the same thing differently, expect questions. Fix the inconsistency first, then resend a clean set.

Step 2: Recover fast with a staged plan (especially if you cannot travel)#

Step 2A: Confirm whether the bank needs physical presence. GoBusiness states: "Account signatories and majority directors be physically present in Singapore for paperwork signing at the time of opening the company bank account." If you cannot meet that, do not stall. Ask what alternative is accepted.

Step 2B: Use accepted signing alternatives when offered. GoBusiness also notes: "Some banks may accept the signing of documents at one of their overseas branches or in front of a Notary Public." Build that into your timeline early if the authorised signatory lives outside Singapore.

Step 2C: Keep a viable "get paid" rail while you finish onboarding. If you need SGD receiving now, consider Wise SGD account details, where available and suitable. Wise makes the constraint clear: "This isn't a bank account, but you can receive money in the same way by sharing the account name and number." Wise also notes payers can send money locally from their Singaporean bank, or internationally by Swift. This can buy you time while you schedule required in-person steps and complete the bank's onboarding.

If you want this to run without heroics, automate your reconciliation and document filing so you can answer queries in one reply: Automating Your Freelance Finances: A Zapier Workflow for Connecting Stripe.

The operator's wrap-up: pick the right path, submit one clean packet, then protect cashflow#

Pick the right rails upfront, then submit one KYB/KYC-ready packet your provider can review without chasing you. Your job is to choose the least painful path, execute cleanly once, then run your early operations so AML-driven questions do not derail cashflow.

Step 1: Choose the account type that matches your actual job-to-be-done#

Start with outcomes, not prestige. Banks in Singapore run customer due diligence for AML and counter-terrorism financing compliance, so complexity can multiply fast under non-resident reviews.

Use this operator table to pick your default:

Step 2: Submit one clean packet, then run a conservative early workflow#

Operate like you will get audited. ACRA is Singapore's national regulator for business registration, and the ACRA Business Profile (Bizfile information product) includes key registration and business activity details. Build one narrative across your registration details, your website, your contracts, and your invoices. Then reconcile every incoming transfer to an invoice number and reference so you can answer compliance questions fast.

If you want a systems layer beyond ad-hoc invoicing, Gruv is modular, API-first infrastructure for money movement. Where enabled, it can help you run collection, balance tracking, conversion, and payouts with compliance gates and traceable, audit-ready records as volume grows. For automation ideas, see Automating Your Freelance Finances: A Zapier Workflow for Connecting Stripe.

Copy/paste checklist (use this before every application):

text [ ] Decision locked: SG bank account (FAST/GIRO) vs SGD receiving route [ ] Entity docs ready: ACRA Business Profile (or local equivalent) [ ] Ownership ready: UBO table + director/shareholder list + authorised signatory identified [ ] IDs ready: passport scans + address proof (for required KYC persons) [ ] Source-of-funds summary + supporting contracts/SOWs + sample invoices [ ] Certificate of Incumbency prepared (if requested) [ ] Translation plan: English versions available if required [ ] Invoice template updated: legal entity name matches your registration details; payer name instructions included [ ] Reconciliation map set: invoice # ↔ transfer reference ↔ fees/FX ↔ exports

If you want to confirm what's supported for your specific country or program, talk to Gruv.