Broker Non-Payment Checklist

How this comes up in practice

An entity distinction that comes up in non-payment escalations: the broker named on the rate confirmation and the entity appearing in payment emails are different — one an LLC and one an Inc. with similar names. The assumption that they are the same company is often reasonable, but when a dispute moves to the claims stage, the L&I record for the MC number on the rate confirmation may point to a different entity than the one answering payment emails. Organizing the dispute file with a clear separation between the rate confirmation MC number, its corresponding L&I record, and the payment correspondence for each entity is what makes the distinction traceable. Legal and bonding channels typically require that separation documented before a claim can proceed.

The difference between organizing a file and building a useful one

A broker non-payment checklist is an organizing tool, not a legal instrument. What it produces is a file — a clear, dated set of records showing what was agreed, what was delivered, what was invoiced, and what the payment history looks like. That file is what makes the next step, whatever it is, actually workable. For adjacent verification steps, compare this with What to Do If a Broker Does Not Pay, Broker Bond / BMC-84 / BMC-85 Explained, and Factoring NOA Explained.

The distinction between an organized file and a useful one is specificity. Not just 'there's a POD' but 'the POD was received at this facility on this date by this person, and submitted to this contact at the broker by email on this date with a delivery confirmation.' Not just 'the rate confirmation has payment terms' but 'the terms specify 30 days from POD submission, which puts the due date at this specific date.'

Organizing the file with that level of specificity takes more time upfront but produces a file that can be handed to a bond claim process, legal counsel, or a factoring company without requiring further reconstruction. A file that already has the dates, contacts, and amounts clearly established is ready for the next step as soon as it's needed.

What to establish in the file before escalating

Create a clean aging timeline and match it to the rate confirmation payment terms.

A non-payment checklist should separate missing documents from disputed facts.

Invoice and delivery records to organize

Build the working file from original records — before pickup, before payment, or before escalating a dispute. Keep each revised version separately from the original.

Non-payment signals worth investigating

A red flag should trigger a slower review and a documented call-back. It is not a public accusation or a final finding.

Questions the non-payment file should answer

Ask questions that can be answered with a record, a known contact, or a dated instruction.

Non-payment documentation assumptions to avoid

Avoid filling gaps with memory, old emails, or a search result that may not belong to the current transaction.

Official resources for broker payment disputes

Use official records as comparison points and save the lookup date. Official status can change, and legitimate company records can be impersonated.

When the file is ready to escalate

Escalation means preserving evidence and moving the question to the right internal, insurance, legal, law enforcement, or official reporting channel. This site does not provide legal, financial, or insurance advice.

Source Notes

FAQ