What an NMLS deficiency actually is

A deficiency is the regulator telling you that something on a specific license is wrong or missing, and that you, not they, have to fix it. NMLS calls it a license item, and its own glossary is blunt: it is "created by a regulator to denote a deficiency in a filing or a jurisdictional requirement."

The part people skip is who does the work. The NMLS Policy Guide, updated August 15, 2026, is direct:

Regulators cannot change a company, branch, or individual's information. If a regulator has an issue with information on an applicant or licensee's record, they may require the applicant or licensee to change their record or they may require an explanation for an item or they may require documentation for an item.

One caveat on the name. The August 2026 release moved the licensee-facing surface to Information Requests and System Tasks in NMLS Connect, leaving some license items in NMLS Classic. The concept did not change, only which screen you read it on.

It is their marker, not your task

Someone outside your organization opens it. Someone outside your organization closes it. Everything in between is yours, and none of it counts until they agree it does. A task you wrote is done when you decide it is done. A deficiency is not, and treating the two alike is the commonest operational mistake we see.

Two words, and only two

Everything a client should ever see about a deficiency reduces to one of two states:

The finer distinctions are operational. They answer whose desk it is on right now, which matters to whoever is working it and not at all to the person who wants to know if the license is clean.

The work loops, it does not descend

A checklist implies each item moves forward one notch at a time until it runs out. Deficiencies do not. There are two loops, and both are ordinary.

The first loop is the client. Many items need something only the client holds: a signature, a financial statement, an explanation of something that predates you. The work leaves your desk and comes back to be finished. Incomplete the whole time, including the stretch where nobody at your firm is touching it.

The second loop is the regulator. An item you have filed against can come back, because filing is a submission and not an approval. It is not a new deficiency and should not be logged as one. It is the same item, reopened, usually because what you sent did not answer what was asked.

What "cleared" actually means

Clearing is the outcome of a condition being satisfied, not an action a licensee performs. On an agency fee invoice, "the license item is cleared when payment has been processed or the regulator cancels the invoice." On quarterly agent reporting, "an upload of any state UAAR will clear the license item." Whether a human has to agree is what tells you to wait or to chase.

1. [1]

   Read the item, not your summary

   Work from the regulator's actual wording. The paraphrase somebody typed into a tracker six weeks ago is where the real requirement goes to die.

2. [2]

   Decide which kind it is

   NMLS names both kinds. A system license item clears the moment the condition is satisfied, with no human deciding anything. A regulator license item clears only when a person at the agency reviews what you filed and accepts it.

3. [3]

   Route it before you work it

   If it needs something only the client holds, hand it over immediately and keep it Incomplete. The handoff is not progress. An item parked with a client is how a deficiency ages quietly.

4. [4]

   File, then mark it Complete

   Complete means you have done everything you can do. It does not mean the regulator agrees, and your language to the client should not imply it does.

5. [5]

   Keep watching it

   A filed item is not an archived item. Only the second kind comes back, and it lands on the person who thought they were finished.

Three Incomplete items on a state page tell you nothing until you know which loop each one is sitting in.