Connect training materials, audiences, repeat schedules, employee completion and signed records in one manageable workflow.
Recurring compliance training is easy to describe but harder to manage well.
An MTO may know that certain staff need training repeatedly. The practical questions come afterward:
What should repeat? Who should receive it? How often should it repeat? When is the current assignment due? Who has completed it? Who is overdue? Was the training assessed? Has the completed record been signed?
When those questions are managed separately, recurring training becomes a cycle of manual reminders, employee lists and record keeping.
A better approach is to treat recurring compliance training as a managed workflow.
For a Money Transfer Operator (MTO), that means connecting the training material, audience, assignment frequency, due date, employee completion, assessment, sign-off and training history.
RemitSo's Training Programme is designed around exactly that workflow.
Recurring compliance training is training that is assigned to staff repeatedly according to a defined frequency, with each training cycle tracked through completion and its resulting record.
A useful recurring-training process should answer five questions:
In RemitSo, those questions are handled through Materials, Audiences, Assignments, My training, Reviews, Sign-off and Reports.
The platform manages the training cycle. The MTO remains responsible for deciding what training is required and how frequently it should be delivered.
In This Article
One of the most common assumptions about recurring compliance training is that every course should simply repeat annually.
That is not a universal rule.
For example, FINTRAC's current guidance for reporting entities says an ongoing training plan should document its training frequency and may use regular intervals such as monthly, semi-annually or annually, event-based training, or a combination. FINTRAC also says the programme should be tailored to the business's size, structure, complexity and exposure to money laundering, terrorist financing and sanctions-evasion risk.
AUSTRAC similarly requires ongoing AML/CTF training and says the frequency and extent should depend on the functions personnel perform and the relevant ML/TF risks. Its guidance gives different example frequencies for different personnel groups rather than imposing one universal interval.
This is where a recurring assignment becomes useful.
Recurring training begins with the material itself.
In RemitSo, the Materials section is where the training is created.
A training material can include:
Once the material is published, that version is frozen.
This is particularly useful for recurring training because a person's training history can remain connected to the material they were actually given.
Consider the difference.
A document can be edited after an employee completes it.
A frozen published version creates a much clearer record:
Employee → training assignment → published training version
That becomes important when the same training is delivered again later.
The goal is not simply to retain the name of the course. It is to retain a meaningful record of the training associated with the employee.
The next question is not how often the training repeats.
Who should receive it?
RemitSo handles this through Audiences.
An audience can be defined by:
That matters because recurring training requirements can differ across the people in an MTO.
A supervisor should not have to maintain a separate employee list every time a recurring assignment is created.
Instead, the audience defines the population that the assignment applies to.
This creates a simple relationship:
Audience = who
Assignment = what, when and how often
That separation makes the recurring training programme easier to manage.
Recurring training needs to survive changes in the employee population.
A training assignment might continue repeating after the original group was created. New hires therefore become part of the tracking problem.
In RemitSo, new hires can be picked up automatically through the relevant audience.
This means the supervisor does not have to rebuild the audience every time a new employee joins the applicable group.
People who are left out can also be recorded with a reason.
That gives the audience a more complete record of how the training population was defined.
The important point is that recurring training is managed against the audience, rather than being treated as a one-time spreadsheet of individual employees.
This is the central step.
In Assignments, the supervisor decides:
The repeat frequency is therefore part of the assignment.
That removes a major source of recurring-training administration: having to remember that a training requirement needs to be recreated later.
Instead, the requirement is defined once as part of the training workflow.
This material is required for this audience, within this completion period, and it repeats according to the defined frequency.
Assigning the training enrols the audience straight away.
Keep the material, audience, completion period and repeat frequency together in the assignment.
These two concepts are related but not identical.
| Timing field | Question it answers |
|---|---|
| Repeat frequency | How often does this training requirement occur? |
| Due date | When does the employee need to complete the current assignment? |
That distinction matters when managing recurring training.
An employee should be able to understand the current task without having to understand the entire recurrence schedule.
RemitSo's My training view provides that employee-facing clarity.
Assigned items are ordered by due date.
Anything past its date is shown in red.
Employees can also see what they have been asked to complete, what is waiting on someone else and what they have finished.
This turns the recurring requirement into a visible current task rather than an abstract schedule.
A recurring training programme should not rely on memory.
Once a training requirement is assigned, there needs to be a clear status for the current cycle.
The employee sees the assignment in My training.
The supervisor sees the broader status in Reports.
What do I need to complete now?
Who has completed the requirement and who is overdue?
This is a much cleaner approach than asking employees individually or maintaining a separate tracking sheet.
The recurring assignment provides the requirement; the views provide visibility into the current cycle.
A recurring training workflow can contain more than one completion step.
Where the material includes a written quiz, RemitSo provides a Reviews stage.
A person reviews each written answer against the model answer and awards the points.
The attempt decides itself once every answer has been marked.
The workflow therefore becomes:
Training completed → quiz reviewed → result determined
After the training is passed, it moves to Sign-off.
The compliance officer signs the passed training.
That sign-off writes the permanent record shown to the supervisor.
This distinction is valuable because it separates:
Employee completion
Reviewed and signed training record
Each has a different place in the recurring process.
Recurring training creates history.
An employee may complete the same requirement more than once over time.
A useful system therefore needs to answer both:
What is outstanding now?
What has this person completed previously?
RemitSo's Reports section provides an individual's full training history.
It also shows:
That makes the recurring programme more than a current-status dashboard.
It creates a continuing record of the training activity associated with an employee.
FINTRAC's guidance specifically says training records should help businesses track training and schedule the next training dates, while also demonstrating that an ongoing training programme is being carried out.
For a related guide to employee-level evidence and training records, read how to track employee compliance training.
Give employees a clear current task and supervisors the history, overdue status and signed evidence they need to review.
As the number of recurring assignments grows, finding the right material becomes part of administration.
RemitSo provides Categories for organising training materials.
Examples include:
This creates a useful separation:
Each part has a different purpose.
That makes the overall recurring-training workflow easier to understand and maintain.
The complete process can be reduced to one repeatable sequence.
This is the core difference between repeating training and managing recurring training.
A useful way for an MTO supervisor to think about recurring training is through five controls:
| Control | Question it answers | RemitSo area |
|---|---|---|
| Material | What training is being delivered? | Materials |
| Audience | Who needs it? | Audiences |
| Schedule | When and how often? | Assignments |
| Completion | Has the current cycle been completed and reviewed? | My training + Reviews |
| Evidence | What permanent record exists? | Sign-off + Reports |
When these five controls are connected, the recurring training process becomes much easier to manage.
The value is not that the system makes a decision about the MTO's training frequency.
The value is that once the MTO has made that decision, the system can manage the resulting workflow consistently.
Before adopting a system, an MTO should be able to answer these questions:
These questions are more useful than simply asking whether a platform is an “LMS.”
They evaluate whether the system actually supports the recurring training workflow an MTO needs to manage.
RemitSo's Training Programme connects each part of the recurring process.
Materials hold the training content, including text, documents, videos and quizzes, while each published version is frozen.
Audiences define who receives the training by department, role, location, everyone or named people. New hires can be picked up automatically, while exclusions can be recorded with a reason.
Assignments define the required material, audience, completion period and repeat frequency.
My training gives employees visibility into what they need to complete, what is waiting on someone else and what they have finished. Items are ordered by due date and overdue items appear in red.
Reviews provide a human review process for written quiz answers.
Sign-off gives the compliance officer the final signing stage for passed training and creates the permanent supervisor-facing record.
Reports show who has done what, who is overdue and an individual's complete training history, with signed records available as a file.
Categories organise the training materials under headings such as anti-money laundering, sanctions and data protection.
Together, these features create one recurring workflow:
Define the material → define the audience → set the assignment → set the repeat frequency → track the current cycle → review → sign off → retain the history.
There is no single universal interval that applies to every MTO or every compliance topic. Frequency can depend on the applicable requirements, the training topic, employee responsibilities and the organisation's circumstances. FINTRAC, for example, allows regular and event-based training frequencies within an ongoing training plan, while AUSTRAC says ongoing AML/CTF training frequency should be appropriate to personnel functions and ML/TF risks.
Define the training material, identify the audience, set the completion period and repeat frequency, assign the training, track employee completion, review the quiz where applicable, obtain sign-off and maintain the resulting history.
Yes. In RemitSo, an audience can be defined by department, role, location, everyone or named people.
Employees can see their current assignments ordered by due date in My training, with overdue items shown in red. Reports provide supervisor-level visibility into who is overdue.
Yes. New hires can be picked up automatically through the relevant audience.
Yes. Training material can contain a quiz at the end. Written answers can be reviewed by a person against the model answer.
Passed training waits for the compliance officer in Sign-off. Once signed, it creates the permanent record shown to the supervisor.
Yes. Reports provide the individual's full training history.
Yes. Signed records are available as a file for a supervisor through Reports.
For an MTO, it is a repeatable recordkeeping workflow:
What was assigned → who received it → when it was due → whether it was completed → whether it was reviewed → whether it was signed → what history remains
The frequency itself should come from the MTO's applicable requirements and training plan.
The technology's job is to make that frequency manageable, visible and traceable.
That is where RemitSo's Training Programme fits.
With Materials, Audiences, Assignments, My training, Reviews, Sign-off, Reports and Categories, recurring compliance training can move through one connected workflow rather than being tracked as separate manual tasks.
