Published: September 18, 2026.
When a carrier sells its invoices to a factoring company, the customer has to be told where to send payment. That instruction travels through a notice of assignment. If the notice is missing, outdated, or filed under the wrong account, the broker may keep paying the carrier directly while the factor expects the money. A register turns that paperwork into a trackable state.
Understand what the notice does
A notice of assignment tells a broker or shipper that the right to receive payment for a specific invoice has been transferred. It is not a contract with the broker, and it does not change the freight agreement. It is an instruction about where money goes. Because brokers process thousands of carriers, they often need the notice in their own format, uploaded to their own portal, and confirmed by their own accounting team.
The register exists to answer one question quickly: for this customer, has the factor's payment instruction been delivered, acknowledged, and made effective? Anything short of an acknowledged, dated instruction is an open item.
Give every customer a current payment profile
Build one profile per broker or shipper account. The profile should record the legal entity name, the remit-to address or bank instruction the factor provides, the effective date, the factor reference, and the contact who confirmed it. Keep the source document linked, not retyped. If the broker supplied a form of its own, store that version alongside the factor's standard notice.
When a customer uses multiple divisions or portals, treat each as its own profile. A broker's van division and its flatbed division may have separate accounting teams and separate upload requirements. Combining them hides the half that never received the notice.
Send and prove delivery separately from acceptance
Delivery and acceptance are two different facts and both belong in the register. Delivery is the date the notice was sent or uploaded, with the method and the recipient. Acceptance is the date the broker confirmed the instruction is active, plus the name of the person who confirmed it.
Do not close a profile because an email was sent. If the broker's portal shows a pending status, keep the item open until the portal shows the notice approved or the broker confirms in writing. When a portal gives no status at all, schedule a follow-up call and record the result.
Handle the awkward cases
The hard cases are the ones that create real risk. A broker says it already paid the carrier's old bank account. A load was booked under a different carrier authority. A customer's parent company wants to pay centrally. Each of these needs more than a resend.
For a payment sent to the wrong party, open an exception with the broker, the factor, and the carrier's accounting owner. Record the invoice numbers, amounts, dates, and the specific instruction each party is following. The register should show the exception until the funds are redirected or reconciled. It should not be closed by the mere promise of a fix.
For a new customer, confirm the current remit-to instruction before the first invoice is sent, not after. Brokers frequently reject invoices that arrive with instructions that do not match their vendor file.
Keep versions instead of overwriting
Factors update their notices, addresses, and reference numbers. When a new version arrives, add it as a new dated version and mark the prior one superseded. Keep the old version attached because it explains what a broker was following at the time a payment was made.
The same rule applies when a carrier changes factors. The transition is a project, not a single email. The register should show which customers have been moved, which acknowledgments are outstanding, and which invoices might straddle the changeover date.
Align the register with billing
The register is only useful if billing uses it. Before an invoice is submitted, the billing team should be able to see the current payment instruction for that customer. Build a short check into the billing routine: confirm the customer profile is active, the notice is acknowledged, and the remit-to details match the factor's current instruction.
Monthly, reconcile the register against the factor's statement. Look for customers with no acknowledgment, invoices paid to the wrong party, and profiles that have not been reviewed in a long time. A brief monthly review catches drift before it becomes a collections problem.
Questions teams usually ask
Does every broker require its own form?
Many do. Some accept the factor's standard notice, but others require the notice on their vendor form or through their portal. The register should record which method each customer uses so the office does not guess.
Who owns the decision to change factors?
That is a carrier ownership and finance decision, not an administrative one. The office can prepare the customer list, send the notices the factor provides, and track acknowledgments once the decision is made.
What if a broker refuses to honor the notice?
Escalate to the carrier's accounting owner and the factor. Do not instruct the broker on legal rights. Document the broker's stated reason and the dates, then let the authorized parties respond.
How long should superseded notices be kept?
Follow the carrier's records policy. In practice, keeping superseded notices until the related invoices are fully settled and the retention period passes prevents gaps when a payment is questioned.
A clean notice of assignment register protects cash flow without adding drama. It makes the current instruction obvious, proves when each customer acknowledged it, and keeps every exception visible until it is truly resolved.
Need help keeping customer payment profiles current? Reach out to our team to discuss how a trucking virtual assistant can maintain this register alongside your billing routine.