Payment on Lodgment: Getting Paid at the Moment of Value
The best time to invoice a compliance job is the moment the client sees the result. Here's how to build that timing into your practice so you stop waiting to get paid.
There is a narrow window in every compliance job where the client is paying attention and grateful in equal measure: the moment you tell them the work is done. The tax return is ready to sign. The BAS is lodged. The financials are finalised. For those few hours the client feels the value of what you do more clearly than at any other point in the engagement.
Most firms miss that window entirely. The job finishes, everyone moves on to the next fire, and the invoice gets raised days later — sometimes weeks later, once someone reconciles the WIP and notices it was never billed. By then the client has forgotten the relief they felt. The invoice arrives cold, into a full inbox, competing with everything else demanding their money.
Getting paid faster is rarely about harder chasing. It's about closing the gap between the moment of value and the moment you ask for payment.
Why the timing matters more than the terms
Payment terms — 7 days, 14 days, on receipt — set the outer boundary of when you should be paid. They don't drive behaviour. What drives behaviour is how the client feels when the invoice lands.
An invoice raised the moment a return is ready to sign carries a completely different weight than the same invoice raised eleven days later. In the first case, the client is looking at their finished work and thinking about how to get it over the line. In the second, they're looking at an unexpected line item with no obvious context.
This is the core problem with treating invoicing as a back-office reconciliation task. When billing happens on a separate schedule from the work, you're always invoicing into a vacuum. The value has already faded.
Tie the invoice to the work item, not the calendar
The fix is structural. Instead of running a billing run at the end of the month and hunting through completed jobs for anything unbilled, the invoice should be attached to the job itself and triggered by the job reaching a specific stage.
In good accounting client management software, a work item moves through stages — information gathered, work prepared, review, ready for client, lodged. One of those stages is the natural billing point. For a tax return it might be "ready to sign." For a BAS it might be "lodged." For an advisory piece it might be "report delivered."
When you build the invoice into the workflow at that stage, three things happen:
- The invoice goes out at the moment of highest perceived value, not days later.
- Nothing slips through unbilled, because the billing step is part of finishing the job — not a separate memory task.
- The amount is right, because the invoice is anchored to a scoped, priced piece of work rather than reconstructed after the fact.
This is where a system that runs the whole practice earns its place. When your client accounting workflow, your job boards and your invoicing all sit in the same place, the invoice can be raised from the work item the instant it's marked ready — and pushed straight to Xero without re-keying. Finye is built exactly this way: the invoice belongs to the job, so payment gets requested when the client is most ready to pay it.
Make paying frictionless at the point of delivery
Timing gets you halfway. The other half is removing every obstacle between the client wanting to pay and the payment clearing.
If the invoice arrives as a PDF attachment with your BSB and account number at the bottom, you've added friction at the worst possible moment. The client has to open their banking app, type in the details, get the reference right, and remember to actually do it. Every one of those steps is a chance for the payment to stall.
Instead, the invoice should carry a pay-now link. When you're integrated with Stripe or Square, the client clicks, pays by card, and it's done — while they're still looking at the notification that their return is ready. You've collapsed the gap between done and paid into a single action.
This matters most for the jobs where the client is signing something anyway. If they're already in the portal approving a return or signing an engagement letter, the payment can sit right there alongside it. One session, one login, no separate errand.
Use the moment for the whole request
The moment of delivery is valuable enough that it's worth using well. When a job is ready and the client is engaged, that's the ideal time to bundle everything you need from them:
- The document to review or sign.
- The invoice to pay.
- Any confirmation the job requires before you lodge.
Sending these as three separate emails over three days dilutes the moment and multiplies the follow-up. Presenting them together — in a portal the client already uses — turns one interaction into a complete transaction. The return is approved, the invoice is paid, the job moves to lodged, all in the same sitting.
This is the practical difference between software that just stores client records and client accounting software that actually moves work forward. The point isn't to have an invoicing feature bolted on somewhere. It's to have invoicing land at the exact moment the rest of the workflow reaches the client.
What to change this week
You don't need to rebuild your whole process to start closing the gap. Pick your highest-volume recurring job — usually BAS or individual returns — and do three things:
- Define the billing stage. Decide exactly which point in the workflow triggers the invoice, and make it a fixed step every team member follows.
- Raise the invoice from the job, not later. When the work hits that stage, the invoice goes out then — not at month-end.
- Give the client one click to pay. Make sure the invoice carries a payment link, ideally in the same place they're already reviewing or signing.
Do that for one job type and watch how the days-to-payment shrink. Not because you chased harder, but because you asked at the right moment and made saying yes effortless. The gap between done and paid isn't a collections problem. It's a timing problem — and timing is something you can design.