Warranty work and your bank statement

An extended-warranty or vehicle-service-contract administrator usually pays the shop directly, often by card once the repair is done and the completed invoice is in, and the customer pays you only the deductible. Some administrators pay by check or transfer after the invoice, days to weeks later. Under some contracts the customer pays you at pickup and claims it back themselves. Each of those puts different lines on your bank statement, and a funding partner reads those lines, not the repair order. Here is what each shape looks like, one ticket worked through, and what a partner sees when it lays the two side by side.

Three ways warranty companies pay, and how each looks on your statement

Which shape a ticket takes depends on the contract and the administrator, and you usually find out on the phone at authorisation. The three are worth telling apart, because they read differently.

By card, once the repair is done

A common shape. Endurance pays the licensed repair facility directly once a repair is authorised, and the customer pays only the deductible (Endurance's payments FAQ, 2026-10-05). MBPI says how: it pays the repair facility "directly with a check or credit card", and on its preferred program pays claims on completion of covered repairs "via electronic virtual credit card payment" (MBPI's FAQ, 2026-10-05). On your statement a card payment arrives as a card settlement, a day or two after you run it, under the administrator's name rather than the customer's. It looks like retail card volume. It is not, quite, and that difference is the point of this page.

By check or transfer, after the invoice

The shape most shop-side advice assumes. You submit the final invoice, the administrator processes it, and the money lands as one lump, days to weeks later, depending on how quickly the paperwork went in, whether an inspection was needed, and whether a coverage question came up. The ticket closed in one month; the deposit may land in the next.

The customer pays, and claims it back

Under some contracts the customer pays you at pickup and sends the invoice to the administrator for reimbursement. To you that is an ordinary ticket: card or check at pickup, from the customer, on the day. It reads that way too, and nothing on this page applies to it except the short-pay, which the customer carries instead of you.

One warranty job, from repair order to bank

Put numbers on the first shape, as an illustration and not a description of any administrator's terms. A $2,400 repair order. The administrator authorises $2,050: labour at book time rather than the hours it took, and the diagnostic hour at the contract's rate rather than yours. Which of those a contract does, and how, varies; this is one made-up ticket. The customer's deductible is $100, paid at pickup. The administrator pays the rest.

Illustration, not a quote or any administrator's schedule. The repair order says $2,400. The statement says $2,050, on two lines, on two days, from two names, one of which is not your customer. Your bookkeeper records $2,400 of revenue the day the car leaves and writes $350 off; your statement never saw the $2,400 at all. That gap, multiplied across a month, is what the next section is about.

A warranty-heavy month: your books vs. your bank

Take a shop that closes about $60,000 of tickets in an ordinary month and has one month at $85,000 because the administrator work ran heavy. As an illustration, not a quote. The repair-order export says $85,000 closed. The statement says $79,000 landed: short-pays took some, and the last week's claims were paid in the following month. A funding partner with both documents sees a $6,000 gap and asks what it is. A partner with only the statement sees $79,000, with a run of card-shaped deposits from names it does not recognise as customers, and no way to know whether they come back next month.

They do not. The next month is $60,000. And in my read of how these files are underwritten, a fixed daily or weekly debit is set off the average of the months a partner can see, so a debit sized while the $79,000 month is in the file is sized for a shop that does not exist in the $60,000 one. The advance guide has the arithmetic: $40,000 at a factor rate of 1.30 over eight months is about $1,550 a week, which is a different share of a $13,800 week than of a $19,600 one. Size it against the ordinary week yourself. The auto repair page makes the same point in short; this is the long version, with the reason the two documents disagree.

What a funding partner sees

In my read, four things, in roughly this order, and then one that is in your favour.

The share. How much of the month is administrator money, and whether that share is steady or came from two big claims. A shop that does a third of its board on service contracts every month is a different file from one that had a warranty month.

The card settlements that are not retail. An administrator's corporate-card payment settles through the same processor as a customer's tap, so on a statement it swells the card line. A partner sizing an advance off card volume, or offering a card split, is looking at that line. On a split, the processor holds back a share of every settlement, including the administrator's, so the remittance comes out of the claim payment just as it comes out of a customer's ticket; the shapes guide covers what a split does. Say which settlements are administrators, and roughly what share.

The lag. Claims paid by check land after the month they were earned in. A statement that starts in a month with a heavy warranty carry-in looks better than the shop; one that ends in a month with claims still out looks worse. Neither is the shop.

The gap. The repair-order total and the deposits do not match on a warranty-heavy month, and a reader who has your software export beside your statement will see that before anything else. Unexplained, a gap reads as a question about the export. Explained in one line, short-pays and claims paid next month, it reads as a shop that knows its own numbers.

And the upside. A warranty ticket paid by corporate card is one of the cleanest deposit lines in this trade: a counterparty that authorises before the work, pays on the invoice, and does not bounce. Once it is named, it is evidence of a shop that does high-ticket work for a payer that pays. The only thing that makes it look like a problem is nobody saying what it is.

Reconcile it before you send it

Four steps, once a month, out of the repair-order system you already run.

1. Export the month's closed repair orders, with the payer on each: customer, administrator, fleet.
2. On each administrator ticket, note four things: which administrator, the approved amount, the deductible, and the date the claim was paid.
3. Match the deposits. Each administrator line on the statement ties to a ticket; each deductible ties to the same ticket on a different day; anything still unpaid at month end is next month's deposit.
4. Write the gap as one line: closed tickets, landed deposits, and the difference split into short-pays and claims paid after the month.

That line is the sentence the bank-statements guide asks for on the half page you send with your statements, and in this trade it is the one that decides the read. If the fleet accounts are the bigger half of the month, that is a different line and a different shape; the unpaid net-30 invoices are what factoring is for, and it is on the shelf.

Customer financing at the counter is a different thing

A ticket the customer finances at the counter, through Affirm, Sunbit or Klarna inside the shop software, is not warranty work and does not behave like it. On the vendor's own description the provider pays the shop in full at checkout, net of a flat fee, so the deposit is smaller than the ticket rather than later than it, and it arrives from the provider's name on the day. It reads as a deposit. The fee is the thing to ask about, and the auto page has the source.

If you have done the reconciliation and the ordinary-week arithmetic clears, and you still want to see what a partner would read, the form takes about two minutes, asks for bands rather than figures, and I do not run credit on it. Partners underwrite and decide. The month with the two big claims in it is yours to explain first.