Set limits on requests, claims or processes
Apply limits on requests, claims or processes, such as maximum claim amounts or time periods. Enforce these limits using IT system controls.
What this countermeasure matters
Not putting limits or boundaries in place, such as maximum claim amounts or time periods can lead to:
- insiders exploiting processes to commit fraud or gain access to sensitive information
- fraudsters receiving larger payments than they otherwise would
- fraudsters continuing to receive payments or services they are no longer entitled to receive.
How to put this countermeasure in place
Some ways to implement this countermeasure include:
- not allowing payments to be paid above a certain limit
- not allowing particular items/payments to be claimed together
- setting transaction limits for credit cards
- setting claiming limits for program payments
- requiring staff to book the cheapest available fare for work travel
- only allowing clients or their registered nominee to change bank account details
- only allowing Australian bank accounts to be recorded for program payments.
How to measure this countermeasure's effectiveness
Measure the effectiveness of this countermeasure by using the following methods:
- Confirm the existence of set limits.
- Confirm that the limits are always applied.
- Review reports to confirm that all payments are within limits/boundaries.
- Review a sample of completed requests or claims to confirm set limits were applied.
- Ask staff about processes to make sure they have a consistent and correct understanding of the set limits.
- Undertake pressure testing or a process walk-through to confirm that set limits are enforced.
- Confirm that someone cannot override or bypass parameters even when pressure or coercion is applied.
- Check if reporting or reconciliation processes exist to identify anything outside normal parameters.
This type of countermeasure is supported by: