Households
One record per person, however many accounts they hold
Households are not a list of accounts. They are people, entities, and the roles that connect them — and re-typing a person for every account is where the errors come from.
Chen Family Office
Margaret ChenPrimary owner
Chen Family TrustTrustee
Apex Capital LLC30% owner
The graph
Model the family, not the form
A trust with two grantors, a beneficial owner at 30%, and a control person is a graph, not a set of fields. Sluice stores it that way: each person exists once, and each account borrows them in whatever role they hold. Fix a date of birth in one place and every application that depends on it is correct.
- People and entities in one member pool, assigned by role per account
- Entity ownership carried as a percentage, so FinCEN's 25% test resolves itself
- Roles are the real ones: primary and joint owner, trustee, beneficial owner, control person, authorized individual
Chen Family Office
Margaret Chenon 5
David Chenon 3
Apex Capital LLCEntity owner
Chen Family Truston 1
Team scope
Advisors see their book; the firm sees the firm
A firm is made of advisor teams, and a team's book is not everybody's business. Scope is enforced at the same chokepoint every screen reads through, and underneath it by row-level security in the database itself — not by a filter a future page could forget to apply.
- Team-scoped views for advisors, firm-wide for principals and admins
- Row-level security is FORCED in Postgres, under a role that cannot bypass it
- The application connects as a non-owner role, so a missed filter fails closed
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