Who approves the rate, who owns the exception, and who pays the carrier?

Key Takeaways

Rate approval, exception ownership and carrier payment are three separate decisions, each needing one owner, a written limit and a backup.
The approved rate becomes the baseline for exception costs, and the invoice audit checks the bill against both.
Most disputes start at the seams, such as a rebooking that raises the cost, so each seam needs its own rule.
Software acts inside each boundary and hands the owner a decision, with evidence, once it is crossed.
Wilson, by Cartage, is an AI logistics agent that negotiates against rate targets, works exceptions and pays carriers from the Wilson Wallet after audit and reconciliation, all under approval rules the company configures.

Who should approve the rate, own the exception and pay the carrier once software runs the freight?

Give each decision its own owner: a logistics lead approves rates within a budget finance sets, logistics owns exceptions with customer-facing teams consulted, and finance owns payment. Software does the work inside each owner's limit and routes everything beyond it to that owner.

A distributor's coordinator used to carry all three decisions in one inbox: she accepted the counteroffer, rebooked the load when the truck didn't show, and forwarded the invoice to accounts payable with "looks fine." Software can send the counteroffer, contact the backup carrier and match the invoice, but someone still decides how high the rate can go, which recovery costs are acceptable and which bill gets paid.

The mistake is treating this as one approval setting. A rate decision is about price before the load moves, an exception decision about recovery while it moves, and a payment decision about money after delivery. Different people hold each judgment, and the limits use different units: dollars over target, recovery cost, and variance from the booking. Without one map, a load can be approved at booking, rebooked at a higher cost in transit and then held at payment because nobody told finance the cost changed.

Five questions to settle for each decision, plus the seams between them

For every decision, answer five questions: who decides, who acts, who is informed, what the limit is and who covers when the owner is out. Then write one rule for each place where one decision changes another.

Who decides. One role per decision, named by role: usually the logistics manager for rates, the logistics lead for exceptions (customer service consulted when a delivery promise changes) and the AP or finance owner for payment.
Who acts. The software, inside the limit. Once the rule is written, countering, rebooking with an approved carrier and releasing a matched payment are actions, not decisions.
Who is informed. People who need the outcome but shouldn't act, such as sales on a late key-account load.
The limit. A condition the software can test. "Reasonable" is not a limit; "lane target plus a set amount" is.
The backup. A second approver and a response window.

The seams matter as much as the rows. There are three:

Rate to exception. A rebooking creates a new rate. Decide whether the recovery limit or the rate approver judges it.
Exception to payment. Detention approved during the load should reach the invoice audit already marked as approved.
Rate to payment. The invoice is checked against the approved rate, not the carrier's quote email.

What each owner actually does once software handles the acting

The owners stop doing the work and start answering well-formed requests, so the quality of each request and the record behind it decide whether the map holds.

For the rate decision, the approver should receive the lane, the target, the approved carriers' quotes, the counteroffers already made and the remaining gap. A request that says only "approve $2,400?" sends the approver back to email. For a broader view of how negotiation limits are set, see how much AI can negotiate before a person approves the rate.

For the exception decision, the owner needs what happened, what was tried with which carriers, and what each remaining option costs against the approved rate. The exception owner decides recovery; customer service decides what to promise the customer.

For the payment decision, finance needs the booked rate, documented changes, supporting evidence such as a signed POD, and the carrier invoice side by side. If they agree within tolerance, payment goes out under the rule; if not, finance sees which line broke. The controls worth testing at this step are covered in freight invoice controls to test before carrier payment.

Two details often get skipped: each approval should reach its owner where that person already works, and carrier payments through the Wilson Wallet should run under the customer-configured payment and approval rules, not under one person's judgment invoice by invoice.

Where the boundaries blur, and how to settle each case

Most ownership arguments come from five recurring situations. Settle them in writing first.

The rebooking costs more than the original rate. Inside the recovery limit, the exception owner decides; above it, the rate approver joins. Either way, the payment owner learns the approved cost changed.
The accessorial appears only on the invoice. If nobody approved detention or a liftgate during the load, it becomes a payment decision, held until the evidence arrives or the carrier withdraws it.
The carrier disputes a short payment. Finance decides what to pay, but the carrier conversation usually belongs to logistics, which holds the relationship. Name who replies.
The approver is unavailable and the quote is expiring. The backup decides; if the backup is silent too, the request escalates to a set role rather than defaulting to approval.
The best option uses a carrier the company hasn't approved. That is a carrier approval decision for whoever owns the approved carrier list, never something the software resolves.

When evaluating software, ask to see one load cross a seam: a rebooking above the original rate, then an invoice with the new cost. If the payment step doesn't already know who approved the rebooking, the seams aren't connected. For the exception rows in more depth, the freight exception responsibility matrix breaks out six common exceptions team by team.

A three-decision responsibility map you can fill in

The roles and limits below are illustrative. Replace them with your own before anything runs.

Decision point	Decides	Software acts	Informed	Limit (illustrative)	Backup
Rate within target	Rule (logistics manager)	Books approved carrier	Requester	At or under target	n/a
Rate above target	Logistics manager	Counters, then sends options	Finance on approval	Up to target plus a set amount	Logistics lead
Rate above ceiling	Finance	Holds booking, sends request	Sales	Above that amount	Controller
Recovery inside rules	Rule (logistics lead)	Contacts carrier, rebooks approved carrier	Team, customer	Within recovery limit	n/a
Recovery outside rules	Logistics lead	Lays out options and costs	Customer service	Above limit or no approved carrier	Logistics manager
Customer commitment	Customer service	Supplies new ETA and reason	Sales	Any promised-date change	CS lead
Invoice matches booking	Rule (finance)	Pays from the wallet	AP	Within tolerance	n/a
Invoice variance	AP owner	Reconciles, attaches evidence	Logistics	Above tolerance	Controller

Each row has one decider; a "Rule" row means the owner set the boundary in advance.

How Wilson, by Cartage, works inside each owner's boundary

Wilson negotiates, recovers and pays inside the limits each owner sets, and escalates to that owner when a limit is crossed.

On rates, Wilson requests quotes from the company's approved carriers and negotiates against the company's rate targets within its approval limits. A rate outside those limits goes to the named approver. On exceptions, Wilson contacts the carrier, notifies configured contacts and initiates rebooking from the approved carrier list, within the rules or with approval. If no approved carrier accepts, Wilson escalates. On payment, Wilson audits and reconciles each carrier invoice against the booked rate, documented shipment changes and supporting evidence, then pays the carrier from the Wilson Wallet under the customer's configured rules. Payments above approval limits or outside the rules wait for a person.

Wilson starts with assisted execution, and each owner decides when to widen the boundary for their own decision. Messages, confirmations and changes are recorded in shipment history, so the payment owner can see who approved a rebooking. Wilson replaces the TMS for freight execution and connects to the company's ERP or existing order flow.

Bring a recent load where the rate, an exception and the invoice each needed someone's sign-off, and see Wilson route each decision to the owner you name.