Skip to main content

Cash flow complaints usually arrive as a story about slow-paying brokers. Sometimes that is what it is. More often, the clock started later than it should have, and nobody noticed because the delay happened inside the carrier's own process.

Before deciding that the answer is factoring, it is worth being honest about which of the two problems you actually have.

The delay you control

Between "wheels stop" and "customer receives a valid invoice" there is a stretch of time entirely inside your business. It typically looks like this:

The driver delivers. The POD sits in the cab, or in a photo on a phone, or in a truck-stop scanner queue. Someone has to notice it exists, match it to the right load, confirm the rate matches the rate confirmation, and cut the invoice.

Every step there is a place to lose days. And they are the cheapest days in the entire cycle to recover, because you do not have to negotiate with anyone to get them back.

Three things fix most of it:

Make the POD a condition of closing the load. Not a reminder — a gate. If a load cannot move to delivered or invoiced without the document attached, the document gets attached. This sounds bureaucratic and turns out to be the single highest-value control in the chain, because it moves the paperwork chase to the moment the driver is still at the dock rather than a week later.

Invoice from the load record, not from scratch. The rate, the accessorials, the customer and the reference numbers are already sitting on the load. Re-keying them into an invoice introduces mismatches, and a mismatch between the invoice and the rate confirmation is one of the most common reasons a broker's AP department parks something.

Send it the same day it is ready. Batching invoices weekly is a habit from paper eras. It adds days to your own terms for no benefit.

The delay you negotiate

Once the invoice is out, you are on the customer's terms. That is a commercial question and it belongs in the conversation before you take the load, not after.

What helps here is an aging report you actually look at. Not to feel bad — to give the collections conversation a fact. "Invoice 2041, delivered the 3rd, terms were 30 days, we are at 58" is a different call than "you guys are always slow."

Group receivables by age. Watch which customers drift. A customer whose average days-to-pay is climbing is telling you something before they stop paying entirely.

Then decide about factoring

With those two cleaned up, factoring becomes an actual decision rather than a reflex.

The mechanics are simple: you sell the invoice, receive most of the value now, and pay a fee for the privilege. The factor advances a percentage and holds the rest until the customer pays.

It genuinely makes sense when:

  • Growth is constrained by cash, not by freight — you can book more than you can float
  • Your customers are creditworthy but slow, and the gap is structural
  • The fee is less than what the delay costs you in missed loads or borrowing

It is expensive when it is quietly subsidizing a paperwork problem. Factoring an invoice you could have sent nine days earlier means paying a fee for days you gave away.

Read the agreement for the parts that are not the rate. Advance rate and fee are the headline numbers, but the terms that bite are elsewhere: whether it is recourse or non-recourse and what specifically counts as a recourse event, whether you must factor everything or can choose per invoice, notification requirements to your customers, minimum volumes, and how to exit. Two agreements with identical advertised rates can behave very differently.

Where the software fits

The three controls above are all system behaviour rather than willpower: gate the load on the POD, build the invoice from the load record, and keep an aging view someone actually opens.

TFS Fleet does those directly — an optional workflow gate blocks a load reaching delivered or invoiced without a POD or BOL attached, invoices are created from delivered loads rather than typed fresh, A/R aging buckets sit alongside them, and factoring submission and funding status live in the same place.

See Accounting & Factoring and Documents & Compliance.

The short version

Fix the days you control before paying for the days you do not. Gate the paperwork, invoice from the load, watch the aging. Then, if cash is still the constraint on growth rather than on tidiness, factoring is a reasonable tool bought at a fair price — instead of an expensive patch over a process you could have fixed for free.

Common questions

Is factoring a bad idea?
No — it is a financing decision, not a moral one. Factoring converts a receivable into cash today at a cost. It is sensible when the growth or stability it buys is worth more than the fee. It is expensive when it is compensating for invoices you could simply have sent sooner.
Recourse or non-recourse?
The difference is who carries the loss if the customer never pays. Non-recourse shifts more of that risk to the factor and generally costs more, but the definitions vary between agreements — read what your specific contract treats as a recourse event rather than relying on the label.
Why do invoices get rejected?
Overwhelmingly for missing or illegible paperwork — most often the POD, sometimes a rate confirmation that does not match the invoiced amount. It is rarely a dispute about the work. It is a document that never made it back.
What is a reasonable time to invoice after delivery?
As fast as the paperwork allows, and the paperwork should be the constraint you attack. Every day between delivery and invoicing is a day added to your own payment terms, and it is the cheapest delay in the whole cycle to remove.

One system of record for the work behind this article

TFS Fleet puts dispatch, ELD and hours-of-service data, fuel and IFTA, maintenance and inspections, documents, settlements, and analytics in the same place — 12 modules on one multi-tenant platform, so the operational detail above has somewhere to live other than a spreadsheet and a text thread.