At a glance
- NIGO ("not in good order") means a new-account or transfer file came back because something in the paperwork or data didn't clear the custodian's checks: treat it as a document-and-data problem, not a judgment call about the client.
- The check table below pairs nine NIGO causes we recommend checking, including two specific to ACAT transfers, with the check to run before a file leaves your desk.
- A worksheet below turns NIGO rate, cycle time, and touches per account into a baseline you can measure again after you change anything.
- AI can pre-fill a custodian form from discovery notes and flag what it can't fill in; which fields are complete enough to submit, and when to escalate, stay with your operations team.
What does NIGO mean in account opening?
NIGO stands for "not in good order." A file is NIGO when the custodian returns a new-account or transfer submission because something in it doesn't clear the custodian's checks: a missing signature, a blank required field, a document that doesn't match another one in the same file. Treat a NIGO as a defect in the paperwork, not a judgment about the applicant, unless the specific cause says otherwise.
Advisory firms don't set these rules themselves. Kitces' AdvisorTech coverage notes that for opening client accounts at a custodian, "the steps are dictated by the custodian: They decide which forms need to be filled out, what client information is needed, whether the form is 'In Good Order' or not" [1]. A custodian such as Schwab, Fidelity, or Pershing sets its own forms; the table below is organized by cause, not custodian.
- A NIGO is caught after your firm has already submitted the file, by the custodian's own intake process.
- Every day a file sits in NIGO status is often a day it isn't funded, and always a day someone has to track it down.
The same Kitces coverage points out that "even though most custodians have switched to a paperless account opening process, there are still issues like manual data entry and insufficient field validation to prevent NIGOs that make the process slower than it should be" [1]. A paperless form only prevents a NIGO if its fields are checked before submission, not after.
The NIGO pre-submission check table
Custodian paperwork automation only pays off if it catches issues before submission, not after the custodian's own review does. The table below sets out nine NIGO causes, what each looks like, the check to run before submission, and a suggested owner. The last two apply to an ACAT transfer rather than a new account; confirm the receiving custodian's own title-match and in-kind-eligibility requirements.
| Cause | What it looks like in the file | Pre-submission check | Who checks it |
|---|---|---|---|
| Missing or unexecuted signature | A signature line is blank, or a wet-ink form was submitted unsigned | Confirm every required signature is present and dated | Account-opening associate |
| Blank required suitability or identification field | A field your own intake form requires — income, net worth, experience, time horizon — is empty | Check completeness against your own required-field list, not only the custodian's | Account-opening associate |
| Expired or mismatched identification | The ID's expiration date has passed, or its name doesn't match the application | Compare expiration date and name against the application | Ops/compliance reviewer |
| Address mismatch across documents | The application address differs from a supporting document's address | Compare addresses across every document in the file | Account-opening associate |
| Missing entity or trust authorization | A trust, LLC, or other entity account is missing its authorization document | Confirm the authorization document is on file before submission | Ops/compliance reviewer |
| Missing joint-owner or authorized-signer signature | A joint or multi-signer account is missing one required party's signature | Check signer requirements against who actually signed | Account-opening associate |
| Illegible or corrupted form | A scanned or uploaded form is unreadable in part or in full | Open and review every page before sending it, not only the summary screen | Account-opening associate |
| ACAT account-title match | Whether the account title must match the delivering firm's records exactly | Confirm the requirement with the receiving custodian, then compare titles character-for-character | Ops/compliance reviewer |
| ACAT in-kind asset eligibility | Whether every position can be held in kind at the receiving custodian | Confirm the eligible-asset list with the receiving custodian, then check each position | Ops/compliance reviewer |
The account-opening associate resolves what's visible in the file: a blank field, an unsigned line, a mismatched address or signer. Identification, entity authorization, and either ACAT row go to an ops or compliance reviewer: each calls for a compliance judgment, and the ACAT rows depend on the receiving custodian's requirements.
The checks above tell you whether a file is ready, not whether they're reducing NIGO. Measure before and after with the same three figures.
| Metric | Baseline | After | What a change tells you |
|---|---|---|---|
| NIGO rate | Files returned NIGO ÷ files submitted, over a full quarter | Same calculation, once the checks above are in use | A falling rate suggests the checks catch what the custodian would otherwise have caught |
| Cycle time | Days from first client signature to a funded account | Same measurement, same account types, after the change | Shorter time alongside a falling NIGO rate suggests the checks aren't a new bottleneck |
| Touches per account | Times a file is opened, corrected, or reassigned before funding | Same count, same account types, after the change | Fewer touches suggests files arrive more complete, not just get corrected faster |
What are the most common NIGO reasons?
Even after a custodian moves to a paperless account-opening process, Kitces' AdvisorTech coverage names issues like manual data entry and insufficient field validation as causes that persist [1]. We recommend grouping the rest into three categories: identity and suitability information, signatures and authorizations, and, for a transfer, confirming the account title and asset eligibility with the receiving firm.
- Identity and suitability data: expired or mismatched identification, address mismatches, and blank required fields.
- Signatures and authorizations: missing signatures, missing joint-owner or authorized-signer signatures, and missing entity authorization documents.
- Transfer-specific checks: confirming the account title matches the delivering firm's records, and confirming every position can be held in kind at the receiving custodian.
Check your own NIGO log before assuming which cause dominates at your firm: a firm opening mostly individual taxable accounts may see more identity and signature causes, while one handling advisor transitions may see more ACAT-specific ones.
How do RIAs automate client onboarding across systems?
Because the custodian sets the account-opening steps [1], RIAs connect systems that already hold that data — a CRM like Salesforce Financial Services Cloud, Redtail, or Wealthbox — instead of retyping it: "digital onboarding tools like Skience, Docupace, and Marstone can take client information from sources like the advisor's CRM and populate it into the custodian's digital account opening interface to save the advisory team from having to populate each form manually" [1].
An ACAT transfer runs on shared infrastructure. ACATS is built to "automate the transfer of customer accounts and assets between brokerage firms and banks" [2], and states "ACATS integrates with DTCC's Fund/SERV® for Fund Solutions" [2] — the same integration its Fund Solutions page describes as automating "transfers and re-registrations" [3]. The table's two transfer rows confirm the receiving custodian's own title-match and in-kind-eligibility requirements.
BNY Pershing, a custodian, describes its platform's integration this way: "our capabilities, APIs and third-party solutions connect to create an integrated technology experience tailored to your business" [4]. Applied at onboarding, that integration can let a CRM or planning-tool field reach a custodian's form instead of being retyped.
Can AI pre-fill custodian forms from discovery notes?
Yes, for fields the notes already state. A model can read discovery-meeting notes, extract facts such as stated income, employment, and investment experience, and map each to the matching custodian-form field. Configure it to leave a field blank and flag it, rather than guess, when the notes don't clearly state a value. Most custodians have already moved to a paperless account-opening process [1], so the gap AI can help close here is accurate prefill and field mapping, not digitizing the form.
Models help with:
- Extracting facts the notes already state, such as employment, income range, or investment experience.
- Mapping each fact to the matching custodian-form field, with a link back to the note.
- Flagging a field the notes don't clearly cover, instead of guessing at a value.
Stays with people:
- Confirming any pre-filled answer that touches suitability or risk tolerance.
- Resolving any field the model flagged rather than filled in.
- Final review against the check table above before it reaches the custodian.
What should an ops person still review before submission?
Run the check table against the file, then check your own NIGO log for what tends to slip through at your firm: every signature matches the signer, and suitability, identification, and KYC (know-your-customer — confirming who the client is) details are consistent across documents. For a transfer, confirm the account title and asset eligibility against what the receiving custodian requires. Account acceptance itself stays with your firm's own operations and compliance staff, not with this checklist.
Where to start: a first scoped workflow
Start with one account type and two or three causes from the table above, not the whole queue.
- Pull your own NIGO log for one quarter
See which causes actually show up at your firm and how often, rather than assuming the table's order.
- Pick one account type and two or three causes
Start with a clear, checkable cause — a missing signature, an expired ID — before ones needing closer comparison.
- Run the baseline worksheet for that account type first
Measure NIGO rate, cycle time, and touches per account before you add or change anything.
- Build the check into the workflow before submission
Run the check table against every file leaving your desk for the account type you picked.
- Expand one cause at a time
Add the next cause once the current ones run cleanly, so a gap in one isn't masked by volume from the others.
When this doesn't apply
- Your NIGO rate is already low, and the fixes above would cost more staff time than they'd save.
- Your custodian's own intake platform already validates every required field reliably. Measure its gaps before adding a layer on top.
- Most of your exceptions are genuine suitability judgment calls, not the kind of defect this table catches.
- You don't have a NIGO log to baseline against yet; the worksheet above depends on building one first.
Frequently asked questions
What does NIGO mean in account opening?
NIGO stands for "not in good order." A new-account or transfer file is NIGO when the custodian returns it because something in the paperwork or data doesn't clear its checks — a missing signature, a blank required field, or a mismatch between two documents in the file. It describes a defect in the submission, not necessarily a judgment about the client.
What are the most common NIGO reasons?
Beyond manual data entry and insufficient field validation on the intake form itself, we group the remaining causes into missing or mismatched identity and suitability information, missing signatures or authorizations, and, for transfers, confirming the account title and asset eligibility with the receiving firm.
How do RIAs automate client onboarding across systems?
Because the custodian, not the advisory firm, sets the account-opening steps, RIAs connect the systems around that process so client data is entered once and lands consistently: a CRM holding the client profile, a financial-planning tool holding discovery data, and an integration that maps both into the custodian's own form fields instead of retyping them.
Can AI pre-fill custodian forms from discovery notes?
Yes, for fields the notes already state. A model can read discovery notes, extract facts like income, employment, and investment experience, and map each to the matching custodian-form field with a link back to the source passage. Configure it to leave a field blank and flag it, rather than guess, when the notes don't clearly state a value.
What should an ops person still review before submission?
Confirm every required signature is present and matches the signer, that suitability and identification fields are complete and consistent across documents, and, for a transfer, confirm the account title and asset eligibility against what the receiving custodian requires. Confirm with compliance or counsel which recordkeeping and client-identification requirements apply to the file.
Related reading
- Document review with human approval covers the broader extract-compare-approve pattern this check draws on.
- Human-in-the-loop AI governance covers how to decide which calls stay with people, beyond onboarding.
- Legacy finance workflow automation covers automating around a system without a modern API.
- AI agent implementation describes how a system like this is scoped, tested, and handed over.
- 360° AI Blueprint helps rank an onboarding build against other candidates.
Sources
- Kitces.com, "The Latest In Financial #AdvisorTech – August 2026" (accessed 2026-09-30)
- DTCC, "Automated Customer Account Transfer Service (ACATS)" (accessed 2026-10-01)
- DTCC, "Fund Solutions" (accessed 2026-09-30)
- BNY Pershing, "Wealth Management Technology Platform" (accessed 2026-09-30)
More in Document intelligence
340B Program Documentation: Where AI Agents Reduce Audit Risk (Not Replace Compliance Officers)
How AI agents can assemble 340B program documentation, from split-billing records to contract pharmacy files, while your compliance officer keeps each decision.
Pharmacy ChainsChargeback and Returns Dispute Document Automation for E-Commerce Brands
Chargeback and returns dispute automation for e-commerce: a step-by-step dispute-document workflow and evidence table, with submission kept with your staff.
Ecommerce OperationsJoint Interest Billing and Land/Lease Administration Document Automation for Independent Energy Operators
Joint interest billing automation for independent operators: a lease-to-distribution workflow showing what an agent drafts and what staff approve.
Utilities and Energy Companies