Why a Written AML Program Is Only the First Step
Creating a written AML program is an important milestone for any money transfer store.
It defines the internal procedures your business follows, including when customer activity should receive additional review, what documentation may be requested, and what steps employees should take when store-defined thresholds are reached.
But once those thresholds are written down, a practical question remains:
How does the store actually review customer activity across multiple providers in day-to-day operations?
This is where many remittance stores encounter a significant operational challenge.
A Written Policy Does Not Automatically Create Visibility
Suppose your AML program states that customer activity should receive additional review when:
- combined transactions exceed $10,000 in a month;
- a customer sends to an unusually high number of beneficiaries;
- a customer completes many transactions in a short period.
These rules may be clearly documented.
The challenge is that the information needed to apply them is often spread across several provider systems.
Western Union sees only Western Union transactions.
MoneyGram sees only MoneyGram transactions.
RIA sees only RIA transactions.
No single provider sees the customer’s full activity across your store.
Example: When No Provider Sees the Full Picture
Imagine your store’s AML program states that customer activity should be reviewed when total transactions exceed $10,000 in a month.
A customer sends:
- $4,000 through Western Union
- $3,500 through MoneyGram
- $3,000 through RIA
The customer has sent a combined total of $10,500.
Each provider sees activity below its own internal controls.
None of them sees the consolidated total.
If the store does not review activity across all providers, this customer may never appear in any operational review.
Why Manual Monitoring Rarely Works Consistently
In theory, employees could export reports from each provider, match customer names, sum transaction totals, and compare the results against the store’s AML thresholds.
In practice, this is difficult to do consistently.
Daily operations are busy, customer names may appear differently across systems, and the process requires time and attention that most stores do not have.
As a result, many written AML procedures are difficult to apply manually in real-world multi-provider environments.
Excel Can Work as a Temporary Solution
Some store owners try to solve this problem with Excel.
For stores with relatively low transaction volume, a spreadsheet can be a practical starting point. If a location processes a small number of remittances each month, staff may be able to enter customer activity manually and review consolidated totals periodically.
The challenge is that every transaction must be recorded by hand.
As volume grows, keeping the spreadsheet current becomes increasingly difficult. When staff are serving customers at the counter and managing a line, manually updating Excel or reviewing transaction history across multiple provider portals often becomes impractical.
Several store owners who contacted us were already using spreadsheets to track customer activity. Their main challenge was not understanding what needed to be reviewed, but keeping the spreadsheet accurate and up to date as transaction volume increased.
For many stores, Excel works as a temporary solution. But once transaction volume increases, manually consolidating customer activity can become time-consuming and difficult to sustain.
The Operational Gap Between Policy and Practice
This is one of the most common gaps in small remittance stores.
The AML program defines what should be reviewed.
But the store does not have a practical way to see which customers meet those criteria across the business as a whole.
Without consolidated visibility, employees may follow procedures correctly when a provider requests documentation, but still struggle to apply the store’s own thresholds consistently across all customer activity.
What Stores Need in Practice
To apply a written AML program effectively, many multi-provider stores need a way to:
- consolidate customer activity across all providers;
- compare combined activity against store-defined thresholds;
- review transaction frequency and beneficiary patterns;
- identify which customers deserve additional review.
The store still defines the criteria.
The store still decides what actions to take.
The operational challenge is simply making the relevant information visible in one place.
From Written AML Program to Daily Review
A written AML program establishes the rules.
The next step is having a practical way to review customer activity against those rules.
Once the store can see consolidated activity in one place, employees are in a stronger position to apply the procedures that the business has already defined.
Final Thought
Creating an AML program is essential.
But a written policy alone does not tell employees which customers are approaching the thresholds defined by the store.
For multi-provider remittance stores, the real challenge is turning written procedures into day-to-day visibility.
When customer activity is consolidated across all providers, the store can apply its own AML program more consistently and with greater confidence.
Want to learn more about building and applying an AML program in your remittance store?
We’re launching a free course for money transfer store managers — with a free certificate of completion. Join the waitlist →
Frequently Asked Questions
Why is a written AML program not enough?
A written AML program defines the store’s internal procedures, but the store still needs a practical way to review customer activity and determine when those procedures should be applied.
Why is this more difficult for multi-provider stores?
Each provider sees only the transactions processed through its own platform. No single provider shows the customer’s total activity across the store.
Who defines the thresholds?
The store defines its own internal thresholds and procedures based on its AML program, applicable requirements, and business judgment.
What happens when no single provider flags a customer’s combined activity?
If the store does not have a consolidated view of customer activity across all providers, that customer may never appear in any operational review — even if their combined transactions have reached the store’s own internal thresholds. This is why consolidated visibility matters for multi-provider stores.
Continue Reading
See how stores configure their own transaction thresholds and review customer activity against those criteria inside MsB Manager.
Read next: