A money service business in the Philippines is a BSP-registered non-bank that moves or exchanges value, such as a remittance and transfer company, a money changer or foreign exchange dealer. Each is a covered person under the AMLA, with the same customer due diligence, transaction monitoring and reporting duties as a bank, scaled to its own risk.
Most online material about a "money service business" describes the United States, where the term is a FinCEN category with its own registration regime. Under BSP and the AMLC the obligations are different, so a compliance programme built from US sources will miss the local reporting clocks and thresholds.
This guide is written for compliance officers at remittance firms, money changers, foreign exchange dealers and pawnshops who need the BSP and AMLC obligations in one place, without the US framing.
What counts as a money service business under BSP?
A non-bank that provides remittance or money transfer, money changing, or foreign exchange dealing, and in practice also the pawnshops and other covered persons that handle cash at scale.
BSP supervises money service businesses as non-bank financial institutions under the Manual of Regulations for Non-Bank Financial Institutions. It has issued a revised framework tightening their governance, reporting and AML controls, as reported during the consultation. The categories that matter for AML are remittance and transfer companies, money changers and foreign exchange dealers. Pawnshops are regulated under their own BSP rules but are also covered persons under the AMLA, so the reporting duties below apply to them as well.
The point for a compliance officer is that registration with BSP is the entry condition, and covered-person status under the AMLA is what brings the reporting obligations. One does not replace the other.
Why is a Philippine MSB different from a US one?
Because the term describes a different regime. In the United States a money service business registers with FinCEN and files a currency transaction report and a suspicious activity report; under BSP and the AMLC it files a covered transaction report and a suspicious transaction report, on different clocks.
The vocabulary overlaps and the obligations do not. A US suspicious activity report, or SAR, runs on a calendar-day clock from detection. A Philippine suspicious transaction report, or STR, is due the next working day from the determination of suspicion, a difference our guide to SAR versus STR sets out. An MSB that imports a US template will file on the wrong timeline. Treat every US-sourced MSB reference as a different system until proven otherwise.
What are an MSB's core AML obligations?
The same four that apply to any covered person: identify customers, assess risk, monitor transactions, and report covered and suspicious transactions on time.
An MSB has to identify and verify its customers, apply enhanced due diligence to higher-risk ones, monitor activity against expected behaviour, and file reports with the AMLC. The reporting clocks are the part most often misread. A covered transaction report is due within five working days, and a suspicious transaction report by the next working day from the determination of suspicion, under the AMLC's GoTRACS issuance at Sections 4.2 and 5.4(b). A covered transaction is a cash transaction exceeding ₱500,000 in one banking day, under Republic Act 9194. We set the two clocks out in full in our STR versus CTR guide.
Which money-laundering risks are specific to MSBs?
Cash intensity, one-off customers, speed, and use as a layer between other accounts.
An MSB handles cash and moves value quickly, often for customers it will not see again, which removes much of the relationship context a bank relies on. Four risks follow. Structuring just below the ₱500,000 threshold, smurfing across several branches or agents in one day, remittances inconsistent with a customer's declared profile, and use of the business as a layer to move scam or mule proceeds. The threshold aggregates over a banking day, so several smaller cash transactions that together exceed it are still covered, which is also how structuring is meant to be caught. Our library of money-mule detection scenarios covers the pass-through patterns that reach these businesses, and the scam context appears in our post on scam compounds and money mules.
How should a lean MSB compliance team set up monitoring?
Aggregate by customer and by agent, segment thresholds by product, and watch the area just below the reporting threshold.
An MSB's monitoring should do three things a generic rule set does not. First, aggregate across agents and branches, because a customer who stays under the threshold at each of five locations is the case the rule exists to catch. Second, segment thresholds by product, so a remittance customer, a money-changing customer and a forex customer are not judged against one average. Third, watch the band just below ₱500,000 for repeated activity, because structuring lives there. These are applications of the ideas in our transaction monitoring guide, and alert quality still has to be tuned against outcomes, as our note on threshold tuning describes. For smaller operators, our piece on lean compliance at rural and cooperative institutions covers the resourcing reality.
What happens if an MSB files late or misses a report?
A late or missing report is non-compliance with the AMLC's submission requirements, and BSP applies monetary penalties for violations of its rules.
The GoTRACS issuance treats a submission beyond the prescribed period as non-compliance. BSP's penalty framework for MSBs sets monetary penalties for each violation and for continuing ones. The exact amounts and the governing circular should be confirmed with compliance counsel before any figure is quoted, because the schedules differ by entity type. The practical exposure is not only the fine. A pattern of late or missing reports is what an examiner treats as a programme failure, which is the standard our guide to independent testing describes.
How does Fyscal ARCX support an MSB programme?
Fyscal ARCX gives a small MSB team the monitoring and reporting controls a bank runs, without a bank's headcount. In Transaction Monitoring, a compliance team defines its own variables and rules, aggregates activity across customers and agents, and tests a rule against historical data before activation. Regulatory Reporting prepares the covered and suspicious transaction reports from the case record and tracks each filing deadline, and Case Management keeps one case per customer with a timestamped trail. Connectors bring in data from the systems an MSB already runs.
If you want to see structuring across agents caught and reported in one workflow, book a walkthrough of Fyscal ARCX and bring a volume pattern you want to test.