Anti-Money Laundering Compliance for Singapore SMEs
A practical guide to anti-money laundering compliance for Singapore SMEs — KYC, record-keeping, STR reporting, and how PDPA data protection fits in.

Anti-Money Laundering Compliance for Singapore SMEs
Anti-money laundering compliance is no longer just a concern for banks — a growing number of Singapore SMEs in regulated sectors must now run formal AML/CFT programmes, and the customer identity data they collect to do so falls squarely under the Personal Data Protection Act (PDPA) 2012. If your business verifies customer identities, screens against sanctions lists, or files suspicious transaction reports, you are simultaneously handling large volumes of sensitive personal data. This guide breaks down what Singapore SMEs must do to stay on the right side of both the anti-money laundering regime and the PDPA.
TL;DR — Key Takeaways
- AML/CFT obligations in Singapore extend to many non-bank SMEs: corporate service providers, accountants, property agents, precious metals dealers, and more.
- The four pillars of an AML programme are customer due diligence (CDD), ongoing monitoring, record-keeping (minimum 5 years), and suspicious transaction reporting (STR).
- KYC data is personal data. The PDPA's Protection Obligation (Section 24) and Retention Limitation Obligation apply to every identity document you store.
- Failure to report suspicious transactions is a criminal offence under Singapore's CDSA, carrying fines and imprisonment.
- Doing AML well and doing PDPA well are the same problem: collect what the law requires, secure it, and dispose of it on schedule.
What Is Anti-Money Laundering Compliance and Who Does It Apply To?
Anti-money laundering compliance refers to the policies, procedures, and controls a business puts in place to detect and prevent criminals from disguising illicit funds as legitimate income. In Singapore, the framework is anchored in the Corruption, Drug Trafficking and Other Serious Crimes (Confiscation of Benefits) Act (CDSA) and the Terrorism (Suppression of Financing) Act, with sector-specific rules issued by the Monetary Authority of Singapore (MAS) and other regulators.
Many SME owners wrongly assume AML is a "bank problem." It is not. Singapore's regime deliberately covers designated non-financial businesses and professions (DNFBPs) because criminals often route money through professional intermediaries. Your organisation likely has AML obligations if it operates as a:
- Corporate service provider or registered filing agent (regulated by ACRA)
- Public accountant or accounting entity (regulated by ACRA/ISCA)
- Estate agent or property salesperson (regulated by the Council for Estate Agencies)
- Precious stones and precious metals dealer (regulated by the Ministry of Law)
- Law firm or legal practice (regulated by the Law Society)
- Payment services or digital token business (licensed by MAS)
Definitive statement: If your Singapore SME falls within a regulated sector, running an AML/CFT programme is a legal requirement — not a best-practice option — and non-compliance can result in regulatory penalties, licence revocation, and criminal liability for directors.
The Four Pillars of an AML Programme
Every effective anti-money laundering compliance programme rests on four operational pillars. A Singapore SME that implements these consistently will satisfy the core expectations of most sectoral regulators.
1. Customer Due Diligence (Know Your Customer)
Customer due diligence (CDD), commonly called KYC, is the process of verifying who your customer really is before you do business. At minimum you should identify and verify the customer's full name, identification number, date of birth, nationality, and residential address using reliable, independent documents such as a NRIC, passport, or ACRA business profile. For corporate customers, you must also identify the beneficial owners — the natural persons who ultimately own or control the entity, typically at a 25% ownership threshold.
Higher-risk customers — for example, politically exposed persons (PEPs) or those from higher-risk jurisdictions — require enhanced due diligence, including senior management approval and source-of-funds checks.
2. Ongoing Monitoring
AML is not a one-time check at onboarding. You must monitor transactions on a risk-sensitive basis throughout the relationship, watching for activity that is inconsistent with what you know about the customer. Periodic reviews should refresh KYC data, and any material change — a new director, a change in ownership, unusual transaction patterns — should trigger a fresh assessment.
3. Record-Keeping (Minimum 5 Years)
Singapore's AML rules generally require regulated entities to retain CDD documents and transaction records for at least five years after the business relationship ends or the transaction is completed. These records must be sufficient to reconstruct individual transactions and be produced to authorities on request. This is where AML and the PDPA intersect most directly, as covered below.
4. Suspicious Transaction Reporting (STR)
If you know or have reasonable grounds to suspect that funds are connected to criminal conduct, you are legally obliged to file a Suspicious Transaction Report (STR) with the Suspicious Transaction Reporting Office (STRO), Singapore's Financial Intelligence Unit, via the SONAR system. Failing to report a suspicious transaction is itself a criminal offence under the CDSA, punishable by a fine and imprisonment — so this pillar is not discretionary.
Where Anti-Money Laundering Compliance Meets the PDPA
Here is the part most Singapore SMEs overlook: every NRIC copy, passport scan, proof of address, and beneficial-ownership record you collect for KYC is personal data, and the moment you store it, the PDPA applies in full. Anti-money laundering compliance and data protection are two sides of the same coin — you are legally compelled to collect sensitive data, and legally compelled to protect it.
Snippet-ready answer: Under the PDPA, personal data collected to meet a legal AML obligation does not require separate customer consent, because the Consent Obligation contains an exception for collection, use, or disclosure that is required or authorised under other written law (PDPA First Schedule). However, all other PDPA obligations still apply — you must protect the data, limit its retention, and honour access requests where the AML exemptions do not override them.
Three PDPA obligations deserve special attention for AML-heavy businesses:
- Protection Obligation (Section 24): You must make reasonable security arrangements to protect KYC data against unauthorised access, disclosure, copying, or loss. In practice this means encryption of identity documents, access controls limiting KYC files to staff who need them, and secure disposal. The PDPC has repeatedly fined organisations that stored NRIC-linked data in unsecured databases.
- Retention Limitation Obligation: Once the mandatory five-year AML retention period lapses and no other legal purpose exists, you must securely dispose of the personal data. Hoarding old KYC files "just in case" is a PDPA breach that also enlarges your attack surface.
- Notification of NRIC collection: Because KYC almost always involves NRIC numbers, your organisation should follow the PDPC's Advisory Guidelines on the NRIC and other National Identification Numbers, collecting full NRIC data only where required by law — which AML expressly is.
For a structured way to see how these obligations map to your day-to-day operations, our PDPA Compliance Checklist for Singapore SMEs walks through each requirement step by step, and if a KYC file is ever exposed, our data breach response guide covers your notification duties under the mandatory Data Breach Notification regime.
How Much Does Getting This Wrong Cost?
Direct answer: The costs of failure come from two directions. On the AML side, sectoral regulators can impose financial penalties, compositions, and licence suspensions, while individuals who fail to file STRs face criminal prosecution under the CDSA. On the PDPA side, the PDPC can impose a financial penalty of up to 10% of an organisation's annual turnover in Singapore, or S$1 million, whichever is higher, for breaches of the data protection obligations.
The reputational damage compounds the financial hit. Regulated SMEs — especially corporate service providers and accounting firms — trade on trust, and a public enforcement decision can end client relationships overnight. To understand how the PDPC actually applies penalties in practice, review the real enforcement outcomes in our analysis of PDPA penalties and enforcement cases. Accounting firms handling client financial data face a particularly acute overlap of AML and PDPA duties, which we cover in depth in our guide to PDPA for accounting firms.
A Practical AML + PDPA Action Plan for Your Business
Bringing anti-money laundering compliance and data protection together, here is a sequence any Singapore SME can follow:
- Confirm your obligations. Identify which regulator supervises your sector and obtain its specific AML/CFT notice and guidelines. Do not assume you are exempt.
- Write a risk assessment. Document your exposure to money-laundering risk across customers, products, geographies, and delivery channels. This underpins a risk-based approach.
- Appoint an AML/CFT compliance officer and, in parallel, a PDPA Data Protection Officer (DPO). In a small SME these may be the same person, but the roles must be clearly defined.
- Draft CDD and record-keeping procedures that specify what you collect, how you verify it, and how long you keep it — aligned to the five-year AML minimum and PDPA retention limits.
- Secure the data. Apply encryption, role-based access, and a clean-desk policy to KYC files. Train staff, because human error is the leading cause of breaches — see our guide on PDPA staff training requirements.
- Set up STR filing through STRO's SONAR portal and rehearse your escalation process so staff know how and when to report.
- Review annually and after any regulatory update.
Building all of this from scratch is where most SMEs stall. This is where ComplyHQ helps: it offers AI-powered compliance that handles your PDPA obligations in minutes, not weeks, generating the data protection policies, retention schedules, and breach-response workflows that sit underneath your AML programme — so your KYC data stays protected without months of manual drafting. For the AML-specific systems and any custom integration work, specialist providers such as Adaptels build digital solutions tailored to Singapore SMEs.
Key Takeaway
Anti-money laundering compliance and PDPA data protection are not separate compliance chores — they are one continuous obligation to collect the identity data the law demands, guard it rigorously, and dispose of it responsibly. Singapore SMEs that treat them as a single, well-documented workflow will satisfy both MAS/sectoral regulators and the PDPC, while protecting the customer trust their business depends on.
Sources
- Monetary Authority of Singapore — Anti-Money Laundering and Countering the Financing of Terrorism — Singapore's primary AML/CFT regulatory framework.
- Singapore Police Force — Suspicious Transaction Reporting Office (STRO) — how and where to file Suspicious Transaction Reports.
- ACRA — Anti-Money Laundering / Countering the Financing of Terrorism for Corporate Service Providers — AML obligations for registered filing agents and CSPs.
- Personal Data Protection Commission — PDPA Overview and Advisory Guidelines — the PDPA 2012, including the Protection and Retention Limitation Obligations.
- PDPC — Advisory Guidelines on the PDPA for NRIC and Other National Identification Numbers — rules on collecting NRIC data for KYC.
Simplify Your Compliance
ComplyHQ's AI can assess your PDPA compliance gaps in under 15 minutes and generate the policies you need.
Try Free AssessmentFrequently Asked Questions
Does my Singapore SME need an AML programme if it is not a bank?
How does AML customer due diligence interact with the PDPA?
How long must I keep AML and KYC records in Singapore?
Mervin Tan — Founder, ComplyHQ
Mervin is a Singapore-based software engineer and the founder of Adaptels, the company behind ComplyHQ. He has 15+ years of experience building software for businesses, and built ComplyHQ to make PDPA compliance manageable for the small businesses that can't justify a consultant's retainer. He writes ComplyHQ's guides with AI-assisted drafting and reviews them against PDPC primary sources — see the editorial policy.
Contact: support@complyhq.app · About ComplyHQ · Not legal advice
Ready to get PDPA compliant?
Stop guessing about compliance. ComplyHQ uses AI to assess your gaps, generate policies, and guide you through every PDPA obligation.