1. Anti-Money Laundering
  2. Features
  3. Control Testing
Feature · Control Testing

Control Testing

Connect each control sample with its result and supporting evidence.

OverviewPending Control Tests
Anti-Money Laundering · Control Testing

Pending Control Tests

Approval conditions

New
ParentLine numberControlRevisionTested atSample size
ASS-67239480CNT-908679004 Oct700
ASS-17979120CNT-664661009 Oct220
ASS-16730830CNT-940395025 Oct690
ASS-48878900CNT-271410017 Oct430
ASS-80443690CNT-570881003 Oct460
6 of 6 records
ER-758Assessment tests · AT-32923
Pending
ParentASS-67239
Line number480
ControlCNT-9086
Revision790
Tested at04 Oct
Example screen with sample data

What you can do

Make the test result explainable

Control testing answers a specific question about how a control operated during the assessment period. The Control Tester records the sample, exception count and result against the relevant control. An evidence reference lets the Independent Reviewer inspect the basis for that result. A label marked Pass is useful only when the supporting work can be followed.

The assessment keeps the plan and period in view while each sample carries its own line number and revision. This helps the team distinguish a corrected sample from a separate test. Supporting files belong with the assessment so that the reviewer can read the work in context and understand which control the evidence addresses.

How the work is organized

  • Sample definition. Identify the assessment and control before recording sample size or exceptions. The exception count cannot exceed the sample tested. Resolve inconsistent quantities before sending the result for a decision, including mistakes caused by mixing samples from different periods.
  • Result and evidence. Use Pending while work remains unresolved and record Pass, Fail or Inconclusive according to the evidence. Every performed sample needs an inspectable evidence reference before review. An inconclusive result needs further attention even when no confirmed exception has yet been recorded.
  • Supporting files. Give each attachment a useful title and evidence type. Record who uploaded it and when. Agree whether the file is Internal or Shared before making it available to the people reviewing the assessment.

What to agree during setup

Define what constitutes a tested sample and how the team counts exceptions. Explain the evidence required for each control and how a reviewer should follow a reference to the underlying material. If evidence remains in a separate repository, arrange the connection and access with its owner before the pilot review.

Agree how the Control Tester records corrections and how the AML Program Manager decides that testing is ready to submit. Keep the selected period visible during that discussion. A result from a different period needs clear handling before it can support the current assessment.

Check the handoff on an actual case

Rehearse an alert escalation test where a sampled case lacks the evidence needed to establish timely review. The Control Tester records the exception and links the available material. The Independent Reviewer checks that the exception belongs to the tested sample and that the result reflects what the evidence establishes.

Repeat the rehearsal with the evidence reference removed and with an exception count larger than the sample. Both cases require correction before review can accept the result. Then add a corrected sample revision and confirm that the reviewer can distinguish the current evidence from the earlier work. Keep the failed control result visible when corrective work begins.

What your team sees

  • Pending Control Tests — Find samples marked Pending and prepare the evidence needed to establish their outcome.
  • Active Controls — Check the control description and owner while preparing a sample.
  • Assessment Review Queue — Follow the assessments that have moved from testing into independent review.

Follow the work through

Use testing to review, then follow unresolved findings into remediation and retesting.

What it keeps track of

Data model
Assessment tests
Evidence-based control test samples
Assessments
Scoped AML control assessments
Controls
AML controls mitigating identified risks
Record attachments
Evidence files attached to assessments

Who uses it

Permissions
Control Tester
, Independent Reviewer, AML Program Manager.
The tester records evidence; the reviewer evaluates it before an assessment decision.

Set up Anti-Money Laundering your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started