Email management for bookkeepers: a dozen clients, one inbox

Bookkeepers manage email best as one small system, set up once and used the same way for every client. Give the inbox an address for each kind of mail, a label for each next step, one read in the morning and one day a month for questions. Keep the work itself on a task list and a calendar, where it can’t scroll away. A dozen clients in one inbox is a normal week for a bookkeeper. You don’t need a new habit for each of them. You need one shape they all fit into.

This page sets out that shape, one part at a time. Each part links to a guide that goes deeper when you want it.

Email management for bookkeepers, in six parts

Here’s the whole system before the detail:

1. Addresses. Your own address for people, and one or two role addresses for documents and machines.
2. Labels. A label says what happens next, so a glance at the inbox is a glance at the work.
3. A morning read. One pass that surfaces documents, bank and software notices, payment requests and dates.
4. A fixed day for questions. Transaction queries go to each client together, on the same day each month.
5. Templates. The five messages you send every month are written once and reused.
6. Work out of email. Tasks, deadlines and call requests move to a list and a calendar the day they arrive.

None of this needs new software. Each part works in Gmail or Outlook as they are. A tool can take on the reading and sorting, and the last section says where that helps.

The addresses: one for you, a few for roles

Most bookkeepers start with one address that does everything. Client questions, bank alerts, payroll confirmations and forty receipts a week all land in the same place. The client email you need sits between two automated notices.

A second address fixes most of that. Ask clients and their software to send documents and notices to a role address, and keep your own address for people.

Role addresses are usually aliases, and they cost nothing extra on either big platform. Google’s own admin help says you “can add up to 30 email aliases for each user at no extra cost” (Google Workspace Admin Help). Microsoft’s says you “can create up to 400 aliases for a user” with no extra fees or licenses (Microsoft Learn). Both were checked on October 4, 2026.

An alias delivers into your one inbox. You read one place, and the “To” line already tells you what kind of mail it is. One detail matters on Microsoft 365. Microsoft says a reply from Outlook on the web uses the alias the mail arrived at, while Outlook desktop replies from your primary address. If a client should always see your own name, reply from the address you want them to keep.

The last row is different. Some clients give you a login to a mailbox on their own domain, such as books@theirbusiness.com. That’s a separate account with its own password, and it belongs to them. Reading several of those alongside your own is its own problem, covered in a mailbox per client.

Labels that say what happens next

A label per client is the first thing most people set up. It’s useful for finding things later. It doesn’t tell you what to do this morning.

The labels that run the week describe the next step. Four are enough for most bookkeepers:

Every thread carries one of these, plus the client’s name if you like. A Monday look at “Waiting on client” is the whole chase list. A Friday look at “To code” is the whole data-entry list. Nothing needs remembering, because the inbox already holds it.

Receipts and statements have their own rhythm and their own filing question. Where they should live once they’ve arrived is receipts and statements. If you use Point, filing a thread writes a real Gmail label, so the system above stays intact in Gmail too (how Point works as your Gmail label manager).

What the morning read should surface

The first look at the inbox decides the day. For a bookkeeper, a good morning read pulls five kinds of mail out of the pile:

• Documents that arrived. The statement you asked for, the receipts batch, the payroll report. Each one closes an open item.
• Bank and software notices. A feed that stopped syncing, a connection that needs signing in again, a payroll run that’s waiting for approval. Most of this mail says nothing. The few that say something has stopped matter more than anything else that morning.
• Payment requests. A client asks you to pay a bill, or a vendor sends an invoice to pay. These go first, and they get checked.
• Dates. A filing date the accountant mentioned, a call the client asked for, a payroll cutoff moved for a holiday.
• Replies to your questions. Answers that came in overnight, ready to code.

Everything else can wait for the afternoon. How to order the pile once it’s sorted is what comes first. What a bookkeeper’s morning summary looks like day to day is the morning read.

One kind of payment request needs a rule of its own. A message asking to pay a vendor at new bank details is the classic business email compromise. The FBI’s Internet Crime Complaint Center counts $55.5 billion in exposed losses from it worldwide between October 2013 and December 2023 (IC3 public service announcement, September 11, 2024). Its advice is short:

