Does the rate confirmation preserve the price that was approved?
Key Takeaways
A rate confirmation preserves the approved price only when someone checks that the price on the document matches the price that was approved, and then checks the invoice against that same document. An AI logistics coordinator should carry the approved price from the quote, through the tender and confirmation, to the invoice, and flag any step where it changes.
- An approved price is the rate a person with authority agreed to pay for a load.
- The price passes through several steps: quote, approval, tender, acceptance, rate confirmation, and invoice.
- At each step, the number can change by mistake, by misunderstanding, or by a real renegotiation.
- The rate confirmation is the best place to lock the approved price in writing with the carrier.
- Any change after approval should go back to someone with the right approval limit.
- Wilson, by Cartage, is an AI logistics coordinator that negotiates within the customer's rate targets and approval limits and audits invoices against what was booked.
Where can an approved price change between quote and invoice?
An approved price can change at any handoff between the quote and the invoice: when the tender is written, when the carrier accepts, when the rate confirmation is issued, when the load changes, and when the invoice is prepared. An AI logistics coordinator should check the price at each handoff, not only at the end.
The path of a price looks simple. A carrier quotes $1,500. A manager approves it. A coordinator tenders the load at $1,500. The carrier accepts. The rate confirmation says $1,500. The invoice says $1,500. In real work, each step is done by a different person or system, often on a different day. Each step is a chance for the number to drift.
The table below shows where drift happens.
| Step | How the price can change |
|---|---|
| Quote | Quote is for a different equipment or date |
| Approval | Approved number is rounded or misread |
| Tender | Coordinator types a different number |
| Acceptance | Carrier accepts "plus fuel" instead of all-in |
| Rate confirmation | Carrier form shows a different rate or terms |
| Load change | New stop or new time adds cost without approval |
| Invoice | Extra lines added; wrong load billed |
The approved price is a decision, not just a number
The approved price is the result of a decision. A manager or finance lead looked at the cost and said yes. If the price changes later, that decision no longer covers the new cost. The new cost needs its own decision. Treating the approved price as a decision makes it clear why changes need approval.
Why matching documents can still be wrong
Many checks compare one document with the next. The confirmation is compared with the tender, and the invoice with the confirmation. If an error enters early, every later document carries it forward, and every comparison passes. Only a check against the original approval catches errors that started inside the team. This is the main reason the approval must be saved with the load.
Who approves freight prices
In many companies, the coordinator approves routine loads within a set range, a logistics manager approves larger or unusual loads, and finance approves loads above a high limit or outside the budget. Some companies require approval for every spot load. A spot load is a one-time load priced at the current market rate, not under a contract. The approval structure should be clear before software can enforce it.
Small drift is still drift
A change from $1,500 to $1,550 may look small. But if it happens without approval, it breaks the control. Over many loads, small unapproved changes add up. They also make budgets less reliable, because the actual cost no longer matches what was planned.
Quotes expire
A quote is often valid for a short time, such as a few hours or a day. If approval takes too long, the carrier may no longer honor the quoted price. Then the tender goes out at a new price that was never approved. Fast approvals protect the approved price as much as careful checks do. The approval and the tender should happen close together.
Hypothetical example: drift at the tender
This example is hypothetical and does not describe a real customer. A manager approves a quote of $2,150 for a reefer load. The coordinator writes the tender at $2,500 by mistake. The carrier accepts quickly. The rate confirmation shows $2,500. The invoice shows $2,500. Every document matches every other document, so the audit passes. Only a check against the approval would show that $350 more was paid than was approved.
Contract rates and spot rates
Contract rates are agreed ahead of time for a lane, often for months. Spot rates are agreed for one load. For contract loads, the approved price is the contract rate, and the confirmation should match it. For spot loads, the approved price is the quote someone approved for that load. The software should know which kind of rate applies, so it compares against the right number.
How does the rate confirmation lock in the approved price?
The rate confirmation locks in the approved price when the team checks that its rate and terms match the approval before it is signed or accepted. An AI logistics coordinator should compare the confirmation with the approved quote, not only with the tender, because the tender itself may be wrong.
Why the confirmation is the right place to lock the price
The confirmation is the last document both sides agree to before the truck moves. After pickup, the shipper has less leverage. After delivery, the conversation moves to billing. Locking the approved price on the confirmation means the carrier has agreed to it in writing at the moment it matters most.
Compare with the approval, not just the tender
Most checks compare the confirmation with the tender. That catches carrier errors. It does not catch errors made when the tender was written. The stronger check compares the confirmation with the approved quote. If both the tender and the confirmation differ from the approval, the problem started inside the team.
Check the carrier too
The approved price was for a specific carrier. If the load is moved to another carrier, the price may still be the same, but the approval may not cover the new carrier. The new carrier should be on the approved list. Wilson books only carriers the customer has approved, and the customer approves each new carrier before Wilson uses it.
Lock the terms, not just the total
The approved price is more than a total. It includes whether fuel is included, which accessorials are expected, and what detention terms apply. An accessorial charge is a fee for extra service beyond the base rate, such as a liftgate. Detention is a fee a carrier bills when its truck waits too long at a dock. A confirmation with the same total but different terms may cost more later.
Check before signing, not after
If the shipper signs the carrier's form, it should sign only after the comparison. If the shipper sends its own form, it should accept the signed copy only after checking that nothing was changed. A signature on a wrong price makes the error much harder to reverse.
What the check should compare
| Approval field | Confirmation field |
|---|---|
| Approved rate | Linehaul or total |
| All-in or plus fuel | Fuel terms |
| Expected accessorials | Accessorials listed |
| Equipment | Equipment type |
| Pickup and delivery dates | Dates on confirmation |
| Carrier | Carrier name and MC number |
An MC number is a carrier's operating authority number from the Federal Motor Carrier Safety Administration.
When the carrier's form uses different words
Carriers use different names for the same thing. One calls it "linehaul," another "freight charges," another "rate." One says "all-in," another "flat," another "includes FSC." The check should understand these as the same terms. If the software cannot read a term, it should ask a person rather than guess.
Keep the approval with the load
The approval should be saved with the shipment record: who approved, when, and what number. Many teams approve quotes in email or chat and never connect the approval to the load. Later, nobody can prove what was approved. An AI logistics employee can save the approval as part of the load the moment it happens.
Hypothetical example: same total, different terms
This example is hypothetical and does not describe a real customer. A manager approves $1,800 all-in with two hours of free time at each stop. The carrier's confirmation shows $1,800 all-in with one hour of free time. The AI logistics coordinator flags the difference in detention terms. The carrier agrees to two hours and sends a corrected copy. A later delivery with a two-hour wait costs nothing extra, as approved.
What should happen when the price changes after approval?
When the price changes after approval, the change should go back to someone with the authority to approve the new amount. An AI logistics coordinator should send the change, the reason, and the options to that person before the load moves.
Approval limits decide who approves
Approval limits set who can approve what. A coordinator may approve changes up to a small amount. A manager approves larger ones. Finance approves changes above a set level. The limits should be written down and applied the same way on every load. Wilson negotiates rates against the customer's rate targets, within configured rules and approval limits. Rates outside those limits go to the logistics team.
Who tells the carrier
Once a change is approved, the carrier should get an updated rate confirmation or a written note that states the new total. Without it, the carrier may bill the old price, the new price, or something in between. The update closes the loop and gives the audit a clear number to check.
Common reasons for a change
| Reason | Example | Approval needed? |
|---|---|---|
| Carrier error | Typo on confirmation | No; correct the document |
| Shipper error | Wrong number on tender | Correct; review if carrier already planned on it |
| Load change | Added stop | Yes, if cost rises above limit |
| Market change | Carrier wants more before pickup | Yes |
| Service added | Liftgate needed at delivery | Yes, if above limit |
Limits should match risk
Approval limits work best when they match the risk. A small dollar limit for coordinators keeps routine changes fast. A higher limit for managers covers most real changes. Finance sees only large or unusual ones. If limits are too low, managers drown in small approvals. If they are too high, large changes pass without a second look.
Record the new approval
When a change is approved, the new approval replaces the old one for that load. The record should keep both: the first approval and the change. This history shows why the final cost differs from the first plan.
Small changes still need a record
Even when a change is small enough for the coordinator to approve, it should be recorded. The note can be short: "Added $40 for appointment rescheduling, approved by coordinator under limit." Small notes add up to a clear picture of where extra costs come from.
Do not approve by invoice
Some teams let changes happen during the load and approve them only when the invoice arrives. By then, the cost is already spent. The approval becomes a formality. Moving the approval to the moment of the change keeps control real.
Do not reuse an old approval
An approval covers one load at one price. It should not be reused for a later load on the same lane, even if the price looks similar. Each load needs its own approval, or a standing rule that clearly covers it.
Hypothetical example: an added stop
This example is hypothetical and does not describe a real customer. A customer asks to add a second delivery stop the day before pickup. The carrier quotes $150 for the stop. The coordinator's limit is $100. The AI logistics coordinator sends the change to the logistics manager: "Load 6230: customer added stop in Peoria. Carrier quotes $150. Approved total was $1,700; new total $1,850. Approve?" The manager approves. The carrier sends an updated confirmation at $1,850, and the approval is saved with the load.
How does the invoice audit protect the approved price?
The invoice audit protects the approved price by comparing each invoice line with the confirmed and approved terms, not only with the carrier's own documents. An AI logistics coordinator should flag any charge that is above the approved amount or was never approved.
Three-way check
A strong audit compares three things:
The approved price and terms.
The rate confirmation and any approved changes.
The invoice.
If all three match, the invoice can be paid within the rules. If the invoice differs from the confirmation, the carrier may have billed in error. If the confirmation differs from the approval, the problem happened earlier, and the record should show whether a change was approved.
Approved budgets and actual spend
Many teams set a freight budget by month or by customer. When approved prices are kept from quote to invoice, actual spend tracks closely to the approvals. When prices drift, actual spend rises without anyone deciding it should. Keeping the approved price is how a team keeps its budget honest.
Event charges still need terms
Some charges depend on what happened, such as detention or a TONU. TONU means truck ordered not used, a fee a carrier bills when a truck is sent but the load is canceled. The approved terms set the rules, and event records show whether the charge applies. An audit should check both.
Hypothetical example: a detention charge within terms
This example is hypothetical and does not describe a real customer. A manager approves $1,600 with two free hours and $60 per hour of detention after that. The truck waits four hours at delivery. The invoice shows $1,600 plus $120 detention. The AI logistics coordinator checks the arrival and departure times, confirms two billable hours, and approves the $120 under the agreed terms. No new approval is needed because the charge follows terms the manager already approved.
Payment follows approval
Payment should follow the same approval rules. An invoice that matches the approved price can be paid within the rules. An invoice above the approved price should wait for a person. Customers who use Wilson pay their carriers through the Wilson Wallet. Payments above approval limits or outside the rules wait for a person.
Hypothetical example: a three-way check catches an early error
This example is hypothetical and does not describe a real customer. Finance approves $1,250 for a load. The tender, confirmation, and invoice all say $1,350. A document-to-document audit passes it. The AI logistics coordinator's three-way check compares the invoice with the approval and flags a $100 gap. The record shows no approved change. The logistics manager finds the tender typo, calls the carrier, and agrees to pay $1,250 as originally quoted. The carrier sends a corrected invoice.
What a broken chain looks like
- The approval lives in an email nobody can find.
- The tender is written from memory.
- The confirmation is filed without reading.
- The invoice is approved because it matches the confirmation.
Each step looks fine on its own. Together, they let the approved price slip away.
How should you test whether software preserves approved prices?
Test the software by approving a price, then introducing a change at each step, and checking which changes it catches. An AI logistics coordinator should catch changes at the tender, the confirmation, the load change, and the invoice.
Demo tests for approved prices
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Saves the approval | Approve a quote | Approval stored with the load |
| Checks the tender | Write a tender above the approval | Difference flagged |
| Checks the confirmation | Send a confirmation with different fuel terms | Terms difference flagged |
| Routes changes | Add a stop that costs more than the limit | Change sent for approval |
| Three-way audit | Send an invoice above the approval | Invoice held |
| History | Review the load | Original and changed approvals shown |
Hypothetical example: testing an expired quote
This example is hypothetical and does not describe a real customer. In a demo, a buyer approves a quote and then waits a day before tendering. The carrier's new confirmation shows a higher rate because the quote expired. The software compares the confirmation with the approval, flags the higher rate, and sends it to the manager with the original quote and the new number. The buyer marks this as a pass.
Demo questions about approved prices
- Where does the AI logistics coordinator store the approved price?
- Does it compare the confirmation with the approval or only the tender?
- How are approval limits set and changed?
- What happens when a load change raises the cost?
- How does the audit know which price was approved?
Ask how approvals connect to finance
Ask how approvals and final costs can be shared with finance. The data should show the approved price, any approved changes, the paid amount, and who approved each step. Finance should not need to ask logistics for this.
How to measure approval control
Track the share of loads where the final paid amount equals the approved amount, the number of changes approved after booking, and the dollars paid above approval without a recorded change. The last number should be close to zero.
Test with a real approval flow
Use your own approval flow in the demo. If finance approves loads above a certain amount, set that rule and send a load above it. If coordinators can approve small changes, set that limit and test a change just above it. The test should show the software follows your rules, not a generic setup.
Scoring and warning signs for approved prices
Score each test as pass, partial, or fail. A pass means the change was caught at the step where it happened. A partial means it was caught later, at the invoice. A fail means it was paid. Warning signs include approvals stored outside the system, audits that compare only documents from the carrier, and no history of changes.
Where does Wilson fit in preserving approved prices?
Wilson, by Cartage, is an AI logistics coordinator that books loads within the customer's rate targets and approval limits, collects rate confirmations, and audits invoices against what was booked. It works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured. EDI, or electronic data interchange, is a standard format that lets two companies' systems exchange business documents.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting.
How Wilson carries the approved price
Wilson negotiates against the customer's rate targets within configured rules and approval limits. Rates outside those limits go to the logistics team. Once a rate is approved and booked, Wilson collects the rate confirmation and checks it against what was booked. Changes after booking follow the same approval rules. Every step is saved in the shipment record with change history.
How Wilson audits and pays
When the carrier invoice arrives, Wilson audits and reconciles it against what was booked. Customers use the Wilson Wallet to pay their carriers. Payments above approval limits or outside the rules wait for a person. Wilson has no subscription or platform fee; its pricing is a percentage of the freight payments coordinated through the Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
What Cartage asks about approved prices in discovery
Cartage asks how quotes are approved today, who holds which approval limits, how changes after booking are handled, and how invoices are checked before payment. These answers become the rules an AI logistics coordinator follows.
What changes for finance
With approvals stored on each load and checked at each step, finance can see why each payment matches or differs from the approved price. Shipment records are searchable and exportable with change history. Questions about a cost can be answered from the record, without asking the logistics team to dig through email.
What Wilson does not do with approvals
Wilson does not approve rates or payments outside the customer's limits. It does not approve new carriers; the customer approves each carrier before Wilson uses it. Specific approval workflows should be confirmed in a demo.
Questions to ask your team about approved prices
Ask where approvals are stored today, how many loads last month were paid above the approved price, and who approved the difference. If nobody can answer quickly, the approval chain needs work.
Where teams start with approved prices
Wilson starts with assisted execution. Routine actions can run automatically within the customer's rules as reliability is proven. Timing depends on scope: most teams start on a few lanes and expand from there.
Teams setting approval steps can read how finance approves freight quotes before booking. Teams tracking final costs can see why the booked rate is not always the final cost. Teams building payment checks can review freight invoice controls before payment.
This article is part of our complete guide to rate confirmations from booking to invoice.
FAQs
Does the rate confirmation preserve the price that was approved?
Only if someone checks that it matches the approval and then checks the invoice against it. An AI logistics coordinator should carry the approved price through every step.
Where does an approved price usually change?
At the tender, the carrier's confirmation, a load change, or the invoice. An AI logistics employee should check the price at each handoff.
Who should approve a price change after booking?
A person whose approval limit covers the new amount. An AI logistics coordinator sends the change, the reason, and the options to that person.
Can an invoice match every document and still be wrong?
Yes, if the tender or confirmation was wrong from the start. An AI logistics employee should compare against the original approval, not only the carrier's documents.
Sources
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator carries an approved freight price from quote to rate confirmation to invoice, and routes every change for approval: talk to the Cartage team.