Compliance Monitoring & Testing
MT-03Sample real transactions against the controls every month
How Leela would run itMonthly · each month, on the prior month’s activity
Walked through · exampleThe requirement
Each month a sample of actual transactions is pulled and tested against the controls that should have applied to them. This checks that controls worked on live activity, not that a policy describes them.
- Applies
- Tell Leela about your company to see whether this applies.
- Status
- Setup needed
Tell Leela how you handle it today, or hand it over: see what’s next.
What Leela would do · example run
- Day 1Defined last month’s population4,812 transactions · example
- Day 1Drew the sample60 transactions
- Day 1Prepared the testing workpaperPopulation, sample, procedure
- Day 2Queued item testing for your testerYour tester completes the results
What Leela keepsThe evidence this obligation leaves, as the work happens
Ready for your bank or examinerContents
- 01PopulationLast month’s transactions and the query that produced them
- 02SampleThe items drawn, and how they were drawn
- 03ProcedureThe controls each item is tested against
- 04Item-level resultsPass or exception for each item, with severity
- 05TesterWho tested each item
- 06DateWhen the testing was done
Evidence pack
Monthly testing workpaper
Compliance Monitoring & Testing §4 · example
6
of 6 parts
An example run. The steps follow the obligation’s action and Leela’s note; the records are the obligation’s evidence in the policy library.