On 20 April 2026, Philippine media reported that the National Bureau of Investigation had arrested 48 individuals after raiding an alleged online scamming hub in Parañaque City. The timing matters. This is not an old case being revisited. It is a fresh reminder that scam operations across Southeast Asia are still active, organised, and scaling fast.

When authorities entered the site, they did not just uncover another isolated scam. They walked into something far more structured — an operation that looked less like opportunistic fraud and more like a production line.

Dozens of individuals. Multiple devices. Coordinated activity. A setup that resembled a call centre more than a loose group of fraudsters.

For compliance teams, this is not just another headline. It is a signal. Modern scam networks are becoming more industrialised, and the financial trails they leave behind are becoming harder to detect with static, siloed controls.

What Actually Happened in Parañaque

The raid exposed an online scamming hub operating at scale. Investigators found individuals actively engaged in defrauding victims, likely through a mix of social engineering tactics — investment scams, impersonation schemes, and possibly romance or job scams.

What stood out was not just the activity itself, but the structure:

• Multiple operators working simultaneously
• Dedicated systems and devices
• Coordinated workflows
• A controlled environment, almost like a call centre

This was not a loose group of fraudsters. It was organised, repeatable, and designed for volume.

That distinction matters.

Because once fraud becomes structured like this, it stops being unpredictable and starts becoming scalable.

The Shift from Scams to Scam Infrastructure

For years, fraud has often been viewed as a series of isolated incidents. A phishing email here. A social engineering case there.

That lens no longer holds.

What the Parañaque case reveals is something deeper: the rise of scam infrastructure.

These are not individuals improvising. These are networks designed with:

• Recruitment pipelines
• Scripted engagement models
• Operational roles and hierarchies
• Performance-driven execution

In many ways, these setups mirror legitimate businesses — except the product being “sold” is deception.

And like any efficient system, they optimise over time.

They test what works. They refine messaging. They reuse successful playbooks. They scale quickly.

For financial institutions, this changes the challenge entirely.

You are no longer detecting one-off fraud. You are up against systems that are constantly learning and adapting.

Why This Matters for Financial Institutions

At first glance, a physical raid in the Philippines may feel distant to a bank in Singapore or a fintech in Australia.

But the financial footprint of such operations is rarely local.

Scam proceeds move quickly — often across borders, across institutions, and across channels.

A typical flow might look like this:

• Victim transfers funds via online banking or wallet
• Funds are routed through mule accounts
• Split into smaller transactions
• Moved across jurisdictions
• Layered further to obscure origin

By the time the money surfaces in a financial institution’s system, it often appears routine.

That is the real risk.

Not at the point of the scam, but at the point where illicit funds blend into legitimate financial flows.

The Hidden Complexity Behind “Simple” Scams

It is easy to dismiss scams as basic manipulation.

But cases like this show how layered they have become.

Behind a single victim interaction, there may be:

• A recruitment network sourcing operators
• A technical setup managing communication channels
• A financial layer handling fund movement
• A supervisory layer coordinating activity

Each layer introduces its own signals.

But those signals are rarely obvious in isolation.

A transaction might look normal.
A customer profile might appear clean.
A payment pattern may not trigger any threshold.

Yet, when viewed together, they form a pattern.

This is the daily reality for compliance teams — connecting weak, fragmented signals into something meaningful.

Where Traditional Detection Starts to Break Down

Most financial institutions still rely, at least in part, on rule-based monitoring.

And rules do have their place.

But against structured scam operations, they begin to show limitations:

• Static thresholds struggle against evolving behaviour
• Isolated alerts fail to capture network patterns
• Manual tuning cannot keep pace with changing typologies

In the Parañaque case, individual transactions may not have appeared suspicious.

What made them risky was the context — the coordination, the repetition, the connections.

This is where traditional systems fall short.

They are built to detect anomalies, not ecosystems.