Use secondary channels and/or two-factor authentication to verify requests for changes in account information.

In practice, that means you call the vendor or the client on a number you already had before the email arrived. What a bookkeeper holds, and what a client expects of you with it, is bank data in a thread.

One day a month for questions

Transaction questions are small. A card charge with a strange merchant name, a transfer with no memo, a deposit that doesn’t match an invoice. Each one is worth less than the email it takes to ask.

So send them together. Pick a day, say the 12th, and send each client one message with every open line in it. Clients learn the day. After a few months, many answer it the same afternoon. A question that comes up mid-month goes on a list for that client instead of into a new email.

Two habits keep the list short:

• Keep the answers. When a client explains a recurring charge, write it into a coding rule or a client note. Next month you won’t need to ask. That’s the same question again.
• Explain before they ask. A client who sees a surprising figure writes in. A one-line note with the month’s numbers heads that off. How to write it is explaining a charge.

The monthly cycle around this day, from the first statement to sign-off, is its own subject. It’s covered in the bookkeeping inbox, and the month that starts again.

Templates for the messages you send every month

A bookkeeper sends the same handful of emails to every client, every month. Writing each one fresh costs time and makes each client’s version drift. Write them once:

1. The monthly question batch
2. The missing statement request
3. The receipts reminder
4. The “your books for the month are done” note
5. The call request before month-end

Every one of them starts the same way. Before you write a word, name the transaction or document exactly. A question about a charge gives the date, the amount and the description as it appears in the bank feed. A request for a statement names the account, the last four digits and the month. A client can answer that from a phone in a minute. “Can you tell me about the Amazon charges?” needs a desk and a search.

Here’s what a single query line looks like when it’s done well:

Aug 14 · $212.40 · SQ *RIVERSIDE SUPPLY
Is this materials for the Elm St job, or general supplies?
If I don't hear by the 20th, I'll code it to general supplies.

The date, the amount and the feed description let them find it. The question offers two answers. The last line says what happens if they’re busy, so silence still settles the line.

A statement that never arrives has its own sequence of messages, covered in the missing statement. If Point drafts these for you, each draft comes back in your own wording and waits for you by default (getting AI replies that sound like you wrote them).

The long thread, in three lines

Some client threads run for weeks. A payroll change, a loan that needs splitting into principal and interest, a sales tax registration nobody finished. By message thirty, nobody remembers what was settled.

A useful note on a long thread answers three questions:

• What was sent. The documents and figures each side has already supplied.
• What’s outstanding. What you’re still waiting for, and from whom.
• What was agreed. Any decision that changes how you code something from now on.

Write it at the bottom of the thread, or keep it in the client’s notes. The next time the thread wakes up, you read three lines instead of thirty messages. Building that note for a bookkeeping thread is the long thread. How a summary of any long chain is put together is how to catch up on a long email chain.

Getting the work out of email

The inbox is a good place for mail to arrive. It’s a poor place for work to wait. A request that becomes a task, and a date that becomes a calendar entry, can’t be buried by tomorrow’s mail.

Three kinds of email should leave the inbox the day they arrive:

• Asks. “Can you run payroll a day early this week?” becomes a task with that date on it.
• Dates. A month-end cutoff, a sales tax due date the client forwarded, or the accountant’s deadline for year-end figures goes on the calendar with the client’s name in the title.
• Call requests. “Can we talk about the numbers?” becomes a booked time, not a thread of suggestions.

Once these leave, the inbox holds only mail. Your list holds what you owe, and your calendar holds when. Booking the month-end call without the back-and-forth is the month-end call. What a task needs to hold when it comes from an email is email task management, without writing it down.

Some of this can run on its own. A rule that files every payroll confirmation, or a watch that tells you when a particular client’s statement lands, saves a check every day. Which jobs are worth handing off is worth automating.

Finding a client’s statement fast

Sooner or later a client asks for the March statement you were sent in April. Or the accountant asks where a receipt is. The search is quicker when the mail was set up to be found.

Three habits make it easy:

• Put the client and the period in the subject. “Riverside · August statements” is findable in any mail app for years.
• Reply in the thread you asked in. The document lands next to your request, so one search finds both.
• File the attachment once it’s entered. Your document store holds the record. The email is how it arrived.

