Manufacturer warranty billing: 6 checks before invoicing

• Match the unit's serial number and purchase date to its warranty.
• Check exclusions and claim requirements before dispatch.
• Save diagnosis notes, photos, and parts instructions together.
• Check the payer and due date before sending the invoice.

Field-service firms run into the same problems again and again. A tech drives out to a machine that turns out to be out of coverage. A claim gets stuck because the serial number on the paperwork does not match the unit in the field. An invoice sits unpaid for months because it went to the wrong party. None of these problems is hard to prevent. They usually come down to a few checks before the truck rolls and a few more before the invoice goes out.

This post walks through six of those checks. They are written for owners and dispatchers, not lawyers, and they stay general on purpose. Warranty terms differ by manufacturer and by product, so the warranty document in your hand always wins over anything here. Where a published source gives a specific rule, number, or date, this post links it. The main reference is the Federal Trade Commission's guide to federal warranty law, which explains how written warranties are laid out and what they should spell out for the buyer.

Start with the unit, not with the customer's memory of when they bought it. "Under warranty" is a statement about one specific piece of equipment, and it is easy to get wrong. The customer may be thinking of a sister model, a refurbished unit, or a machine that another company installed years ago. Before anyone commits to a diagnosis, get the model number, the serial number, and the purchase or installation date. Then match them against the warranty terms and, where the manufacturer keeps one, its registration record.

Warranties usually spell out three things: what is covered, how long the coverage lasts, and what the company will do if something goes wrong. The FTC's guide uses that structure when it walks through a sample warranty, and it makes a useful checklist for reading your own. Coverage periods are often tied to a date, such as the date of purchase, so check which date the warranty actually uses. A unit that looks new may already be outside its coverage window. Do not estimate the dates from memory or from the age of the equipment. Look them up in the warranty document or the manufacturer's record, and write the answer on the job.

Make this a required step at intake. Add a warranty yes/no field to your dispatch form, along with a field for the serial number and a field for the date that supports the answer. If the answer is "unknown," treat the call as billable until someone has checked. A few minutes at intake saves an awkward conversation later, when a customer who assumed a repair was free is told it is not.

Also check which company is actually making the promise. The warranty document names the company that stands behind the coverage. Sometimes the dealer, the installer, or a separate service contract is the party a customer remembers, and that is not always the same company as the manufacturer. If the names do not match what the customer believes, sort that out before the tech is on site.

It also helps to ask for proof of purchase at the start of the call rather than at the end. An invoice or an installation record gives you something concrete to point to if the manufacturer later asks when the unit was sold. If the customer cannot find any of it, write that in the job notes so the gap is visible to everyone who handles the claim later.

Warranties cover defects, and they tend to exclude a great deal else. A defect is a fault in the product itself, such as a component that failed because of how it was made or put together. Damage from something outside the product is a different category, and many warranties treat it differently. Examples that often fall outside coverage include damage from a storm, a power surge, a leak from a separate system, improper installation, or a repair that someone else already made. Those examples are kinds of issues to look for, not a list of what any particular manufacturer excludes. The exclusions in the warranty you are working under are the only list that counts.

That is why you should pull the exclusions before the visit. Most manufacturers put them in the same document as the coverage terms, often in a separate section that is easy to skip. If the exclusions are not in front of the dispatcher, the tech becomes the first person to read them, and that is the wrong moment. Put the warranty terms in the job file so the tech can see them on a phone or tablet before the diagnosis starts. Ask the tech to note any facts that bear on the exclusions, such as signs of water exposure or evidence of a previous repair.

Diagnosis notes matter more than most people expect. A reviewer deciding which part of a warranty applies is working from what the tech wrote, not from what the tech remembers saying to the customer. Plain language works best: what was tested, what the reading was, what failed, and what the tech believes caused the failure, with the reason. A note that says "compressor failed, winding resistance open on test" tells a reviewer far more than "unit dead, replaced compressor."

Be ready for a mixed job. A single visit can include covered parts and uncovered parts, or covered work alongside a separate problem the customer also wants fixed. Decide in advance how you will split the bill. Quote the customer for any uncovered portion before the work starts, not after the tech has already spent the time. Get that approval in writing, whether through your field app, a signed ticket, or an email that goes into the job record. An approval you cannot find later is the same as no approval at all.

Many manufacturers run their own claim process. It may involve a claim number, a required form, a list of authorized servicers, a parts order placed through a portal, or a deadline for submitting the claim. Some want to hear from you before any work is done. Others accept claims after the repair. You need to know which applies to this brand and this product before the tech starts. Otherwise you may do covered work that the manufacturer will not pay for, not because the repair was wrong, but because the claim was never opened the right way.

Check whether your firm is an authorized servicer for the brand. The warranty or the manufacturer's service portal usually says who may perform covered work. If you are authorized, confirm that any training or certification the manufacturer requires is current for the technician being sent. If you are not authorized, tell the customer before you dispatch anyone. Explain that the manufacturer may require the repair to go through an authorized servicer, and offer to help them find one if that is the case. Sending a tech who is not allowed to do the work wastes a visit and frustrates the customer.

Parts logistics are where many arrangements break down. The FTC's guide includes a sample warranty term that shows how this can be spelled out. In that sample, the company says: "If you inform us that you wish us to provide necessary parts to you but you wish to have repairs performed elsewhere, we will return the aid and replacement parts to you within 72 hours." That is one sample's wording, not a rule that applies to every warranty. What it shows is the kind of detail worth getting in writing: who supplies the parts, and what happens to them if the customer decides to move the job to another shop. Ask the manufacturer those questions directly and save the answer in the job file. Do not assume a part will arrive, or that a returned part will be handled, unless the manufacturer has said so.