The Role of Mule Networks in Scaling Fraud

No large-scale scam operation works without one critical component: money mules.

These accounts absorb, move, and disguise illicit funds.

And they are becoming increasingly sophisticated.

Some are unwitting — recruited through job offers or incentives.
Others are complicit — knowingly participating in exchange for a share.

Either way, they create a buffer between fraudsters and the financial system.

In operations like the Parañaque hub, mule networks likely operate in parallel:

• Receiving funds from multiple victims
• Redistributing across accounts
• Moving funds rapidly across borders

From a compliance perspective, mule activity often appears as:

• High-velocity transactions
• Rapid inflows and outflows
• Accounts with little genuine economic activity

But again, these signals are rarely conclusive on their own.

The Cross-Border Reality

Modern fraud rarely stays within one jurisdiction.

A scam initiated in one country can impact victims in another, with funds routed through multiple regions.

This creates three persistent challenges:

1. Fragmented visibility
   No single institution sees the full transaction chain
2. Jurisdictional differences
   Regulatory expectations and data access vary
3. Delayed intervention
   By the time alerts are triggered, funds have already moved

The Parañaque case reinforces a simple truth: financial crime is global, even when it appears local.

What Compliance Teams Should Be Looking For

Rather than focusing on isolated red flags, institutions need to identify patterns of behaviour.

Indicators aligned with operations like this include:

• Clusters of accounts exhibiting similar transaction flows
• Repeated low-to-mid value transfers across multiple beneficiaries
• Rapid movement of funds with minimal retention
• Shared identifiers such as devices, IPs, or contact details
• Activity inconsistent with stated customer profiles

Individually, these may not trigger concern.

Collectively, they signal coordination.

Moving from Detection to Understanding

There is a broader shift underway in financial crime prevention.

From generating alerts…
To understanding behaviour.

It is no longer enough to flag transactions.

Teams need to ask:

• Why is this activity happening?
• How is it connected to other behaviour?
• What broader typology does it resemble?

This shift is not easy.

Because understanding requires context — and context requires intelligence beyond internal data.

The Role of Collaborative Intelligence

Cases like the Parañaque scam hub highlight a structural gap.

No single institution has full visibility.

Fraud patterns are distributed across:

• Banks
• Fintech platforms
• Payment processors
• Geographies

Which means detection cannot rely on isolated systems.

Collaborative intelligence becomes critical.

By sharing typologies, behavioural patterns, and risk signals without exposing sensitive data institutions can:

• Detect emerging threats earlier
• Improve accuracy
• Reduce false positives

This is where community-driven intelligence models are gaining traction.

Where Technology Needs to Evolve

To keep pace with structured fraud operations, detection systems need to evolve in three ways:

1. From rules to adaptive intelligence
Systems must continuously learn from emerging patterns

2. From transactions to networks
Detection must capture relationships, not just events

3. From alerts to actionable insights
Outputs must support faster, clearer investigation decisions

This is not about replacing existing systems overnight.

It is about enhancing them to reflect how fraud actually operates today.

The Cost of Getting This Wrong

The impact of missing these signals goes beyond financial loss.

There are broader consequences:

• Increased regulatory scrutiny
• Reputational damage
• Erosion of customer trust

In fast-growing digital markets, trust is not easily rebuilt once lost.

And fraud, left unchecked, directly undermines it.

A More Grounded Way Forward

The Parañaque case is not an anomaly. It is part of a pattern.

Fraud is becoming:

• More organised
• More scalable
• More adaptive

And increasingly embedded within legitimate financial systems.

Responding to this requires a shift:

From reactive to proactive
From siloed to collaborative
From static to adaptive

For compliance teams, this is not about chasing every new scam.

It is about building the capability to recognise patterns — even as they evolve.

Conclusion: Beyond the Raid

The arrest of 48 individuals is a meaningful enforcement action.

But it is not the end of the story.

