Skip to main content

Clarity to decide what’s next.

Match supplied evidence to your approved EDD requirements and make gaps, judgement calls and the next decision clear.

Map an EDD reviewSee the case

Illustrative workflow · MeshQu is not a screening provider, KYC platform or data source

Turn requirements into an operational review.

EDD requirements arrive as regulation, internal risk policy and jurisdiction-specific rules. Analysts apply them case by case, from a checklist and from experience. Two analysts can read the same requirement differently, and the reasoning behind an approval is hard to reconstruct a year later.

MeshQu turns those requirements into explicit checks: what must be established, what evidence shows it and who may decide. Your own agent can draft the checks from the source material. People review and ratify them before they are used on a case.

The rules remain your organisation’s. MeshQu does not interpret regulation for you, and it does not replace your screening, KYC or data providers.

From requirement to Decision Receipt.

  1. Requirements

    AML/KYC rules, internal risk policy and jurisdiction-specific requirements.

  2. Criteria

    What must be established for this customer, derived from the requirements and ratified before use.

  3. Evidence

    Identity and business documents, ownership, screening results, transaction and customer data, external sources and analyst findings.

  4. Judgement

    Findings that are ambiguous or cannot be settled by a rule, assessed by an analyst who records their rationale.

  5. Authority

    Analyst, senior reviewer, MLRO or delegated approver, as your policy assigns.

  6. Outcome

    Approve, reject, escalate or request further evidence.

  7. Decision Receipt

    A signed record of each recorded assessment, tied to the policy version in force.

Illustrative. Your requirements, roles and outcomes come from your own policy.

Use what you have. Record what was decided.

  • Evidence

    Gather evidence from wherever it lives

    Screening, registry, document and customer data stay with the providers and systems you use. MeshQu links what each check needs by reference and digital fingerprint.

  • Checks

    Automate the repeatable checks

    System checks, agents and manual checks can run against the same rules. Automating one check does not change what the case is judged against.

  • Judgement

    Preserve analyst judgement

    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.

Follow an EDD review from trigger to approval.

A fictional corporate customer is referred for enhanced due diligence. Screening, ownership analysis and an analyst’s review each add to the case before a delegated approver decides.

Each recorded assessment is signed. The analyst’s review and the approval are linked records alongside it, so the chain shows what was checked, what needed judgement and who acted at each step.

Map an EDD reviewAML workflow recipe (opens in a new tab)
  1. Initial assessment recordedSystem · EDD policy v3 · screening result linked
  2. Enhanced review requiredBeneficial ownership not yet verified
  3. Ownership evidence supplied, assessment run againRegistry extract linked by reference
  4. Analyst finding recordedEDD analyst · rationale recorded
  5. Approval recordedMLRO delegate · within delegated authority
Illustrative EDD review · fictional customer

Know exactly what supported the decision.

For each recorded assessment, the Decision Receipt keeps the policy version in force, the context and evidence references supplied, the actor identifier your systems provide and the outcome. Integrity and signature checks together let another party check whether the bound record has changed.

An audit log tells you that a system did something. A Decision Receipt keeps what governed the decision: which policy applied, what the case was assessed against and what came out.

The sample below is a separate signed sandbox record from a synthetic fraud review. It shows the structure of a receipt, not the EDD case above.

External review package4 checks remaining
Reviewing
Policy in force
Evaluating
Supporting evidence
Queued
Accountable authority
Queued
Decision history
Queued
Assembling review packagePortable · signed

4 checks remaining

Signed authorised push payment (APP) fraud exampleInspect the decision recordOpen the identifiers, signing key and transparency record behind a synthetic fraud review.
Signed sandbox exampleAPP fraud review · payment released

This synthetic record captures an analyst-authorised payment release. It is not a reimbursement decision and contains no customer data.

How Decision Receipts work
Receipt ID
747a7983-6b8b-45fc-a8b8-ebfb64edfd53
Decision
ALLOW
Policy snapshot ID
2e3d955d-6fc8-4cdc-b2c7-6161e942e752
Timestamp
2026-08-13T06:17:48.482Z
Rules evaluated
4
Signature kid
meshqu-sandbox-2026-06 · ed25519
Transparency anchor
rekor.sigstore.dev · log 2447666518

Review the decision later.

Policies change. Evidence is refreshed. Reviewers move on. A periodic review or a regulator’s question can arrive months after the decision.

The receipt stays tied to the state at decision time: the policy version that applied and the evidence references that were used. A later review is its own linked record, so the history shows what was decided then and what has changed since.

What the record establishes, and what it does not.

The recorded basis

  • The policy version the assessment used.
  • The context and evidence references supplied.
  • The verdict, the outcome and the linked reviews.
  • A signature that can be checked against trusted keys.

Your organisation’s judgement

  • Whether the evidence was genuine and complete.
  • Whether the policy meets your regulatory obligations.
  • Whether the customer should have been accepted.

Follow the decision further.

Map one EDD decision.

Tell Qu how an EDD case moves through your team today: the checks, evidence, judgement and approval involved. If MeshQu can help, we’ll map the decision with you.

MeshQu is currently available for research, evaluation and design-partner deployments. Production availability and support commitments are agreed per engagement.

Map an EDD reviewBook a call