First-depth synthetic demo

KYC/KYB Onboarding Proof

Replay why a synthetic business onboarding request was escalated for enhanced review by tracing onboarding evidence, beneficial ownership policy, AI/rule signals, reviewer action, approval history, and audit-ready evidence output.

Head of KYC OperationsKYB Onboarding LeadCompliance AssuranceInternal Audit
Evidence context4 synthetic records
Policy and obligationEnhanced due diligence trigger
Model or rule traceSynthetic Identity Risk Model v1.8
Human approvalKYC operations lead
Proof readinessReady, weak, and missing
Replay and outputAdditional verification required

Synthetic demo boundaries

Synthetic examples only. No customer data.

Read-only. No writeback or case mutation.

No production or autonomous decisioning.

No auto-disposition or source-system replacement.

No filing automation, compliance guarantee, or regulator approval.

Humans retain ownership and authorization.

Synthetic scenario

Synthetic decision scenario

KYC/KYB operations and compliance assurance need to prove why the request moved to enhanced review before approval and what evidence supported the routing decision. The scenario is generic and uses synthetic data only.

Synthetic KYC/KYB onboarding intake

Source event

A synthetic business onboarding request triggered risk indicators due to ownership complexity, incomplete beneficial ownership evidence, and inconsistent document metadata.

Escalation rationale

Decision being proved

Why the onboarding request was escalated for enhanced review instead of approved automatically.

Role-based ownership

Decision owner

KYC/KYB operations and compliance assurance.

Synthetic outcome

Outcome

Escalated for enhanced review with a synthetic proof pack prepared.

Synthetic assumptions

  • Generic synthetic onboarding metadata is used instead of real application identifiers.
  • Business, ownership, document, and risk references are abstract categories.
  • The source event is read-only and remains separate from onboarding, case, and source systems.

Capture

Evidence and source context

Synthetic business, ownership, identity, and document context is shown without real people, businesses, identifiers, geographies, or production connectors.

Application context

Synthetic onboarding application

Synthetic applicant type, onboarding channel, review queue label, and requested onboarding path.

Synthetic onboarding intake snapshot

Captured as source-context metadata with no real business identifiers.

Synthetic evidence

Entity evidence

Business registration evidence

Generic incorporation-status category, entity-type category, and registration-evidence completeness.

Synthetic registration evidence snapshot

Shows registration evidence status without real registries, jurisdictions, or registration identifiers.

Synthetic evidence

Ownership evidence

Beneficial ownership declaration

Generic ownership layers, control thresholds, and completeness status.

Synthetic beneficial ownership declaration

Links ownership evidence to the decision record without real owners, names, addresses, or documents.

Synthetic evidence

Control-person context

Control-person identity evidence

Generic role category, identity-evidence completeness, and review requirement.

Synthetic identity evidence checklist

Preserves identity-evidence status without real person names, document numbers, or identity records.

Synthetic evidence

Document quality

Document completeness check

Missing-field indicators, inconsistent metadata categories, and completeness result.

Synthetic document metadata check

Shows why document quality affected review routing without real files or contents.

Synthetic evidence

Risk context

Risk questionnaire response

Generic business activity category, expected activity profile, and questionnaire status.

Synthetic questionnaire response

Adds risk context without real business activity, address, or customer profile.

Synthetic evidence

Review history

Prior review notes

Synthetic prior-review context and unresolved evidence notes.

Read-only synthetic reviewer note

Links review context without real case history or reviewer names.

Synthetic evidence

Govern

Policy and obligation trace

Synthetic policy versions show how criteria, evidence standards, and escalation conditions can be attached to a replayable decision without making a compliance guarantee.

KYC-KYB-Onboarding-vSynthetic-02

KYC/KYB Onboarding Policy v2.8

Onboarding due diligence

Onboarding decision criteria

Decision criteria

Determine whether evidence supports approval, rejection, escalation, or enhanced review.

Required evidence

Onboarding application, registration evidence, ownership declaration, control-person evidence, and risk questionnaire.

Escalation condition

Enhanced review is required when ownership complexity or evidence gaps prevent automatic approval.

Review standard

Preserve evidence, rationale, policy version, and reviewer role before final onboarding decision.

Beneficial-Ownership-vSynthetic-04

Beneficial Ownership Evidence Standard

Beneficial ownership review

Ownership evidence sufficiency

Decision criteria

Determine whether ownership and control-person evidence is complete enough for approval.

Required evidence

Ownership declaration, control-person evidence, document completeness result, and analyst rationale.

Escalation condition

Route for enhanced review when ownership layers are incomplete or inconsistent.

Review standard

Capture reviewer rationale and evidence gaps as part of the decision record.

Enhanced-Review-Trigger-vSynthetic-03

Enhanced Review Trigger Standard

Enhanced review trigger

Escalation threshold

Decision criteria

Identify when risk indicators require additional review before onboarding approval.

Required evidence

Risk questionnaire, metadata consistency check, and ownership complexity signal.

Escalation condition

Enhanced review is required when multiple synthetic indicators remain unresolved.

Review standard

Record role-based approval and escalation rationale.

Onboarding-Approval-Control-vSynthetic-01

Onboarding Approval Control

Approval governance

Final approval control

Decision criteria

Require final review before approval when enhanced-review triggers were present.

Required evidence

Decision record, evidence lineage, policy trace, AI/rule trace, approval chain, and replay timeline.

Escalation condition

If required evidence is incomplete, approval remains blocked until enhanced review is complete.

Review standard

Produce an audit-ready evidence pack from rendered synthetic content only.