Operations like these rarely disappear. They adapt, relocate, and re-emerge.

For financial institutions, the real question is not whether such scams exist.

It is whether their systems can detect the financial signals these operations inevitably leave behind.

Because while enforcement can shut down a physical hub, the financial trails continue to move.

And that is where the real battle is being fought.

Picture a compliance officer at a Malaysian licensed bank three weeks out from a BNM AML/CFT examination. She has read AMLATFPUAA. She knows the Act was amended in 2014 and again in 2020. What she needs now is not another legislative summary. She needs to know what BNM's examiners will actually open on their laptops when they arrive — which files, which logs, which policy documents — and where programmes at institutions like hers most commonly fall short.

That is what this guide covers.

The legislative history of AMLATFPUAA and its impact on Malaysia's financial sector is covered in our [overview of AMLA and its impact on the Malaysian financial landscape](/compliance-hub/understanding-amla-impact-on-malaysia-financial-landscape). This article focuses on the operational layer: the ongoing compliance obligations that BNM-supervised institutions must meet, the specific thresholds and timelines that govern reporting, and the recurring examination gaps that BNM has identified in practice.

The Regulatory Framework in Brief

Two instruments govern AML/CFT compliance for BNM-supervised institutions in Malaysia.

AMLATFPUAA 2001 is the primary legislation. The 2014 amendment expanded the list of predicate offences and brought Designated Non-Financial Businesses and Professions (DNFBPs) into the compliance perimeter. The 2020 amendment strengthened beneficial ownership requirements and raised maximum penalties to MYR 3 million per offence, or 5 years imprisonment, or both. For financial institutions, the penalties can run per transaction or per day of non-compliance — which changes the risk calculus considerably.

BNM's AML/CFT and TF Policy Document (2023) is where the day-to-day compliance standards sit. The Policy Document translates AMLATFPUAA's obligations into specific programme requirements: who must be screened, how, at what intervals, and with what documentation. BNM's Financial Intelligence and Enforcement Department (FIED) is the enforcement arm that reviews STR filings and leads enforcement action.

When a BNM examiner cites a deficiency, the reference is almost always to the Policy Document, not to the Act itself. Knowing the Act is necessary; knowing the Policy Document is what keeps a programme compliant.

Who Must Comply: Reporting Institutions Under AMLATFPUAA

AMLATFPUAA defines "Reporting Institutions" across three categories, each carrying distinct obligations.

Category 1 covers licensed banks, Islamic banks, and development financial institutions. These institutions carry the fullest set of AML/CFT obligations under the Policy Document, including mandatory enterprise-wide risk assessments and comprehensive transaction monitoring programmes.

Category 2 covers money service businesses (MSBs), remittance operators, and e-money issuers. The obligations are materially equivalent to Category 1 for CDD and reporting, but the Policy Document recognises that the risk typologies differ — particularly for remittance operators processing high-frequency, lower-value cross-border transfers.

Category 3 covers DNFBPs: lawyers, accountants, and real estate agents, brought in under the 2014 amendment. DNFBP obligations are threshold-triggered — they apply when a transaction reaches a defined cash value or when the DNFBP is facilitating a category of activity specified in the Act.

The DNFBP category matters for banks because banks deal with these professionals as customers. When a law firm holds a client account at your institution, BNM expects you to recognise that relationship as carrying elevated risk — and to apply the CDD standards appropriate to it.

Customer Due Diligence: Three Tiers, Different Standards

BNM's AML/CFT Policy Document sets three CDD tiers. Which tier applies depends on the risk profile of the customer and the nature of the business relationship — not on an institution's convenience.

Standard CDD

Standard CDD applies to all new customers unless simplified CDD conditions are met. It requires identification and verification of the customer, documentation of the purpose and intended nature of the business relationship, and a customer risk assessment at onboarding. Verification must be based on independent and reliable sources — a customer self-certifying their identity is not sufficient.

