Most bookkeeping practices don't have a client communication problem — they have a structure problem. Email arrives continuously, phone calls interrupt deep work, and the bookkeeper ends up context-switching between client queries, coding, and administrative responses all day. The result: lower quality on all three tasks.
This guide describes the communication structures used by practices that manage 20 or more clients with one or two bookkeepers — and what they do differently.
The core problem: reactive vs proactive communication
The default communication mode for most practices is reactive: respond to emails and calls as they arrive. This feels attentive, but it's cognitively expensive. Every incoming message breaks focus on the task at hand and requires re-orientation when you return to it.
Research consistently shows that context-switching between tasks reduces cognitive performance by 20–40%. For a bookkeeper juggling complex coding decisions, that cost is material.
Proactive communication structures batch similar tasks together, set client expectations upfront, and reduce the volume of inbound queries by anticipating what clients will ask before they ask it.
Structure 1: Fixed communication windows
The single most impactful change a practice can make is setting fixed communication windows and holding to them.
Typical structure:
- 8:30–9:00 am: Review and triage all overnight email
- 12:00–12:30 pm: Second email check, respond to anything urgent
- 4:30–5:00 pm: Final daily communication check
Everything outside these windows: deep work, coding, BAS preparation.
Clients are informed of this structure at onboarding: "We process client queries twice daily and respond within 4 business hours." Most clients find this completely acceptable — they don't actually need an instant response; they need a predictable response time.
Practices that implement communication windows report reclaiming 60–90 minutes per day of fragmented time and delivering more consistent, higher-quality work as a result.
Structure 2: Portal-first query management
Email is a poor tool for transaction queries. An email thread with "what was this $340 payment to Bunnings on 14 March?" requires:
- Reading the query
- Locating the transaction
- Composing a reply with context
- Waiting for the client's response
- Updating the transaction
- Notifying the client the transaction is coded
Reconlink's client portal replaces this with a purpose-built query workflow:
- The bookkeeper flags the transaction in Reconlink with a note: "Please confirm what this Bunnings purchase was for."
- The client sees all flagged transactions in their portal view
- The client adds a note or uploads a receipt — directly against the transaction
- The bookkeeper reviews the response and codes accordingly
- No separate email thread required
The portal approach reduces query round-trips from an average of 2.4 emails per query (initial question + response + confirmation) to a single interaction logged in context.
For practices managing 15+ clients, the administrative overhead reduction is significant. A practice with 15 clients and 8 queries per quarter per client (typical) is handling 120 query interactions per quarter — 300+ emails vs 120 portal interactions.
Structure 3: Proactive BAS communication calendar
Most client-initiated BAS-period emails arise from one of three causes:
- The client doesn't know the lodgement deadline and asks
- The client has a question about a figure on the draft BAS
- The client wants to know when their refund is expected
All three can be pre-empted with a BAS communication calendar — a standard sequence of messages sent to every client at the same relative dates each quarter:
Week before period end:
"Just a reminder that your [Q3] BAS period closes on 31 March. Please forward any outstanding bank statements or transaction queries by [date]. We'll aim to have your draft BAS ready by [date]."
Draft BAS sent:
"Your draft BAS is attached. [Key figures: G1 $X, 1A (GST payable) $X, 1B (ITC) $X.] Please review and confirm approval by [date] so we can lodge before the [date] deadline."
Lodgement confirmation:
"Your [Q3] BAS has been lodged. [Brief summary of outcome: refund of $X expected within 14 days / payment of $X due on [date] via bank transfer to ATO BSB 093 003.] Next BAS period opens [date]."
These three messages, templated once and personalised with mail merge fields, eliminate 80% of the routine client queries that would otherwise arrive reactively.
Structure 4: Client tiering by contact intensity
Not all clients require the same communication investment. A simple tiering system lets the bookkeeper allocate attention where it generates most value:
Tier 1 (high-touch): Large retainer, complex business, frequent advisory requests. These clients get proactive monthly calls (15 minutes) in addition to the standard BAS calendar. They're the relationship clients.
Tier 2 (standard): Mid-range retainer, predictable transactions, occasional queries. The BAS calendar and portal handle 90% of communication. Annual review call.
Tier 3 (low-touch): Simple sole trader or dormant entity. Portal-only communication. BAS calendar. Minimal advisory.
The tiering is not visible to the client — they all receive professional, responsive service. The difference is in how the bookkeeper schedules their attention, not in service quality.
What NOT to do
Don't give clients your mobile number as the primary contact. Once a client knows they can call your mobile and reach you immediately, they will. Set a clear expectation at onboarding: email is the primary contact method; phone calls are by appointment for complex matters.
Don't respond to email immediately. Instant responses train clients to expect instant responses. A consistent 2-4 hour response time (within business hours) is professional and sustainable. An inconsistent mix of instant and 24-hour responses creates anxiety for both parties.
Don't process urgent-seeming requests without context. "This is urgent!" is a judgment call by the client. Assess whether it actually is — a BAS lodgement deadline is urgent; a client curious about a transaction from 2 months ago is not. Responding to all requests with equal urgency burns out the bookkeeper and doesn't serve clients well.
Don't let query backlogs accumulate. A portal or inbox with 30 unanswered queries is more stressful to process than 5. Clear queries the day they arrive, even if the resolution takes longer.
The communication agreement in the engagement letter
Communication expectations should be written into the engagement letter, not assumed. Include:
- Primary communication method (email / portal)
- Response time commitment (e.g., within 4 business hours during business hours)
- Phone call availability (by appointment only, or specific days)
- BAS calendar dates (when the bookkeeper will contact the client and for what)
- Client obligation (providing requested information within X business days)
A clear written agreement prevents the majority of communication friction before it starts. Clients who sign a well-written engagement letter know what to expect — and when they don't receive it, they have a clear reference point rather than vague dissatisfaction.
This article is general guidance for bookkeeping practice management. Communication structures should be adapted to the practice's specific client mix and service model.