OpenChainGraph Suite · ART-519 · Government & Public-Money Payment Evidence

Payment Data Migration Completeness

Verifies that historical data moved from a legacy system to a successor is complete, value-preserving, and reconcilable — the evidence a migration actually needs. You declare per-partition source and target record counts and control totals (by period, agency, or rail — whatever partition scheme fits your migration), known exclusions with reasons, declared transformation rules, and any fields you observed changed. This tool never reads your source or target dataset: it reconciles the figures you already have. It checks every partition individually as well as the aggregate, because an aggregate that nets to zero while individual partitions do not is the failure a rushed sign-off misses. Emits a hash-anchored OpenChainGraph v0.4 artifact. Region-portable: every fact below is an input you declare, never a hardcoded country, currency, agency, or rail.

Per-partition and aggregate completeness Transformation coverage Sampled-verification residual risk

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

⚠ This tool does not read your source or target dataset — you supply counts and totals your migration tooling already produced. A clean result is not a determination that any underlying data quality control has been met; it is an arithmetic reconciliation over the figures you declare. It computes once when you press the button, stores nothing, runs on no schedule, and retains nothing.

Migration

The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own. Load the partition-inconsistent demo to see the flag this tool exists to catch.

Migration ID

As-of (ISO yyyy-mm-dd, your input, never a clock read)

Currency

Reconciliation tolerance (minor units, value variance allowed per partition and in aggregate) Declared partitions (JSON array: partition_label, source_record_count, source_control_total_minor_units, target_record_count, target_control_total_minor_units, known_exclusions [{reason_code, excluded_record_count, excluded_value_minor_units}], sample_verification {sampled, sample_size, discrepancies_found})

Declared transformation rules (JSON array: field, description)

Observed changed fields (JSON array of field names your own comparison found different pre/post)

Partitions

Transformation coverage

Rejected inputs

Rationale

Execution Hash (SHA-256)

What this does not do

It does not read your source or target system, extract records, or compute a migration from raw data — you run that separately and declare the counts and totals here. It is not a regime-specific migration tool: it does not validate ISO 20022 address fields, VIDA recapitulative statements, x402 protocol versions, or TLS/PKI cutover, and it does not score migration readiness maturity. A clean result is not a determination that any underlying data quality control has been met, and where a partition was verified by sampling only, this tool reports that as a residual-risk statement rather than a completeness verdict.

Prior art it does not duplicate, all regime-specific: ART-161 (VIDA recapitulative statements), ART-393 (x402 v2 protocol), ART-86 (TLS/PKI), RCA-03 (ISO 20022 PostalAddress24 fields), and 101 (ISO 20022 migration readiness scoring across 7 maturity dimensions — a self-assessment, not a completeness verifier). This node is the generic completeness verifier none of those provide. Part of the government-payment-lifecycle chain alongside the programme's other audit-evidence nodes as they ship.