For individual customers, verification typically involves government-issued identification. For corporate customers, it extends to directors, authorised signatories, and ultimate beneficial owners (UBOs).

Simplified CDD

Simplified CDD is available for customers assessed as low-risk: listed companies on a regulated exchange, government entities, and FIs supervised by BNM or an equivalent foreign regulator. Under simplified CDD, identification is still required but the depth of verification can be reduced, and ongoing monitoring can operate at lower intensity.

The Policy Document is explicit that simplified CDD is a risk-based determination — not a category exemption. An institution cannot apply simplified CDD to a listed company without first concluding that the specific company and the specific transaction type present low money laundering risk.

Enhanced Due Diligence

Enhanced Due Diligence (EDD) is mandatory for four customer categories:

• Politically Exposed Persons (PEPs) — domestic and foreign
• Customers from FATF-identified jurisdictions with strategic AML/CFT deficiencies
• Corporate customers with complex or non-transparent ownership structures
• Customers engaged in cash-intensive businesses

EDD requirements under the Policy Document are specific. For PEPs, the institution must verify source of funds and source of wealth — not just identify the customer's occupation. Senior management approval is required before establishing or continuing a relationship with a PEP. The approval must be documented, with a named approver. Periodic review of PEP relationships is mandatory at least every 2 years.

For all EDD customers, monitoring intensity must be increased. What "increased" means in practice is calibrated monitoring rules, not a generic note in the file that the customer is high-risk.

Beneficial ownership threshold: BNM sets the threshold for identifying UBOs at 25% ownership or control — consistent with the FATF standard. Institutions must trace ownership to natural persons. Nominee structures, trusts, and multi-layer corporate arrangements are not a legitimate stopping point. If your CDD file shows a holding company as the UBO rather than the individuals who own it, the file is incomplete.

For institutions operating digital onboarding channels, the BNM eKYC Policy Document sets out the technical requirements that must be met for remote CDD to carry the same assurance as face-to-face verification. The specifics for digital banks and e-money issuers are covered in our eKYC Malaysia guide.

Ongoing Monitoring Requirements

Onboarding CDD is not a one-time event. BNM's Policy Document requires institutions to monitor the business relationship throughout its duration — which means monitoring transactions for consistency with the customer's risk profile, stated purpose, and expected transaction patterns.

When Re-KYC Is Required

The Policy Document specifies triggers that require re-assessment of a customer's KYC data:

• A material change in the customer's circumstances (change in business activity, change in ownership structure, change in country of domicile)
• A change in the customer's risk rating — either triggered by a system alert or a periodic review
• Reactivation of a dormant account (inactive for 12 months or more)
• Scheduled periodic review for high-risk customers — at minimum every 2 years

The 12-month dormancy trigger and the 2-year PEP review cycle are not recommendations. They are requirements. BNM examiners check whether these cycles are documented and whether the reviews are substantive — not whether a checkbox was ticked.

Transaction Monitoring Calibration

BNM's examination findings have repeatedly cited one gap above others: institutions running transaction monitoring with default threshold settings that have not been calibrated to the institution's own customer risk profile.

Default thresholds — those that come with a monitoring system out of the box — are designed to be functional across a broad range of institutions. They are not designed to reflect the specific risk profile of your customer book. A licensed bank whose retail clients are primarily salaried employees in Klang Valley has a different expected transaction pattern than an MSB processing remittances to Southeast Asian labour markets. Their monitoring should look different.

BNM expects institutions to document why their thresholds are set where they are, when they were last reviewed, and who approved the current calibration. If the answer is "these are the system defaults," that is a finding waiting to be written.

To understand what an effective transaction monitoring programme should look like — and what to evaluate when selecting or upgrading a system — see our Transaction Monitoring Software Buyer's Guide and What Is Transaction Monitoring.

Reporting Obligations: Timelines and Thresholds

