Custodians Supported

NIGO onboarding rules and portfolio CSV import both work against the same three custodians today, detected by export column shape, not a broker you have to select manually.

Charles Schwab

Recognized columns

SymbolMarket Value / Mkt ValCUSIPDescription

Fidelity

Recognized columns

SymbolCurrent Value / ValueCUSIPDescription

Vanguard

Recognized columns

SymbolTotal Value / ValueCUSIPInvestment Name

How detection works

01

Upload

A CSV export, held in memory only — never written to disk before normalization runs.

02

Fingerprint match

Column headers are matched case-insensitively against each known custodian's export shape to identify the source.

03

Strip and normalize

Every column that looks like an account number, SSN, tax ID, name, address, phone, or email is dropped unconditionally — before the row is mapped into ticker, asset type, weight, and market value.

Onboarding

New account applications for these three custodians are checked against each firm's own document and field requirements — not a generic checklist applied to every custodian the same way.

When a file doesn't match

A different custodian, or an export layout that's changed since this list was last checked — either way, an unrecognized fingerprint doesn't fail silently or guess at a bad parse. It returns a pointer to the manual import template instead, so the position data still gets in cleanly.

Working with a custodian not listed here?

Let us know