The short answer: never retype a signed quote into an invoice. Retyping is where the line items drift, the tax gets recalculated and a number quietly changes between what the client agreed and what you billed. Converting the quote instead carries the lines, the tax and the client across untouched, so the invoice matches the thing that was signed.
It is 9:40 on a Tuesday night and you are invoicing at the kitchen table. The signed quote is open on your phone, propped against a coffee mug, and you are copying it line by line into an invoice: same client, same address, same fourteen lines, same tax. On line nine you type $1,840 as $1,480.
Nobody catches it. The client pays the invoice without comment, because clients do not complain about invoices that are too low, and $360 of margin evaporates without anyone ever knowing it existed. Or the error runs the other way and the client does catch it. Now every other number on the invoice is under suspicion, on a job that, until that email, had gone perfectly.
Either way, the mistake was not made at 9:40. It was made the moment the workflow required typing the same fourteen lines twice.
Why does retyping a quote cost you money?
Copying a quote into an invoice feels like clerical work, which is exactly why it is dangerous. It happens when you are tired, it is boring enough that attention drifts, and its failure modes are quiet.
Undercharges are silent. A transposed digit, a $60 line that did not survive the copy, a quantity of 12 that became 2. None of these announce themselves. The client pays what the invoice says, the job closes, and your job costing later shows a margin problem you will misdiagnose as a pricing problem.
Overcharges are loud. The same typo in the other direction gets found, and the cost is not the $360. It is that the client now audits everything with your name on it. Trust in an invoice is binary, and one wrong number flips it.
The tax line is its own trap. Retyping means reapplying tax treatment from memory: which lines are taxable, at what rate, on which portion. Get it wrong and you either eat the difference at remittance time or send the client a correction email that no one enjoys writing.
And the retype has a schedule cost. Because invoicing-by-retyping is a chore, it waits for a quiet evening. Quiet evenings are scarce in season, so finished jobs sit uninvoiced for days. Every one of those days is you financing the client's project interest-free, purely because data entry was annoying.
Typing more carefully at 9:40 at night is not the fix. Removing the second typing entirely is.
The job profitability calculator shows whether a finished job made the profit you priced it to make.
Conversion: the invoice is the quote, promoted
In Zeus, a signed quote converts into an invoice directly. The line items come across exactly as quoted: descriptions, quantities, unit prices. The tax treatment comes with them. The client and the job come with them, because the invoice is created on the same job the quote lives on, not as a free-floating document you have to re-address.
What used to be an evening chore becomes the last thirty seconds of the job. You can generate the invoice in the driveway, before the truck leaves the curb, from the same record the client signed.
There is a second benefit hiding in there that is easy to miss: the client recognizes the invoice. When an invoice arrives carrying the same lines, the same wording, and the same totals as the document they signed, it reads as confirmation, not as a new artifact to scrutinize. Familiar invoices get paid; unfamiliar ones get studied. A retyped invoice, with reworded descriptions, reordered lines and a total that is close but somehow different, invites the study even when every number is right.
Conversion does not lock you out of editing. Sometimes the invoice legitimately differs: a line the client canceled mid-job, a materials substitution. You can adjust before sending. The point is the starting position: you begin from the signed document and change only what genuinely changed, instead of beginning from a blank page and hoping to reconstruct it.
Change orders join the same job
Mid-job changes are where invoice reconstruction really goes wrong. The quote said $8,400. Then the client added an outlet, approved a fence section, and canceled the shed shelf, all agreed across three conversations and one text thread. At invoicing time, the retyping contractor is now an archaeologist, assembling the final number from memory and scrolling.
When changes are written up as change orders on the same job (priced, signed, filed alongside the original quote), the final invoice stops being an act of reconstruction. It is the signed quote plus the approved changes, each one a document the client has already put their name to. Nothing on the invoice is new information.
That changes the handover conversation completely:
"The invoice matches the quote you signed on the 4th, plus the three changes you approved: the extra outlet on the 11th, the fence section on the 15th, and the shed shelf we took out. Same numbers as the paperwork, nothing new on there."
Try to have that conversation from a hand-built invoice and a memory of three site chats. The difference is not politeness; it is that one version can be checked against signatures in ten seconds and the other cannot.
What happens when your invoice numbers have gaps?
A small thing that stops being small at tax time: numbering.
Hand-numbered invoices drift. You skip a number, reuse one, or run two sequences because your phone and your laptop each had their own idea of what came next. It all seems harmless until someone whose job is scrutiny (a bookkeeper, an accountant at year-end, a tax reviewer) asks what happened to invoice #1047. A gap in an invoice sequence looks like a deleted invoice, and "I think I just skipped it" is not the answer you want to be giving about your own revenue records.
Zeus assigns invoice numbers from the server, as a single gap-free sequence for the business. You never pick a number, two devices can never collide on one, and the sequence has no holes to explain. One practical note that follows from the design: because the server issues the number, an invoice drafted offline gets its final number when it syncs. The sequence stays clean precisely because no device is allowed to guess.
The companion rule: mistakes get voided, not deleted. A voided invoice stays in the record, marked as void, keeping the sequence intact and the history honest. An invoicing system you can silently delete from is an invoicing system whose reports you cannot fully trust, including your own.
Batch invoicing the Friday backlog
Even with conversion, real weeks end with a stack: four jobs wrapped since Monday, none invoiced, because each wrap-up had a next job waiting behind it.
Batch invoicing exists for exactly this pile. Instead of processing each finished job one at a time, you generate invoices for several jobs in one pass: each one built from its own signed quote and approved change orders, each numbered in sequence, ready to send. The Friday backlog goes from an evening you keep postponing to minutes.
The economics of this are boring and real. An invoice that goes out the day the work finishes starts the clock immediately, while the job (and your goodwill premium) is still fresh in the client's mind. Invoices sent while the client is still admiring the work get treated better than invoices that arrive two weeks later like a bill from a stranger. You do not need a statistic to know which one sits in the client's inbox longer.
What this does not fix
Worth being plain about, because a tool that claims to fix everything fixes nothing.
It will not chase your money for you unless you ask it to. Automatic overdue reminders exist — Chase Overdue Invoices emails at 3, 7 and 14 days past due, then stops — but they are off until you switch them on, and most contractors leave them off. Unpaid invoices show up in Alerts, the queue of things wanting your attention, and in your aged-receivables report, so nothing slips out of sight. But the follow-up call or message is still yours to make. An invoice sent the day the work finished, with your payment details on it, lowers their friction; it does not replace your voice on day fifteen.
It faithfully reproduces a wrong quote. Conversion copies what was signed. If the quote underpriced the job, the invoice will underprice it identically, with perfect formatting. Estimating discipline lives upstream, and no invoice mechanism repairs it.
A deposit changes the balance, not the invoice logic. Deposits and partial payments recorded against the job show up against what is owed, so the client sees credit for what they have already paid. That only works if payments actually get recorded when they land. The system reflects your bookkeeping; it does not perform it.
Frequently asked questions
What if the final price is different from the signed quote?
If it changed because scope changed, the answer is a change order at the moment of the change: signed, priced and attached to the job. The invoice is then automatically the quote plus approved changes. Editing lines at conversion time is possible and sometimes right, such as a canceled line or a substitution. But every edit is a divergence from what the client signed, so it deserves a sentence of explanation when you send the invoice rather than a silent difference they discover.
Can I invoice part of a job before it is finished?
Yes. Deposits, partial payments, and payment schedules are the normal shape for larger jobs: an amount up front, a draw at a milestone, the balance at completion. Recording each payment against the job keeps the running balance honest, so the final invoice conversation is about the remainder, not a renegotiation of the total.
Why can I not choose my own invoice numbers?
Because the value of an invoice sequence is that it is boring: one series, no gaps, no duplicates, nothing to explain to a bookkeeper or a tax reviewer. Server-assigned numbering is what makes that guarantee hold across multiple devices and an offline-capable app. The trade (an offline-drafted invoice receives its number at sync) is precisely what keeps the sequence unimpeachable.
The client already paid a deposit. Does the invoice show it?
Yes, if the deposit was recorded when it was received. Recorded payments count against the job's balance, so the client sees the original amount, what they have paid, and what remains. That is the difference between an invoice that answers questions and an invoice that starts a phone call.
ZEUS