BNM-supervised institutions have two primary reporting obligations to FIED. Both have defined timelines that examination teams check.

Cash Threshold Reports (CTRs)

Any cash transaction — or series of related cash transactions — of MYR 25,000 or above must be reported to FIED via the goAML system (Malaysia adopted the UNODC goAML platform in 2020). The filing deadline is 3 business days from the date of the transaction.

CTR filing is largely mechanical for institutions with core banking systems capable of automated flagging. Where BNM has found gaps is in the manual detection of structured transactions — multiple sub-MYR 25,000 cash deposits by the same customer within a short period, designed to stay below the CTR threshold. Structuring is a predicate offence under AMLATFPUAA. Failing to detect it is a monitoring failure, not just a reporting failure.

Suspicious Transaction Reports (STRs)

An STR must be filed when a staff member or system alert produces grounds to suspect that a transaction involves the proceeds of a scheduled offence or is connected to terrorist financing. The deadline is 3 working days from the point at which suspicion is formed — not from when the transaction occurred.

That distinction matters. If a transaction alerts in your monitoring system on Monday and a compliance analyst forms a reasonable suspicion on Wednesday, the STR clock started on Wednesday, not Monday.

BNM examination findings have identified a specific quality gap in STR filings: reports submitted without an adequate documented basis for suspicion. An STR that records "transaction appeared unusual" without specifying what pattern triggered the suspicion, what investigation was conducted, and why the analyst concluded suspicion was warranted, does not meet the standard. The goAML system requires structured data fields to be completed — but the narrative quality of what goes into those fields is what BNM examiners assess.

The internal pathway matters too. Institutions must have a documented process for staff to escalate concerns to the MLRO via an Internal Suspicious Transaction Report (ISTR). Frontline staff who identify red flags and have no clear escalation route — or who fear that escalating will reflect poorly on them — are a systemic gap. BNM expects staff training to address this directly.

AML/CFT Programme Governance

A compliant AML/CFT programme is not a set of policies in a folder. BNM's Policy Document specifies the governance structure that must be in place.

Board-approved compliance programme. The institution's AML/CFT programme must be documented, formally approved by the Board of Directors, and reviewed at minimum annually. A programme that exists only in the compliance officer's head — or that was last updated before the 2020 AMLATFPUAA amendments — is non-compliant.

Designated Compliance Officer (DCO). The DCO must sit at senior management level and must have direct access to the Board or Board Audit Committee when escalation is required. BNM examiners specifically check whether the DCO has the seniority and independence to escalate concerns without internal obstruction. An institution where the MLRO reports upward through the business line whose clients they are monitoring has a structural governance problem.

Independent AML/CFT audit. The audit function — whether internal or conducted by a qualified external party — must assess the AML/CFT programme at least once per year. The scope must cover policy adequacy, operational effectiveness, and staff training outcomes. An audit that confirms the policies exist but does not test whether they work is not what BNM requires.

Staff training. Training must be documented, with records of attendance and assessment results. BNM examiners have cited institutions where training records were incomplete or where training had not been updated to reflect regulatory changes — including the goAML transition and the 2020 AMLATFPUAA amendments.

Common BNM Examination Gaps

Based on publicly available BNM guidance and supervisory feedback, five gaps recur across examinations of Malaysian institutions.

Outdated customer risk assessments. Customers onboarded years ago under different risk criteria and never re-assessed — even when their transaction patterns have materially changed.

Incomplete beneficial ownership documentation for corporate customers. Files that identify a corporate structure but stop at the holding company level, without tracing to the natural persons who ultimately control it.

STRs filed without documented analytical basis. The filing exists, but the rationale is absent. This satisfies neither the spirit nor the operational requirement of the obligation.

Default monitoring thresholds. System thresholds not calibrated to the institution's specific customer risk profile — and no documentation that the calibration question was ever asked.

