KYC Policy Name, kyc policy name, and kyc_policy_name are all the same
column, and column order never matters.
Two kinds of “required” apply:
- Required header — the column must exist in row 2, or the whole workbook is rejected.
- Required value — the cell must be non-blank on each data row, or that row is rejected (or skipped, for identifier columns that mark blank rows).
Upload order matters across categories: policies → subnetworks → data.
Subnetworks reference policies by name, and data rows reference subnetworks
by name. A reference to something not yet ingested fails at the row level.
KYC Certificate Policy
Directory:kyc_cert_policy/
Defines Know Your Customer verification policies. Each row configures a named
policy whose operation flags control which verification steps are active.
Policy workbooks configure the network, so they are accepted only from the
network’s governor.
Download Template
KYC Certificate Policy Template (.xlsx)
Required columns
Operation flag columns (headers required)
Each flag enables or disables a verification step in the policy. Accepted values:true/false, yes/no, y/n, 1/0 (case-insensitive).
A blank cell is read as false. All nine headers must be present.
Optional columns
KYB Certificate Policy
Directory:kyb_cert_policy/
Defines Know Your Business verification policies. Same structure as KYC
policies, with business-specific operation flags. Governor-only, like all
configuration categories.
Download Template
KYB Certificate Policy Template (.xlsx)
Required columns
Operation flag columns (headers required)
Same value rules as the KYC flags (blank reads asfalse):
Optional columns
kyb_policy (policy number; Ex. prefix marks example rows) plus the same
optional metadata columns as the KYC Certificate Policy category
(end_date_if_applicable, data source, storage system, consent fields,
permitted purpose scopes).
Subnetworks
Directory:subnetworks/
Configures network subnetworks that link KYC and KYB policies together with
effective date windows. One spreadsheet row becomes one subnetwork plus one
subnetwork–policy link per filled slot. The template provides 5 KYC slots and
5 KYB slots per row. Governor-only.
Download Template
Subnetworks Template (.xlsx)
Required columns
Policy slot columns
Each slot follows the pattern below, where{n} is the slot number (1–5 in
the template):
Per-slot rules, enforced row by row:
- A slot whose name, start, and end are all blank is skipped silently.
- A slot with a name but no start date rejects the row.
- A slot with a date but no name rejects the row.
- The end date is always optional — leave it blank for open-ended links.
KYC Furnish Data
Directory:kyc_furnish_data/
Consumer onboarding records furnished toward KYC certificates. Each row is one
consumer tied to a subnetwork; at ingest the row is matched against the
subnetwork’s linked policies by application_date, and runs once per policy
whose window
covers it (rows outside every window are filtered, not errored).
Download Template
KYC Furnish Data Template (.xlsx)
Required columns
Optional columns
KYB Furnish Data
Directory:kyb_furnish_data/
Business onboarding records furnished toward KYB certificates. Each row is one
business tied to a subnetwork, with the same subnetwork/policy resolution
behavior as KYC data.
Download Template
KYB Furnish Data Template (.xlsx)
Required columns
Optional columns
When the three verification timestamps are omitted, the furnish pipeline
falls back to the calendar date of
application_date for each one. Provide
them when you have the real dates — they become the evidence timestamps on
the resulting certificates.Quick reference
For layout, header normalization, and cell-type rules shared by every
category, see Workbook Format.