The Engagement Letter That Doesn't Match the Work You Do
A signed engagement letter isn't worth much if its scope no longer describes what your firm actually delivers. Here's how to close the gap between the letter and the work.
Most conversations about engagement letters focus on getting them signed. That matters — an unsigned letter is a real problem. But there's a quieter risk that trips up firms who have collected the signature: the letter that no longer describes the work being done.
You signed a client up two years ago for a company tax return and quarterly BAS. Since then you've added their SMSF, taken over payroll, and started doing monthly management reports. None of that is in the letter. The scope on file describes a smaller, older version of the relationship — and if there's ever a dispute about fees, deliverables, or who was responsible for what, the letter is the document that gets read.
Scope drifts even when nothing goes wrong
Scope creep isn't a failure. It's usually a sign the relationship is working. A client trusts you, so they ask for more. You say yes, because saying yes is good client service. The problem is that the extra work rarely gets written down anywhere formal. It lives in an email thread, a phone call, or nobody's memory at all.
The result is a growing gap between three things:
- What the letter says — the scope you agreed to in writing, often long ago.
- What you actually do — the current, expanded set of services.
- What you bill for — which may or may not reflect either of the above.
When those three drift apart, you carry risk you never decided to take on. Extra services with no documented terms. Fees you may not be able to justify. Deliverables a client assumes are included because they've been getting them for months.
The verbal 'yes' that never made it into the file
The most common way scope drifts is the mid-year request. "Could you also look at the trust distribution this year?" "We've hired two staff — can you handle their super?" These are answered on the spot, delivered promptly, and forgotten as documentation events.
The fix isn't to be more formal in the moment — clients don't want a fresh contract every time they ask a question. The fix is to have a system that makes updating scope cheap and routine, so an agreed change becomes a re-issued letter without a day of admin.
This is where the letter needs to live close to the work. If your engagement letters are PDFs in a folder and your actual jobs sit in your accounting practice management software, the two will never stay in sync. Nobody cross-checks a document store against a work board. But if the letter is generated from the same system that holds the client record and the work items, adding a service to the client naturally prompts the question: does the letter still cover this?
Why this matters more as you grow
In a two-person firm, the person who agreed the extra work is probably the person doing it and the person billing it. The knowledge lives in one head. It's fragile, but it exists.
Add staff and that breaks. A team member picks up a job, sees the client is getting management reports, and assumes it's in scope because it's in the workflow. It might not be. Nobody set out to under-price or over-deliver — the information simply wasn't visible in one place. Good accounting client management software closes this gap by tying the engagement terms to the client record everyone works from, so the current scope isn't a matter of who remembers.
The yearly refresh is the real safeguard
Even with disciplined mid-year updates, engagement letters need a scheduled review. Not because the law demands a new one every twelve months for every client, but because a yearly touchpoint is the natural moment to reconcile the three things above: what the letter says, what you do, and what you charge.
A practical annual re-engagement pass looks like this:
- List every service you actually delivered this year for the client, not the services you signed them up for.
- Compare that to the current letter. Anything you did that isn't described is a gap.
- Check the fee against the scope. If the work grew and the fee didn't, that's a decision to make deliberately — not a discount you gave by accident.
- Re-issue and re-sign a letter that describes the relationship as it is now.
Done once a year across your client accounting base, this catches the drift before it becomes a problem. It also gives you a clean, honest basis for any fee conversation, because the client is signing off on the actual scope rather than an outdated one.
Make the re-issue frictionless
The reason firms skip the yearly refresh isn't that they don't value it. It's that re-drafting, sending, chasing and filing a signed letter for every client is a genuine amount of work. If each one takes twenty minutes, doing two hundred is a week of someone's time.
That cost is what a modern client accounting software setup is meant to remove. In Finye, engagement letters are generated from templates against the client record, sent for e-signing, and tracked to signed — all inside the same system that holds the client's jobs, deadlines and portal. When you add a service to a client, the letter can be re-issued from the current details rather than rebuilt from scratch. Signatures are captured electronically and stored against the client, so at lodgment or during a review you're never hunting for a PDF someone emailed months ago.
Because the letter, the work items and the recurring jobs sit together, the scope in the letter and the scope on the board reference the same source. That's the whole point: the document that describes the engagement should live where the engagement actually happens.
The letter is only as good as its accuracy
A signed engagement letter gives you protection, clarity and a fee basis you can stand behind. But a signed letter describing work you stopped doing — or missing work you've been doing for a year — gives you a false sense of all three.
Getting it signed is step one. Keeping it true to the work is the step most firms skip. Build a yearly refresh into your calendar, update scope the moment it changes, and keep the letter in the same system as the jobs it describes. Then the document on file will actually match the practice you're running.