Inadequate scrutiny of DNFBPs as customers. Banks treating law firm client accounts or real estate agent trust accounts the same as ordinary business accounts, without recognising the elevated risk profile those relationships carry under AMLATFPUAA.

Malaysia's FATF Context: Why Examination Intensity Has Increased

Malaysia's FATF Mutual Evaluation in 2023 assessed both technical compliance and effectiveness — two different standards. Technical compliance measures whether the laws and regulations are in place. Effectiveness measures whether they work.

Malaysia's technical compliance ratings were largely Compliant or Largely Compliant. Its effectiveness ratings were lower — particularly for the transparency of corporate beneficial ownership, where the evaluation found that beneficial ownership information was not always available to competent authorities in a timely way.

For BNM-supervised institutions, the practical effect is this: BNM is under pressure to demonstrate that AML controls are operationally effective, not just formally present. Examination intensity has increased since 2023. The scrutiny on beneficial ownership documentation, on monitoring calibration, and on STR quality is not coincidental. These are the areas the FATF evaluation identified as weakest, and they are the areas BNM examiners are examining most carefully.

Preparing for What Examiners Actually Review

The compliance officer three weeks out from her BNM examination should be checking seven things:

1. Are customer risk assessments current — specifically for dormant accounts and for customers whose transaction patterns have changed?
2. Do all corporate customer files trace beneficial ownership to natural persons at the 25% threshold?
3. Are monitoring thresholds documented with a calibration rationale — and reviewed within the last 12 months?
4. Do STR files contain a structured basis for suspicion, not just a transaction reference?
5. Is the DCO's seniority and Board access documented?
6. Was the AML/CFT audit conducted in the past year, and did its scope include operational testing?
7. Are staff training records complete and current for all frontline and compliance staff?

These are not abstract compliance questions. They are the specific items that BNM examinations have produced findings on. Getting them right before the examination is considerably easier than explaining gaps during it.

If you want to see how Tookitaki's platform supports CDD, transaction monitoring calibration, and STR quality management for BNM-supervised institutions, book a demo. Or download our Malaysia AML compliance checklist for a full pre-examination review framework tailored to AMLATFPUAA and the BNM AML/CFT Policy Document. For institutions evaluating or upgrading their monitoring systems, the Transaction Monitoring Software Buyer's Guide covers what to look for and what to ask vendors about calibration and alert management. If you're new to the foundations of KYC and CDD, our What Is KYC guide provides the conceptual grounding the Policy Document assumes you have.

In today's financial landscape, understanding the source of funds (SOF) is crucial for ensuring compliance and preventing financial crimes. Financial institutions must verify the origin of funds to comply with regulations and mitigate risks. This blog post delves into the meaning, importance, best practices, and challenges of verifying the source of funds.

Source of Funds in AML: What It Is and How Banks Verify It

Source of Funds Meaning

The term "source of funds" refers to the origin of the money used in a transaction. This can include earnings from employment, business revenue, investments, or other legitimate income sources.

{{cta-first}}

Source of Funds Example

For instance, if someone deposits a large sum of money into their bank account, the bank needs to verify whether this money came from a legitimate source, such as a property sale, inheritance, or salary.

Here are some common sources of funds:

• Salary: Imagine you've been saving up from your job to buy a new gaming console. When you finally get it, your salary is the Source of Funds for that purchase. In the grown-up world, this could mean someone buying a house with the money they've saved from their job.
• Inheritance: Now, let's say your grandma left you some money when she passed away (may she rest in peace), and you use it to start a college fund. The inheritance is your Source of Funds for that college account.
• Business Profits: If you have a lemonade stand and make some serious cash, and then you use that money to buy a new bike, the profits from your business are your Source of Funds for the bike.
• Selling Assets: Let's say your family decides to sell your old car to buy a new one. The money you get from selling the old car becomes the Source of Funds for the new car purchase.
• Investments and Dividends: Suppose you've invested in some stocks, and you make a nice profit. If you use that money to, say, go on vacation, then the money you made from your investments is the Source of Funds for your trip.

