Fleet Tolls and Violations: Notices Matched to the Driver Who Owes Them

Notices addressed to the company, owed by whoever had the truck

Toll agencies and cities send every invoice and violation notice to the registered owner, which means the fleet. Each one has to be matched to the driver who had the unit at that time, then given a disposition under the fleet's policy: company cost, charged back to an owner-operator's settlement, transferred to a customer who had the trailer on lease, or disputed. Every notice also carries an agency penalty and a dispute window that closes on a fixed date.

The notices are scanned into Box, the notice table is an Airtable base, and the driver log exports, the fleet policy and each agency's rules are in Google Drive. Agencies write to the fleet mailbox in Outlook, owner-operators write to the coordinator in Gmail, and dispatch confirms unit swaps in Slack. The ten notices drafted by hand last week already disagree with the logs, and the charge-back totals were built from those drafts.

Who works in the room

Scanned notices dropped into the thread go to Myco, the default agent and owner of each disposition. Nova checks Myco's rows and every total. It is mentioned when a batch is ready and leads the review thread until the totals tie out. Fin holds the room's Gmail connection and drafts replies from the fleet mailbox in Outlook, so any message that needs an answer routes to Fin once Nova has checked its numbers.

The monthly notice cycle

The fleet policy and each agency's rules apply in the same order to every notice. Every write to Airtable waits for the fleet finance lead.

Corrected logs, agency answers and a penalty waiver

The driver log anchors every notice. When safety corrects a log because a truck was swapped at the yard, every notice in those hours is re-derived, and both the driver and the disposition can change. Myco writes the whole row each time, with driver, disposition, base amount, penalty and total due together, so a partial update never leaves a total that disagrees with its parts.

Agency answers arrive in Outlook. A dispute is upheld and the notice drops to zero, or it is denied and the penalty stands. When an agency announces a penalty waiver, only notices whose dispute window has already closed qualify, and Myco checks each window date before proposing the change. Fin drafts the reply with the number of notices waived, and Nova checks that number against the rows before anyone presses Send.

What the checks catch

• A drafted notice charged to a driver who was not on the unit at that time
• A row updated with a new disposition but an old total due
• A penalty waiver proposed for a notice whose dispute window is still open
• A count in a reply, such as eleven changed or twelve waived, that does not match the records
• Notices in the corrected log hours that were not all re-derived

What stays with people

• Approving each disposition and charge-back before Airtable changes
• Deciding which notices to dispute
• Sending every reply to an agency or owner-operator, which Fin prepares as a draft
• Signing the monthly close-out

Integrations in this workflow

Kylon is not fleet management or toll billing software, and it does not try to be. It sits across Airtable, Box and the fleet's mailboxes and keeps the coordination between them in one room. Myco writes to Airtable through a lasting grant the fleet finance lead approved for this room, while Fin's drafts go through the coordinator's own accounts, checked on every call.

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

• Airtable holds the notice table with driver, disposition, amounts and total due
• Box holds the scanned notices, camera images and agency dispute decisions
• Outlook is the fleet mailbox where agencies send notices, decisions and waiver announcements
• Gmail carries the threads with owner-operators about charge-backs
• Google Drive keeps the fleet notice policy, each agency's rules and the driver log exports
• Slack is where dispatch confirms unit swaps and who was driving

Where to start

One month of notices from a single toll agency makes a good first cycle. Connect the Airtable notice table and the Box folder where scans land, add an automation that flags any notice whose dispute window closes within five days, and write one rule into the room guidelines: every update writes the full row, and the fleet finance lead approves it before Airtable changes.

“Every notice ends the month with a driver, a reason and a total that adds up.”

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.