Why Your Custodian Packets Keep Bouncing as NIGO

You spent forty minutes on the Schwab packet.

Account application. Transfer form. Beneficiary designation. Every field, by hand, off the client’s statement and their 1040.

You sent it Tuesday.

Thursday, it’s back. NIGO.

Not In Good Order. And here’s the entire reason:

Client 1 first name: “Shaun” on page 1. “Shawn” on page 3. Same client. Same field. Two spellings.

That’s it. One name, keyed twice, spelled two ways. The custodian rejects the whole packet.

Maybe next time it’s an SSN off by a digit. Or a signature date that doesn’t line up with the transfer instruction. Same story every time: one mismatch out of hundreds of fields, and the entire thing bounces.

So you start over. And the client emails: “Is my account open yet?”

This isn’t rare. It’s one in four.

Industry-wide, 10 to 30% of advisor submissions bounce as NIGO.

Sit with that. For every four packets your team sends, one comes back. Each rejection restarts the clock on account opening. That’s another few days the client’s money isn’t invested, another email you have to answer, another quiet ding to the modern-firm impression you work hard to project.

The cost was never the retype. A retype takes ten minutes.

The cost is the delay. The client waiting. Your ops person running the same packet twice. The transfer funding a week late. The slow erosion of trust every time paperwork makes your firm look slower than it actually is.

And the part that stings: the error was almost never a knowledge problem. Your team knows the forms. They know the rules.

They just retyped the same SSN into six fields, and on the fourth one, a finger slipped.

NIGO isn’t a paperwork problem. It’s a retyping problem.

Every rejection traces to the same root: the same client data, keyed by hand, into multiple places.

The CRM. The application. The transfer paperwork. The beneficiary form.

Every manual entry is a fresh chance for a typo or a mismatch, and custodians reject on exact-match rules no human holds perfectly across forty pages. The SSN on page 3 has to match the SSN on page 11. This address has to match that one. Every required field has to be there.

Miss once. Bounce.

So the firms that beat NIGO don’t check harder. Checking harder just adds a human to catch a human, and a human is what introduced the error in the first place.

The firms that beat NIGO stop introducing the error at all.

The fix: enter it once, right, everywhere.

That’s what Emma does.

She reads the source documents (the 1040, the statement, the ID) and pulls each field once. Then she fills every form in the custodian packet from that single record.

The name spelled one way, the same way, on every page. Same SSN everywhere. Same address everywhere. The account number matched across the application and the transfer form. Every required field, populated from the source.

There’s no second spelling of “Shaun” to get wrong, because the name was only entered once.

You’re not scanning forty pages hoping to catch a slip. There’s no slip to catch.

You review, send for signature, done. The packet reaches the custodian the way it should have the first time.

Firms running Emma submit under a 5% NIGO rate.

What that actually changes

Accounts open on the first submission.

Your ops team stops doing packets twice. The client stops asking where their money is. The transfer funds on schedule. And “we’re a tech-forward firm” stops being something you say and becomes something they feel.

Not because you added a checker.

Because you stopped needing one.

---

Stop retyping. Stop bouncing. Upload your next custodian packet and watch Emma fill it clean. No card required.

Common questions

What does NIGO mean? NIGO stands for Not In Good Order. It’s a custodian’s rejection of a submission it can’t process, usually for missing fields, mismatched data, or wrong form versions. Industry-wide, 10 to 30% of advisor paperwork bounces as NIGO, and each bounce restarts the clock on account opening.

What causes most NIGO rejections? The same client data retyped by hand into multiple forms. Every manual entry is a chance for a typo or a mismatch. A first name gets keyed as “Shaun” on one page and “Shawn” on another, and custodians reject on exact-match rules a person can’t hold perfectly across dozens of pages.

How do you prevent NIGO rejections? Stop introducing the errors in the first place. When every form is filled from a single source record, the same value appears on every page, so there are no mismatches to catch. Finpace’s Emma extracts each field once and fills every form from that record, and firms using her submit under a 5% NIGO rate.