Difference Between Source of Funds and Source of Wealth

Source of Funds (SOF) refers to the origin of the specific money involved in a transaction, such as income from employment, sales, or loans. It is focused on the immediate funds used in a particular financial activity.

Source of Wealth (SOW), on the other hand, pertains to the overall origin of an individual’s total assets, including accumulated wealth over time from various sources like investments, inheritances, or business ownership. It provides a broader view of the person's financial background.

Importance of Source of Funds Verification

Regulatory Requirements and Compliance

Verifying the source of funds is essential for financial institutions to comply with regulations such as anti-money laundering (AML) laws. Regulatory bodies like the Financial Action Task Force (FATF) mandate stringent checks to ensure that funds do not originate from illegal activities.

Financial and Reputational Risks

Failure to verify the source of funds can result in significant financial penalties and damage to an institution's reputation. Banks and other financial entities must implement robust verification processes to avoid involvement in financial crimes and maintain public trust.

Best Practices for Source of Funds Verification

Risk-Based Approach

Implementing a risk-based approach means assessing the risk level of each transaction and customer. Higher-risk transactions require more rigorous verification, ensuring that resources are allocated efficiently and effectively.

Advanced Technology Utilization

Utilizing advanced technologies such as artificial intelligence and machine learning can enhance the efficiency and accuracy of source of funds verification. These technologies can analyze large datasets quickly, identifying potential red flags.

Regular Updates and Audits

Maintaining updated records and conducting regular audits are crucial for an effective source of funds verification. This ensures that the verification processes remain robust and compliant with the latest regulations.

Source of Funds Requirements Across APAC

FATF Recommendation 13 requires financial institutions to apply enhanced due diligence, including source of funds verification for high-risk customers and transactions. In practice, each APAC regulator has translated this into specific obligations.

Australia (AUSTRAC)

Under the AML/CTF Rules Part 7, AUSTRAC requires ongoing customer due diligence that includes verifying source of funds when a transaction or customer profile is inconsistent with prior behaviour or stated purpose. Enhanced customer due diligence — triggered by high-risk customer classification, PEP status, or unusual transaction patterns — requires documented source of funds evidence before the transaction proceeds or the relationship continues.

Acceptable documentation under AUSTRAC guidance includes: recent pay slips (last 3 months), business financial statements, tax returns, property sale contracts, or investment account statements. For inheritance-sourced funds, a grant of probate or solicitor letter is required.

Singapore (MAS)

MAS Notice 626 requires Singapore-licensed FIs to verify source of funds as part of enhanced due diligence for high-risk customers and any customer whose funds originate from high-risk jurisdictions. MAS examination findings have consistently cited inadequate SOF documentation as a gap — specifically, accepting verbal declarations without supporting evidence.

Malaysia (BNM)

BNM's AML/CFT Policy Document requires source of funds verification for EDD-triggered customers, high-value transactions above MYR 50,000 in cash-equivalent form, and corporate accounts where beneficial ownership is complex. BNM specifically requires that SOF evidence be independently verifiable — a customer's own declaration is not sufficient for high-risk accounts.

Philippines (BSP)

BSP Circular 706 and its amendments require source of funds verification for customers classified as high-risk under the institution's risk assessment, and for any transaction that appears inconsistent with the customer's known financial profile. AMLC's guidance notes that source of funds documentation must be retained for a minimum of 5 years.

Common Sources of Funds

Legitimate Sources

Legitimate sources of funds include earnings from employment, business income, investment returns, loans, and inheritances. These sources are generally verifiable through official documentation such as pay slips, tax returns, and bank statements.

Illegitimate Sources

Illegitimate sources of funds might include money from illegal activities such as drug trafficking, fraud, corruption, or money laundering. These sources often lack proper documentation and can pose significant risks to financial institutions if not properly identified and reported.