A claim can also stall between submission and approval. The part may be ordered before the claim is approved, or the approval may come in and nobody tells the dispatcher. Put a follow-up on the calendar at the point where you submit the claim, and assign one person to check its status on a regular schedule. A claim with a named owner is far more likely to move than one that everyone assumes someone else is watching.

Claims get reviewed, sometimes weeks after the visit, by someone who was never at the job. Your records have to explain the failure without relying on anyone's memory. Treat the job file the way you would want it read if a dispute comes up. At a minimum, the file should include:

• The model and serial number, photographed from the rating plate rather than copied from the customer's paperwork.
• Photos of the failed component in place, plus close-ups of any wear, damage, or the failed part itself.
• The symptoms as the customer described them, with the date and time they were reported.
• The tech's diagnosis, test results, and readings, and a plain conclusion about what failed and why.
• The names of everyone present on site, and who signed the completion record.

Keep the failed part when the manufacturer may want it back. Tag it with the job number, the serial number of the unit it came from, and the date it was removed. Then ask the manufacturer whether they want it returned, and how. If the claim instructions say nothing, ask before anyone throws the part away. A part that was discarded cannot be produced later, and a reviewer who asks for it and does not get it is unlikely to read the rest of your file generously.

Store the documentation in your job management system, not on a paper ticket in the truck or on a personal phone. A shared system keeps the record attached to the job, lets the dispatcher see it, and makes the file easy to find when a claim is questioned months later. Photos should be time-stamped and tied to the job. If your crew uses phone cameras, check that the app keeps the date, time, and location information rather than stripping it out during upload.

This is where many firms lose money without noticing. A covered repair is usually billed to the manufacturer, while the service location stays at the customer's site. The scheduling and invoicing software has to reflect that split. If it does not, the invoice goes to the wrong party, the claim is held up, and the customer receives a bill they should never have gotten.

ServiceTitan's help documentation for in-house warranties describes one way to set this up. Its recommended workflow says to click on "Update Invoice Details" and change the bill-to customer to the manufacturer while leaving the service location unchanged. The steps are written for that platform, so the menu names in your software may differ. Check whether your software keeps bill-to and service location as separate fields, as ServiceTitan's in-house warranty steps describe, and review both before invoicing. For a closer look at that workflow, see warranty billing for ServiceTitan repairs.

Before sending any warranty invoice, run a short check. Confirm the bill-to party is the manufacturer and the service location is the customer's site. Confirm the model and serial number match the claim. Confirm the claim number is on the invoice, along with the labor and parts lines the manufacturer needs to see. If there is an uncovered amount going to the customer, put it on a separate invoice. That way the manufacturer is not asked to pay for work it is not responsible for, and the customer sees exactly what they owe.

A missing claim number or a mismatched serial number gives a reviewer an easy reason to send a claim back. Rejections like that cost time, and the tech's hours are already spent. Build the check into your invoice process so it happens every time, not only when someone remembers to look.

Tell the customer what to expect as well. Many people do not understand why the manufacturer is paying for the repair while they are the one who called you. A short, plain explanation at the end of the visit, such as "the manufacturer is billed for covered work, and you will get a separate invoice for anything that is not covered," prevents most of the confusion. Put that explanation in writing on the completion record so it is not a matter of memory later.

Illustrative example: split a mixed job

Suppose a job has an approved covered portion of 500 dollars and an uncovered portion of 500 dollars. Invoice the manufacturer for the covered portion and the customer separately for the uncovered portion, after written approval. These amounts are illustrative, not warranty rates.

Last, confirm when the money is due and when the job counts as finished. Invoicing systems often tie the due date to the job's status, so a job left open can leave the due date blank or wrong. Housecall Pro's help center describes this for one of its invoice settings: "The due date for this due term is populated once the job is marked as finished." That behavior applies to the quoted Housecall Pro due-term setting. Check when your own software fills in a due date.

That makes the finish step more important than it looks. If you mark a job finished before the completion paperwork and photos are attached, the record may look complete when it is not, and a claim reviewer who opens it will find gaps. If you leave it open after the work is done, check its due date before scheduling follow-up. Set a simple rule: mark a job finished when the work is done and the documentation is attached, then check the due date before sending the invoice. Dispatchers should be able to see at a glance which warranty jobs are finished and which are waiting on paperwork. A short weekly review of open warranty jobs catches most problems before they become old, unpaid invoices.

Money that comes in before the work is complete needs care too. Some firms take a deposit or prepayment on warranty work, or on a mixed job where part of the bill is paid up front. ServiceTitan's guidance on in-house warranties makes the accounting point plainly: "After accepting payment, you only recognize it as income upon delivery of services, when the revenue is earned." That is a reason to ask your accountant how to record prepayments in your books, and to keep each payment tied to its job until the service is delivered. It is not a reason to guess.

Finally, track every claim in one place. Record the claim number, the date it was submitted, the amount, the date it was paid, and the name of the person who follows up. A log like this turns a vague feeling that "the manufacturer still owes us" into a specific list you can act on. Send follow-ups on a set schedule, and keep every reply with the job file. When a payment is short or missing, the log tells you exactly which claim to chase and what the paperwork shows.

This post is general information, not legal advice. When a manufacturer's decision is in dispute, the warranty document itself is the first thing to re-read, and a qualified advisor is the right next step if the amount at stake is significant.

Today, open a pending warranty job and compare its serial number, claim number, bill-to party, and due date with the job file before sending its invoice.

What if coverage is unknown?

Check the unit's warranty terms and purchase or installation record before promising a covered repair.

Who pays for uncovered work?

The customer pays the uncovered portion after approving it in writing; keep it on a separate invoice.

When should the invoice go out?

Send it after the work and documentation are finished and you have checked the due date in your software.