When the words don’t come back to you, search by what you remember instead. In Point you can type “the bank statement Riverside sent in the spring” and get it back. You can also ask for the number inside a PDF (ask a question, get the answer out of the attachment). How meaning-based search works is find an email when you can’t remember the words.

What Point takes off a bookkeeper’s desk

Point is an email app that works on the Gmail or Microsoft 365 account you already have. Your address, your aliases and your history stay where they are. For a bookkeeper, it takes on the reading so you can do the books:

• Triage as mail lands. Every thread is ranked the moment it arrives. The client who needs you sits at the top, and the forty notices sit below. How the ranking works is how email triage works.
• A briefing at the hour you pick. Documents in, notices that need you, payment requests and today’s calendar arrive as one read (everything today asks of you, in one read).
• A summary on every thread. You know what a thread is about before you open it.
• Tasks from asks. When a client’s email asks something of you, it lands on your list.
• Watches. Tell Point once to watch for a client’s statement. When it lands, Point prepares the next step and waits for your go (when an email watch lines up the next piece of work).
• Drafts in your voice. The monthly asks come back written the way you write them.

You choose how far each kind of work goes, from suggest-only to fully handled. Review is the default out of the box (setting how much your inbox does on its own). The ledger, the bank feeds and the coding stay in your accounting software. Which app to do that work from is the app you work in. The rest of what Point does is on the benefits page.

When the answer is somewhere else

An inbox system is right for one bookkeeper, or two who each look after their own clients. It isn’t enough for everything.

If you hire staff and hand clients between people, a practice management tool fits better. Those tools keep the work, the deadlines and the client mail in one record with an owner. If clients send scans of bank statements and IDs by email, a client portal is a safer place for them to upload. How much time all of this is actually costing you, in a bookkeeper’s own unit of time, is hours in the week. What to do when you’re the only one and there’s no one to hand the inbox to is no admin help.

Common questions

How should bookkeepers manage email?

Bookkeepers manage email best as one system that every client fits into. Use your own address for people and a role alias for receipts and notices. Label each thread with its next step, such as “Waiting on client” or “To code”. Read once in the morning for documents, bank notices, payment requests and dates. Send each client their transaction questions together on a fixed day each month, and move tasks and deadlines out of the inbox the day they arrive.

What is the first step in composing an email for bookkeeping purposes?

Name exactly what the email is about before you write anything else. For a transaction question, that’s the date, the amount and the description as it appears in the bank feed. For a document request, it’s the account, its last four digits and the month. With those in the first line, a client can answer from a phone without opening their books.

How do you manage company emails?

Separate the mail by kind before it reaches you. Personal addresses take mail from people, and role addresses or aliases take receipts, alerts and notices. Then give every thread a label that says what happens next, read at set times instead of all day, and move tasks and dates to a list and a calendar. If several people answer the same address, you need a shared inbox with clear ownership.

What are the 5 C’s of email?

There’s no single official list. The version most often quoted says an email should be clear, concise, correct, courteous and complete. For a bookkeeper, “complete” does the most work. A question that includes the date, amount and feed description gets answered the first time.

What are the 7 types of emails?

Lists of seven email types come from marketing, and they cover newsletters, welcome emails, promotions and similar. A bookkeeper’s inbox sorts more usefully by what each email needs from you. Most of it falls into client questions, documents, bank and software notices, payment requests, dates, replies to your queries and mail that needs nothing.

Are you allowed to have multiple email accounts?

Yes. Running several addresses is normal and allowed on Gmail, Google Workspace and Microsoft 365. For a bookkeeper, the simplest setup is usually one account with aliases. Google Workspace allows up to 30 aliases per user and Microsoft 365 up to 400, both at no extra cost. A mailbox a client created for you on their domain is a separate account that belongs to them.

Should a bookkeeper have a separate email for each client?

Usually not. One inbox with a label per client is easier to keep up with than a dozen logins. A separate mailbox makes sense when the client owns it and wants vendors and their bank writing to it, and then it’s theirs to keep when you part ways.