When should an estimate become an invoice?

The moment the work is done and verified against the estimate, same day. Every day between job completion and invoice delivery is pure aging added to your receivables. Shops that convert on the spot, with the customer standing there to sign, remove the entire chase phase for most retail jobs.

What if the customer wants changes after accepting the estimate?

Document the change before doing the work: update the estimate or write a supplement, get a fresh acceptance, then convert. An invoice that is higher than the accepted estimate without a signed change behind it is the most common trigger for payment disputes and the easiest one to prevent.

Do online payment links actually get invoices paid faster?

The published data says yes, by a lot. Stripe reports 87% of its invoices are paid within 24 hours, Intuit measures roughly 1.4x faster payment for invoices sent with its online payment feature, and Xero cites online-enabled invoices being paid up to twice as fast as offline methods. For a PDR shop, the practical version is: the emailed invoice should contain a pay button, not bank details.

How does Steelie handle the estimate-to-invoice conversion?

One action on an accepted estimate creates the completed work order and the invoice together, carries every line item and discount, calculates tax, and sets the due date from that customer's payment terms. An idempotency guard prevents duplicate conversions, signatures are captured on the device, and sending or marking paid syncs the invoice and payment to QuickBooks Online automatically, including a hosted payment link button in the customer email.

Can I invoice part of a job up front?

Yes. Deposits and progress billing are both legitimate: collect a deposit at acceptance for large jobs, then invoice the remainder at completion. If you run on QuickBooks Online, its progress invoicing feature bills a single estimate in stages; an integrated PDR platform handles the deposit at estimate time and the balance at conversion.

From Accepted Estimate to Paid Invoice: The Workflow PDR Shops Get Wrong

The customer said yes. The dents are out. The vehicle is gone. And in a shocking number of PDR shops, the invoice for that job will not exist for another week, will be retyped by hand from a text thread, and will be paid whenever the dealership's office manager gets around to it.

The gap between an accepted estimate and a paid invoice is a process problem, and process problems have process fixes. I build invoicing software for PDR shops, which means I have seen how this goes wrong at every possible step. Here is the workflow that closes the gap, with the payment-timing data that explains why each step matters.

How big is the problem, really?

Bigger than most owners think, and getting worse. Intuit's QuickBooks small-business late-payments research, surveying about 2,500 US small businesses, found that 56% were owed money on unpaid invoices, averaging $17,500 per business, with 47% carrying invoices overdue by 30 or more days (2025 report). The 2026 follow-up put average owed at $17,700 and the 30-plus-days-overdue share at 59%.

The knock-on effects in the 2025 data read like a PDR shop's storm-season stress list: about a quarter of affected owners delayed their own pay, roughly one in five took on debt or paid their own bills late because customers had not paid theirs.

And the baseline is slow even when nothing is "late": Xero's small-business data measured US firms waiting an average of about 28 days to get paid, with late payments running about 8 days past due on top (Xero Small Business Insights). Net-30 on paper is net-36 in practice. Your invoicing workflow either fights that gravity or feeds it.

What has to be true before you convert?

A clean conversion starts with a clean estimate. Before an estimate becomes an invoice, four things should be true:

The estimate is actually accepted, and the acceptance is recorded: a signature, a portal click, a written yes. Even QuickBooks enforces this ordering; its convert flow requires the estimate to be in accepted status first (Intuit's conversion help article).
The line items match what actually happened. Final dent counts after teardown, R&I that proved necessary, the supplement if one was approved. On hail work especially, the estimate written under a tent and the repair done under shop lighting are rarely identical, and the delta belongs on a documented supplement, not smuggled into the invoice.
Discounts and tax treatment are settled. Percentage or flat, taxable or not, per your state's rules on repair labor. These carry over from the estimate; the invoice is the wrong place to be deciding them.
Payment terms exist for this customer. Retail is due on receipt. Dealerships and insurers have terms, and the due date on the invoice should come from the customer record, not from whatever the tech remembers.

The conversion workflow, step by step

The generic version, tool-agnostic:

Verify acceptance and pull up the accepted estimate. Never build the invoice from scratch beside it.
Reconcile lines against the finished job. Add approved supplements, remove anything that did not happen.
Convert, carrying everything over: line items, discounts, tax, customer, vehicle. Each retyped field is a fresh chance for a $575 panel to become $57.50.
Set the due date from the customer's terms. Due on receipt for retail; their negotiated terms for wholesale.
Capture the signature at delivery. The walkaround, the before-and-after photos, the signature on the invoice: that is your dispute insurance, collected while everyone is still standing next to the car.
Send it the same day, with an online payment link. This is the step with the most data behind it. Stripe reports that 87% of its invoices are paid within 24 hours; Intuit measures customers using its online invoice feature getting paid about 1.4x faster than those who do not.
Record the payment and sync your books. However the money arrives, the payment gets recorded against the invoice and lands in your accounting system once, automatically, not re-keyed at month-end.

Shops that run this list same-day have functionally no accounts-receivable process for retail work, because nothing survives long enough to need chasing.

How do you handle changes after acceptance?

There are only two honest paths, and both happen before the invoice:

Scope grew during repair (hidden damage, extra R&I, an insurer supplement): document it, get it approved, and let the approved supplement flow into the invoice as its own visible lines. On insurance work, expect the supplement cycle to take days, and do not start the extra work before approval clears.
Customer-requested changes: update the estimate or write a change order, capture a fresh acceptance, then convert.

The anti-pattern is the invoice that quietly differs from the accepted estimate. It costs more than the disputed line: it costs the trust that makes the next estimate's acceptance easy.

Why an integrated flow beats the spreadsheet-and-QuickBooks relay

You can run all of the above manually: estimate in a spreadsheet, invoice in QuickBooks Online, photos in your camera roll, tech pay in a second spreadsheet. QBO's own conversion tooling is decent, including progress invoicing for staged billing. The problem is not any single tool; it is the relay. Every handoff between systems is retyping, and every retype is a place where the invoice stops matching the estimate, the books stop matching the bank, and tech pay stops matching production.

An integrated PDR platform collapses the relay: the estimate, work order, invoice, signature, photos, tech pay, and accounting sync are one record changing status, not five documents being reconciled.

How Steelie closes the gap

Steelie's invoicing implements this workflow as a single motion:

One-tap conversion. An accepted estimate becomes a completed work order and an invoice together. Line items, discounts, and the vehicle carry over; tax is calculated; the due date comes from that customer's stored payment terms. An idempotency guard means a double-tap cannot create a duplicate invoice.
Signature on the device. Capture at delivery, embedded on the branded invoice PDF, with before-and-after photos attachable to the same email.
A pay button in the email. Invoices sent through Steelie with QuickBooks connected include a hosted payment link, so the customer's path from opening the email to paying is one click. That is the 87%-within-24-hours mechanic, applied.
QuickBooks Online sync included. Sending an invoice or marking it paid pushes the customer, invoice, and payment to QBO automatically, with idempotent IDs so nothing duplicates. No exports, no month-end reconciliation pile.
Statuses that match reality. Draft, sent, partially paid, paid, overdue, voided, with work orders relinked correctly when an invoice is voided. Tech pay rides on its own field per work order, so paying your techs never requires reading customer invoices.

The whole loop, from "customer said yes" to "money recorded in the books," is the workflow Steelie was built around. The 7-day trial is the easiest way to test it against your current relay; pricing is published and no card is required.