Email management in an accounting practice comes down to one answer, held for every client on the list. What are we still waiting for, and whose move is it. Reading, filing and replying all serve that question. The answer lives in the mailbox, and the mailbox is the one system in the firm filed by something other than a client.
- Every other record a practice keeps is filed by client. The inbox is filed by the minute somebody pressed send, and what it holds is the part of the job that’s still out with somebody else.
- Volume counts the wrong thing. Thirty messages about one return is one situation. One message each from thirty clients is thirty.
- You already know what you’re waiting for. The list exists before the client sends a thing. The work is matching that list against the arrivals, and nobody’s day has an hour set aside for it.
- Past one person, the mail about a single client lands in several mailboxes. One of them becomes the record when the firm says so.
What the inbox is really a list of
Ask where anything in a practice lives and the answer is a client. Returns sit in the tax software under a client. The books sit in the ledger under a client. The workpapers, the prior year, the engagement letter and the signed authorization sit in a folder under a client. That’s the only order the work has. The work is a set of obligations to named people and entities, each one carrying its own date.
Then there’s the mailbox, filed by the clock.
Look at what’s in there on an ordinary Tuesday. A bank statement for one client, and a note saying the second account is coming. A question about a vehicle, and a depreciation schedule waiting on the answer. An engagement letter that’s been out unsigned for nine days. A payroll summary photographed on somebody’s kitchen table. A notice with a response window on it. A supplier invoice, and two newsletters.
That’s a work list, written by other people. Every item is a piece of an unfinished job, and it sits in the mail rather than in the file because somebody outside the firm still has it.
So the mailbox is a report on work in progress. Your clients write it, and it’s ordered by the moment each of them pressed send. Your tax software knows what a return needs. The inbox knows the client answered the question on Tuesday, and it has filed the answer under Tuesday.
That’s why getting on top of email, in a practice, feels like it’s about something else. An empty inbox and a full one can describe the same firm on the same day. What changes the firm is whether somebody can say what each client still owes from where they’re sitting.
Why the client is the unit
Read a hundred messages from the top and you make a hundred decisions. Group the same mail by client and you’re usually looking at thirty situations. Most of them can wait.
The gain here is accuracy rather than tidiness. Messages about one return depend on each other, and arrival order makes you act on information a later message has already replaced.
A client sends her bank statements at nine. At 9:30 she writes to say ignore those, wrong year. At eleven the right ones arrive. At four she asks whether her daughter’s tuition is deductible. In arrival order that’s four items, and two of your decisions are wrong before you make them. Read as one client, it’s one delivery and one question. The question is the part that needs you.
The harder half is what a client actually is. In this trade a client sits a long way from a single email address.
A married couple filing jointly is one client and two addresses. Make it three when an adviser is copied in. A business client is an entity, and the mail comes from the owner, the controller, and a bookkeeper who may write to you about two other companies as well. One person can be several clients. The owner of three entities writes from one address about three returns with three different dates on them. Sorting by sender sorts the wrong thing in both directions.
Those same groupings are where the confidentiality lines run. That’s a subject of its own, and the lines the software cannot see has it. For the working day the rule is short. Mail belongs to a matter, a matter belongs to a client, and a sender is a third thing.
Reading an inbox against a list
Here’s what makes a practice unusual, and it’s worth more than it usually gets credit for. You know what you’re waiting for before the client sends a thing.
The organizer, the request list, last year’s return, the standing monthly schedule for a bookkeeping client. Between them, the set of documents a job needs exists on paper at the start. Almost nobody else works this way. A design studio has no list of the seven things a client owes it. You do.
That changes the daily question. The question is what moved today. Every message advances an item on a list, or opens a new one, or does neither. The third case is most of them.
It also puts the real failure somewhere unexpected. You know what’s missing. The trouble is that the list lives in one system and the arrivals land in another, and the only join between them is somebody’s memory of reading a message.
So items arrive out of order. Three come in one email and one is spread across five. One arrives as a bare attachment, under a filename the client’s phone chose. The tick against the list never happens. Everyone here is careful. The day simply has no moment where the list and the mailbox sit open together, with reconciling them as somebody’s job.
The cost shows up as the same work, done again. Every time anyone asks what the Nolans still owe, somebody rebuilds the answer by searching the mailbox. That’s several minutes, and it turns on guessing the right word. The answer is only ever as good as the person searching. Repeat that across a client list and a season. A real part of the firm’s week goes on establishing facts it already established last Thursday, by someone who isn’t sure it was Thursday.
The fix is plain, and every firm already knows it. Update the list when the message lands, rather than when you sit down to prepare the return. The rest is worth saying out loud, because this work files itself under admin so easily. Reconciling is the job. The return can only be finished once the list is complete, so keeping the list true is the same work as preparing the return, done earlier and more cheaply.
The two clocks on every request
Every request you send sits between two clocks. Only one of them is yours.
Yours is fixed, and it comes from outside. A filing date somebody else set stays where it is while a client is on vacation. Theirs is whenever they get to it. Nobody can know that in advance, and it runs almost independent of how urgently you wrote.
General advice about when to follow up is about manners. Give it a few days, stay polite. In a practice the answer is arithmetic. Take the date the thing is due. Subtract what your side still needs once the document arrives. That’s preparation, a review, the client’s signature and the transmission. What’s left is the client’s window. The follow-up date is the end of that window, and you set it the day you ask, rather than the day you notice the silence.
Firms tend to dislike where that lands. The right follow-up date comes out of the arithmetic rather than out of how long feels polite. For a client whose return needs two days of work behind the missing statement, two weeks of silence is fine. For one whose file needs a week of clean-up and a partner review, writing again the day after you asked is the only date that works.
There’s a second date, and it’s the one that gets set late or never. It’s the day waiting stops being the plan. That’s the day you tell the client the original date is at risk, or open the extension conversation, or say plainly what happens if the document stays where it is. That date has to fall early enough that the sentence is still true when you say it.
Unanswered emails and the threads that come back has the general case. It covers how quickly replies actually arrive, and why the careful message waits longest. The part specific to a practice is short. Both of your dates come off a deadline somebody else set, so you can work them out rather than feel them.
Four mailboxes and one client
In a practice of one, the inbox is the firm, and the record is wherever you last looked. At five or fifteen people that stops being true, and it stops quietly.
Mail about one client arrives at the general address on the website. It arrives at the partner who signed the engagement, because that’s who the client thinks of. It arrives at the preparer who asked the question, because the client pressed reply. It arrives at the bookkeeper, who has her own address and her own relationship with the client’s office manager. Four mailboxes, one client. Every one of those routes makes sense from the sender’s end.
You see it when “did the Nolans send the statements” gets different answers depending on who you ask. All of them are given in good faith.
The fix is a decision rather than a purchase, and it’s one sentence long. For each client, or for the whole firm if that’s simpler, name the address that’s the record for documents. Anything landing elsewhere gets moved into it. Forwarding, an alias, or a rule in the mail system the firm already runs will each do the job. What matters is that the sentence exists in writing. Then the answer to where the record lives holds steady, whoever’s in the office that week.
Two honest notes on that. You make this decision, and every email product waits for you to make it, so a product promising to route a practice’s mail correctly before being told what correct means has skipped the only hard part. And your clients will go on replying to whoever wrote to them last. That’s the reasonable thing to do, and it will carry on. Any arrangement that depends on two hundred people learning an internal convention will fail in the first heavy week.
Two people sharing the work of one practice is a subject of its own, and when an email falls through the cracks between you is where that one is told.
What has to survive the reading
Everything above works while the person holding it is at their desk and remembers reading it. Two tests tell you whether you have a system or a talent.
The first is the week that person is away. A client phones and asks where their return stands. If the answer needs the one who’s out, the state of the work was living in one person’s reading of the mail.
The second is the February conversation. A client says, with complete sincerity, that they sent it. Sometimes they did, to an address nobody watches. Sometimes they’re remembering that they meant to. Either way, a record with a date on it settles that conversation, and “I am fairly sure we asked twice” loses it. Being proved right is beside the point. What matters is a deadline that’s now three weeks nearer, and what you can honestly tell them about it.
So the standing shape is short. Anything you’re waiting for is written down outside the reading. It carries the client, the date you asked and the date you decided you’d chase. The message it came from stays attached, so the record is the mail itself rather than a note about the mail. And the mailbox is kept rather than cleared, because here the archive is evidence. What you asked and when is the thing you may one day have to show.
The gain here is steadiness rather than speed. What all of it buys is one sentence, said on the phone, about where a client’s return actually stands. In a practice that sentence is most of what people mean by good service.
Where does Point fit?
All of that is a way of working, and firms have run it on paper for decades. Software changes where the effort falls. Point takes over the bookkeeping about the mailbox and leaves the judgment with you.
The feed arrives already ranked. Point weighs how much a message matters and how soon, so a client with a date on them sits above a receipt on the worst morning of the year. How that weighing is done is a subject of its own. Every thread carries a summary in a line. You can tell whether a forty-message chain about one return needs you before you open it.
Where a message puts an obligation on you, Point lifts the ask out and dates it, with the thread it came from hanging underneath. You type it nowhere. Requests you’ve sent are tracked as things you’re owed, and they come back on the day you set rather than the day you happen to remember. That’s the waiting register, kept by the one system that watched the message leave.
You can also leave a standing request. Ask to be told when the K-1 from a particular client arrives, or the signed letter. You hear about it once, when it lands, and the checking stops. Attachments gather into one list, and each one stays joined to the thread that carried it. Put a question to a document and the answer comes back with a link to the page it was read from, which is what a mailbox made mostly of paperwork actually needs. Duplicate contacts are merged, and the people who matter are marked, so a household writing from two addresses reads as one relationship rather than two strangers.
Replies come back drafted the way you write. Point runs the scheduling back-and-forth itself when a review needs to go on the calendar. How much happens on your behalf is a dial, and each kind of task carries its own setting. It starts at review. Point prepares the work, and the work waits for you. Raise a setting and Point handles that kind of task for you, which is the point of raising it. What was done shows in a log with times against it, and most of it can be reversed from there. One exception holds for every product of this kind. A message already delivered to somebody else’s server is gone.
Point signs in to the Gmail or Microsoft 365 mailbox the firm already runs. The address on your letterhead and eleven years of archive stay exactly where they are. If you also run a rental company or a second practice, each business is sealed off from the other. That boundary goes around a business you operate, rather than around the clients inside one. That’s what you want here, because half the value is noticing that the same client has written three times this week.
The list stays yours. Your engagement schedule stays in practice management, the checklist stays in your tax software, and the firm names the mailbox that is the record. Point works on the mail and leaves the ledger and the return where they are. The full inventory is on the benefits page, Point for accountants walks it through a practice, and Point itself is the short version.
Common questions
How much email is too much for a practice to handle this way?
Message count is the wrong number to watch. A firm quoting it is usually describing how the morning feels. Count open engagements and open requests instead. That’s the returns in progress, and the items you’re waiting on across all of them. A firm taking a hundred and twenty messages a day with eleven open requests is comfortable. A firm taking sixty with ninety open requests is in trouble. Inbox discipline leaves that hidden, because the trouble sits entirely in the mail that has yet to arrive.
Should the firm use one shared address or personal ones?
Either works, once you add the one sentence. What decides it is whether one address has been named as the record for a client’s documents. A general address with nobody accountable for it becomes a place mail goes to be unread. Personal addresses with no named record leave four honest people holding four different answers about the same client. Choose whichever suits how your firm actually deals with people. Then write down which one is authoritative, and move everything else into it.
Is this practice management software for accounting firms?
No, and this is the one distinction the whole piece turns on. Practice management software holds the list: the jobs, the stages, the deadlines and who’s doing what. The stream of arrivals that decides whether any item on that list is complete sits outside its view. An email tool is the other half, and the gap between the two is where a practice loses its days. If your workflow system is fine and the mailbox is where the state goes missing, you want both. AI email for accountants maps the categories properly, portals and shared-inbox tools included.
What about the client who always writes to the wrong person?
They’ll carry on, and the arrangement has to survive that. A client replies to whoever wrote to them last. That’s sensible, and it’s why the habit outlasts any reminder you send. Treat it as a routing fact rather than a training problem. The mail arrives wherever it arrives, and something moves it to the address that’s the record. A practice that depends on its clients learning an internal convention has built its filing system out of other people’s habits.
Is it safe to point AI at a mailbox with client returns in it?
A fair question, and a longer one than it looks. What you’d be connecting is the register of the whole practice. It holds every client’s name, most of their documents, and the record of everything you’ve ever asked them for. That’s exactly why it deserves the full answer rather than a reassurance. Is it safe to use AI with client financial data sorts it by what the data is and what the tool is allowed to do next, and the questions to put to any vendor is the list to send before anything gets connected.
The short version
A practice mailbox is a report on work in progress that your clients write for you. It’s ordered by arrival time, which is the one fact about a message that carries no information. It’s also the one record in the firm filed by something other than a client. Four moves convert it. Read by client rather than by message. Reconcile arrivals against the list you already have. Set both dates on a request the moment you ask. Name the one address that is the record. Do that and the state of the work stops living inside one person’s reading of the mail. The rest of this collection takes those jobs one at a time. For the buying question there’s AI email for accountants, and for what you’re aiming at, what a calm inbox actually feels like.