The Round Number Estimate: Pricing Compliance Before You Start
Vague verbal quotes are where scope creep and slow payment begin. Here's how a written, itemised estimate speeds up getting paid — before the work even starts.
Most disputes about accounting fees don't start when the invoice lands. They start months earlier, in a conversation nobody wrote down — the one where you said the tax return would be "around a thousand dollars" and the client heard "a thousand dollars, all in, whatever it takes."
The round-number estimate feels helpful in the moment. It moves the conversation along, it sounds confident, and it lets you get on with the work. But it quietly sets you up for a slow payment later, because the number your client remembers and the number on your invoice rarely match. And when a client is surprised by an invoice, they don't pay it — they query it. That's a week gone before you've even started chasing.
Why a vague quote costs you at both ends
An off-the-cuff estimate creates two problems, and they compound.
First, it makes the work harder to scope. If you never wrote down what "the tax return" included, you'll do the extra rental schedule, the extra crypto reconciliation and the phone call about the trust distribution without ever deciding whether they were in or out of the price. That's unbilled work — WIP that sits on your ledger and never makes it onto an invoice.
Second, it makes the bill harder to collect. When the final fee is 40% higher than the round number, you now have to explain the difference before the client will pay. That explanation is a debtor conversation you created for yourself, at the least convenient moment: after the work is done and your leverage is gone.
A written, itemised estimate delivered before the work starts fixes both. It anchors the price, it defines the scope, and it turns the eventual invoice into something the client already expected rather than something they have to reconcile against a half-remembered chat.
What a good estimate actually contains
You don't need a ten-page proposal. You need enough detail that the invoice, when it arrives, reads like the sequel to a story the client already knows.
- The specific deliverable, not the category. Not "tax return" but "2024 individual tax return including one rental property schedule and salary/wage income." The line items are where the scope lives.
- What's explicitly not included. If the crypto trades, the second entity or the amended prior year are extra, say so now. "Additional schedules quoted separately" costs you one line and saves you an awkward call.
- The price against each component. Itemising doesn't just look professional — it means when the client asks for something more, you can point at the line that doesn't exist yet and quote it before you do the work.
- Payment terms. When it's due, how it's paid, and whether there's a deposit. This is also where you set the expectation that payment terms are enforced, not decorative.
None of this is new to good practices. What's new is treating the estimate as a system output rather than a one-off email you rebuild from scratch every time.
The estimate and the invoice should be the same object
The reason round-number quotes persist is friction. Writing a proper estimate feels like extra admin, so people default to the verbal number and move on. The fix isn't discipline — it's removing the gap between quoting and billing.
In practice, this means your accounting client management software should let the estimate flow into the work and out the other side as the invoice, without you retyping anything. When you scope a job in Finye, you attach the estimate to the actual work item on the board. The fee sits with the job, not in someone's sent folder. As the work progresses and you record time or add a line for the extra schedule, the invoice builds itself from what you agreed and what you actually did — so the number the client sees at the end is traceable straight back to the estimate they approved at the start.
Because Finye handles engagement letters with e-signing, the estimate and the scope aren't two separate documents living in two places. The client sees the deliverable, the price and the terms, signs once, and you have an audit trail showing exactly what was agreed and when. If a query does come up later, you're not reconstructing a conversation — you're opening a signed record.
Productise it so you're not quoting from scratch
The same individual return, the same company financials, the same annual BAS cycle — you quote these dozens of times a year. Every time you price them from memory, you invite a different number and a different scope. That's how the same job ends up priced three ways across three clients, and how you end up under-quoting the one who negotiates hardest.
Templating recurring work solves this. Build the standard estimate once — the line items, the exclusions, the price — and reuse it. When a return has an extra property or an extra entity, you add the line rather than rebuilding the quote. This is what turns compliance work into a product with a known price and a known scope, instead of a bespoke negotiation every time.
The payment benefit is direct: a client who received a clear, itemised estimate and signed off on it has already made the decision to pay. The invoice isn't a request for approval — it's a formality confirming something settled weeks ago. That's a faster payment, every time.
Kill the round number
Next time you're tempted to say "probably around a thousand," stop and send the estimate instead. It takes a few minutes if the template already exists, and it removes the single most common reason invoices sit unpaid: surprise.
Getting paid faster isn't only about better reminders and a card on file, though those help. It starts earlier, with an agreement so clear that the invoice never comes as news. Write the number down, itemise it, get it signed, and let the same system that scoped the job be the one that bills it. The round number feels like the fast option in the moment — but it's the slowest possible path to the money.