Cut Advisor NIGO Rate to Under 5% at Custodians 2026
A NIGO — Not In Good Order — is a new-account or service request that the custodian kicks back because something is missing, mismatched, or improperly signed. For a financial advisor, every NIGO is a quiet tax on growth: a household that wanted to fund an account this week instead waits eleven days, an operations associate re-keys the same SSN a third time, and the advisor spends a Friday afternoon chasing a wet signature that a digital workflow should have caught at intake. The work to fix a single NIGO is small. The aggregate drag across a book of business is not.
This is an ROI question disguised as an operations one. If your firm sits at a 20% NIGO rate — roughly one in five new accounts bounces at least once — and you can route that under 5%, you are not just saving rework hours. You are compressing the time-to-fund, which is the moment a prospect becomes a paying relationship and the day your AUM-based fee actually starts accruing. Below is the data, the per-step economics, a worked example tied to a real custodian event, two CRM comparisons, and an honest read on where automation is the wrong tool. The target is a sub-5% NIGO rate without adding headcount.
Key Takeaways
NIGO is a revenue-timing problem, not just a rework problem: every kickback delays the day a fee-paying relationship begins.
The fix is validate-before-submit — check signatures, beneficiary fields, funding instructions, and ID matches at intake, not after the custodian rejects.
The opportunity is large per advisor: Average advisor book size: $98M AUM according to Cerulli Associates (2024), so each delayed funding compounds.
A worked example takes a 40-account month from a 22.5% NIGO rate to 4% by gating submissions on a
account.statuschange.US Tech Automations fits RIAs routing new accounts across a CRM, an e-signature tool, and a custodian portal — not a solo advisor opening two accounts a quarter.
TL;DR
To get NIGO under 5%, stop treating it as something operations cleans up after the fact. Build a pre-submission gate that validates the high-failure fields — beneficiary designations, signature completeness, funding/ACAT instructions, and name/SSN/DOB matches against the custodian's record — before any package reaches Schwab or Fidelity. Route exceptions to the right person automatically, log every check for compliance, and measure first-pass yield weekly. Firms that do this routinely move from a 15–25% NIGO rate to low-single-digits, recovering both staff hours and weeks of lost funding time.
What "NIGO rate" actually measures
NIGO rate is the share of submitted account-opening or service packages a custodian rejects on first review for missing or incorrect information. A 12% NIGO rate means 12 of every 100 packages come back requiring a fix and a resubmit.
The number matters because it is a leading indicator of two things advisors care about: client experience and time-to-revenue. A high NIGO rate means clients sign things twice, get confused emails, and form an early impression that your firm is disorganized. It also means accounts fund late — and an unfunded account generates no advisory fee. The investment-advisory industry is sizable enough that these timing losses add up: according to the U.S. Securities and Exchange Commission (2024), registered investment advisers managed well over $100 trillion in regulatory assets, almost all of it fee-based on funded accounts.
There is a definitional trap worth flagging. Some firms quietly count only custodian-rejected packages and exclude items their own ops team catches and fixes internally before submission. That understates the true rework burden. A clean metric counts every package that required a correction after the client first signed, whether the custodian or your own associate flagged it. That is the number this playbook is trying to drive under 5%.
| Term | Plain-English meaning |
|---|---|
| NIGO | Not In Good Order — package rejected for missing/incorrect info |
| IGO | In Good Order — package accepted on first submission |
| First-pass yield | Share of packages accepted with zero corrections |
| ACAT | Automated Customer Account Transfer — moving assets between firms |
| Wet signature | A physical ink signature, vs. an e-signature |
| Funding instruction | How the account will be funded (ACH, ACAT, check, wire) |
| Cycle time | Days from client signature to account fully funded |
Why NIGO is expensive: the per-step economics
The industry runs on this paperwork at scale. SEC-registered RIAs: roughly 15,000 firms according to SIFMA (2024), and each opens, transfers, and updates accounts continuously across custodians with their own forms and rules. When the forms are wrong, the cost shows up in three places: staff time, delayed revenue, and compliance exposure.
Take staff time first. A single NIGO is not one email. It is the associate diagnosing what failed, re-contacting the client, re-collecting a signature or document, re-keying corrected data, and resubmitting — then often waiting another custodian cycle to confirm acceptance. Industry operations leaders commonly peg the fully loaded cost of resolving one NIGO in the tens of dollars once you count the touch points and the management oversight. The labor is not cheap: according to the U.S. Bureau of Labor Statistics (2024), the median wage for securities and financial-services operations staff sits comfortably in the mid-five-figures annually, so re-keyed rework is real money.
| Cost driver | Low NIGO firm (4%) | High NIGO firm (22%) | Delta |
|---|---|---|---|
| New accounts/month | 40 | 40 | — |
| NIGO incidents/month | ~2 | ~9 | +7 |
| Rework hours/month | ~1.5 | ~9 | +7.5 |
| Avg time-to-fund (days) | 4 | 12 | +8 |
| Resubmit cycles/account | 0.04 | 0.30 | +0.26 |
Then there is the regulatory layer. Operating a compliant RIA is not cheap to begin with — Mid-size RIA annual compliance cost: in the six figures according to FINRA (2024) — and sloppy account records make exams harder and remediation more likely. A NIGO that involves a beneficiary or suitability field is not just an inconvenience; it is a documentation gap an examiner can flag.
The point of automation here is not to "go faster." It is to move the error-catch upstream, to the moment of intake, where a fix costs seconds instead of a fix that costs an eleven-day round trip.
Who this is for
This playbook is written for established RIAs and advisory teams, not solo shops doing occasional paperwork.
Firm size: roughly 5–75 staff, with at least one or two dedicated operations or client-service associates.
Revenue/AUM: generally $300M+ in AUM or $2M+ in annual revenue, where account volume is high enough that a few points of NIGO rate translates into real hours and real delayed fees.
Stack: you already run a CRM (Redtail, Wealthbox, Salesforce, or similar), an e-signature tool (DocuSign, or the custodian's native flow), and you submit to one or more custodians (Schwab, Fidelity, Pershing).
Pain: new accounts bounce, ops re-keys data, and advisors lose visibility into where a household's onboarding actually stands.
Red flags — skip automation for now if: you open fewer than ~5 new accounts a month, your stack is paper-and-PDF with no CRM of record, or annual revenue is under ~$500K. At that scale the build-and-maintain cost outruns the rework you would save, and a disciplined checklist plus the custodian's own digital onboarding will get you most of the way.
The pre-submission gate: where the 15 points come from
Getting from 20% to under 5% is rarely one heroic fix. It is closing the handful of fields that cause most rejections. Custodian operations teams consistently report that a small set of fields drive the majority of NIGOs.
| Failure category | Typical share of NIGOs | Catchable pre-submission? |
|---|---|---|
| Missing/incomplete signature | ~30% | Yes — e-sign field validation |
| Beneficiary designation errors | ~20% | Yes — required-field + percentage-sum check |
| Name/SSN/DOB mismatch | ~15% | Yes — match against existing record |
| Funding/ACAT instruction gaps | ~15% | Yes — conditional required fields |
| Missing supporting document | ~12% | Yes — checklist gate by account type |
| Other (misc. custodian rules) | ~8% | Partly |
A pre-submission gate is software that refuses to let a package leave your firm until each of those checks passes. The beneficiary percentages have to sum to 100. A Roth IRA package has to carry a contribution-year selection. A trust account has to carry the trust document. A signature block has to be fully executed. None of this is novel logic — it is the custodian's own rejection criteria, simply applied before submission instead of after. The upside of catching errors upstream is well documented in operations research: according to Deloitte (2024), front-office process automation in wealth management cuts manual exception handling by a substantial double-digit percentage when applied at the point of data capture.
This is the layer where orchestration across your CRM, e-signature tool, and custodian portal earns its keep: the data exists in three systems, and the gate is the thing that reconciles them and decides whether the package is truly in good order.
Worked example: a 40-account month at a custodian
Consider a $620M-AUM RIA in Denver opening 40 new accounts in a month, historically at a 22.5% NIGO rate — meaning about 9 packages bounce and require an average of 1.3 correction cycles each, pushing average time-to-fund to 12 days. The firm wires its Redtail CRM, DocuSign, and the Schwab Advisor Center together so that a package can only be submitted after a validation routine confirms beneficiary percentages sum to 100, the SSN matches the household record, the funding method is populated, and every DocuSign field is signed. When Schwab posts an account.status change to "Open – Pending Funding," the workflow listens for it and only then triggers the ACAT or ACH instruction; if the status instead returns a rejection reason code, the package routes straight to the assigned associate with the exact field flagged. In the first full month the firm submitted 40 packages, saw NIGOs drop to fewer than 2 (a 4% rate), cut rework from ~9 hours to under 2, and pulled average time-to-fund from 12 days down to 4 days — eight days of fee accrual recovered on every new household, with no added headcount.
That eight-day compression is the part that pays for the project. On a $98M average book, accelerating the funding of even a handful of larger relationships a month moves real fee revenue forward — which is why this reads as an ROI initiative, not an ops cleanup. For teams mapping where these handoffs live, our guide to the advisor CRM to portfolio-management workflow shows how the same data has to stay clean as it moves downstream.
How US Tech Automations fits the workflow
US Tech Automations sits between your CRM, e-signature tool, and custodian portal and runs the pre-submission validation gate described above: it reads the assembled package, checks the high-failure fields against custodian rules and the client's existing record, and blocks submission until each check passes. When a custodian posts a status or rejection event, US Tech Automations routes the exception to the named associate with the specific field flagged, rather than dropping a generic "NIGO" notice into a shared queue. Every check and every routing decision is written to a timestamped log, so the same workflow that lowers your NIGO rate also produces the audit trail your CCO needs at exam time. You can see how the broader finance and accounting automation pieces connect across the account lifecycle.
The honest framing: this is orchestration above your existing tools, not a replacement for your CRM or your custodian. The custodian still adjudicates the account. Your CRM still owns the client record. The automation layer's job is to make sure what you send is right the first time and to tell the right person, fast, when it is not.
CRM comparison: Redtail, Wealthbox, and the orchestration layer
A frequent question: "Doesn't my CRM already do this?" Redtail and Wealthbox are excellent systems of record and workflow trackers, and both have improved their account-opening features. But there is a difference between tracking an onboarding workflow and gating a submission on validated, cross-system data.
| Capability | Redtail CRM | Wealthbox | With US Tech Automations orchestrating |
|---|---|---|---|
| Client record of truth | Strong | Strong | Reads from CRM, does not replace it |
| Workflow/task tracking | Strong | Strong | Reads task state to route exceptions |
| Cross-field validation pre-submit | Limited | Limited | Core function — blocks bad packages |
| Listen to custodian status events | No | No | Yes — acts on account.status changes |
| Auto-route exception to named owner | Manual rules | Manual rules | Field-level, automatic |
| Compliance log of every check | Partial | Partial | Timestamped, per-check |
Where Redtail and Wealthbox clearly win: as the day-to-day CRM your advisors live in, with contact management, pipeline tracking, and native account-opening integrations to the major custodians. If your only goal is a better CRM, you do not need an orchestration layer — pick the CRM whose interface your team prefers. For a deeper feature-by-feature read, see our comparisons of the leading CRM alternatives for financial advisors and Salesforce vs. Zoho for advisory firms.
When NOT to use US Tech Automations
Be honest about fit. If you open fewer than five accounts a month, your NIGO volume simply does not justify an orchestration build — a tight checklist and the custodian's native digital onboarding will catch most of it for free. If your bottleneck is lead and client tracking rather than account accuracy, you are better served choosing a strong standalone CRM first; our roundup of lead management software for advisors is a better starting point than an automation layer. And if every account you open is a simple individual brokerage with no beneficiaries, no trust documents, and ACH-only funding, your NIGO rate is probably already low and the marginal gain from automation is thin. Automation pays when complexity and volume are both present.
A decision checklist before you build
Run through these before committing to a NIGO-reduction project:
Can you measure your current NIGO rate honestly, counting internal catches and custodian rejections both? If not, instrument that first.
Do you know your top 3 NIGO causes by frequency? Most firms find signatures and beneficiaries dominate.
Is your CRM the genuine system of record, or do associates keep data in spreadsheets? Automation amplifies clean data and amplifies messy data equally.
Do you submit to one custodian or several? Multi-custodian firms get more value because each custodian's rules differ.
Who owns exceptions today, and is that ownership ambiguous? Routing only helps if there is a clear named owner per account type.
Common mistakes that keep NIGO high
Treating NIGO as an ops problem, not a process problem. Adding a reviewer at the end catches errors later but does not stop them. The gate has to sit at intake.
Validating only at final submit. If the client already signed, a beneficiary error means re-signing. Validate the data before you send for signature wherever possible.
One generic "NIGO" alert. A shared-queue notice with no field-level detail just moves the diagnosis work, it does not remove it. Route the specific failed field to a named owner.
No first-pass-yield metric. If you do not measure the share of packages accepted with zero corrections weekly, you cannot tell whether a fix worked.
Ignoring the funding step. Many firms get the account opened cleanly and then stall on the ACAT or ACH — a NIGO on funding still delays revenue.
Benchmarks: where firms land before and after
These ranges reflect commonly cited industry experience rather than a single published figure; treat them as directional targets to instrument against, not guarantees.
| Metric | Typical "before" | Target "after" |
|---|---|---|
| NIGO rate | 15–25% | Under 5% |
| First-pass yield | 75–85% | 95%+ |
| Avg time-to-fund | 9–14 days | 3–5 days |
| Rework hours / 40 accounts | 8–10 | 1–2 |
| Resubmit cycles / account | 0.25–0.35 | Under 0.05 |
The cross-firm spread is wide because account mix matters: a firm doing mostly simple brokerage transfers will sit lower than one doing trusts, IRAs, and ACATs. Time-to-fund commonly compresses from ~12 days to ~4 days when validation moves upstream — the single number most advisors feel, because it is the gap between a signed prospect and a paying client.
Putting it together
The path to a sub-5% NIGO rate is not exotic. Measure honestly, find your top failure fields, gate submissions on those fields before anything reaches the custodian, route the exceptions that remain to a named owner with the specific problem flagged, and log it all. The hard part is discipline, not technology — and the payoff is measured in both recovered staff hours and the weeks of advisory fees you stop leaving on the table. Pricing for an orchestration layer scales with volume; if you want to see where your firm lands, our pricing page lays out the tiers.
FAQ
What is a good NIGO rate for an RIA?
A good target is under 5%, with best-run firms operating in the low single digits. Many firms start in the 15–25% range before they instrument the metric. The exact achievable floor depends on account mix — simple brokerage transfers fail far less often than trust accounts and IRAs with beneficiary designations. The more important discipline than hitting a specific number is measuring first-pass yield weekly so you can tell whether changes are working.
How do advisors cut NIGO rate to under 5 percent?
By validating the high-failure fields before a package ever reaches the custodian. The bulk of NIGOs come from a handful of causes — incomplete signatures, beneficiary errors, name/SSN mismatches, and missing funding instructions — and all of them can be checked at intake. A pre-submission gate refuses to let a package through until those checks pass, which is the difference between catching an error in seconds versus an eleven-day custodian round trip. Routing the remaining exceptions to a named owner closes most of the rest.
What are typical NIGO benchmarks at Schwab and Fidelity?
Both custodians publish "in good order" guidelines rather than a single public NIGO benchmark, and the practical rate you experience depends mostly on your own intake process, not the custodian. Firms submitting clean, validated packages to either Schwab or Fidelity routinely run under 5%, while firms submitting unvalidated paper run far higher. The custodian's rejection criteria are knowable in advance, which is exactly why a pre-submission gate built around those criteria works — you are applying their own rules before they apply them.
Does my CRM already prevent NIGOs?
Your CRM tracks the workflow but typically does not gate a submission on validated, cross-system data. Redtail and Wealthbox are strong systems of record and improving their account-opening features, but cross-field validation — confirming beneficiary percentages sum to 100, that the SSN matches the household record, that funding is populated — and listening to custodian status events generally sits outside the CRM. That validation-and-routing layer is where an orchestration tool adds value above the CRM rather than replacing it.
How long does it take to see results?
Most firms see NIGO rate drop within the first full month of new account submissions once the gate is live, because the change is mechanical: errors that used to escape now get caught at intake. The bigger lever — average time-to-fund compressing from roughly 12 days to 4 — also shows up quickly because it is downstream of the same fix. The slower part is building the validation rules for every account type you handle; firms with simpler account mixes are live faster than those handling trusts and complex IRAs.
Is automating NIGO reduction worth it for a small firm?
Only above a volume threshold. If you open fewer than about five new accounts a month, the build-and-maintain cost of an orchestration layer outruns the rework you would save, and a disciplined checklist plus the custodian's native digital onboarding will get you most of the way. Automation pays when both volume and complexity are present — multiple custodians, trust and IRA accounts, and enough monthly accounts that a few points of NIGO rate translate into real hours and real delayed fees.
About the Author

Helping businesses leverage automation for operational efficiency.
Related Articles
From our research desk: sealed building-permit data across 8 metros, updated monthly.