Submit it Once,
in good order.
Stop sending NIGOs to your custodian. Sluice validates and routes every account before it can be rejected — so it opens in good order the first time. AI proposes; the rules engine disposes.
- Holding the score
- Non-US client · AML lockdown-10
- Funding ≥ $1M · supervisor-8
- OFAC screen · verifying-4
The reading
One score you trust at a glance. It reads 100 only when every check is affirmed and zero holds are open — never progress-theatre.
Who actually signs
Beneficial owners are computed by multiplying ownership through every sub-entity, down to the natural people. CDD ≥ 25%, enforced.
- Non-US client · AML
- Funding ≥ $1M · supervisor
- OFAC · verifying
Decided up front
Rules trigger holds and reviews off the data — deterministically, before anything reaches the custodian.
Every rule is transcribed from a production account-opening system — the 39-type matrix, the entity beneficial-ownership bubble-up, the fail-closed gate. Not a greenfield guess.
Others clean up NIGOs after the custodian rejects them. Sluice shifts quality control upstream — validating documentation and data before submission, so only in-good-order business enters the flow.
AI proposes. The rules engine disposes.
The model drafts every field in seconds. Then a deterministic engine checks each one against the custodian's registry and your firm's policy — and affirms it or holds it. Nothing posts on the model's word.
One gate. Every account clears it before it moves.
Validation, screening, and routing all resolve at a single fail-closed checkpoint — live in the browser as you work, and again on the server as the source of truth. Nothing reaches the custodian until the gauge reads 100.
The rules don't advise; they decide. AI proposes the answers — the engine verifies every one against the custodian's registry and your firm's policy before anything posts.
Quality control, moved to where it's cheap — the front of the flow. Caught up front, an issue is a field to fix; caught downstream, it's a rejected account and a phone call.
The gate clears an account check by check — before it posts.
Sanctions screening, beneficial-ownership CDD, signer resolution, documents, ACAT eligibility — each resolves deterministically. The account only reads good order when every one is green.
- Sanctions / OFAC screen
- Beneficial ownership · CDD
- Signer bubble-up
- Documents · in good order
- ACAT eligibility
Validation and routing, decided up front.
Rules trigger holds and reviews off the data — deterministically, before anything proceeds. Nothing reaches the custodian until the gauge reads 100.
- Non-US client → AML lockdown
- Entity → beneficial-ownership CDD
- Funding ≥ $1M → supervisor review
Entity-of-entity, resolved to who actually signs.
Signers bubble up through entity chains. Beneficial owners are computed by multiplying ownership through sub-entities. Control persons and the regulatory invariants — enforced, not assumed.
- Signer bubble-up through sub-entities
- CDD owners ≥ 25%, ownership multiplied
- Control-person invariant · ownership ≤ 100%
One custodian baseline. Every firm's policy on top.
A shared NFS baseline of 39 registration types, transcribed from the real custodian registry. Each firm layers append-only holds — tighten the floor, never lower it. Onboarding is three inputs.
- 39 registration types, day one
- Append-only firm overlay
- Same client, different firms — your policies
Every change re-runs the same gate before it posts.
A citizenship update, an address synced from the CRM — each runs the same gate before it posts back to the custodian. Inbound diffs are gated, not trusted. In good order stays in good order.
- Citizenship update → re-gate
- CRM address sync → re-gate
- Post-back only in good order
Not just new accounts — every request your firm runs.
Account opening, cashiering, address changes, transfers — each lands in the right queue and only goes out once it's in good order. Need to track a new kind of work? Add a queue yourself, in minutes — no IT project, no waiting on a vendor.
Pull relationships in. Interpret them. Feed good order anywhere.
Households and entity structures arrive however your firm holds them — a CRM, a custodian feed, a spreadsheet, the data a moving advisor brings from their last firm. Sluice ingests them, interprets the members, accounts, and ownership chains into one relationship, and pushes the in-good-order result wherever it needs to live.
Enter a household once. Reuse it everywhere. No re-keying, no copy that drifts.
More than a gate — a platform your firm runs on.
White-label, per firm
Make it the firm's own — the wordmark and the whole palette derive from one accent, toggled on for the firms you onboard. No rebuild, just a token.
Secure self-profiling links
Send a client a secure link to profile themselves. Their answers land straight in the relationship — gated, deduped, ready for the advisor to review.
Team-scoped visibility
Advisors, principals, and the OSJ each see exactly their book. Supervision and signing roles map to the org and are enforced per user.
Three inputs, then it's live.
Custodian
Policy
Client data
One reading you can trust at a glance.
- ● In progress — data still missing, nothing blocking yet.
- ◐ Verifying — impure checks running: OFAC, CIP, ACAT.
- ● Blocking — a hold is open; the arc caps below 100 and the account cannot post.
- ✓ In good order — zero blocking, every check affirmed; the arc completes in teal.
Evidence-grade by design.
Isolated by the database
Append-only evidence
PII sealed at rest
AI that never decides
In Good Order, the first time.
Built for the front office that can't afford a NIGO — validated and routed the first time, or held before it can do damage. That's the whole product.