From an accepted estimate to the invoice
How a shop moves from an accepted estimate to an invoice without rewriting the job, and keeps a clear payment status.
The estimate comes from the job
An estimate written from memory drifts as soon as there is an extra part or an extra hour. If it starts from the repair order, the customer, the vehicle, and the reason are already there.
Show it before the customer authorizes the work. Labour, parts, and the total should be visible. A verbal yes, without that page, becomes the argument at handover.
Accept, then invoice
When the customer accepts, the invoice should not start from a blank page. It carries what was agreed. If the job changes in the bay, update the estimate before you continue, not when you ask for payment.
The invoice needs a status: draft, sent, paid, or overdue. Without it, «it is done» can mean nobody has been paid. The front desk should see the ones still open.
Local rules, same trail
Invoice rules differ by country. A shop in the Basque Country also has TicketBAI on that same document. The product prepares that path. Sending it depends on the shop's own certificates.
Everywhere else, the useful trail is the same: estimate, acceptance, invoice, payment status. The local rule is a layer. It is not a reason to keep the job in a loose PDF.
Handover is not a PDF
A PDF on the desktop does not say whether anyone paid. The invoice should stay tied to the location and the order. A month later, the shop can see what was done and whether the money came in.
Before the car leaves, check that the invoice is paid or that a payment term is written down. Handing over the keys and chasing payment on Friday is the work nobody has time for.