Preserve the source before improving the presentation
MEMA recommends a controlled intake that preserves originals and creates a working copy for extraction or annotation. Record when an item was received separately from when the document was created or the underlying event occurred. A recently scanned passport or exported audit history may contain older evidence; its upload date alone does not establish when the control was performed.
Use an evidence index with a stable identifier, source location, document or system date, receipt date, version, owner and related reference. File hashes can identify byte-identical copies; they do not prove that the contents are accurate. Separate different versions even where filenames are similar, and keep an explicit link to the canonical copy of a genuine duplicate.
Inspect the container as well as the visible document
Workbooks may contain images beside the response cells, hidden sheets, comments or embedded objects. Archives may contain nested folders and further ZIPs. Inventory these contents before concluding that no evidence was supplied. Exclude system files and OCR sidecars from substantive counts only through a recorded classification, not an unexplained deletion.
OCR helps search scanned documents, but it can misread names, dates, decimal points and negative wording. Visually inspect the source where those details affect the conclusion. Do not rely on the text layer alone to decide whether an identity document belongs to a client or whether an account number, expiry date or screening result supports the finding.
- Inventory top-level files and substantive archive members.
- Inspect workbook images and map them to the correct response.
- Flag protected, corrupt, incomplete or unattributed items.
- Reconcile every exception before making a completeness claim.
Use the evidence form that answers the question
A legible screenshot can be sufficient to demonstrate an attributable system field, workflow stage or setting. It may not show the full history, actor, time basis or document. Where the point concerns a transfer, verification report or legal agreement, request the relevant source record only if the image does not answer it. Asking for every screenshot to be printed to PDF adds work without necessarily adding evidence.
Check context carefully. A cropped image with no reference may not establish whose record is shown. A bank receipt can show money arrived without proving the payer’s underlying transaction for that customer. A displayed score may need the operative method or inputs to explain it. Record both what is accepted from the image and the narrow remaining question.
Maintain a usable audit trail
Use one controlling findings register and record each management response against the same point. Link later evidence and explain whether it answers, changes or contradicts the previous position. Keep dates in the source format until the format is established; record time zones and conversion assumptions explicitly. A transaction date, PDF creation stamp and screenshot date serve different purposes.
Limit access to personal data, use the agreed secure channel and test retrieval against the correct reference. For firms subject to regulation 40, apply the relevant retention and deletion requirements; do not assume one blanket retention period for every record across the business. The suggested index supports evidence handling but does not replace the firm’s legal retention assessment, privacy obligations or backup and restoration controls.
A fictional worked example
The starting point
No document was attached to the response.
A more useful approach
The workbook contains an attributable system screenshot, which we accept as evidence of the current setting. It does not show the earlier decision or approval history, so that specific source record remains needed.
The assessment credits what exists and explains the exact evidential gap instead of issuing a blanket repeat request.
Useful templates
Questions on this topic
5 questions
Are screenshots sufficient evidence for an FCA review?
Sometimes. A legible, attributable screenshot may establish a system field, current setting or workflow step. It may not show the complete history or the document underlying the entry.
Assess the question being answered. Request a source document only where its content, authenticity, context or transaction linkage is still needed; printing every screenshot to PDF does not necessarily strengthen the evidence.
What if a historic compliance record cannot be found?
Record what is missing, the searches made, the systems and periods affected, and any alternative evidence. Distinguish not yet located, inaccessible, never created and irrecoverable.
Explain the current risk response without presenting a new check as historic proof. Assess retention, notification and customer-impact implications with the appropriate specialists.
How does MEMA use a portal during a review?
A controlled workspace can organise evidence, link responses to points and retain versions. The important outcome is traceability: the reviewer can see what was supplied, what it proves and what remains.
Portal availability does not itself mean every item has been reviewed or accepted. Access, confidentiality, retrieval and the scope of any platform support are agreed for the engagement. Public demonstrations use fictional data.
Does a later screening check close an onboarding screening gap?
It can establish the later screening position, but it does not prove what was checked or decided at onboarding. Keep the historical limitation separate from the current relationship assessment.
Review the complete report, identifiers, coverage and reasoned disposition. A current clean result does not retrospectively establish that the earlier process operated.
How should we respond when a reviewer repeats a request already answered?
Point to the exact response, evidence identifier and page, cell or image location. Explain what it answers and ask the reviewer to state any narrower remaining gap.
The controlling register should credit the evidence, revise the assessment where warranted and retain the history. Neither side should need to restart from an unstructured email chain.
Official sources and further reading
Read the underlying material alongside the request or requirement that applies to your firm. MEMA's workflow suggestions are not additional regulatory rules.
- Money Laundering Regulations 2017: regulation 40 (opens in a new tab)
- FCA: customer due-diligence processes and controls findings (opens in a new tab)
- FCA Financial Crime Guide: money-laundering controls (opens in a new tab)
- FCA Handbook: general notification requirements (opens in a new tab)
- FCA: sanctions systems and controls findings (opens in a new tab)
How MEMA can help
We can help interpret the scope, organise evidence, test controls or deliver a defined remediation workstream. Where independent assurance is required, the scope and reviewer separation are agreed explicitly.
Discuss your firm's position