Where accounts land
The custodian's requirements, encoded
Every custodian wants the same account described differently. Sluice keeps the mapping, the form versions, and the record of what was filled from where.
Mapped
35/35
fields resolved
NFS · individual brokerage
Mapping
One application, each custodian's shape
The account you modelled and the payload a custodian accepts are not the same object. Sluice resolves one into the other, records which source filled each field, and refuses the send when a required field on the signable surface cannot be filled.
- NFS today, with the registration-type requirement set encoded
- API-only custodians supported: the payload is the application
- Per-field provenance, stripped of PII, kept as the drift key after signing
Ready to submit
35/35
fields resolved
NFS · individual brokerage
Adding one
A new custodian is data, not a fork
Custodian rules live as a transcribed registry, not as code branches. Adding one means encoding its registration types and its field mapping — the engine, the gate and every screen above them stay exactly as they are.
- Requirement sets are configuration, read at run time
- Forms custodians and API-only custodians run the same resolve step
- A required-but-unfillable field stops the send rather than shipping a blank
Custodian registry
NFS · Fidelity39 types
AltruistAPI-only
Field mappingper target
Reads from and writes back to
- NFS · Fidelity
- Altruist
- Envestnet
- Wealthbox
- Dynamics 365
- DocuSign
- Salesforce
- Redtail
See it against your own book
Bring a household that has given you trouble. Thirty minutes, no deck.
Request a demo