Enhanced due diligence decisions with MeshQu
How does MeshQu support an enhanced due diligence (EDD) decision, and what does it not do?
Enhanced due diligence (EDD) is the deeper review a regulated firm applies to higher-risk customers. MeshQu turns your EDD requirements into explicit rules: what must be established, what evidence shows it and who may decide. People ratify the rules before use. Each recorded assessment is tied to the policy version in force. The rules remain your organisation’s: MeshQu does not interpret regulation for you or replace your screening, KYC or data providers.
In more detail
EDD requirements arrive as regulation, internal risk policy and jurisdiction-specific rules, and analysts apply them case by case. Your own agent can draft the rules from the source material; people review and ratify them before they are used on a case. Screening, registry, document and customer data stay with the providers and systems you use, and MeshQu links what each check needs by reference and digital fingerprint. System checks, agents and manual checks can run against the same rules. Where a finding needs interpretation, the analyst’s rationale and the role they acted in are recorded with the case, as your systems record them. Authority is whoever your policy assigns, such as an analyst, a senior reviewer, the MLRO or a delegated approver, and the outcome can be to approve, reject, escalate or request further evidence. Each recorded assessment has a signed Decision Receipt. The receipt stays tied to the state at decision time, and a later periodic review is its own linked record, so the history shows what was decided then and what has changed since.
Limits
Screening, registry, document and customer data stay with your providers. MeshQu links them by reference and digital fingerprint; it does not establish that they are genuine or complete.
The record does not establish whether the policy meets your regulatory obligations or whether the customer should have been accepted.
Roles such as analyst or MLRO are recorded as your systems supply them. MeshQu does not authenticate the actor.
The EDD case on the page is fictional. The receipt sample shown there is a separate signed sandbox record from a synthetic fraud review, not the EDD case.
MeshQu is currently available for research, evaluation and design-partner deployments. Production availability and support commitments are agreed per engagement.
Where it applies
Make what must be established for a higher-risk customer, the evidence that shows it and who may decide explicit before cases are worked.
Keep analyst judgement, escalations and the final approval as linked records beside each assessment.
Answer a periodic review or a regulator’s question from the policy version and evidence references used at decision time.
Sources
MeshQu docs — Recipe: AML screening workflow (opens in a new tab)
An engineering walkthrough of a multi-step AML case: screening, analyst review and final disposition. This entry relies on it for the scope boundary only, not for chain sealing or offline verification.
MeshQu docs — Decision chains (opens in a new tab)
How the steps of a case are linked, and why a later step never edits an earlier record.
MeshQu docs — Actor attribution (opens in a new tab)
How roles such as analyst or MLRO are recorded, and that MeshQu does not authenticate actor identities.
MeshQu docs — Trust model (opens in a new tab)
Evidence is bound by reference and digest; source material stays with its custodian.
Related answers
Evidence, references and source custody
What does MeshQu do with the evidence behind a decision, and does it establish that the evidence is true?
What MeshQu is not
What is MeshQu not, and which problems does it deliberately not solve?
Decision Receipts: what the record contains
What is in a Decision Receipt, and what does it prove?
Human-in-the-loop automation with MeshQu
How can we automate checks in a review process while people keep authority over the decision?
Next step
Read more on meshqu.com/enhanced-due-diligence