What a mobile mechanic invoice must include

What each line is doing when somebody disputes the bill

This is a description of what repair invoices commonly carry and what each part contributes when the bill is questioned. It is not a template and it is not a statement of what your state requires.

Your business name, address and contact details. Beyond looking legitimate, this is what makes the document findable and answerable later, and it is what a customer needs if they want to reach you about warranty work.

A unique invoice number and the date of the work. The number is how you and the customer refer to the same piece of paper without confusion, and the date is what fixes the whole document in time. Both are more useful than they look until the first time you need them.

The customer name and contact details, and, where the payer is not the person who owns the car, both. Fleet work, family cars and vehicles being sold all produce invoices sent to somebody who was not standing there, and recording who was who is what stops that unravelling.

The vehicle: make, model, plate, mileage on the day, and the vehicle identification number where you have it. Mileage is the field people skip and the one that anchors a warranty conversation, because it answers how far the car has travelled since you touched it.

The reported complaint, in the words the customer used. It shows what you were asked to address, which is a different thing from what you found, and it is the reason a later claim of not fixing something can be answered calmly.

The work performed, described so somebody else could recognise it. Which component, which side, what was actually done to it. The single most common weakness on a repair invoice is a work description short enough to be argued about.

Parts, itemised with quantity, and marked where relevant as new, used, remanufactured or supplied by the customer. That marking matters because it changes what your warranty covers, and a part the customer brought is the classic source of a disagreement about who is responsible for what.

Labour, shown separately from parts. A single combined figure invites the question of what was included, and it makes any later discussion of a warranty repair harder than it needs to be.

Other charges, each named for what it is. Callout or travel, consumables, waste disposal, anything else. A named charge is answerable. A vague one attracts suspicion out of proportion to its size.

Tax, handled the way your state requires. Whether repair labour is taxed, and how parts are treated, differs by state and this page states no rule about it. It is a question for your state tax agency or for whoever prepares your returns.

The total, what has been paid, by what method, and any balance outstanding with the terms attached to it. An invoice that does not say what is still owed is the one that gets forgotten by both sides.

Warranty terms, saying what is covered, for how long, and separating your workmanship from the parts you fitted. Writing it on the invoice is what makes it a term of the job rather than a memory of a conversation.

A reference to the approval: what was authorised, when, and by whom, including any additional work agreed mid job. This is the line that connects the money to the agreement, and it is the one that makes the rest of the document persuasive.

Estimate, invoice and receipt are three documents doing three jobs

These get used interchangeably in conversation and they are not the same thing. Knowing which one you are producing prevents a surprising amount of trouble.

The estimate comes first and describes work that has not happened yet. Its job is to obtain agreement, so it needs the scope and the price and it needs to be approved before anybody touches the vehicle. It is a proposal, and its value is entirely in existing beforehand.

The invoice comes after and describes work that has happened. Its job is to record what was done and to request payment. It should look like the estimate with the future tense removed, which is why writing a careful estimate makes the invoice almost automatic.

The receipt comes last and confirms that money changed hands. Frequently the invoice does this job as well, by carrying the amount paid, the date and the method, and marking the balance as nil. That is fine as long as the payment information is actually on it.

The failures come from collapsing them. An estimate written after the work is not an estimate, it is an invoice pretending to have been agreed. An invoice with no payment record leaves the customer unable to prove they paid you, which becomes your problem when they need it for a warranty claim or an insurance form.

One more distinction worth keeping straight in your own head: a quote and an estimate are not the same promise. A quote implies a price you are committing to, while an estimate implies a considered figure that could move. Whichever you use, use the word deliberately and say what happens if the figure changes, because that sentence is doing a lot of work.

Numbering it, storing it, and finding it a year later

The part of invoicing nobody thinks about until it matters is retrieval. A perfect invoice you cannot find is worth nothing, and the moment you need one is always a moment when somebody is waiting.

Number them in a sequence that never repeats and never restarts. Gaps and duplicates are how two jobs end up referring to the same document, and how you lose track of whether something was ever paid. The sequence itself does not have to be clever, only unique and unbroken.

Keep a copy somewhere that is not the phone in your pocket. A device that goes in a puddle should cost you a phone, not a year of records. Whatever you use, make sure the copy leaves the device automatically rather than when you remember.

Store them so they can be found by the things you will actually search for: the plate, the customer name, and the date. Nobody has ever gone looking for an invoice by its number when the customer is on the phone describing a noise.

Keep the approval and the photographs with the invoice rather than in three different places. A job is a bundle, and a bundle that has been scattered across a messaging app, a camera roll and a notebook is a bundle you will not reassemble under pressure.

How long to keep them is a question for whoever handles your taxes, and it is worth asking once rather than guessing. The answer usually outlasts your memory of the job by years, which is another argument for storage that does not depend on you.

And when a customer asks for a copy, send it without friction. A mechanic who produces a two year old invoice in a minute has said something about how the business is run that no amount of marketing achieves.