No category
The carrier revised the rate confirmation after acceptance. Which one applies?
Key Takeaways
When a carrier revises a rate confirmation after acceptance, the version that both sides agreed to applies, which is usually the original unless the shipper accepted the revision in writing. An AI logistics coordinator should keep every version, flag what changed, and ask the right person to accept or reject the revision before the load moves.
A rate confirmation is the document that states the agreed price and terms for one load.
A revision is a new version of that document sent after the first one was agreed.
A revision sent by one side does not replace the agreed version on its own.
Some revisions are valid, such as a correction for an agreed load change. Others are not.
Every version should be saved, with what changed and who accepted it.
Wilson, by Cartage, is an AI logistics coordinator that collects rate confirmations, compares versions with what was booked, and audits each invoice before payment.
Which rate confirmation applies when there are two versions?
The version both sides agreed to applies. In most cases, that is the original confirmation, unless the shipper accepted the revised version in writing. An AI logistics coordinator should treat a revision as a proposal until a person with the right authority accepts it.
A carrier may send a revised confirmation for many reasons. Some are good reasons: the shipper added a stop, changed the pickup time, or asked for a different trailer. Some are errors: the carrier fixed a typo or used the wrong load number. And some are attempts to change the deal: the carrier wants a higher rate or adds a fee that was not agreed.
The table below shows how to think about each case.
Reason for the revision | Which version applies |
|---|---|
Shipper requested a load change and agreed to the new cost | Revised version, once accepted |
Carrier fixed a clear typo to match the agreed rate | Revised version |
Carrier raised the rate without a load change | Original, unless shipper accepts the new rate |
Carrier added a fee not agreed | Original, unless shipper accepts the fee |
Carrier changed detention or TONU terms | Original, unless shipper accepts the change |
Two versions with no record of acceptance | Unclear; needs review |
TONU means truck ordered not used, a fee a carrier bills when a truck is sent but the load is canceled. Detention is a fee a carrier bills when its truck waits too long at a dock.
Why carriers send revisions
Carriers send revisions for practical reasons. Fuel prices change. A driver becomes unavailable and the replacement costs more. The dispatcher finds a mistake. Sometimes a carrier hopes a busy shipper will not notice a higher number. Understanding these reasons helps the team respond fairly: correct honest mistakes quickly, and say no clearly to changes that were never agreed.
The rule in one sentence
A revision applies only when both sides agree to it. A carrier cannot change an agreed price by sending a new document, and a shipper cannot change it by ignoring the carrier's request. Silence is not agreement.
What counts as acceptance
Acceptance should be clear and in writing. A signed revised form, an email that says "We accept the revised rate of $1,800," or an approval recorded in the shipment record all count. A coordinator saying "OK" on a phone call should be followed by a written note. An unread email does not count, and neither does a revision that sat in an inbox until pickup.
Why this matters at invoice time
If both versions sit in the file with no note, the invoice audit does not know which to use. The carrier will bill from the revised version. The shipper may expect the original. The dispute that follows depends on emails and memory. A clear rule and a clear record prevent it.
Revisions and the approved price
A revision that raises the cost also moves the load away from the approved price. The approver should see the original approval, the revised cost, and the reason in one place. If the new cost is within the person's limit and the reason is fair, the change can be approved. If not, it goes up to the next level.
Hypothetical example: a revision after acceptance
This example is hypothetical and does not describe a real customer. A carrier signs a rate confirmation for load 7102 at $1,650 all-in on Monday. On Wednesday, the day before pickup, it sends a revised version at $1,800, with no note. The AI logistics coordinator compares the two versions and flags the $150 increase. It asks the carrier for the reason. The carrier says diesel prices rose. The logistics manager decides to hold to $1,650, and the carrier agrees. The original version stays the active one, and the revision is saved as rejected.
When the carrier says the revision is standard
Some carriers say that revisions are part of their normal process, such as updating fuel each week. If the original confirmation was all-in, a weekly fuel update does not apply to that load. If the original said "plus fuel" and pointed to a fuel table, the fuel line can change as the table says, and no new acceptance is needed for that line. The original terms decide.
What should happen when a revised confirmation arrives?
When a revised confirmation arrives, the team should compare it with the active version, identify every change, find the reason, and decide to accept or reject it. An AI logistics coordinator should do the comparison right away and send the changes to the person who can decide.
Step 1: compare every field
The comparison should cover the rate, fuel terms, accessorials, detention and TONU terms, dates, stops, equipment, and reference numbers. An accessorial charge is a fee for extra service beyond the base rate, such as a liftgate. A change in any field may affect cost.
Check fields that did not seem to change
A revision may change a small field that is easy to miss, such as the free time at delivery or the payment terms at the bottom of the page. The comparison should cover every field, not only the ones the carrier mentions in its email. Hidden changes are the ones that cause surprises later.
Step 2: show the changes clearly
The changes should be shown side by side. For example:
Field | Original | Revised |
|---|---|---|
Linehaul | $1,650 all-in | $1,800 all-in |
Detention | 2 hours free, $50/hour | 1 hour free, $75/hour |
Pickup | Thursday 8 a.m. | Thursday 8 a.m. |
A side-by-side view lets a person see the effect in seconds.
Watch the timing of the revision
The timing tells a story. A revision sent minutes after the first confirmation is often a correction. A revision sent the day before pickup, with a higher rate, is often a renegotiation. A revision sent after delivery may be an attempt to add charges. Timing alone does not decide the outcome, but it helps the person who must decide.
Step 3: find the reason
Some revisions explain themselves, such as an added stop the shipper asked for. Others need a question to the carrier. The reason helps decide whether the change is fair.
Who decides on a revision
The person who decides should be the one whose approval limit covers the change. A small correction can be accepted by the coordinator. A rate increase may need the logistics manager. A large change or a new payment term may need finance. The AI logistics coordinator can route each revision to the right person based on the size and type of change.
Step 4: decide and record
The person with authority decides. If the change is accepted, the revised version becomes the active one. If not, the original stays active, and the carrier is told. Either way, the decision, the person, and the time are saved with the load.
Respond to the carrier quickly
A revision deserves a fast answer. If the shipper accepts it, the carrier needs to know the load is still on. If the shipper rejects it, the carrier needs time to decide whether it will run the load at the original rate. A late answer can lead to a truck that does not show up. An AI logistics employee can send the answer as soon as the decision is made.
Hypothetical example: a rejected fee
This example is hypothetical and does not describe a real customer. A carrier sends a revised confirmation that adds a $75 "driver assist" fee. The tender did not ask for driver assist, and the shipper's dock loads the freight. The AI logistics coordinator flags the new fee and asks the carrier why it was added. The carrier says it was added by default. The coordinator rejects the revision, and the carrier sends a corrected version without the fee.
Do not let the latest file win by default
Many systems treat the newest document as the current one. That is a risk with rate confirmations. The newest file is only the current one if it was accepted. Software should mark which version is active based on acceptance, not on upload time.
Put Wilson to work on your freight
Wilson handles quoting, booking, tracking, carrier communication, invoice auditing, and payments. Unlimited use, $0. You pay one rate per load.
Which revisions are usually valid?
Revisions are usually valid when they reflect a change the shipper asked for, or when they correct a clear error so the document matches the agreed terms. An AI logistics coordinator should still check that the revised numbers match what was agreed for the change.
Valid does not mean automatic
Even a valid revision needs a quick check and a recorded acceptance. Making it automatic lets errors slip through with the valid changes. A short review keeps the process both fast and safe.
Shipper-requested changes
If the shipper adds a stop, changes the delivery date, or asks for a different trailer, the carrier may need to change the price. The revised confirmation should show the change and the new cost. The shipper should check the new cost against what was agreed for the change and against approval limits.
When the shipper made the error
Sometimes the original confirmation was wrong because the shipper's tender was wrong. For example, the tender listed the wrong delivery city, and the carrier priced the wrong lane. The carrier's revision may be fair. The shipper should review the change honestly, approve it if the new price fits the real lane, and fix the tender process so the error does not repeat.
Load changes need the carrier's new price in writing
When the shipper asks for a change, the carrier should state the new price in writing before the change happens.
Corrections
If the first confirmation had a typo, such as the wrong date or a wrong rate that did not match the acceptance, a corrected version is fine. The check is simple: does the revised version now match what was agreed?
Check the revised cost against approval limits
Even a valid revision may need approval. If the shipper asked for a change and the carrier priced it at $200, the coordinator may still need a manager's approval if $200 is above the coordinator's limit. The fact that the change was requested does not mean any price is acceptable.
Revisions that need a closer look
Revision | Why it needs a closer look |
|---|---|
Rate up with no load change | Carrier wants a new deal |
New accessorial fee | Service may not be needed |
Shorter free time | Raises detention risk |
Higher TONU | Raises cancellation cost |
New payment terms | Affects cash flow |
Revisions after pickup
Sometimes a carrier sends a revision after the truck has picked up. It may add detention at pickup or a change made during the trip. These revisions should be checked against event records, such as arrival and departure times. If the event happened and the terms allow the charge, the revision may be valid. If not, it should be rejected.
Hypothetical example: a valid revision
This example is hypothetical and does not describe a real customer. A distributor's customer asks for a delivery appointment two hours earlier. The carrier needs a team of two drivers to make it and sends a revised confirmation adding $200. The logistics manager approves the $200 because the customer asked for the change. The AI logistics coordinator marks the revised version active, saves the approval, and notes that the customer requested the change.
How should freight software keep confirmation versions clear?
Freight software should keep every version, mark one as active, show what changed between versions, and record who accepted each change. An AI logistics coordinator should make it obvious which version the invoice audit will use.
What a good version record shows
Field | Example |
|---|---|
Version number | v1, v2, v3 |
Received | Date and time |
Sent by | Carrier contact |
Changes from previous | Rate, terms, dates |
Reason | Customer change, typo, carrier request |
Status | Active, superseded, rejected |
Accepted by | Name and time |
Tie versions to the conversation
Each version should link to the email or message that came with it and to the reply that accepted or rejected it. The document alone shows what changed. The conversation shows why and who agreed. Together, they settle almost any later question.
Keep rejected versions
A rejected revision should not be deleted. It shows that the carrier tried to change the deal and that the shipper said no. If the carrier later bills from the rejected version, the record shows why the invoice should be corrected.
Show who changed the status
The record should show who marked each version active or rejected, and when. If a coordinator accepted a revision above their limit by mistake, the record shows it, and the team can correct it before payment.
Link the active version to the invoice audit
When the invoice arrives, the audit should use the active version. If the invoice matches a rejected version, the audit should flag it. This is the main reason to track status, not just files.
Name files clearly
Each version should have a clear name: load number, document type, and version. For example, "Load 7102 – rate confirmation – v2 – rejected." Clear names help anyone who opens the folder. They also help when records are exported for finance or an audit.
Hypothetical example: two versions, no notes
This example is hypothetical and does not describe a real customer. An auditor reviewing an invoice finds two rate confirmations for the same load: one at $1,200 and one at $1,350. Neither has a note. The invoice is for $1,350. The auditor spends an hour searching emails and finds that the $1,350 version was never accepted. After the team adopts version status, the next case like this is resolved in seconds because the record shows "v2 – rejected."
Avoid side agreements
Sometimes a dispatcher and a coordinator agree on a change by phone and nobody updates the document. The invoice then reflects a change no document shows. Any change agreed by phone should be followed by a written note or a revised confirmation that is accepted.
Share the active version with the carrier
When a revision is rejected, send the carrier the active version again with a short note: "We are keeping the rate confirmation dated Monday at $1,650 all-in." This makes sure both sides are looking at the same document. It also gives the carrier a clear chance to decline the load if it will not run at that rate.
Common version mistakes
Saving all versions with the same name.
Treating the newest file as active.
Deleting old versions.
Accepting a revision without checking all fields.
How should you test version handling in freight software?
Test version handling by sending a revised confirmation after acceptance and checking whether the software spots the changes, routes them for a decision, and uses the right version at invoice time. An AI logistics coordinator should never let a revision become active by default.
Demo tests for revised confirmations
Buyer requirement | Demo test | Evidence to see |
|---|---|---|
Detects revision | Send a second version after acceptance | Revision flagged |
Shows changes | Change rate and detention | Side-by-side changes |
Asks for reason | Send without a note | Reason requested from carrier |
Routes decision | Revision raises cost above limit | Sent to approver |
Keeps original active | Reject the revision | Original stays active |
Audits correctly | Invoice from rejected version | Invoice flagged |
Keeps history | Review the load | All versions with status |
Test a revision after pickup
Ask the vendor to show a revision that arrives after pickup with added detention. The software should compare it with the arrival and departure times and the free time in the active version. It should approve the charge only if the times support it.
Demo questions about revised confirmations
How does the AI logistics coordinator know a document is a revision?
Does it compare every field, or only the total?
Which version does the invoice audit use?
Can a revision become active without a person's approval?
Are rejected versions kept?
Hypothetical example: a demo that overwrites files
This example is hypothetical and does not describe a real customer. In a demo, a buyer uploads a revised confirmation with a higher rate. The software replaces the first file with the new one and shows only the higher rate. There is no flag and no history. The buyer marks this as a fail, because the audit would later approve an invoice at a rate nobody accepted.
How to measure version control
Track revisions per 100 loads, the share accepted and rejected, and the number of invoices billed from a rejected or unclear version. The last number should be near zero.
Ask how revisions show up for managers
Ask how a manager sees a pending revision. It should appear as a clear request with the changes, the reason, and a way to accept or reject in one step. If the manager must open several screens or files, revisions will wait too long.
Scoring and warning signs for revised confirmations
Score each test as pass, partial, or fail. A pass means the revision was flagged, decided, and the right version used at invoice. A partial means it was flagged but the newest file was treated as active. A fail means the revision was filed without notice. Warning signs include overwriting files, no version status, and no link between versions and the audit.
Where does Wilson fit when a carrier revises a rate confirmation?
Wilson, by Cartage, is an AI logistics coordinator that collects rate confirmations, compares new versions with what was booked, and routes changes within the customer's approval limits. 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 handles a revision
When a revised confirmation arrives, Wilson compares it with what was booked and flags the changes. Changes that raise cost above the customer's limits wait for a person. Wilson negotiates rates against the customer's rate targets within configured rules and approval limits. Every version and decision is saved in the shipment record with change history.
How Wilson audits the invoice
When the carrier invoice arrives, Wilson audits and reconciles it against what was booked, including any accepted changes. 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. An optional deployment fee applies only if the customer wants Cartage to handle setup.
What Cartage asks about revised confirmations in discovery
Cartage asks how often carriers send revised confirmations, who decides on rate changes after acceptance, what approval limits apply, and how disputes are handled today. These answers shape how an AI logistics coordinator treats revisions.
What changes with clear version control
With Wilson tracking versions, nobody has to wonder which confirmation is current. The active version is marked, revisions are flagged as they arrive, and decisions are recorded. When the invoice arrives, the audit uses the right version without a search. Shipment records are searchable and exportable with change history.
What Wilson does not do with revisions
Wilson does not accept rate changes outside the customer's approval limits. It does not approve new carriers; the customer approves each carrier before Wilson uses it. Specific version workflows should be confirmed in a demo.
Questions to ask your team about revised confirmations
Ask how many revised confirmations arrived last month, how many were accepted without review, and how many invoices led to disputes about which version applied. The answers show whether version control needs work.
Where teams start with revised confirmations
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 handling rate changes can read what happens when a carrier changed the rate after booking. Teams checking bills can see which rate the final invoice should match. Teams building review steps can learn how freight invoice audit works before payment.
FAQs
Which rate confirmation applies after a carrier revises it?
The version both sides agreed to, usually the original unless the shipper accepted the revision in writing. An AI logistics coordinator should treat a revision as a proposal until it is accepted.
Is a revised rate confirmation valid on its own?
No. A revision sent by one side does not replace the agreed terms. An AI logistics employee should route it to a person who can accept or reject it.
Should old versions be deleted?
No. Keep every version with its status. An AI logistics coordinator uses the record to show which version is active and why.
What if the invoice matches a rejected version?
The invoice should be flagged and corrected. An AI logistics employee audits against the active version, not the newest file.
Sources
Cartage, Wilson product scope and pricing position, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator handles a revised rate confirmation, keeps every version clear, and audits the invoice against the right one: talk to the Cartage team.
Put Wilson to work on your freight
Wilson handles quoting, booking, tracking, carrier communication, invoice auditing, and payments. Unlimited use, $0. You pay one rate per load.
Other latest news and success stories
January 25, 2022
Ergomotion books 1,800+ shipments end to end with Wilson
Read more →
January 25, 2022
Flexocraft runs its daily freight operation with Wilson
Read more →
