Dealing with client emails when every document is an attachment
The monthly and annual document cycle arrives as mail, and a mailbox is a poor filing cabinet. Searches an inbox for a document is never a good day.
Clients will keep emailing. Clients pay - and that makes them feel entitled to correspond in the way that suits them. But an inbox is a terrible way to manage a practice, but what if it wasnt, what if email was actually amazing?
The list is predictable. The mail is not.
What a practice needs from a client is close to a standing order. Monthly, for a bookkeeping client: statements for every bank and payment-provider account, sales invoices issued, supplier invoices and credit notes, slips for anything paid in cash, and the payroll pack.
Annually, for a company: a signed-off trial balance, financial statements signed by the public officer, the fixed asset register behind every wear-and-tear claim, loan agreements, dividend and shareholder changes, assessed losses brought forward.
Same documents, same clients, same months, every year. What actually arrives is an unlabelled stream in no order.
The problem is going from emails and attachments into a structure that your practice can extract, use and track.
Three places the document gets lost
The filename carries no client. IMG_4821.jpg, scan0001.pdf, Statement (3).pdf, Document.pdf. The client’s identity is in the From: header, not in the file — so the moment a file is dragged out of the mailbox onto a drive, the only thing that identified it is gone. This is why a folder of scan0001(3).pdf is often worse than leaving everything in mail.
The thread is the unit, not the document. A client replies to a three-week-old request, so the March statement arrives under the subject line you wrote for February. Sort by subject and the documents are in the wrong years.
The mailbox belongs to a person. Clients send to whoever they have dealt with, which means the practice’s filing system is distributed across individual inboxes and stops moving when someone is on leave.
The searches that work today
Both clients will narrow by sender, attachment and period. In Gmail, the operators compose:
from:client@example.com has:attachment filename:pdf after:2026/03/01 before:2026/04/01
has:attachment larger:5M # won't fit eFiling as-is
from:client@example.com has:attachment -in:trash
in:sent to:client@example.com has:attachment # what you already sent them
In classic Outlook for Windows, the equivalent is Advanced Query Syntax:
hasattachments:yes from:client@example.com received:last month
attachments:*.pdf from:client@example.com
messagesize:>5 MB hasattachments:yes
⚠ Check which Outlook you are in before trusting a result. from:, hasattachments:yes and relative dates work everywhere, but date-range received:, filename attachments: and messagesize: are only partly supported in new Outlook and Outlook on the web, which lean on the Has attachments filter buttons instead. On Mac the keyword is HasAttachment:yes. A query that silently returns less than it should reads exactly like a client who never sent the file.
The question search cannot answer
Every recipe above answers did it arrive. None of them answers what is still missing, because that is the complement of a set the mailbox never had: it needs the request list beside the arrivals. In most practices that list is a spreadsheet, a WhatsApp, or somebody’s memory — and it is the single thing that decides whether a deadline is comfortable or not.
Kasteel. Is purpose built to solve these problems. Emails are the start of a pipeline that makes organising client documents a breeze.