Freight Invoice Audit: Carrier Bills Paid at the Contracted Rate, Within the Cash Cap

Why freight bills slip past a busy audit desk

A weekly freight audit has simple rules. Each carrier invoice should match the contracted rate for its lane and weight tier, the fuel surcharge for the week the freight moved, and only the accessorials someone authorized. The bill of lading says what really shipped. When the invoice and the paperwork agree, it gets paid. When they do not, someone decides whether to short-pay, dispute or hold.

The pieces sit in different places. The invoice register is an Airtable base, bills of lading and reweigh certificates land in Box, the rate card and fuel table are documents in Google Drive, carriers argue their case by email, and treasury posts the week's cash cap in Slack. A carrier that bills the heavier tier, a reference that appears on two invoices, or a remittance that picks up last week's invoice is easy to miss when an analyst is switching between six windows.

Who works in the room

Each pay week gets its own Kylon room, opened every Monday by an automation with the week's invoice range. A message that names no agent goes to Ryan, the room's default. Questions about runs or the remittance reach Myco, which already owns that work in the thread. When a carrier reply changes an invoice, Fin mentions Ryan with the invoice number and the evidence, and Ryan leads the thread until the re-priced record is approved. Fin drafts in Gmail and Outlook as the person it is working for, checked on every call.

A pay week from first pass to close-out

The audit policy, rate card and fuel table live in one Drive folder linked from the room guidelines, so every agent prices from the same version. Each stage stops at a person.

When a carrier pushes back or the contract moves

Mid-week changes arrive by email. A carrier sends a reweigh certificate, confirms that two invoices with the same reference were separate pickups, or disputes a short-paid liftgate charge with a signed delivery receipt. Fin reads the reply and hands the affected invoices to Ryan, who re-prices only those records and notes on each one what changed and which message it came from. Each carrier thread gets one reply covering every invoice in question, not one reply per invoice.

A rate amendment is the change most likely to go wrong. The carrier manager posts that the Phoenix to Denver lane has a new rate for one weight tier. Ryan selects invoices on that lane, filters them by the tier of the true weight rather than the weight billed, and re-prices only those. Everything else keeps its audited amount. The thread shows the before and after for each moved invoice, and the run history keeps each step for the day a carrier asks how a figure was reached.

What the checks catch

• An invoice priced from the weight the carrier billed when the bill of lading or a reweigh certificate puts it in a lighter tier
• Two invoices sharing a bill of lading reference, held as a possible duplicate until the carrier confirms they were separate shipments
• A remittance line for an invoice outside this cycle, which would pay it twice or before it was audited
• A rate amendment applied to every invoice on a lane, when only those whose true weight falls in the amended tier should move
• A fuel surcharge taken from the invoice date instead of the week the freight moved

What stays with people

• Approving each disposition, short-pay and dispute before the register changes
• Setting the cash cap and approving any run that would exceed it
• Sending every remittance advice and carrier reply, which Fin prepares as a draft
• Deciding how an amendment applies when its wording leaves room for doubt

Integrations in this workflow

Kylon is not a freight payment system and it does not replace one. It works alongside the register, the document store and the two mailboxes the desk already runs, and keeps the coordination between them in one room.

• Airtable
• Box
• Gmail
• Google Drive
• Outlook
• Slack

• Airtable holds the invoice register, the payment runs and the close-out rows
• Box stores bills of lading, delivery receipts and reweigh certificates
• Google Drive keeps the rate card, the fuel surcharge table and the audit policy
• Gmail carries the dispute threads with carriers, answered through drafts a person sends
• Outlook is the accounts payable mailbox, where remittance advice goes out once the AP specialist sends Fin's draft
• Slack is where treasury posts the cash cap and the shipping dock answers weight questions

Where to start

Begin with a single pay week and one carrier. Connect the Airtable base that holds the register, point the room at the Box folder where bills of lading land, and put the rule that matters most in the room guidelines: price from the true weight, and nothing is written to the register or added to a run until the audit lead approves it.

“The audit did not get stricter. It got traceable, because every short-pay now points to the document behind it.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.