What goes wrong when fleet work looks like retail work
Picture a landscaping company that has nine trucks and trailers serviced at the same independent shop. At the end of the month, its office manager asks for one thing: a summary of what was done to each unit, under which purchase order, and what is still owed. The shop's front counter can pull up every repair order, but fleet tickets are mixed in with walk-in oil changes and retail brake jobs. Someone spends an afternoon building the summary by hand, and the invoice goes out late.
Fleet work is valuable because it repeats. It also follows different rules than retail work: approvals come from a fleet contact instead of the driver, payment often comes on terms instead of at pickup, and the customer wants reporting by vehicle, not by visit. When fleet and retail tickets run through the same undifferentiated queue, those rules get lost.
TwoQM has already written about routing service requests, estimate approvals, and pickup updates and about special-order parts status for advisors and customers. This piece covers the billing side of fleet accounts: tagging fleet work as it happens so the monthly summary builds itself instead of being rebuilt at month-end.
Here is an original illustration, not a TwoQM client and not a measured result. A shop services a few small fleets: a plumbing company, a property maintenance crew, and a nonprofit with two vans. Drivers drop vehicles off and sometimes approve work themselves. Repair orders list the driver's name but not the unit number or purchase order. Some fleet tickets are paid at the counter by card, others are put on account, and nobody is sure which. At month-end, the fleet customer disputes a charge because the driver approved it without their office knowing.
The usual causes:
No account flag on the repair order. Fleet work is not marked as fleet work when the ticket opens.
Unit numbers are optional. Without the customer's unit or asset number, the summary cannot be organized by vehicle.
Approval rules live in memory. Who can approve, and up to what amount, is known by one advisor.
Payment method is unclear. Ticket-by-ticket payment and on-account billing get mixed together.
Tag fleet work when the repair order opens
The summary starts at check-in, not at month-end. For every fleet account, store on the account record:
Authorized approvers. The fleet contacts who can approve work, with contact details.
Approval limit. The amount above which the fleet office must approve, even if a driver is present. Your shop and the fleet customer agree on this; software only stores it.
PO rules. Whether a purchase order number is required, and whether one PO covers a month or each job.
Billing method. On account with terms you set, or paid at pickup.
Then, for each repair order on a fleet account, require:
Unit number from the customer's own list.
Mileage or hours at check-in.
PO number if the account requires one.
Approval record. Who approved, when, and by what channel.
A repair order for a fleet account cannot close without these fields. That one rule does most of the work.
Build the summary by unit and by period
With fleet work tagged, the billing summary is a report rather than a project. For each account and billing period:
By unit. Each vehicle, with every repair order, labor and parts lines, and mileage.
By PO. Totals under each purchase order, for customers who reconcile that way.
Open items. Recommended work that was declined or deferred, so the fleet office sees what is coming.
Balance. What was billed on account, what was paid, and what is outstanding.
The fleet summary and the retail counter can share the same shop management system. The difference is that fleet repair orders carry account fields and land in an account statement, while retail tickets keep moving through pickup and payment as usual.
Connect the shop system to accounting
Most shops already have a shop management system and separate accounting software. Connected systems can move closed fleet repair orders into the right customer account so statements and receivables match what the shop actually did. Ordinary business automation can generate the period summary on a schedule your shop chooses, send it to the fleet contact for review, and remind staff when an account balance passes its terms. If your shop's workflow is unusual, for example mixed fleet and retail pricing or fleet-specific inspection checklists, custom software can be scoped around the systems you already use.
Where AI helps, and where it stops
AI can draft a plain-language cover note for a monthly summary, highlight units with repeated repairs for an advisor to review, or prepare an English and Spanish version of a deferred-work reminder. A person reviews and sends every message. AI does not approve work, change prices, set terms, or mark invoices paid. Tax treatment and contract terms stay with your accountant and your agreements.
Where to start this week
Pick your largest fleet account. Pull last month's repair orders for it and check how many have a unit number, a PO, and a recorded approver. Whatever is missing tells you which fields to require first.
TwoQM builds connected systems, automation, and custom software for auto repair shops. If fleet billing means an afternoon of copy and paste every month, TwoQM can scope a workflow that keeps fleet and retail work separate from check-in to statement. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Fleet Billing Workflow · Explore TwoQM business automation