Scope & Fees

Unpaid Extra Work in an Accounting Firm: How to Catch It Before the Team Starts

July 31, 2026

Unpaid extra work in an accounting firm usually starts before anyone thinks to call it scope creep.

A bookkeeper answers "one quick question" and ends up rebuilding a client's chart of accounts. A tax preparer chases missing documents for the third time because the return is already in motion. A payroll specialist fixes prior quarter setup errors because the client says it should be simple. By the time billing reviews the job, the work has already happened. The only decision left is whether to write it off, have an awkward fee conversation, or pretend it was included all along.

This post is for firm operators who see those small requests turning into unpaid staff time. The goal is to catch extra work at intake, route it through scope review, and require written approval before the team starts.

If your larger problem is that clients keep asking for free extras after work has begun, start with how to stop doing unpaid work for clients. If the issue starts at pricing, read pricing your accounting services. This article focuses on the internal handoff before staff time disappears.

Why extra work becomes free so early

Most unpaid work does not begin with a dramatic client demand. It begins with a normal service instinct.

A client asks for help. A staff member wants to be responsive. The task seems small enough to handle now and clean up later. Nobody wants to slow the job down for a manager approval on something that may only take 20 minutes.

The trouble is that firms rarely lose margin on one 20-minute favor. They lose it when the same habit repeats across bookkeeping, tax, payroll, and advisory work:

staff accepts the request before checking the signed scope
the client describes cleanup work as a "fix"
a missing document chase turns into repeated admin time
an extra meeting gets added because "we already know the client"
a manager hears about the request only after the work is partly done
the invoice shows time that nobody wants to bill

That is why the control point has to move earlier. Billing review is too late. Timesheet review is often too late. The useful moment is when the request first enters the firm.

Warning signs before work starts

Train the team to pause when a request contains any of these signals.

Bookkeeping

The client asks the firm to "clean up a few old transactions" outside the monthly period.
The bank feed is broken and prior months need to be rebuilt.
The client changed payroll, POS, or payment tools without telling the firm.
The monthly close cannot start because old categories, reconciliations, or opening balances are wrong.

Tax

The client adds a new state, entity, rental, K-1, crypto activity, or prior-year issue after the engagement letter was signed.
The preparer has to chase missing forms multiple times.
The client asks whether a planning question is "included with the return."
Books arrive late or not ready, but the return is already on the schedule.

Payroll

The client asks the firm to fix a prior quarter setup issue.
A benefits, garnishment, or employee classification question turns into research.
The client wants help moving payroll platforms midyear.
A missed filing requires correction work outside ordinary payroll processing.

Advisory

The client asks for an extra forecast, meeting, lender package, or management report.
A monthly advisory call turns into a one-off project.
The owner asks the firm to review a purchase, financing decision, or new service line without a separate advisory agreement.

None of these requests are automatically bad work. Some are good revenue opportunities. The problem is letting them slip into the team's queue without checking whether they are included, separately quoted, or outside the relationship.

A cleanup request handoff example

Picture a CAS team with a monthly bookkeeping client. The signed engagement covers monthly bank reconciliations, standard categorization, monthly financial statements, and one scheduled review call.

On Tuesday morning, the client emails the assigned bookkeeper:

Can you clean up the last six months of Stripe deposits? I think they are duplicated in QuickBooks. Need this fixed before the bank meeting Friday.

A weak workflow looks like this:

Before	What goes wrong
The bookkeeper starts looking at Stripe and QuickBooks right away.	Staff time is spent before anyone checks whether cleanup is included.
The client frames the work as a fix.	The firm treats a prior-period cleanup project like ordinary monthly bookkeeping.
The manager hears about it during review.	The work is already partly done, so pricing feels late and awkward.
Billing sees extra time after month end.	The firm either writes it off or sends an invoice the client did not approve.

A stronger workflow gives staff a clean handoff:

After	Why it works better
The bookkeeper checks the signed scope before starting.	The team can see whether prior-period cleanup is included.
The request is tagged as possible extra work.	The manager reviews it before staff time is spent.
The manager decides: included, quote, revise, or decline.	The firm uses one decision path instead of inbox judgment.
The client receives written approval terms before work starts.	The client knows the fee, timing, and deliverable before the team touches the cleanup.
The approval is saved with the engagement record.	Billing, scheduling, and service delivery can see the same decision.

The bookkeeper should not have to become the firm's pricing department. Their job is to spot the request and route it.

