Reconcile Accessorial Charges with Authorization Evidence

To review a questioned accessorial invoice line, connect five records: the service originally agreed, the event that occurred, the request for any change, the response covering that change, and the billed quantity and rate. Keep missing links visible. Evidence that unloading happened does not, by itself, establish who approved its price; an approval for one amount does not explain a different invoice amount.

This guide helps shipper transportation administrators and broker operations teams answer: Which service and authorization evidence supports this particular extra charge? The result is a concise evidence packet for the authorized invoice reviewer. The method organizes records; it does not decide contractual liability, a payment deadline or whether to pay, deduct or withhold money.

Begin with the invoice line, not a general complaint

An accessorial charge concerns an additional service or condition outside the stated base transportation scope. Start with the exact line under review: invoice number and revision, line number, charge description, shipment and stop references, currency, quantity, unit, rate and amount. Preserve the invoice as received.

Keep similar labels separate until their meaning is clear. “Unload assistance,” “unloading service” and a third party's unloading receipt may refer to one event, different work, or different billing relationships. A familiar charge code cannot resolve that question. Ask the issuing provider what service, event and calculation the line represents.

Record who issued the invoice and which party your organization engaged. If a broker invoice includes an underlying carrier or service-provider cost, identify the references without assuming the underlying amount must equal the customer charge. The applicable arrangement may distinguish a direct charge, reimbursement or another pricing basis. Obtain that basis instead of inferring it from a receipt.

This is a completed-work review. The carrier quote comparison guide covers the earlier decision about what to buy. Here, preserve the accepted offer from that decision and test how the questioned line connects to it.

Recover the applicable scope and its version

Collect the accepted quotation, agreement and referenced conditions, including versions, dates and the evidence linking them to this shipment. Record which services were included, which were conditional, and which required a separate response under the actual process. Do not replace a missing shipment document with today's website price.

Provider examples show why that distinction matters. Old Dominion's tariff page identifies its accessorial brochure as an abbreviated, nonbinding reference and says service pricing may vary with the rate structure. The page also provides access to canceled or replaced tariffs. Those statements support obtaining the applicable source and version; they do not supply the terms for your own invoice.

Schneider's FreightPower brokerage booking conditions state that additional charges may appear on the final invoice. This is a provider-specific example of why a quoted starting amount and a final invoice need reconciliation. It does not establish that every later charge is supported or that every provider uses the same conditions.

If two documents conflict, flag the exact passages and their versions for the authorized commercial or contract reviewer. Do not silently choose the sentence that produces the preferred amount. Likewise, do not invent a universal “written approval required” rule: whether separate authorization is necessary, and who can give it, depends on the applicable arrangement.

Separate the event, the request and the response

Build the record in three layers before calculating anything.

What happened: name the shipment, leg and stop; the service actually performed; the event date and times when relevant; and the evidence source. A facility receipt may support unloading completion. A gate record may support check-in. A driver's report may describe waiting. Preserve what each source actually says, including conflicting accounts.

What was requested: identify the requester, request time, service change, quantity, proposed rate or ceiling, affected shipment scope and any conditions. Record whether the request preceded the work or was a retrospective explanation. A request to “get the truck unloaded” may leave the price, payer and service-provider choice unspecified.

What was answered: preserve the response, sender's role, referenced request and limits. Distinguish acknowledgment, operational permission, commercial authorization and later reconciliation. A receiver can confirm the dock is available without necessarily answering who agreed to a charge. A responder can approve a price ceiling without accepting a different unit or additional service.

Where the appointment changed, link the shipment schedule revision record rather than reconstructing a new schedule inside the invoice worksheet. Its accepted version supplies context; it does not resolve the commercial question by itself.

Use neutral evidence states: linked, missing, conflicting, or awaiting authorized interpretation. “Missing from the packet” describes the search result, not proof that an approval never existed. Give each unresolved link an owner and a specific document or answer to obtain.

Worked example: USD 240 approved, USD 288 invoiced

Fictional teaching example. The shipment, parties, documents, prices and approval procedure are invented. These are not market rates, terms of the providers cited above, or a legal determination.

Shipment A-318 consists of 12 pallets delivered to one Ohio facility on October 14, 2026. The accepted quotation Q-318 revision 2 provides a base transportation price of USD 1,400. The receiver was to unload the trailer using its own team; separately hired unloading labor was outside that quoted scope.

For this example only, the parties' documented change procedure requires a named shipper commercial approver to accept separately hired unloading labor and its price before that service begins. A ceiling covers only the scope stated in the request. A changed price requires another response. The example makes no assumption about detention or other charges; those are outside this reconciliation.

The available evidence

All times below are October 14, 2026, local Eastern daylight time, UTC-04:00.

• 09:10, event E-1: the receiver reports that its unloading team is unavailable. The record identifies shipment A-318 and its only delivery stop.
• 09:15, request R-1: carrier operations proposes one outside unloading service covering all 12 pallets, at a total price of USD 240. The request excludes additional handling and asks for commercial approval.
• 09:22, response A-1: the named shipper approver accepts R-1's stated scope for a total not exceeding USD 240. The record preserves the response and the sender's assigned approval role.
• 09:30–10:10, service E-2: the unloading record identifies all 12 pallets and completion of the stated work. Receipt U-77 lists USD 240 for one unloading service. The record does not describe extra handling.
• October 15, invoice I-318: the carrier bills the USD 1,400 base price plus line 2, “unloading,” with quantity 12 pallets at USD 24 per pallet, totaling USD 288. The packet contains no revised request or response for that price basis.

The receipt, request and response all refer to the same shipment and stop. That establishes a useful connection. It does not make the invoice's per-pallet basis the approved basis.

