--- title: "Fleet Toll and Violation Reconciliation | Kylon" description: "How a fleet team matches toll and violation notices to drivers, keeps charge-back totals right and handles disputes and waivers in one Kylon room, with people approving." url: "https://kylon.io/use-cases/fleet-tolls-and-violations" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Fleet Tolls and Violations: Notices Matched to the Driver Who Owes Them Use Case8 min read # Fleet Tolls and Violations: Notices Matched to the Driver Who Owes Them Toll and violation notices are matched to drivers, charged back or disputed, and kept consistent through log corrections and waivers in one Kylon room. Agents work Airtable from Box scans and driver logs, and the fleet finance lead approves each change. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## 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 People - Fleet finance lead Owns the notice policy, approves every disposition and charge-back, and signs the monthly close-out - Fleet coordinator Drafts first dispositions, files disputes and sends the replies - Safety manager Owns the driver logs and issues a correction when a unit swap was missed Agents - MycoNotice desk Matches each notice to the driver on the unit at that time, applies the agency's rules and proposes the full row for Airtable AirtableBoxOutlookGoogle Drive - NovaTotals checker Audits drafted dispositions, recomputes charge-back totals and checks every count before a reply goes out AirtableGoogle Drive - FinCorrespondence Drafts replies to agencies and owner-operators for a coordinator to send, and reads unit swaps from Slack Outlook[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) 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. ```mermaid flowchart TD dispose["Myco matches each notice to the
driver on the unit at that time"] audit["Nova checks the coordinator's
drafts against the driver logs"] approve["Fleet finance lead approves
before Airtable is written"] totals["Nova recomputes charge-back
totals from the full rows"] oktotals["Fleet finance lead
approves the totals"] logfix([Safety corrects a log
for a missed unit swap]) agency([An agency decides a dispute
or announces a penalty waiver]) rederive["Myco re-derives every notice
in the corrected hours"] waiver["Myco proposes the waiver only for
notices past their dispute window"] safety["Safety manager confirms,
fleet finance lead approves"] reply["Fin drafts each reply with
the number of notices waived"] check["Nova checks that number
against the rows"] send["Fleet finance lead approves,
fleet coordinator sends each reply"] close["Nova reads the close-out
counts from Airtable"] sign["Fleet finance lead
signs off the month"] audit --> approve dispose --> approve approve --> totals --> oktotals oktotals --> rederive & waiver logfix --> rederive --> safety agency --> waiver --> reply --> check --> send safety & send --> close --> sign class audit,dispose,totals,rederive,waiver,reply,check,close agent class approve,oktotals,safety,send,sign person class logfix,agency event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Draft audit | The coordinator's first ten drafted notices are checked against the driver logs and agency rules | Nova | The fleet finance lead approves each correction | | Notice disposition | The remaining notices get a driver, a disposition and a total due from the logs and each agency's rules | Myco, from Box scans and the log exports | The fleet finance lead approves before Airtable is written | | Charge-back totals | Totals per owner-operator and per customer are recomputed from the full rows | Nova | The fleet finance lead approves the totals | | Log correction | Every notice in the corrected hours is re-derived for driver and disposition | Myco | Safety confirms the correction and the lead approves | | Disputes and waiver | Agency decisions update disputed notices, and a penalty waiver applies only to notices past their dispute window | Myco, then Fin for the replies | The lead approves and a coordinator sends each reply | | Close-out | Paid, charged back, disputed and waived counts are read from Airtable | Nova | The fleet finance lead signs off the month | The notice month in stages. Notice numbers, units and amounts are illustrative. ## 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](https://kylon.io/integrations/gmail) - Google Drive - Outlook - [Slack](https://kylon.io/integrations/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. Set-up prompt Set up our fleet tolls and violations desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Box, Gmail, Google Drive, Outlook and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the fleet finance lead, the fleet coordinator and the safety manager. Help me invite them to this Room. 3. Build a Fleet Notices App with Notice, Unit and driver, Total due and Status, one record per notice. Pull in the open notices from Box and the existing drafted rows from Airtable. 4. Check each notice against the driver log exports, the fleet policy and our rules in Google Drive. Propose a driver, a disposition and a total due for every row. Show me any row where the fields disagree with the logs or where a penalty waiver is proposed for a notice whose dispute window is still open. 5. Flag any reply that states a count and hold it until the totals match the rows. The safety manager confirms each log correction first. The fleet finance lead approves every disposition, charge-back total and log correction before Airtable changes. The coordinator sends each reply after I prepare it as a draft. 6. Write the rule order and who approves what into this Room's guideline, including the rule that every update writes the full row before Airtable changes. 7. After one clean monthly cycle, offer to turn the dispute window check into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Backorder Communications: Customers Hear the Latest Date, Not Last Week's Customers hear the latest supplier date, an approved substitute or a cancellation offer, line by line. Agents work Pipedrive lines against Outlook notices and the Notion substitution table in one Kylon room, and every notice is a draft a rep sends. Logistics & supply chainEmail operationsSupport & customer success ](https://kylon.io/use-cases/backorder-communications)[ ### Carrier Damage Claims: Filings That Match the Tariff and the Paperwork Thirty freight damage claims, the filing manifest, carrier acceptances, a disputed delivery receipt and a tariff revision run through one Kylon room. Agents read ClickUp and the Dropbox claim packets, and the claims manager approves every change. Logistics & supply chainFinance operationsSupport & customer success ](https://kylon.io/use-cases/carrier-damage-claims)