Field-level Data Flow Atlas

Who reads this section? Backend engineers building an integration with a specific destination (NSE UCC, NSDL BO, FIU-IND, etc.). Product / compliance readers tracing where each onboarded field ends up. Vendors checking which fields flow through their touchpoint. New to the site? Try Choose Your Role first.

Two views on the same dataset. Engineers building an integration with a specific destination land here, scan the destination sub-pages, and pull the master CSV for programmatic use. Product / compliance readers scan the per-section sub-pages to see where each onboarded field ends up.

TL;DR

• 1314 field-destination relationships mapped across 38 sections and 14 destination systems.
• 999 rows (76.0%) cite a public regulatory or vendor specification source.
• 315 rows are tagged [industry typical] where no public spec was reachable — verify with vendor before acting.
• Downloadable CSV: field-atlas-master.csv (all rows, all columns, quoted-CSV).
• AI-generated synthesis; verify each row against the cited circular or vendor doc before implementation.

Conceptual overview

Every field captured during onboarding (or generated during operations) ends up in multiple downstream systems with potentially different field names, formats, lengths, and update frequencies. This atlas maps those flows explicitly. The per-section view (below) groups by where the field is captured; the per-destination view groups by where it is consumed. The Master Dataset is the canonical source for field definitions; this atlas adds the downstream picture.

Some rows use bracket pseudo-sections like [trade], [margin], [dmf] for fields that are computed or generated at operations time (not captured during onboarding) and therefore have no home in the KYC-oriented master-dataset’s A–AC sections.

Browse by section (field-first)

Sections A through AC follow the Master Dataset order. Bracket pseudo-sections ([trade], [margin], etc.) for computed/derived fields appear after the lettered sections.

Section	Field-destination rows	Page
A	219	A
B	138	B
C	81	C
D	21	D
E	20	E
F	56	F
G	83	G
H	69	H
I	58	I
J	46	J
K	32	K
L	76	L
M	10	M
N	7	N
O	30	O
P	24	P
R	2	R
S	16	S
T	12	T
U	90	U
V	20	V
W	12	W
X	20	X
Y	25	Y
Z	19	Z
AA	13	AA
AB	17	AB
AC	11	AC
[cfr]	7	[cfr]
[dmf]	8	[dmf]
[ecn-meta]	14	[ecn-meta]
[ecn-tax]	5	[ecn-tax]
[margin]	10	[margin]
[peak-margin]	6	[peak-margin]
[reporting]	4	[reporting]
[settlement]	4	[settlement]
[surveillance]	2	[surveillance]
[trade]	27	[trade]

Browse by destination (system-first)

Each destination’s page shows the fields it consumes with format / frequency / quirks per row.

Destination	Field-destination rows	Page
Back-office (vendor-neutral)	260	back-office
KRA (Identity Registry)	124	kra
CKYC (Central KYC Registry)	122	ckyc
CDSL BO Opening	108	cdsl-bo
NSDL BO Opening	108	nsdl-bo
BSE UCC	86	bse-ucc
MCX UCC	86	mcx-ucc
NSE UCC	86	nse-ucc
Contract Notes / ECN	81	contract-notes
RMS (Risk Management System)	72	rms
Regulatory Reports (DMF / CFR / Peak Margin)	67	regulatory-reports
AML Reports to FIU-IND	55	aml-fiu
FATCA / CRS Reports	33	fatca-crs
DLT Comms (SMS / Email)	26	dlt-comms

Practical notes

• [industry practice] For any integration build, start at the destination sub-page — it lists every field the destination needs, its format, and its quirks. Then map back to the master-dataset to confirm source fields exist.
• [gotcha] Same field can have different names at different destinations (PAN at KRA, PAN_NO at NSE UCC, pan_number in back-office). The destination_field_name column is the destination’s literal name; the field_id is the source canonical ID.
• [cost optimization] Use the master CSV programmatically for impact analysis: grep -E '"A-pan_number"' field-atlas-master.csv lists every destination that consumes PAN.
• [risk trade-off] Rows tagged [industry typical] are best-guess descriptions of vendor-specific behavior; they’re useful for design but require vendor confirmation before production use.
• [industry practice] Bracket pseudo-sections ([trade], [margin], [dmf], etc.) cover computed or operations-generated fields that don’t exist at KYC onboarding time. The Field Atlas covers them; the master-dataset doesn’t.

Verified through

2026-05-14

---

AI-generated and not legal advice. See the project README for full disclaimer.