Reconcile the amount without inventing an entitlement

The invoice arithmetic is internally correct:

Invoice line: 12 pallets × USD 24/pallet = USD 288
R-1 / A-1: one stated unloading service = USD 240
Difference requiring explanation: 288 − 240 = USD 48

Invoice's listed total: 1,400 + 288 = USD 1,688
Base plus recorded approval: 1,400 + 240 = USD 1,640
These are comparison amounts, not a payment instruction.

Dividing the approved USD 240 by 12 produces USD 20 per pallet as an arithmetic equivalent for this exact workload. It does not convert the fixed-service authorization into a standing per-pallet agreement. If the quantity had changed, the team would need to inspect the agreed scope and actual response rather than multiply USD 20 by a new count.

The evidence packet's disposition is:

“Unloading occurrence and the USD 240 request/approval are linked. Invoice I-318 line 2 uses a different price basis and is USD 48 higher. No revised price authorization is present in the reviewed packet. Provider explanation and authorized commercial review pending.”

That wording identifies the question without declaring the invoice invalid. The reviewer asks the invoice issuer for the basis of USD 24 per pallet and any applicable revision. A handling fee, an invoice-entry error or a later agreement are possibilities to investigate, not facts to choose between without evidence.

If the provider issues a correction or the parties document a later resolution, attach that record with its actual date and scope. Keep I-318 and A-1 intact. A later settlement does not become an approval that existed at 09:22.

Match units and clocks before judging a discrepancy

For a quantity charge, compare the billed unit with the accepted unit: stop, pallet, shipment, hour, attempted delivery or another defined measure. Verify that the quantity belongs to the billed service. Twelve pallets on a load do not prove twelve separately chargeable services. Use the shipment-quantity reconciliation guide when packing lists, handling units and delivery counts disagree.

For time-based charges, record the applicable event definitions, allowance, billing increment and rounding rule if documented. Then preserve each source timestamp, date, zone and event meaning. Gate arrival, completed check-in, unloading start and release are different events. Two conflicting times should remain separate observations until the evidence owner explains them.

Do not calculate a supposedly final charge when a material rule is missing. A useful packet can say: “Start time supported; release time conflicts; rounding rule not supplied.” That tells the next reviewer what would change the calculation. A spreadsheet's ability to produce a number is not evidence that its inputs are agreed.

Copy this accessorial evidence checklist

Use one short record for each questioned line. Keep controlled references to private shipment records rather than copying entire document collections into every handoff.

INVOICE LINE
Issuer / invoice revision / line:
Shipment / leg / stop / service date:
Charge description / currency:
Billed quantity / unit / rate / amount:

AGREED SCOPE
Accepted quote / agreement / version:
Referenced conditions / applicable date:
Included service / conditional service:
Approval requirement / role / evidence:

EVENT AND RESPONSE
Reported event / source / event time / zone:
Requested change / request reference / time:
Response / role / request version / time:
Approved scope / amount or formula / limits:
Work completed / receipt / quantity / source:

RECONCILIATION
Calculation / units / rounding source:
Evidence: linked / missing / conflicting
Exact unanswered question / owner:
Authorized interpretation needed:
Disposition / reviewer / actual review date:
Correction or resolution / prior records retained:
Next review / trigger:

Before handing it over, confirm five things: the line points to the correct stop; the applicable scope version is identified; the event and price authorization are separate; the arithmetic uses supported units; and every unresolved question has an owner. The packet should let a reviewer reproduce the comparison without treating an assumption as a source.

Frequently asked questions

What if no approval can be found?

Record where you looked and which response is missing. Ask the responsible parties for the relevant evidence, and have the authorized reviewer check whether separate approval was required by the applicable arrangement. Missing evidence in one packet is not proof that the work was unauthorized or that the charge is unpayable.

Does a delivery signature approve the accessorial price?

Read the document, its stated purpose and the applicable terms. Record exactly what the signer acknowledged and the person's role. Do not infer commercial approval solely because the signature supports delivery or completion of work. Refer an ambiguous document to the authorized reviewer.

How should an extra stop be reconciled?

Identify the added location and stop reference, who requested it, the instruction accepted, and any separate price response required by the actual agreement. Match the invoice's counting unit to that record. A changed route, a second attempt at the same location and an added delivery stop should not become interchangeable labels without checking the defined service.

What if a fixed charge becomes a per-pallet charge?

Preserve both versions and compare their scope, quantity and total. An equivalent rate calculated by division is useful arithmetic, but it is not evidence that the parties adopted that unit. Ask for the pricing basis or revision supporting the invoice, as in the worked example.

Which timestamp should be used when records conflict?

First identify the event the applicable charging rule measures. Preserve competing records with their source, time zone and event definitions. Ask the event owner to resolve the discrepancy; do not choose the earliest or latest time simply because it favors one party. Leave the dependent amount unresolved if the evidence remains insufficient.

Who decides whether the charge should be paid?

The people authorized under your organization's invoice, commercial and legal review process make that decision using the applicable terms and evidence. This worksheet gives them a traceable question. It supplies neither a universal payment rule nor authority to deduct or withhold an amount.

Close the evidence gap, then record the actual disposition

Start with one questioned line and identify the earliest broken connection: applicable scope, reported event, authorization, quantity or calculation. Obtain that evidence through the established business process and record the reviewer's actual conclusion when it arrives. Keep the delivery-performance scorecard separate: a service exception can inform operational improvement without deciding a billing dispute.

Sources reviewed October 16, 2026. John Hauler is USDOTData's editorial persona. The reconciliation method is an editorial recommendation; the shipment and approval procedure are fictional. Provider-specific source statements are attributed, and the worksheet does not determine legal responsibility or payment obligations.