Wealth management client onboarding that stops not-in-good-order before the custodian sees it
Accounts open the same day, and not-in-good-order stops before the custodian sees it.
See one case, screen by screen ↓Wealth management client onboarding is the work of opening a new household's accounts: the application, IDs, transfer form, trusted contact form and advisory agreement checked for good order, Form CRS and the customer profile evidenced, a principal's approval and the submission to the custodian. Wealth Client Onboarding puts seven agents on every packet to read, check and draft, and stops not-in-good-order before submit; a new-accounts specialist sends and a registered principal approves.
AI in asset management: a buyer's guide to agentic AI for investment managers →
Updated
In wealth management client onboarding, every new account opening arrives as a packet: the account application, government IDs, a transfer initiation form with the prior firm's latest statement, a trusted contact form, the advisory agreement, W-9 or W-8BEN and beneficiary designations. A new-accounts specialist reads it against a paper checklist for the account type, re-keys it into the custodian's screen and checks the transfer form against the statement by eye, 60 to 80 packets a day.
Not in good order is found late. A signature line skipped, a trusted contact page left blank for owners over 65, a TOD split that does not total 100%, or one wrong digit in the account number on the transfer form. The delivering firm takes exception within one business day under FINRA Rule 11870, the advisor calls the client, and the client re-signs a whole new packet, days after choosing you. Meanwhile Form CRS delivery, the customer profile and the principal's acceptance must be on record for every account (SEC Rule 17a-3, FINRA Rule 4512).
Estimated split for one household with a transfer in, by hand and with the solution.
Seven agents read, check and draft every packet; a specialist sends, a registered principal approves.
Elena (67) and Marcus Ortega (69) of Rye, New York, sign a joint account with transfer on death and a $1,421,380.55 transfer in from Harborline Securities. Their advisor is Daniel Reyes, NY Midtown. Here is the wealth management client onboarding of that one packet at Quillfield Private Wealth, screen by screen, in the working solution.
Priya's Today screen shows 2,184 packets this week, 85.2% clean on first pass, 323 stopped before submit and 9 rejected after submit. Needs you lists six items, the Ortega household first: two stops and one decision, 1h 59m left on the clock. Beside it the agents report in plain words, and she can ask them anything.
Good-Order Checker: “323 were not in good order and stopped before submit; 64 need a specialist today, and 6 are within an hour of the 4-hour clock.”
The Packet Reader read envelope ENV-77188-OR: 7 documents, 21 pages, 44 fields, each with its place on the page, and all 6 signature lines signed. The Good-Order Checker applied the 14 rules for a joint account with transfer on death: 41 green, 1 amber, 2 red. The Ready to submit gate stays closed until the last red clears.
“The gate opens when the last red clears.”
The transfer form says 5PX-48311; Harborline's September 30 statement says 5PX-48317. Clicking the stamp shows the value on the page, the rule, the agent that checked it, its confidence of 0.99 and four sources, each with the passage highlighted.
“The delivering firm would take exception ‘invalid account number’ within one business day.”
The transfer form sits beside the prior statement: account title, tax ID, account type, delivering firm and value agree; the account number differs. The forecast names reject code 05, invalid account number. All 14 positions are listed, 13 to transfer in kind and one proprietary fund to liquidate. One initial on page 9 avoids the reject.
“The agent never changes a number; a correction needs the client's initial.”
The trusted contact page is blank and both owners are over 65, so firm policy makes it a stop. The Second Reader re-reads both stops on a different model without seeing the first reading, and agrees. The Profile & Disclosure Checker found Form CRS delivered October 9 at 14:02, before opening, and cleared Marcus's “Retired” employer from a March 2025 CRM note. The objective “Growth” against the Balanced Growth model is an amber: Priya accepts it with the reason code “Consistent with model risk band”.
Second Reader: “Digit 8 is ‘1’ on the form and ‘7’ on the statement; the trusted contact page is blank.”
Fix request ENV-77310-OR asks the Ortegas for two things, pre-filled: initial the corrected account number at Harborline Securities, and name a trusted contact or tick the box to decline. Everything else on the 21 pages is already in good order, so they do not re-sign the packet. The message is in plain words from Daniel Reyes, and the language can be English, Spanish, Simplified Chinese or French.
“Nothing is sent until you press Send.”
Priya sends the request at 10:58. Elena signs at 11:31 and Marcus at 11:38. The Good-Order Checker re-checks pages 9 and 12: the account number now reads 5PX-48317, initialed by both owners, and Sofia Ortega-Lane, their daughter, is named as trusted contact. The gate reads “Ready to submit · open”, and Priya sends the packet to Catherine Wu at 11:44.
“Catherine Wu approves openings for NY Midtown.”
In Approvals the Ortega opening is flagged “Large transfer · review the transfer check”. The drawer lists the evidence the agents assembled. Because the transfer is $1,000,000 or more, she confirms she reviewed the transfer check, 9 of 9 agreeing after the correction. She picks the reason code “All good-order checks met” and types her full name as her e-signature. Priya could not have approved it: specialists prepare packets and never approve them.
“The person who prepared a packet can never approve it. Agents never approve.”
The account file shows 10 of 10 items, each with the rule it answers: Form CRS delivered before opening (SEC Rule 17a-3(a)(24)), the customer account record (17a-3(a)(17)), Regulation Best Interest (Reg BI) information (17a-3(a)(35)), identification and sanctions (31 CFR 1023.220), the trusted contact and the principal's acceptance (FINRA Rule 4512), and the e-signature certificates. It seals when the account opens: account QPW-6603-1847, transfer validation due Monday, October 19.
“Kept 6 years after closing.”
Reports show not in good order by branch and cause: 14.8% this week, down 7.8 points from 22.6% eight weeks ago, and 0.46% rejected after submit. Miami is highest at 31 of 162 packets. The Branch Coach found that 9 of its 12 trusted contact stops used the old 2024 packet template, and drafts a coaching note for the branch principal.
“All 9 were delivering-firm data changes after validation.”
The same packet, seen by five of the people who carry it — what their week looked like, and what it looks like now.
Seven agents read, check and draft every packet; a specialist sends, a registered principal approves.
Reads every page from e-sign envelopes, branch scans, uploads and the mail room; classifies documents; extracts every field with its position; reads other languages beside an English reading.
Applies the firm's good-order rulebook by account type and stamps every field green, amber or red with the rule and the source; re-checks returned pages on arrival.
Reconciles the transfer form with the prior firm's statement digit by digit — account number, title, tax ID, account type and positions — and forecasts the exception the delivering firm would take.
Evidences Form CRS delivery before opening, the customer profile, the trusted contact, identity verification and sanctions screening.
Re-reads every red and every transfer over $250,000 independently, on a different provider's model, without seeing the first reading.
Drafts one e-sign request with only the fields to fix, pre-filled, in plain words and the client's language; tracks the return, reminds the client at 24 hours and tells the advisor at 48.
Finds each branch's top cause of not-in-good-order packets and drafts a coaching note for that branch's principal.
Maker and checker. The agents propose; a named person decides.
Ask the agents in plain words — why a packet is stopped, what the client must sign, which branch is struggling — or ask them to act. Every answer points to the page behind it.
Why is the Ortega packet stopped?
Two stops, both re-read by the Second Reader. The transfer form says 5PX-48311; Harborline's Sept 30 statement says 5PX-48317, so the delivering firm would take exception “invalid account number”. And the trusted contact page is blank while both owners are 65 or older. One amber waits for you: objective “Growth” against the Balanced Growth model.
Draft the fix request for the Ortega household
Drafted ENV-77310-OR with only two items for Elena and Marcus to sign: initial the corrected account number 5PX-48317, and name a trusted contact or decline. Nothing is sent until you press Send.
Which branches have the most NIGO this week, and why?
Miami is highest: 31 of 162 packets (19.1%). Its top cause is the trusted contact for clients 65+ (12 of 31), and 9 of those 12 used the old 2024 packet template. Next are Houston (17.8%) and Philadelphia (17.3%). The Branch Coach has a draft note for the Miami principal.
Add a rule: stop IRA packets whose beneficiaries don't total 100%
Rule GO-06 already covers TOD and IRA beneficiaries per tier. A stricter version that also stops contingent beneficiaries without a percentage, run on last week's 2,184 packets, would have stopped 7 more. It goes to the CCO as a change request.
13 screens from the working solution, on its sample data. Pick one to see it large.
Client onboarding automation has to follow your firm's own policy. The rules every packet is checked against, the thresholds and the clocks are settings — set once, changed with a second approver, and every change is logged.
| Setting | Default | Choose from |
|---|---|---|
| Good-order rules in force | 14 rules · firm policy WO-7.3 | Each rule applies by account type and either stops, asks a person to decide, sends to AML or asks for principal review |
| Auto-green when confidence is at least | 0.97 | Set per agent; a change goes to the CCO as a change request |
| Amber below | 0.90 | Below it, a person decides with a reason code |
| Second Reader re-reads | Every red and transfers of at least $250,000 | On a second provider's model |
| Principal reviews the transfer check | At or above $1,000,000 | Rule GO-14 |
| Prior-firm statement no older than | 90 days | A change to 60 days (GO-12) is waiting for the CCO's approval |
| Clocks | Specialist 4 business hours · principal same business day | At risk with 1 hour left · team lead told; branch manager told at 15:00 ET |
| Reason codes to accept an amber | Consistent with model risk band | Consistent with model risk band · Explained by a CRM record · Within tolerance (rounding or FX) · Client confirmed by phone (recorded line) · Other (note required) |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (industry estimates of paper NIGO rates cited by vendors; a wealth-technology vendor's survey of wealth firms, July 2024, on onboarding times for ultra-high-net-worth clients; FINRA Rule 11870 on transfer validation; SEC Rule 17a-3(a)(17), (a)(24), (a)(35), FINRA Rule 4512 and DTCC ACATS reject codes as context). Quillfield Private Wealth, the Ortega household, Harborline Securities and every person named on this page are fictional — characters and sample data in the working solution.
Wealth management client onboarding is the work of opening a new household's accounts: the application, IDs, transfer form, trusted contact form and advisory agreement checked for good order, Form CRS and the customer profile evidenced, a principal's approval and the submission to the custodian. Wealth Client Onboarding puts seven agents on every packet to read, check and draft, and stops not-in-good-order before submit; a new-accounts specialist sends and a registered principal approves.
A packet is not in good order when something the custodian or the firm requires is missing or wrong — a signature, a trusted contact, a profile field, an expired ID, a transfer form that does not match the statement. Here the Good-Order Checker applies the firm's 14 rules by account type to every field before submit, and the Fix Request Drafter asks the client once for only what is missing. In the demo week 323 of 2,184 packets were stopped before submit and 9 of 1,958 were rejected after.
The Transfer Matcher compares the transfer form with the prior firm's latest statement digit by digit — account number, title, tax ID, account type and positions — and names the exception the delivering firm would take under FINRA Rule 11870, such as reject code 05, invalid account number. It never changes a number; the client initials the correction on one page instead of signing a new form.
Yes. The Profile & Disclosure Checker finds the Form CRS delivery in the e-delivery log and checks that it came before opening — the date SEC Rule 17a-3(a)(24) asks firms to record — and checks each customer account record field listed in 17a-3(a)(17). Both land in the account file with identity verification, sanctions screening and the principal's acceptance.
Yes. Rule GO-03 stops a packet when owners are 65 or older and there is neither a named trusted contact nor a signed decline, reflecting FINRA Rule 4512's reasonable-efforts requirement. The fix request asks the client to name one or tick the box to decline, and the reply is re-checked when it arrives.
Yes. Digital client onboarding still meets paper, so the Packet Reader reads typed, handwritten and scanned pages and shows a Simplified Chinese, Spanish or French page beside its English reading, every figure cited. It will not guess a value on a page below 200 dpi; it names the page and asks for that one page to be rescanned.
Yes. Agents never approve, submit, send to a client unseen, clear a sanctions match, change client data or waive a rule. The specialist decides every amber with a reason code and presses Send, a registered principal who did not prepare the packet approves with an e-signature, and an AML analyst clears any possible list match.
It is not client onboarding software you configure from a blank screen: the Agentic Solution Engine builds and deploys it from your requirements and documents — your good-order rulebook, packet templates by account type and a sample of past packets — and it goes live once every quality gate has passed. In the working solution the last gate is a golden set of 1,200 packets reviewed against people's decisions and approved by the CCO.
Every dollar of a client's wealth traced to cited evidence before the BSA/AML Officer signs.
1-min demoReg BI Compliance ReviewEvery recommendation reviewed overnight; every flag decided by a principal, with evidence.
1-min demoIRA Rollover AnalysisEvery rollover file carries a specific, cited best-interest rationale, ready in minutes.
1-min demoWe'll run Wealth Client Onboarding on a sample of your own past new-account packets.