How to review and investigate findings with Myaza Trust
Turn a risk alert into owned casework. Review the reason, gather evidence and record a clear outcome that the next team member can understand.
Charles Archibong, Co-founder
· 3 min read
Key takeaways
- The case stays scoped to the intended customer.
- The assignee can inspect the linked evidence.
- Every material transition records its rationale.
- Resolution and closure remain distinguishable.
- A report retains the external filing reference when actually submitted.
Turn a risk alert into owned casework. Review the reason, gather evidence and record a clear outcome that the next team member can understand.
Before you begin
Investigation permissions and a review owner
Available alert or case evidence
Use a team member with permission for this control. Check the organisation and environment before changing a setting. Review the current price before a paid check or ongoing enrolment. Screenshots show an example workspace or the public integration reference; they do not show a real customer or a completed paid check.
Set up and use the capability
Step 1: Open the relevant review queue
Choose your organisation and environment, then open Risk Intelligence → Investigations and the alert or Review Queue view offered there. Search or filter for the known customer and finding. An alert is a triage signal; it is not yet a complete investigation. Check permission to read the alert before opening evidence.
Integration reference: Alerts
Step 2: Read the decision and its strongest reasons
Open the alert. Check the customer, activity or transaction reference, decision, risk score and reasons. Inspect the linked rule and screening evidence. Record what is actually known and what still needs confirmation. A Review or Block result explains the control’s response; it does not automatically establish criminal conduct or require a regulatory filing.
Integration reference: Alert or investigation?
Step 3: Open an investigation when more work is needed
Select Open investigation and choose an investigator from your organisation. You can group multiple alerts only when they belong to the same entity. Check the linked alerts and owner before saving. Use a concise investigation purpose so the assignee knows the question to resolve, rather than copying every alert detail into an unexplained case title.
Integration reference: Opening and assigning an investigation
Step 4: Work the evidence and timeline
Use the investigation workspace to inspect State, Why, Evidence, Owner and Next action. Add permitted supporting evidence and record review notes. Move through review or escalation with a rationale. Keep the original decision evidence available. New evidence belongs in the timeline; do not edit source records solely to make an investigation appear consistent.
Integration reference: Investigation workspace
Step 5: Resolve the finding, then close operational work
Choose the appropriate cleared, confirmed, escalated or inconclusive outcome and record the analyst rationale. Resolve records the evidence-backed outcome; Close completes the operational work. Reopening retains the earlier timeline. Clearing the investigation does not approve the customer’s KYC or confirm that funds moved. Apply any customer action through its separately authorised decision process.
Integration reference: Investigation workspace
Step 6: Prepare regulatory reporting only when required
Where your authorised team determines the case is reportable, draft the supported SAR or STR with a reason. Review and export the goAML XML for submission through your regulator’s process. Record the external filing reference when filed. A drafted report and a filed report are different states, and a report does not assert guilt. Keep the external submission and internal audit evidence together.
Integration reference: SARs & STRs
Get more from the capability
Assign a named owner and a clear review question early so an alert cannot remain indefinitely unowned.
Use grouped investigations for related alerts on the same customer, preserving each originating decision.
Read the audit trail and resolution rationale when reopening. Use confirmed downstream outcomes to support effectiveness analysis.
Test before relying on it
Run the supported Sandbox or simulator scenarios for this product. Where a tool is Production only, check access and scope first, then use only a permitted, deliberately reviewed Production test. A documentation screenshot or a successful page load is not an end-to-end integration test.
The case stays scoped to the intended customer.
The assignee can inspect the linked evidence.
Every material transition records its rationale.
Resolution and closure remain distinguishable.
A report retains the external filing reference when actually submitted.
Troubleshooting
I cannot change the case
Check investigation-management permissions; read access does not grant transition authority.
Resolve did not close the case
Resolution and operational closure are separate steps.
I need to add another customer’s alert
Keep different entity investigations separate rather than merging their personal evidence.
Open the setup and integration references
Read the integration reference
Back to Solutions. Choose the capability you want to activate, then follow its own guide.
Sources
Charles Archibong
Co-founder
Charles Archibong co-founded Myaza Trust. He writes about identity verification, financial technology, and the practical work of building trusted digital services.