Challenges in Verifying Source of Funds

Complex Transactions

Complex transactions, involving multiple parties and jurisdictions, pose significant challenges in verifying the source of funds. Tracing the origin of such funds requires comprehensive analysis and robust systems to track and verify all related transactions.

Privacy and Data Protection Concerns

Verifying the source of funds often involves handling sensitive personal data. Financial institutions must balance the need for thorough verification with strict adherence to privacy and data protection regulations, ensuring that customer information is secure.

{{cta-guide}}

What Good Source of Funds Verification Looks Like in Practice

The institutions that handle SOF verification most effectively treat it as a tiered process, not a one-size-all checklist.

For standard-risk customers, verification at onboarding is enough — pay slips, a bank statement, or a tax return. For high-risk customers, EDD-triggered accounts, or transactions that don't fit the pattern, that standard is higher: independently verifiable documentation, a paper trail that shows the funds' journey from origin to arrival, and a compliance officer's written sign-off.

The documentation requirement is not the hard part. The hard part is knowing when to apply it — and that is a transaction monitoring question as much as a KYC question. A source of funds issue that doesn't get flagged at monitoring never reaches the verification stage.

For more on building the monitoring programme that surfaces these cases, see our Transaction Monitoring Software Buyer's Guide and our complete guide to KYC and customer due diligence.

Talk to Tookitaki's team about how FinCense handles source of funds flags as part of an integrated AML and transaction monitoring programme.

Frequently Asked Questions

1. What is source of funds in AML?
Source of funds refers to where the money used in a specific transaction or business relationship comes from. In AML compliance, financial institutions review source of funds to understand whether the money is legitimate and whether it matches the customer’s profile and declared activity.

2. Why is source of funds important in AML compliance?
Source of funds is important because it helps financial institutions assess whether the money involved in a transaction is consistent with what they know about the customer. It supports due diligence, helps identify unusual activity, and reduces the risk of money laundering or other financial crime.

3. What is the difference between source of funds and source of wealth?
Source of funds refers to the origin of the money used in a particular transaction or account activity. Source of wealth refers to how a customer built their overall wealth over time. In simple terms, source of funds looks at where this money came from, while source of wealth looks at how the person became wealthy in general.

4. How do financial institutions verify source of funds?
Financial institutions may verify source of funds using documents such as bank statements, salary slips, business income records, property sale agreements, inheritance papers, dividend records, or other documents that explain where the money originated. The exact documents required depend on the customer, the transaction, and the level of risk involved.

5. When is source of funds verification required?
Source of funds verification is commonly required during customer onboarding, enhanced due diligence, high-risk transactions, or periodic reviews. It may also be requested when a transaction appears unusual or does not match the customer’s known financial behaviour.

6. Is source of funds verification required for every customer?
Not always. The depth of source of funds verification usually depends on the customer’s risk level, the nature of the transaction, and applicable AML regulations. Higher-risk customers and more complex transactions generally require closer scrutiny.

7. What source of funds documentation does AUSTRAC accept?
AUSTRAC's AML/CTF guidance accepts: recent pay slips (last 3 months), business financial statements or tax returns, property sale contracts with settlement documentation, investment account statements, and for inherited funds, a grant of probate or solicitor's letter. Verbal declarations are not sufficient for high-risk customers or transactions triggering enhanced due diligence.

8. Is source of funds verification required for every transaction?No. Source of funds verification is triggered by risk level, not transaction volume. Standard-risk retail customers verified at onboarding do not require SOF documentation for routine transactions. The trigger points are: EDD classification, PEP status, transactions inconsistent with the customer's stated financial profile, high-value cash transactions above reporting thresholds, and periodic review of high-risk accounts. See your regulator's specific guidance — AUSTRAC's Part 7, MAS Notice 626, or BNM's AML/CFT Policy Document — for the applicable triggers in your jurisdiction.