OpenChainGraph Suite · ART-537 · Bank Regulatory Reporting

QFC Part 371 Recordkeeping File Validator

Validates the shape of your own 12 CFR part 371 qualified-financial-contract recordkeeping file, the position/counterparty/collateral record set the appendix to part 371 requires, against its published record layout: required field presence, malformed notional or collateral values, and a repeated position identifier. Ties the file's declared totals to a supplied control-total summary you provide. A shape defect and a totals mismatch are two separate findings, never merged: a shape problem is checked first and routes to review, regardless of how the totals compare, and only a clean-shaped file with a totals disagreement escalates. Position identifier and counterparty identifier are enumerable low-entropy identifiers, salted before this tool computes anything with them; QFC type and currency code stay opaque strings throughout, with no table of part 371 contract-type or currency codes held here. Emits a hash-anchored OpenChainGraph v0.4 artifact carrying a §27.4 gate-policy decision at a predictable pointer.

Shape defect and totals mismatch, two separate findings Position and counterparty IDs salted, QFC type/currency opaque No control-total summary ⇒ did_not_run

🔒 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 holds no table of 12 CFR part 371 QFC contract-type or currency codes, offers no advice on whether a contract is a covered QFC, and is not a filing. It computes once when you press the button, stores nothing, runs on no schedule, and retains nothing. Position identifier and counterparty identifier are enumerable low-entropy identifiers within the meaning of SPEC.md §25.1; salt yours before pasting a file row here, since this tool never salts on your behalf and never sees a raw identifier's salt.

Recordkeeping file rows

The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own. Load a demo to see a structure defect, a totals mismatch, or a missing control-total summary. Position and counterparty identifiers in the demo are placeholder salted-form strings, so supply your own already-salted identifiers, never a raw one.

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

Institution reference

File rows (JSON array: row_ref, position_id, counterparty_id [both salted per §25], qfc_type, currency_code, notional_minor_units, collateral_minor_units) Tied control-total summary (JSON object: position_count, distinct_counterparty_count, notional_minor_units, collateral_minor_units; or leave empty to see did_not_run)

File structure errors

Totals reconciliation

Rationale

Execution Hash (SHA-256)

What this does not do

It does not salt a position or counterparty identifier for you, interpret a QFC type or currency code, hold a table of part 371 contract-type or currency codes, or determine whether a given contract is a covered QFC; you supply the file rows and the tied control-total summary, both already in the shape this tool expects. It is not a filing tool and produces no part 371 appendix submission format. A clean shape-and-tie-out pass is not a determination that the file would satisfy an examiner's part 371 review.

ART-535 validates the sibling 12 CFR part 370 output-file shape using the same discipline: a structural defect and a totals mismatch as two separate, never-merged findings. This node applies that same discipline to the 12 CFR part 371 QFC recordkeeping file, tying its totals to a caller-supplied control-total summary rather than to another node's coverage recompute.