Use a four-option scope decision

When a possible extra request arrives, the manager should choose one of four answers.

Decision	Use it when	What to document
Included	The signed engagement clearly covers the request.	Where the current scope covers it and who owns the task.
Quote	The work is valuable but outside current scope.	Fee, timing, deliverable, and required approval before work begins.
Revise	The request changes the ongoing relationship.	Updated scope, recurring fee change, effective date, and client signature.
Decline	The work does not fit the firm's services, risk tolerance, or capacity.	The response sent to the client and any referral or alternative offered.

This framework keeps the firm from treating every request as a custom debate. Staff can ask, "Which bucket is this in?" Managers can answer without rewriting policy every time.

Staff should capture the right details at intake

The first person who sees the request does not need to solve it. They do need to capture enough information for the manager to make a fast decision.

Use this intake checklist before any extra work begins:

Who made the request?
Which client, entity, or engagement does it relate to?
What exactly is the client asking the firm to do?
Is there a deadline or outside dependency, such as a bank meeting, payroll run, filing deadline, or board packet?
Does the request relate to current-period work or prior-period cleanup?
Does the signed engagement mention this work, exclude it, or stay silent?
Has staff already spent time on it? If yes, how much?
Does the client expect this to be included?
Who needs to approve the decision internally?
What written approval does the client need to sign before work starts?

That last question is the margin saver. If the answer is "none," the firm is relying on memory and goodwill.

How to require approval without annoying good clients

Firms sometimes avoid scope review because they worry it will make the client experience feel stiff. That is understandable. Nobody wants a simple request to feel like a legal negotiation.

The fix is to make the pause short and normal.

A staff response can be plain:

We can help, but this may be outside the current monthly bookkeeping scope. I am going to have the manager review it before we start so we can confirm timing and fee in writing.

That message does three useful things. It stays helpful. It does not accuse the client of asking for free work. And it stops the team from beginning before the firm has made a business decision.

For tax or payroll work, the same idea applies:

This looks different from the work covered in the current engagement letter. We will review it first and send the approval details before starting.

Clients are usually not shocked by this when the firm treats it as standard operating procedure. The awkwardness comes when the team already did the work and then tries to explain the fee afterward.

Keep approval with the engagement record

Written approval should not live only in a reply thread that half the firm cannot find.

At minimum, the engagement record should show:

the original signed scope
the extra request
the manager decision
the fee or pricing method
the person who approved it internally
the client approval or signature
the date approval was received
whether the work can now be scheduled

This matters for realization, but it also matters for team behavior. If staff can see signed scope and approved changes in one place, they are less likely to guess. If managers can see pending approvals, they can stop bottlenecks before staff quietly works around them.

It also creates better renewal conversations. If the same client needs cleanup, extra advisory calls, and document chasing every month, the firm has evidence that the engagement needs to change instead of relitigating each request.

A simple workflow to install this week

You do not need a giant process redesign to start catching unpaid extra work earlier. Start with a lightweight workflow the team can actually follow.

Pick the intake trigger. Any request outside recurring monthly work, signed tax scope, payroll processing, or the scheduled advisory package must be paused.
Give staff a standard response. Make it easy to tell clients the request needs scope review before work starts.
Create one internal handoff form or task type. Capture client, request, deadline, signed-scope check, and whether time has already been spent.
Assign one reviewer. A manager, partner, or service-line lead decides included, quote, revise, or decline.
Require written client approval before the work enters the queue. Email approval may be enough for small work if that is your policy. Larger changes should tie back to an updated engagement letter or change approval.
Save the decision where billing and delivery can see it. Do not leave it buried in one person's inbox.
Review patterns monthly. Repeated one-off approvals may mean the client's base scope or price needs to change.

The first week will feel a little slower. That is fine. You are replacing invisible leakage with visible decisions.

What Feesable helps control

Feesable is built around the part of this workflow that accounting firms often lose track of: signed scope and approval status.

When engagement letters, reminders, and signed records are scattered across documents, DocuSign emails, spreadsheets, and inbox notes, staff end up relying on whoever remembers the last conversation. That is how extra work turns into free work before anyone notices.

Feesable helps firms keep engagement letters and signature status visible so teams can confirm what is signed before work starts. For extra work, that same discipline matters: scope should be tied to written approval, not a casual inbox decision.

If your firm wants a clearer way to keep extra work connected to signed scope and approval, log in to Feesable and tighten the handoff before the team starts.