Why a monitoring credit was refunded instead of used
If you've noticed a monitoring credit was refunded rather than used when you turned on ongoing monitoring for a client in EngageAML, this article explains why, and how to fix it.
How the Anti-Money Laundering check works in step 6
In step 6 of the EngageAML workflow, turning on ongoing monitoring for a client triggers an Anti-Money Laundering (AML) check. This check only runs once per client:
If the AML check passes, ongoing monitoring stays enabled for that client.
If the AML check fails, ongoing monitoring is turned off for that client.
In both cases the credit is used, because the check has actually been performed.
Why some checks don't run at all
Before the AML check can run for an organisation entity, EngageAML needs two pieces of information:
An Australian Business Number (ABN) entered in step 3 for the organisation entity.
A matching Australian Company Number (ACN), which EngageAML looks up automatically based on the ABN.
The AML check only runs if both the ABN and the ACN are valid. If either one is missing or invalid, EngageAML does not run the check, and your monitoring credit is refunded automatically. This is expected behaviour: you're only charged for a check that's actually carried out.
Checking the reason in the status column
In the step 6 screen, the table's Status column shows you why a check didn't run for a specific organisation entity. You'll see one of the following:
ABN Required — no Australian Business Number has been entered for this organisation entity. Go to step 3 and enter the ABN, then return to step 6 to try again.
ACN Required — an ABN has been entered, but EngageAML couldn't find a matching Australian Company Number for it. Double-check the ABN entered in step 3 is correct for this organisation entity.