The New Client Welcome Packet That Sets Expectations for Accounting Clients

27 August 2026·5 min read

Quick answer: A welcome email sequence tells a new accounting client what's happening; a welcome packet gives them something to actually keep and refer back to — portal login steps, a plain-English timeline of what happens when, and a document checklist they can tick off before their first deadline sneaks up on them. It's one PDF, built once, sent to every new client with minor tailoring. The firms that skip this spend the first three months answering the same five questions on repeat. 🤍

If you've read our piece on the law firm welcome email sequence, this is a different animal, built for a different problem. Emails are great for drip-feeding information over time, but a new accounting client doesn't just need to be told things once — they need somewhere to look back at when they've forgotten the portal password in week six or can't remember whether you need last year's depreciation schedule or this year's. A proper welcome packet is a reference document, not a sequence: one PDF that lives in their inbox and gets opened again and again in the first few months 💖. Firms that only send emails lose that referenceability the moment the client archives the message.

What most firms get wrong

Most new-client "welcome" material is really just an engagement letter and a portal invite, sent separately, with no single document tying them together. The client is left to piece together what happens next from memory — when they need to send records, what actually happens between "we've signed" and "your return's lodged," what a portal notification even means when it lands. Firms assume this gets covered "in the first meeting," but new clients forget most of what's said in that meeting within a day, and there's rarely anything written down to fall back on. The result is a stream of "quick questions" in the first few months that a two-page packet would have answered before they were even asked.

Welcome packet table of contents

Welcome + who's who: your name, your accountant's name and direct contact, and who to go to for what — bookkeeping query vs tax question vs urgent deadline.
Portal setup, step by step: screenshots, not just a link — how to log in, where documents get uploaded, how to reset a password without emailing you about it.
What to expect, month by month: a plain-English timeline — when you'll be in touch, what happens between signing and lodgement, and roughly when to expect first contact after onboarding.
Document checklist: exactly what you need from them, grouped by type (income, expenses, prior-year records), in a simple tick-box format.
Fees & billing: how and when they're billed, what's included in the fee already agreed, and what would trigger an additional cost.
FAQ: the five questions every new client asks in month one, answered once so they don't need to ask.

A new small business client, a design studio with two employees: The owner kept emailing to ask "did you get the invoice I uploaded?" because the portal gave no confirmation she recognised. The packet's portal section now includes a screenshot of exactly what a successful upload looks like, plus a line explaining the automatic email receipt she'd been missing. Those check-in emails dropped to almost none the following quarter.

A sole trader tradie client: He'd never used a document portal before and defaulted to texting photos of receipts to his accountant's personal mobile, which took twice as long to process. The packet's checklist, written for someone who'd never done this before ("take a photo, upload it here, that's it"), moved nearly all of his records into the portal within the first month, with far less manual chasing from the bookkeeping team.

A hospitality group with three related entities: The owner genuinely didn't know which entity a given expense should sit under, and every quarter meant a round of clarifying emails before BAS could even start. The firm added an entity-specific version of the document checklist as an appendix, one page per entity, and the quarterly back-and-forth shrank to a handful of genuinely tricky items instead of everything.

How to actually build and send it

Build it once as a proper PDF, not a Word doc with your logo slapped on, using real screenshots from your actual portal, because generic stock screenshots confuse clients more than they help. Keep it to four or five pages; anything longer and it becomes something nobody opens past page one. Send it as an attachment in the first welcome email, but also flag in your onboarding checklist to mention it verbally in the first call — "there's a PDF in your welcome email with all of this, keep it handy" — because clients skim emails and won't remember it exists unless you say so out loud. Update the fee and timeline sections at least once a year; a packet with last year's turnaround times or an outdated fee structure does more damage than not having one.

💡 The document checklist earns its keep fastest. Of everything in the packet, the checklist is what clients actually screenshot and refer back to when they're gathering records — get that page right and the rest of the packet can be fairly plain.

Mistakes to avoid

Making it a generic template with no firm-specific screenshots or process detail.
Letting it go stale — outdated fees or timelines are worse than no packet at all.
Sending it as an attachment with no verbal mention, so it goes unread.
Cramming in everything instead of keeping it to the handful of pages people will actually read.
Treating the packet as a replacement for the welcome email sequence rather than a companion to it.

Frequently asked questions

Do we still need a welcome email sequence if we have this packet?

Yes — they do different jobs. The sequence paces information over the first few weeks and prompts action at the right moment; the packet is the reference document clients come back to when they've forgotten what the sequence said.

How long should the packet actually be?

Four to five pages is the practical sweet spot — long enough to cover the essentials, short enough that a client will actually read it in one sitting rather than filing it away unopened.

Does this work for every type of accounting client?

The core structure does, but the document checklist and fee section need real tailoring by client type — a sole trader's checklist and a multi-entity group's checklist shouldn't look the same, and using one generic version undermines the point of the exercise. That's the honest limitation: this isn't a fully set-and-forget asset, it needs light customisation per client segment.

Should the packet be branded or plain?

Branded, but kept simple — it's a working document a client will refer to repeatedly, not a marketing piece, so prioritise clarity over design flourish.