botminds.aiRequest a demo
WorkflowFreight Brokerage

Carrier Invoice Processing

Carrier invoice processing that ties each invoice to its rate confirmation and signed POD, pays the party named on the notice of assignment, and pays each load once.

See the demoBook a demo
See one load billed twice, and who the papers say to pay ↓
Watch with transcript →
The problem

The carrier's copy asks for a new bank, and the factor already billed the load

A carrier invoice should be paid only when it agrees with the rate confirmation the carrier signed and the signed proof of delivery, with each extra approved. Those papers, the load notes and the notice of assignment live in five places, and a pay specialist lines them up by hand before the weekly run.

Once a factor's notice is on file, paying the carrier does not settle the debt, so the obvious payee can be the wrong one. The same load arrives from the carrier and from its factor, detention gets rounded up, and a remit-to on the invoice names an account nobody has called to verify.

Built forFreight brokersCarrier pay teamsCarrier pay managersControllersOperations reps

The Problem Today

A factor's notice can make the payee on the invoice the wrong one, and two copies of one load can both get paid.

22%
of brokers surveyed lost over $200,000 to fraud in six months published

Lined up by hand before each run

  • Rate con
  • POD times
  • NOA on file
  • Remit-to
  • Detention billed past the termsHours rounded up beyond what the rate confirmation pays
  • Bank changes ride on invoicesA new remit-to names an account nobody has verified

The Solution

  1. Three papers tiedInvoice, rate confirmation and signed POD agree fact by fact, each cited
  2. Extras worked from the PODDetention from the POD's arrival and departure stamps, in whole hours
  3. Payee from the noticeThe factor confirms or releases; a challenger hunts double payments
  4. Two people signThe specialist decides; the pay manager signs a payee unlike the invoice

Built-in controls

  • Payees come from the notice on file, never the invoice
  • A new bank account waits for a callback
  • Agents never pay; a second person signs

What You Get

Carrier pay closes each week knowing who was paid, how much and why.

  • Detention paid as agreedWhole hours past free time, from the signed POD
  • Duplicate copies closedCarrier and factor copies of one load, paid once
  • One file per paymentWho decided, who signed, why, and the papers behind it
Features

Carrier invoice processing features, from three papers to the weekly pay run

Carrier pay specialists use them to pay each load once, to the right party, at the agreed amount; the pay manager, operations and the controller sign what falls to them. The screens follow one factored dry-van load.

demoEvery name, load and dollar figure here is invented sample data.

  1. 01Three papers

    Invoice, rate confirmation and signed POD lined up on nine facts

    • Three papers in three columns. Nine facts each get a row across the three papers, so a gap shows at a glance instead of across three open files.
    • Nothing judged before the agents read. Before the run the cells show only what each paper says, so the specialist sees the raw papers first.
  2. 02Ties and gaps

    Carrier invoice matched to rate confirmation and POD, with a payee stamp

    • A tie or a gap between papers. Agreeing facts get a check; a disagreement shows the agent's working underneath, such as detention from the POD's in and out times.
    • A payee stamp from the notice on file. Who gets paid, on which notice, with release status and remit-to history, so a new bank on the invoice cannot pick the payee.
    • Steer the agents mid-run. A one-line instruction, for example to look at the carrier's other open invoices this week, adds a step, and the matcher reports on each one.
  3. 03Double-pay test

    Each way a load could be paid twice or to the wrong party, played first

    • Carrier, factor and auditor played in turn. Each path states the argument that party would make and is closed by a paper or flagged for the pay manager.
    • Our own draft tested too. A first draft that took the payee from the invoice is caught and redrafted to the party on the notice.
    • Quick pay on an assigned invoice refused. The rate confirmation's terms keep quick pay off a factored load unless the factor asks for it.
  4. 04Factor request

    Notice of assignment confirmed with the factor at the contact on the notice

    • Contact taken from the notice. The factor is asked at the address on its own notice, so an invoice cannot steer who answers.
    • Answers in fields and signed letters. Notice in force, release and purchase come back as fields; the factor's typed note goes to a person.
    • Bounces and overdue requests in view. A failed address goes to a person to pick from the factor's listing, with each request's answer-by time shown.
  5. 05Decision

    Pay, hold or send back, played forward before the specialist signs

    • Each option played forward. Before signing, the specialist sees which choice would leave money still owed, or send it to an account nobody has verified.
    • Signing blocked until the notes are read. The specialist opens the carrier's typed note and the factor's answer before deciding.
    • Code and reason in the specialist's words. Nothing is pre-filled, and the signature spells out what was opened.
  6. 06Bank changes

    New remit-to bank accounts held for a callback before any payment

    • New bank details marked not verified. A change asked for on an invoice goes to review instead of into the pay run.
    • Callback logged in fixed fields. Compliance dials the carrier's number from before the request, logs the answers, and the controller countersigns.
    • Notices of assignment by factor. Each factor's carriers on notice and the contact used to verify them sit in one table.
  7. 07Extra charges

    Detention, lumper and TONU charges worked against the rate confirmation

    • Billed amount beside what the terms allow. The extras checker works each charge from POD times, receipts and dispatch records, so operations decides on the figures.
    • No lumper without a receipt. A lumper charge with no receipt cannot be approved, whatever the invoice says.
    • Proof opened before deciding. Operations opens the load notes and terms before approving at the terms or declining.
  8. 08Approvals

    Second signature on large payments and on payees unlike the invoice

    • Papers opened by the signer. Approve stays off until the pay manager has opened each paper personally.
    • Approve and send-back codes. Each outcome takes a code and a note in the manager's words, kept with the payment.
  9. 09Pay run

    Weekly carrier settlement run released only once the controller signs

    • Factors and carriers paid in one run. Payments to factors on notice are split from payments to carriers direct, so treasury sees where the money goes.
    • Held and duplicate invoices left out. Held invoices and closed duplicate copies are listed as outside the run.
    • Release blocked by a missing signature. The controller cannot release the run while a payment over the setting lacks its second signature.

