Most notice of assignment disputes are not arguments about the law. They are gaps in your own process: a notification that never proved it arrived, a proof request nobody answered, or a debtor still paying the carrier because your notice did not clearly say which invoices it covered. The UCC gives you a strong position. Keeping it is operational work.
Search “notice of assignment” and everything you find is written for someone else. There are guides telling carriers what an NOA means for them and guides telling brokers what to do when one lands. What almost nobody writes is the side of the desk we sat on: what the factor has to do to make a notification hold, and what to actually do when a debtor pays around you.
That is this page. It explains the mechanism, it is specific about where notifications fail, and it stops at the line where a dispute becomes a legal position rather than an operational one. FRC is an operations consultancy, not a law firm, and the moment a dispute turns on your rights rather than your paperwork, it belongs with a commercial attorney.
What the notification actually does
The whole structure rests on one sentence. Under UCC § 9-406(a):
“After receipt of the notification, the account debtor may discharge its obligation by paying the assignee and may not discharge the obligation by paying the assignor.”
In freight terms: once the broker has received your notification, paying your client does not settle the invoice. The obligation stays live and it is owed to you.
That is a strong position, and it is why a factor can advance against an invoice at all. It is also why new factors sometimes treat the NOA as a formality, mail it once, and assume the protection is permanent. It is not permanent. The same section of the code describes two ways it stops working, and both of them are things you do or fail to do.
The two ways your notification quietly stops working
First, a notification that does not reasonably identify what was assigned is ineffective. Section 9-406(b) says so directly. A notice that names your client and your remittance address but leaves a debtor guessing which receivables are covered is doing less work than you think it is. This is the failure that hides, because nothing happens at the time. You find out months later, when a payment went the wrong way and the notice you relied on turns out to be vague.
Second, and this is the one to build a process around, a debtor can ask you to prove it. Section 9-406(c) is worth reading in full:
“Subject to subsection (h), if requested by the account debtor, an assignee shall seasonably furnish reasonable proof that the assignment has been made. Unless the assignee complies, the account debtor may discharge its obligation by paying the assignor, even if the account debtor has received a notification under subsection (a).”
Read the second sentence again. If a debtor requests proof and you do not seasonably furnish it, the debtor can go back to paying your client and be discharged, notification or no notification. Your protection is conditional on your own responsiveness.
Most factors have no named owner for that request, no standard proof package, and no clock on it. It arrives as an email to whoever is on the account, gets treated as an annoyance, and sits. That is the gap, and it is entirely inside your control.
The disputes you will actually see
Four shapes cover most of what comes across the desk, and they call for different responses.
The debtor paid your client anyway. Sometimes it is a genuine accounts-payable error, sometimes the carrier asked them to. Either way the question you need answered first is factual, not legal: can you show the notification was received, and when. That is the whole case. If the answer is a mailed letter with no delivery record, you do not have a dispute, you have a conversation.
The debtor says it never received the notice. Same question, which is why the answer to it should be a filing rather than a memory.
The debtor requests proof of the assignment. This is 9-406(c) and it is not an obstruction tactic. It is a right the code gives them. Treat it as a clock that has started.
The client is leaving and wants a release. A departing client, or one moving to another factor, will need your notification withdrawn before the new arrangement works. That is ordinary and it is part of the buyout choreography we cover in taking a client over from another factor, viewed from the other direction. The operational point is that a release is a decision with conditions attached, not a courtesy, and you want the conditions written down before you are asked.
What the statute is actually asking of you
Read (b) and (c) together and they describe a standard of upkeep, not a one-time act. A notification has to identify its scope clearly enough to be effective, and it has to be backed by an assignee who can produce proof on request. Everything below is what meeting that standard looks like as ordinary intake and documentation work, which is why it belongs in the onboarding workflow rather than in a collections scramble.
Send a notification that identifies the receivables clearly. Your attorney drafts the language. Your job is to make sure the operational fields are right every time: the client’s exact legal name, the debtor’s exact legal name, and an unambiguous statement of the scope of the assignment. Entity names matter more than people expect, because the broker’s accounts payable system matches on them.
Prove receipt, and keep the proof where the collector can find it. Whatever channel you use, the evidence that it arrived is worth more than the notice itself, and it needs to live in the debtor’s record in your system rather than in somebody’s sent folder. The day you need it is the day you are already behind.
A proof request needs an owner and a standard package. “Seasonably” is not a number, and we are not going to tell you what it means in your jurisdiction. What the code makes plain is that the clock is yours to lose: a factor who answers the same day is in a different position from one who took three weeks, and the difference is entirely about who was responsible for the reply.
Verify before you fund, not after. An invoice verification step catches the load that was never delivered, the rate that does not match, and the debtor who has no record of the carrier at all. It is also where you find out whether the debtor has your notification on file. The collections process is where a dispute gets worked, but verification is where most of them get avoided.
Re-notify when the relationship changes. New debtor, new client entity, a broker acquired or renamed. Each of those is a moment your existing notification may no longer describe reality.
Watch which debtors generate disputes. A debtor that repeatedly pays around notifications is telling you something about its accounts payable discipline, and that belongs in the credit view alongside its payment history. Our guide to building a broker credit scoring policy covers where a signal like that fits.
Where this stops being operational
Everything above is process. At some point a dispute stops being about your documentation and starts being about your rights, and the honest answer is that we are the wrong people for that part.
Route it to counsel when the debtor asserts a defence, a setoff, or a contractual term that limits assignment; when the load turns out to have been double brokered and the question is who owned the receivable; when a bankruptcy or an insolvency filing enters the picture; or when the amount is large enough that you would rather have an opinion than a view. FRC advises on how factoring operations run. Whether you have a claim, and against whom, is a legal question, and the cost of guessing at it is higher than the cost of asking.
Where an outside read fits
Notice of assignment problems are almost always onboarding problems that surfaced late. The notice went out once and nobody owned it afterwards, the proof of receipt lived in an inbox, and nothing in the workflow said who answers a 9-406(c) request or how quickly.
That is the kind of gap FRC’s 90-Day Operational Audit is built to find. It reviews six domains, collections, onboarding, risk, technology, staffing and financial reporting, and ends in a written assessment and a prioritized 12-month roadmap, with no long-term commitment. The notification lifecycle sits across onboarding and collections, which is exactly the kind of thing that falls between two desks and belongs to neither.
FRC’s founder, Renee Williams, spent 25+ years inside factoring operations, including the calls where a broker has paid the carrier and everyone is looking for the file. We consult, advise and audit. We do not fund invoices, we do not give legal advice, and we will not tell you a process makes a dispute impossible. What a good process does is make most of them short.