After the account is open
Account changes are events, not emails
An address change, a margin add, a new authorized individual — each one carries a source, a status, and a route back to the custodian and the CRM.
Pending changes
Address changeCRM sync
Add marginAdvisor
CitizenshipPortal
Every change, attributed
Who asked, what changed, where it went
Maintenance is where a clean book quietly goes stale: a client updates an address in the portal, an advisor adds margin, the CRM syncs something inbound, and three systems drift apart. Sluice treats each change as a record with a source and a destination, and the same gate decides whether it can be posted.
- Sources are explicit: advisor, client portal, or an inbound CRM diff
- A change that would not pass gets held with the reason, not posted and reversed
- Posted changes go back to the custodian and the CRM, and the write is audited
Pending changes
Address changeCRM sync
Add marginAdvisor
Citizenship updatePortal
The same gate
A change can be not-in-good-order too
The gate is not something an account passes once. A margin add, a new authorized individual, an address that moves a client to a different jurisdiction — each one re-runs the same requirement set the opening ran, against the same firm policy.
- One engine for opening and for maintenance — not two rule sets to keep in step
- A change that would not pass is held with its reason, never posted and reversed
- The post back to the custodian and the CRM is audited like any other write
Add margin · AO-4774
Account eligible
Suitability on file
Investment objective
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