What this is
What is a Rate Confirmation Record?
What is a Rate Confirmation Record?
A Rate Confirmation Record is a KnowLogistics record that fixes the agreed linehaul rate, rate basis, fuel surcharge basis, accessorial charges and payment terms for a load or lane in writing, before the vehicle moves. It exists to give Invoice Verification something firm to check the carrier's invoice against, rather than relying on whatever was agreed by phone at tender acceptance.
How is a rate confirmation different from a load tender?
A Load Tender is the offer and acceptance of the load itself — who's carrying it, origin, destination, timing. The Rate Confirmation Record is the commercial terms attached to that acceptance: the rate, its basis, and the accessorials, captured separately because tenders are often accepted verbally or in a system that doesn't retain the full rate detail.
What does 'Rate Basis' actually mean on this record?
Rate Basis states how the Linehaul Rate is calculated — per mile, per load, flat rate, per pallet or per hour. The same headline number means something different depending on which basis it's quoted against, and a mismatch here is one of the more common sources of an invoice that looks wrong but technically follows what was said.
Scope
When is a rate confirmation record required?
This record is one step in the Payment and Procurement Fraud Control programme. Using it to hold the master supplier record, approve a purchase, or review a whole contract at renewal produces records that read fine on their own but don't line up with the rest of that programme later.
Use this template when
- A load or lane has been tendered and accepted, and the commercial terms need fixing in writing before the vehicle moves
- A carrier rate was agreed verbally or informally and needs converting into a document that Invoice Verification can check against
- An invoice has landed and needs matching against what was actually confirmed, including any variance to tariff
- A linked record needs this one to exist: Load Tender or Invoice Verification
- You are running the Payment and Procurement Fraud Control programme and this is one of its steps
Do not use it for
- Contract Register, which holds every commercial agreement, its value, term, renewal date and owner — not the rate for a single load or lane.
- Contract Review Record, which reviews an agreement before renewal, covering performance, price and risk over the life of the contract, not a single confirmed rate.
- Purchase Requisition Record, which requests a purchase and routes it for approval, before there's a confirmed rate to check anything against.
- Supplier Bank Detail Verification, which validates where the payment goes, not what the payment should be.
- Anything outside KnowLogistics, which belongs in the workspace that owns that process.
Compliance mapping
Which Contract requirements requirements does this satisfy?
This template is built against contract requirements rather than a single numbered standard, so the clauses below draw on the broker recordkeeping duty and the contract doctrine that governs when a quoted rate becomes binding.
| Clause | Requirement | Where it lands |
|---|---|---|
| 49 CFR 371.3 | A property broker retains a record of the rate, accessorial charges and compensation method agreed for each transaction with the motor carrier. | Header |
| 49 CFR 371.3 | The retained record covers the full rate structure — basis, surcharges, accessorials — not only the headline linehaul figure. | What was agreed |
| Contract requirement — offer and acceptance | Terms only bind once accepted in the same form they were offered; a rate agreed by phone and never returned in writing has not, in that form, been accepted. | What was agreed |
| Contract requirement — mutual assent | A carrier's written acknowledgement of the confirmation is what converts a quoted rate into an agreed one. | Confirmation |
| Contract requirement — course of dealing | A rate paid above the agreed tariff without documented approval risks becoming the precedent a carrier can later claim as the norm. | Confirmation |
| 49 CFR 371.3 | The record is retained specifically so it can be checked against the carrier's invoice, not filed once and forgotten. | Outcome |
| Contract requirement — dispute evidence | A variance between the invoice and the confirmed rate is resolved by reference to the written confirmation on file, not by whoever argues more persistently. | Outcome |
What it does not cover
- A confirmation logged only after the invoice was already received, which means it was written to win a dispute rather than to prevent one.
- Linehaul Rate Stated marked Yes with no Rate Basis selected, which leaves the figure open to being read as per-mile by one side and per-load by the other.
- Approved Where Above Tariff left blank on a rate that exceeds the agreed tariff, which lets an off-tariff rate through with nobody accountable for the exception.
- Retained For Invoice Matching marked No, which discards the one document that would have settled the next dispute.
- Dispute Raised marked Yes with no Invoice Variance figure entered, which turns a quantifiable discrepancy into an argument about who remembers what.
Global
Rate Confirmation Record requirements by country
Contract requirements set the baseline everywhere, but three contexts change how much this record is actually expected to prove.
49 CFR 371.3
The recordkeeping duty attaches to the party acting as broker, not automatically to the shipper or the carrier.
Where your organisation is arranging carriage as a broker, this record is close to a regulatory obligation rather than a nice-to-have — exactly these records get used to settle broker liability disputes.
CMR Convention, Art. 6
The consignment note is expected to record the carriage charges alongside the movement details, but it documents the shipment, not the commercial negotiation behind the rate.
A CMR consignment note is not a substitute for a written rate confirmation — it can show a rate was stated, but not that it was the rate actually agreed at tender.
Parol evidence doctrine
Once a rate is confirmed in a document both sides treat as the final statement of terms, earlier verbal negotiation generally cannot be used to contradict it.
The written confirmation, once issued and acknowledged, is what an auditor — or a court — looks at. Whichever phone call either side remembers best is not the record that decides the dispute.
How to complete it
How to complete a rate confirmation record, step by step
Filling in the Yes/No/N/A checks is mechanical. What actually decides whether this record protects anyone is a smaller set of calls made along the way.
A confirmation the carrier never actually responded to is a one-sided document, however clearly it's written. Acknowledged By The Carrier should mean something came back — an email reply, a signed copy — not that a set period passed without objection.
Approved Where Above Tariff answers a yes/no question, but the record doesn't itself distinguish approval granted in advance from approval rubber-stamped once the load has already gone. The first is a control; the second is a formality.
Dispute Raised is binary, but variances aren't. A threshold — in currency or in percentage of the confirmed rate — decides whether Invoice Variance gets escalated or absorbed, and that threshold, not the field itself, is what actually protects the spend.
Confirmed Before Movement can be true while Invoice Matched On Receipt is still unknown weeks later. Treating the record as done once the rate is confirmed loses the point of the Outcome section, which exists to close the loop back to the actual invoice.
What auditors find
Most common rate confirmation record findings
The same few gaps recur across most Rate Confirmation Record registers we've reviewed.
| Finding | Clause | What fixes it |
|---|---|---|
| Confirmed Before Movement is marked Yes on records dated after the load's linked pickup date. | Contract requirement — offer and acceptance | Compare the confirmation's Date and Time against the linked Tender ID's pickup date, and flag any confirmation logged after the fact. |
| Rate Basis is left blank on a material share of records with a Linehaul Rate entered. | 49 CFR 371.3 | Make Rate Basis mandatory whenever Linehaul Rate is populated. |
| Within Agreed Tariff is No with Approved Where Above Tariff answered Yes but no named approver anywhere on the record. | Contract requirement — mutual assent | Add a named-approver field that's required whenever Approved Where Above Tariff is Yes, rather than leaving it as an unattributed toggle. |
| Invoice Matched On Receipt is Yes despite a non-zero Invoice Variance on the same record. | 49 CFR 371.3 | Block Invoice Matched On Receipt = Yes whenever Invoice Variance is non-zero; route it to Dispute Raised instead. |
| Dispute Raised is Yes with Feeds Carrier Scorecard left as No. | Contract requirement — course of dealing | Auto-set Feeds Carrier Scorecard to Yes whenever Dispute Raised is Yes — a scorecard built from a filtered subset understates real carrier performance. |
| Retained For Invoice Matching is No on records that later turn out to be needed for a dispute. | 49 CFR 371.3 | Default Retained For Invoice Matching to Yes and require a stated reason whenever it's set to No. |
Case in point
Case in point: the fuel surcharge nobody wrote down
A carrier accepted a lane at a linehaul rate agreed by phone, with the fuel surcharge basis 'to follow' — never confirmed in writing. Six weeks and forty loads later, the fuel surcharge on every invoice was running on a different index than transport thought had been agreed, and Within Agreed Tariff had been marked Yes on all forty because no one had a document to check it against.
The dispute wasn't really about the fuel index. It was that Fuel Surcharge Basis Stated had been ticked Yes on every Rate Confirmation Record in the run, meaning the field had been treated as a box to clear rather than a fact to check — and by the time Finance asked to see the confirmation that supposedly settled it, there wasn't one that predated the first invoice.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- LOG-035
- Archetype
- Record
- Record ID
- RATE-2026-000
- Scoring
- Invoices matching rates
- Direction
- High is good
- Singleton
- Yes
- Basis
- Contract requirements
- Links
- Links Load Tender and Invoice Verification
- Tags
- Commercial, Carrier, Rate
- Sections
- 4
- Fields
- 41
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
15 fieldsConfirmation ID*
Auto sequence. Format RATE-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Carrier*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Load Or Lane Reference*
Tender ID
Links to LOG-007 Tender ID
Carrier 2
Linehaul Rate*
Rate Basis
Total Expected Cost
Verbal Rates Become Disputed Invoices
The rate agreed on the phone and the rate on the invoice differ often enough that confirming in writing before the vehicle moves pays for itself several times a year.
What was agreed
6 fieldsLinehaul Rate Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Fuel Surcharge Basis Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Accessorial Charges Listed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Detention Terms Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Equipment Type Confirmed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Payment Terms Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Confirmation
6 fieldsIssued In Writing Before Collection*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Acknowledged By The Carrier*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Matches The Tender Accepted*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Within Agreed Tariff*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Approved Where Above Tariff*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Retained For Invoice Matching*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Outcome
14 fieldsConfirmed Before Movement*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Variance To Tariff
Invoice Matched On Receipt*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Invoice Variance
Dispute Raised*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Feeds Carrier Scorecard*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Transport*
Signature*
Finance*
Second Signature*
LOG-035 · record IDs look like RATE-2026-000 · Links Load Tender and Invoice Verification
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form fixes a rate on paper. Checking that paper against every invoice that follows, and catching the pattern across lanes and carriers, is where this actually pays for itself.
Holds the Rate Confirmation Record against the linked Load Tender and Invoice Verification, and flags any invoice that lands without a matching confirmation on file.
Cross-checks the confirmed rate and lane against carrier performance and scorecard history, so a pattern of disputes on one carrier surfaces before the next tender goes out.
Tracks Within Agreed Tariff and Approved Where Above Tariff across every carrier, so an off-tariff exception granted quietly on one lane doesn't become the unapproved baseline for the next.
Coordinates the crew across KnowLogistics, KnowFleet and KnowComply, rolls variance and disputes into one view, and holds every write for your approval before it touches a record.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Glossary
Rate Confirmation Record definitions and key terms
- Linehaul rate
- The core transport charge for moving a load from origin to destination, before accessorials, fuel surcharge or detention are added. Its meaning depends entirely on the Rate Basis it's quoted against.
- Accessorial charge
- Any charge added to the linehaul rate for a service outside standard pickup and delivery — layover, liftgate, redelivery, extra stops. Disputes cluster here more often than on the headline rate, because accessorials are the terms most likely to be agreed loosely.
- Detention
- A charge the carrier applies when a vehicle is held at pickup or delivery beyond an agreed free time. Detention Terms Stated exists because an undocumented detention policy turns every delay into a negotiation.
- Tariff
- The standing rate agreement or rate card a carrier is contracted against for a given lane. A confirmed rate is checked against tariff specifically to catch quiet rate creep on individual loads.
- Fuel surcharge basis
- The index or formula used to calculate the fuel component of the rate, typically tied to a published fuel price benchmark. Stated separately from the linehaul rate because it moves independently and is renegotiated far less carefully.
FAQ
Frequently asked questions about rate confirmation record
What is the Rate Confirmation Record template based on?+
It's built against contract requirements rather than a single regulatory standard: obligations the parties accept in their own agreement, reinforced in the US by the broker recordkeeping duty at 49 CFR 371.3 where a broker is involved.
What sections does the Rate Confirmation Record contain?+
Four sections: Header, What was agreed, Confirmation, and Outcome. Together they hold 41 fields, 31 of which are required.
How is a Rate Confirmation Record scored?+
Scoring is invoices matching rates, with high being good. Confirmation and Outcome fields are weighted toward whether the confirmed rate actually held through to a matched invoice, not just whether the paperwork was completed.
Why is Dispute Raised scored Yes=0, No=2 instead of the other way round?+
Because a dispute is a cost, not a neutral event. Scoring it as a negative stops the record rewarding a pattern of confirm-then-dispute that would otherwise look fine on paper while quietly costing money on every invoice cycle.
What's the difference between Rate Basis and Linehaul Rate?+
Linehaul Rate is the number; Rate Basis is what the number means — per mile, per load, flat rate, per pallet or per hour. The same figure is a different price depending on which basis applies, which is why the two are captured as separate fields rather than one free-text rate line.
Can the template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to Load Tender and Invoice Verification come with it. Most teams install it as it is, run it for a lane or two, then adjust the tariff and variance thresholds to match their own contracts.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Payment and Procurement Fraud Control
Conflict of Interest Declaration
Records a declared interest that could affect a business decision, and how it will be managed
Anti-Bribery Risk Assessment
Assesses exposure to bribery and improper payments across procurement, permits, inspections and customer relationships
Contractor Rate and Invoice Verification
Verifies contractor invoices against agreed rates, hours recorded on site and work actually completed
Purchase Requisition Record
Requests a purchase, states the justification and routes it for the right level of approval
Supplier Bank Detail Verification
Verifies a supplier's bank details through an independently obtained phone number before any payment is set up or changed
Supplier Master Data Setup
Creates the supplier record in the systems that will use it, covering codes, terms, tax status, addresses and approval scope
More in Contracts and Commercial
Contract Register
Holds every commercial agreement, its value, term, renewal date and owner
Contract Review Record
Reviews an agreement before renewal, covering performance, price, risk, obligations accepted and whether to continue
Purchase Requisition Record
Requests a purchase, states the justification and routes it for the right level of approval
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- 49 CFR 371.3 — Property broker records
- CMR Convention, Art. 6 — Consignment note particulars
- Contract requirements — offer, acceptance and mutual assent doctrine
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.