Govern

AI/rule trace

AI/rule trace is synthetic and illustrative. No live model inference is performed.

No AI runtime. No production decisioning.

This section is static explanatory content. It does not run AI, score live records, or make a production decision.

Synthetic Identity Risk Model v1.8

Synthetic signals

  • Synthetic document completeness rule
  • Synthetic beneficial ownership complexity rule
  • Synthetic metadata consistency signal
  • Synthetic risk-tier suggestion
  • Synthetic onboarding review priority label

Human review required

Feature group examples

Document completeness categoryOwnership complexity categoryMetadata consistency categoryRisk-tier category

Human review is required before enhanced-review routing or onboarding approval.

Human accountability

Approval and override chain

Role-based review is captured without real names. The page shows who reviewed the synthetic decision, what action they took, and whether an override was recorded.

Review step 01

Onboarding analyst

Reviews evidence, identifies ownership and metadata gaps, and records escalation rationale.

Rationale

Evidence is not sufficient for automatic approval.

No override recorded

Review step 02

KYC/KYB reviewer

Reviews analyst rationale, evidence gaps, and policy trace.

Rationale

Enhanced review is appropriate before approval.

No override recorded

Review step 03

Compliance assurance sample

Samples the synthetic decision for control trace, evidence sufficiency, and policy-version capture.

Rationale

Decision record contains evidence, policy, trace, and approval markers.

Assurance sample only

Review step 04

Enhanced review decision

Records enhanced-review outcome and evidence pack generation.

Rationale

Onboarding request requires enhanced review before approval.

Escalated for enhanced review

Assess

Proof readiness and proof gaps

The onboarding record preserves the proof path while exposing where documentary completeness would require source verification.

Ready

Source evidence context

4 synthetic evidence records retain source and decision-time context.

Ready

Policy and trace versions

1 governing control record and Synthetic Identity Risk Model v1.8 are attached to the replay.

Ready

Human accountability

KYC operations lead remains the recorded decision checkpoint.

Weak

Ownership-document completeness

Document metadata is illustrative and cannot establish beneficial-owner verification in a public synthetic preview.

Missing

Production source verification

Intentionally absent from the public lab because it contains no live connectors or customer data.

Prove

Replay timeline

The replay reconstructs the synthetic onboarding decision without approving an applicant or changing an onboarding workflow.

01

Application received

Synthetic onboarding intake is captured with source context.

Source event

02

Evidence attached

Application, registration evidence, ownership declaration, control-person evidence, document completeness, questionnaire response, and prior notes are linked.

Evidence lineage

03

Policy matched

Onboarding, beneficial ownership, enhanced-review, and approval-control policies are associated with the review.

Policy trace

04

Rule/AI trace recorded

Synthetic rule and signal summaries are preserved where applicable.

AI/rule trace

05

Analyst rationale captured

Onboarding analyst records why enhanced review is required.

Human rationale

06

Reviewer approval added

KYC/KYB reviewer confirms enhanced review is supported.

Approval chain

07

Enhanced review decision recorded

Final synthetic routing decision is recorded with role-based approval context.

Decision record

08

Evidence pack generated

A synthetic audit-ready evidence pack is assembled from the replay record.

Evidence pack

Evidence output

Evidence pack output

The page shows what a static synthetic evidence pack can contain. The JSON control creates a deterministic local file in this browser; it makes no backend call and performs no regulatory submission.

Decision record

A rendered record of the synthetic onboarding routing decision and owner.

Evidence lineage

Source-context links showing what evidence supported enhanced review.

Policy trace

Onboarding, ownership, enhanced-review, and approval-control policy versions.

AI/rule trace

Synthetic rule signal, score placeholder, and rationale summary where applicable.

Approval chain

Role-based review sequence, rationale, and override status.

Replay timeline

Ordered reconstruction of how the synthetic onboarding decision happened.

Onboarding audit summary

Concise summary for KYC/KYB QA, assurance, and internal audit review.

Buyer value

What this proves

The walkthrough connects identity and ownership evidence to versioned controls, risk signals, reviewer decisions, proof gaps, and replay.

Why the onboarding decision happened

The page links enhanced-review routing to evidence gaps, policy criteria, and human rationale.

What evidence supported enhanced review

Evidence cards show which onboarding, ownership, document, and risk context was available.

Which policy version applied

Policy trace cards preserve synthetic version labels, criteria, and review standards.

Whether AI/rules influenced the decision

Synthetic rule-trace content explains influence without running a model.

Who approved the decision

Role-based approval history records accountability without real names.

Whether the decision can be replayed for audit

The replay timeline and evidence pack show the decision can be reconstructed and defended.

Doctrine boundary

What this does not prove

The synthetic walkthrough demonstrates proof structure, not operational authority, customer deployment, or a regulated outcome.

Onboarding outcome

The walkthrough does not approve, reject, or onboard a person or business.

Production operation

The public walkthrough uses synthetic content and does not connect to or operate a production system.

Decision authority

RecordArc does not approve, reject, clear, escalate, or dispose of the underlying decision.

Source-system control

The walkthrough performs no writeback, case mutation, workflow execution, or source-system replacement.

Compliance outcome

The proof record does not guarantee compliance or imply regulator approval.

Customer implementation

The synthetic example is not evidence of customer data, deployment, adoption, or production readiness.

More synthetic workflows

Back to Decision Proof Lab

Map an onboarding decision proof path to RecordArc.

Use the synthetic walkthrough to assess how approved onboarding evidence and human review context could be reconstructed read-only.