Regulators do not ask whether you have a training course. They ask whether you run an ongoing training programme that fits your risks, whether each person was trained for their role, and whether you can prove it. FINTRAC expects a documented, ongoing training plan with a stated frequency. AUSTRAC expects ongoing AML/CTF training whose frequency and depth fit what each person does and the risks they face. For most money transfer operators, the course is the easy part. The hard part is the calendar: who needs what, how often, who is overdue, and where the signed record is when an inspector asks. This guide is for MLROs, compliance heads and HR leads who own that calendar.
It covers what the regulators say, a sample calendar by department, and a worked example of a new hire, an overdue refresher and a sign-off. Frequencies in the examples are illustrative; your own risk assessment decides yours.
What regulators expect: a programme, not a yearly course
A common assumption is that every course repeats once a year. That is not a universal rule.
- FINTRAC says an ongoing training plan should document its training frequency, which may use regular intervals such as monthly, semi-annually or annually, event-based training, or a mix, and should fit the business's size, structure and complexity. It also says training records should help you track training and schedule the next dates.
- AUSTRAC requires ongoing AML/CTF training, with frequency and extent depending on the functions people perform and the money laundering and terrorism financing risks they face. Its guidance gives example frequencies, such as every 6 to 12 months for compliance officers and senior management and every 12 months for customer-facing staff, and is clear these are examples, not one fixed interval.
The practical reading for an operator is the same in both: decide frequency by role and risk, write the decision down, add event-based training when something changes, and keep records that show each cycle was completed.
A sample training calendar by department
Most operators find it easiest to plan by department, because that is where both the risks and the line managers sit. The seven departments below are the ones RemitSo ships ready-made.
| Department | Core training | Repeat | Also when | Signed off by |
|---|---|---|---|---|
| Senior Management and Board | AML/CTF duties, risk appetite, sanctions exposure | Every 12 months | A new regulatory requirement or a major finding | MLRO |
| Compliance | Full AML/CTF programme, sanctions, suspicious activity reporting, typologies | Every 6 months | New typologies or a change in reporting rules | MLRO; the MLRO's own by a deputy or board member |
| Customer Service and Onboarding | ID checks, red flags, scam warnings, when to escalate | Every 12 months | On hire, before handling customers | Compliance |
| Payments and Treasury | Sanctions, unusual payment patterns, payout red flags | Every 12 months | A new corridor or payout partner | Compliance |
| Finance | AML for finance teams, refunds and chargebacks as risk signals | Every 12 months | A change in refund or reconciliation process | Compliance |
| Technology | Data protection, access control, handling customer data | Every 12 months | A security incident or new system access | Compliance, with the technology lead |
| Agents and Branch Staff | Cash red flags, ID checks, structuring, when to refuse | Every 12 months | On appointment, before serving customers | Compliance |
Write a short reason beside each frequency, tied to your risk assessment. "Every 6 months, because Compliance makes the reporting decisions" is the kind of sentence an inspector wants to read.
Useful habit: keep event-based training on the same calendar as the repeats. A new corridor, a new payout partner or a new typology should create an assignment with a due date, not an email saying "please read this".
Doing it with RemitSo
RemitSo, a white label remittance platform, offers a staff training programme as an optional add-on, built to be read by an inspector. Your team still decides what to train, how often and who signs off. The platform runs the cycle and keeps the proof.
| Part | Question it answers |
|---|---|
| Materials and versions | What is being taught, and which version? |
| Audiences and departments | Who must complete it? A department can be used to say who must complete a training |
| Assignments | Which material, for which audience, by when? |
| My training | What do I need to do now? Every staff member can see and complete their own training without extra permissions |
| Review desk | Who marks written quiz answers? |
| Sign-off desk | Who confirms the training is complete? Nobody signs off their own |
| Records | What can we show an inspector? Signed records |
Reminders come through alerts that reach the people subscribed to them: Quiz answers waiting to be marked, Training completion waiting for sign-off and Required training long overdue, which repeats once a day until it is fixed. A department's head is told when someone in it falls behind on required training. Switching a department off keeps its membership and history.
A new hire, an overdue refresher and a sign-off
Here is how one month of the calendar runs for an operator using the training programme.
| Day | What happens | Who acts |
|---|---|---|
| Day 1 | A new customer service adviser joins. HR puts them in Customer Service and Onboarding from their profile. That department is set to complete "ID checks and red flags", due within 10 days and before they handle customers alone | HR; the training lead |
| Day 1 | The assignment appears in the adviser's My training with its due date | The adviser |
| Day 6 | The adviser finishes the material and the quiz, which has two written answers. Quiz answers waiting to be marked goes to the review desk | The adviser |
| Day 7 | A compliance analyst marks the written answers against the model answers. The adviser passes | Compliance analyst |
| Day 7 | Training completion waiting for sign-off goes to the sign-off desk. The MLRO signs it off, and a signed record is kept | MLRO |
| Day 12 | Meanwhile, a branch agent's annual refresher passes its due date. The head of Agents and Branch Staff is told | Head of department |
| Day 26 | Still not done. Required training long overdue starts going to its subscribers once a day. The head of department suspends the agent's customer-facing duties until it is complete | Head of department; compliance |
| Day 28 | The agent completes the refresher; it is reviewed and signed off. The daily alert stops | Agent; compliance; MLRO |
When an inspector later asks "show me this adviser was trained before handling customers", the answer is a signed record, not an email thread. When they ask "what do you do when someone is overdue?", the answer is the day 12 and day 26 entries above, with a named owner for each.
Watch out: completion is not the same as sign-off. A person can finish a course and still be waiting for review. Count someone as trained only once the signed record exists.
Questions to settle before your next cycle
- Is each department's frequency written down, with a reason tied to your risk assessment?
- Which events trigger extra training, and who creates the assignment?
- Can new joiners be kept from customer-facing work until their training is signed off?
- Who marks written answers, and who signs off, and who signs off the MLRO's own training?
- What happens on the first overdue day, and on the fourteenth?
- Can you produce a signed record for any named person within an hour?
For tracking completion across the whole team, see the admin features and the add-on price list. For the wider programme, see compliance and risk management. Read the release notes, or book a demo.
Sources
- FINTRAC, Compliance program requirements (ongoing compliance training program)
- AUSTRAC, AML/CTF training
Checked October 2026. Regulations change; confirm current requirements with the regulator or your adviser.
Frequently asked questions
How often should MTO staff repeat compliance training?
There is no single interval. FINTRAC allows regular and event-based frequencies within a documented plan. AUSTRAC says frequency should fit each person's functions and risks, and gives examples such as every 6 to 12 months for compliance officers and senior management and every 12 months for customer-facing staff.
Can training be assigned by department?
Yes. In RemitSo a department can be used to say who must complete a training, and its head is told when someone in it falls behind.
How are overdue staff chased?
The department head is told when someone falls behind on required training. If it stays undone, a "Required training long overdue" alert goes to its subscribers once a day until it is fixed.
Can someone sign off their own training?
No. In RemitSo nobody signs off their own training, and the sign-off produces a signed record.
Is the training programme included in the platform fee?
No. The staff training programme is an optional add-on, licensed separately. Every staff member can still see and complete their own training in My training.