What is Compliance Monitoring as a Service?
An always on layer that watches a roster of entities for changes across sanctions and recall data, generating a logged alert when something changes rather than requiring a manual recheck.
How do I get alerted when a customer appears on a sanctions list after onboarding?
Registering the customer on a monitored roster means any future appearance on a watched list fires an alert automatically, rather than waiting for a scheduled recheck.
What is ongoing compliance monitoring and why is point in time screening not enough?
Point in time screening checks a status once. Sanctions lists and recall data change continuously, so a clean result at onboarding doesn't stay accurate indefinitely. Ongoing monitoring rechecks on a regular cadence and flags any change.
How do I monitor thousands of entities for sanctions changes without a full compliance team?
Roster based monitoring runs the recheck automatically across every registered entity, which is the part that doesn't scale manually past a small number of relationships.
How do I get notified when an Australian food recall affects one of my suppliers?
Suppliers can be added to the monitored roster, and a recall affecting one of them fires an alert, checked automatically against the FSANZ feed.
How does sanctions rescreening work in practice?
Monitored entities are rechecked against sanctions data to match the list's own update cycle. Any new match fires an alert automatically.
How do I prove to a regulator that I ran ongoing monitoring between onboarding checks?
The audit trail of every monitoring run and every event generated is the record that demonstrates monitoring actually happened continuously, not just at onboarding.
What events trigger a CMaaS alert and what does the alert payload include?
An entity appearing on or being removed from the OFAC SDN list triggers an alert. A change in ASIC or ABR registration status, or a change in active food recalls for a monitored supplier, also triggers an alert. The payload includes the entity, the event type, the source, the detection timestamp, and the matched record detail.
How do fintechs with limited compliance headcount do continuous customer monitoring?
Automating the recheck removes the need for a person to manually rerun and record checks on a schedule, which is usually the actual constraint for a small team.
What is the difference between batch rescreening and event driven compliance monitoring?
Batch rescreening reruns checks on a fixed schedule regardless of whether anything's changed. Event driven monitoring surfaces a change as it happens, which is the model used here.