Four people between a carrier invoice and the bank file

The specialist decides, the pay manager and controller countersign, and operations owns the extras.

Carrier pay specialists

Deciding who is paid and how much on each held invoice

  • Three papers lined up with ties and gaps
  • The payee from the notice, with its history
  • Each way a load could be paid twice
Carrier pay managers

Countersigning payees unlike the invoice and payments over the threshold

  • The notice and the factor's answer to open first
  • Detention rules learned from their decisions
  • Held invoices past their target
Operations reps

Approving or declining extras on the loads they run

  • What the terms allow beside what was billed
  • The proof to open before deciding
  • No lumper approved without a receipt
Controllers

Releasing the weekly pay run, bank changes, settings and learned rules

  • Exceptions listed before the run goes out
  • Large payments still unsigned, by name
  • Setting changes that need their signature

A load billed twice, detention rounded up, a draft paying the wrong party

What lined-up papers showed on one factored load before the pay run.

The factor had already billed the load

The carrier's emailed invoice and the factor's schedule carried the same invoice at $2,665.00; the draft pays one copy and closes the other as a duplicate.

Detention rounded up to three hours

On site 13:05 to 17:10 with 2 hours free is 2 whole hours under the terms: $100.00, not $150.00.

Our first draft paid the wrong party

The first draft took the payee from the invoice; the challenger caught it, and the second draft proposes $2,615.00 once, to the factor, pending its answer.

demoSample data, from the working solution.

Around the load

The pay week, learned rules, carrier messages and each payment's trail

Screens the carrier pay desk works from while one factored load waits for the factor's answer.

Invoices this pay weekThe week's invoices split into matched clean, adjusted and held, each with its payee, status and owner; held ones past target are marked.
Rule learned from rulingsFrom the pay manager's rulings on detention when a rate confirmation is silent on rounding, a proposed rule appears; the controller decides whether it applies.
Messages to carriers and factorsAnswers to carriers asking where their money is, and short-pay notices with their reasons, drafted from the papers and sent by a person.
Audit trailAgent findings and human actions on the load, with reasons, in one trail. The auditor or administrator exports it with an evidence binder.
Settings and who decidesTolerances, the second-signature threshold, quick-pay terms, the cut-off and who decides each change. The administrator proposes; the controller signs.

demoSample data, from the working solution.

Six systems behind each carrier payment decision

The agents cite each one; outside parties can alter a case through structured answers alone.

Transportation management systemLoads, rate confirmations and load notes
ERP accounts payablePayees, payments and the weekly pay run
EmailInvoices, POD photos and lumper receipts
Carrier portalInvoices and documents carriers upload
Factor portalsSchedules of accounts, notices and releases
Document managementNotices of assignment, signed PODs and evidence binders

What carrier pay managers ask about carrier invoice processing

What is carrier invoice processing?

Carrier invoice processing means checking each carrier's bill for a load against what was agreed and delivered, then paying it. Here, carrier invoice processing ties each invoice to its rate confirmation and signed POD, works out the extras and pays the party the papers name, once.

How does it handle invoices sold to a factor?

The payee comes from the notice on file, never from the remit-to on an invoice. The factoring agent asks the factor to confirm or release at the contact on the notice, and only its fields and signed letters change the case.

Can it stop us paying the same load twice?

It gathers each copy of a load, from the carrier, its factor or a re-sent invoice, and a challenger plays each way the load could be paid twice. One payment goes forward and the other copies are closed.

Does it offer quick pay?

Quick pay follows the rate confirmation's terms, and it is not offered on an assigned invoice unless the factor asks for it.

Who approves detention and lumper charges?

Operations. The extras checker shows what was billed beside what the terms allow, from the POD times and receipts, and the operations rep rules on each, giving a reason.

What happens when a carrier sends new bank details?

The change goes to account-change review as not verified. Carrier compliance rings the number the brokerage held before the request and logs what it hears; the controller countersigns.

Freight Brokerage

Other solutions for brokerage back offices

All 7 solutions →
Broker-Shipper Agreement Review

Shipper drafts read against counsel’s playbook in minutes; no legal position leaves unsigned.

1-min demoFreight RFP Response

Lanes priced on what you pay, and the terms that cost money found first.

1-min demoCarrier Sourcing

Loads go to carriers with a record on the lane, not to strangers from a board.

1-min demo

Bring a pay week
with a factored load in it.

We will line up one of your factored loads with you, paper by paper, and show who the notice says to pay.

Book a demoBrowse solutions