Design a Freight Accessorial Invoice Review Queue

Why accessorial charges need their own queue

Freight invoices often combine a base transportation charge with accessorial items such as detention, fuel surcharge, liftgate service, inside delivery, or a reconsignment fee. The base charge may match the rate agreement while an accessorial line remains unsupported. Mixing both into one approval decision makes the invoice look approved when only part of it has been explained.

A separate accessorial queue lets the team test each charge against the service record and the applicable rate term. It also creates a useful history of recurring exceptions. If the same charge appears every month without documentation, the issue may be a missing rate schedule, a carrier process problem, or a service change rather than an isolated billing error.

Tie each charge to a rate and service record

For every accessorial line, capture the carrier, invoice number, shipment or tracking reference, charge code, amount, service date, and the rate source that is supposed to govern the charge. The rate source might be a contract, a tariff, a signed quote, or an approved accessorial schedule. Record the version or effective date so a later reviewer knows which terms applied.

Then attach the service evidence: a delivery receipt, appointment record, scale ticket, gate log, or carrier event history. The evidence does not have to prove that the charge is correct. It has to let the reviewer decide whether the charge is supported, disputed, or still missing information. That distinction is the core of the queue.

Use the related specialist service role as a starting point for defining scope and evidence.

Classify exceptions with consistent reasons

Use a short reason list so the queue can be reviewed and compared over time. Useful categories include no rate reference, rate mismatch, missing service evidence, duplicate charge, wrong shipment, wrong date, fuel index question, and carrier credit pending. Avoid a generic other category unless a reviewer adds a specific note and assigns a follow-up owner.

The reason should describe what is missing or inconsistent, not who is at fault. A note that says the detention charge has no appointment record is actionable. A note that says the carrier is wrong invites an argument without a next step. Keep the language factual and attach the source that supports the classification.

Keep disputes inside the review record

When a charge is disputed, record the dispute date, the amount, the carrier contact or portal reference, the evidence sent, and the expected response date. Do not let the dispute live only in an email thread. The payables record should show whether the disputed amount is on hold, paid under reservation, or excluded from the current run.

A dispute is not a reason to stop reviewing the rest of the invoice. Split supported and unsupported lines so the approved portion can move while the disputed portion remains visible. This reduces unnecessary payment delays and prevents a small question from hiding the rest of the payable.

Federal Motor Carrier Safety Administration provides public guidance that can help your team test relevant workflow assumptions.

Measure queue health without guessing

Track open accessorial items by age, reason, carrier, and amount. Also track how often a dispute results in a credit, a corrected invoice, or a payment. Those outcomes tell you whether the queue is resolving questions or simply moving them around. Do not present the counts as industry benchmarks; they describe your own population and definitions.

Review a sample of closed items each month. Confirm that the rate source was current, the service evidence matched the shipment, the reason code was accurate, and the final disposition was recorded. If the same reason keeps appearing, fix the upstream cause, such as a missing rate schedule or an unclear delivery process.

Compare this approach with our guide to the next related workflow.

Start with one carrier lane

Pick one carrier and one common accessorial category. Define the required fields, the evidence sources, the reason list, and the reviewer. Run the queue for a month and compare the results with the prior process. Look for reduced search time, fewer unclear holds, and a clearer record of carrier responses.

Add categories or carriers only after the first lane is stable. Freight terms vary widely, and a queue that works for parcel delivery may not fit a dedicated truckload lane. The operating model should follow the evidence and the contract, not a generic template.

Common questions answered

Ready to create a clearer support role?

Bring the workflow that consumes the most attention. We will help you shape the role, handoff, decision boundaries, and review points.