GTD

Bookkeeper email: chasing documents without the dread.

Missing receipts, unanswered queries, and month-end walls. The chasing system that keeps client books closeable.

By Mathias CelisJune 19, 20265 min readLast updated August 2026
TL;DR

Bookkeeping stalls on other people: missing receipts, unexplained transactions, unanswered queries. The work is ready; the inputs aren't. The fix is a chasing system rather than a memory: a per-client outstanding-items list generated from sent requests, reminders on a fixed and polite cadence, query emails that make answering one-click easy, and month-end status visible per client at a glance.

Ask a bookkeeper what actually delays month-end and the answer is rarely the bookkeeping. It's the missing receipts, the unexplained transactions, the query email sent nine days ago that three clients haven't opened. The work is ready; the inputs aren't, and the inputs live in other people's inboxes. Bookkeeping at scale is a chasing operation with a ledger attached.

One consolidated ask beats a drip of them

Clients don't ignore bookkeepers out of malice; they ignore friction. Five separate requests across two weeks each cost the client a context switch, so each gets deferred. One consolidated request per period (a short checklist: these six documents, these three answers) gets handled in one sitting. Fewer, bigger, easier asks; that's most of the improvement before any tooling.

The query email clients actually answer

Transaction queries die when they arrive as paragraphs. The format that gets answered between two of the client's meetings: one transaction per line, date and amount stated, one specific question, answerable in a word or two. Scannable lists get replies; narrative queries get flagged for later, and later is where month-end goes to slip.

How do bookkeepers chase without dreading it?

By making the cadence a system property instead of a personal act. The reminder isn't you nagging; it's the process running: request, reminder at three business days, second at a week, consequence named where real (close delayed, filing at risk). Clients learn the rhythm and increasingly beat it, because predictable processes train predictable behavior. The follow-up craft applies wholesale, and the per-client outstanding list is the waiting-for discipline doing accounting work.

The loop that runs itself

Request, track, remind, receive, match: the loop is mechanical end to end, which is why it automates so cleanly. Pidgy builds each client's outstanding list from your sent requests on Gmail or Outlook, drafts the reminder when silence passes the cadence, and queues it for your approval, so the chasing runs on the calendar instead of on your memory (or your dread). Month-end becomes a date again. The bookkeeping setup in full: the bookkeepers use case.

Frequently asked questions

How do bookkeepers get clients to send documents?

By making it easy and rhythmic: one consolidated request per period instead of a drip of asks, a fixed reminder cadence clients learn to expect, and requests phrased as a short checklist. Clients respond to patterns; sporadic chasing trains sporadic replies.

What should a bookkeeper's query email look like?

One transaction per line, one question per transaction, answerable in a word or two: date, amount, and the specific question. Long narrative queries get deferred; scannable lists get answered between meetings.

Can AI automate document chasing for bookkeepers?

It's among the best fits in professional services: the outstanding list builds itself from sent requests, silence past the cadence triggers a drafted reminder, and the bookkeeper approves each send. Pidgy runs this loop on Gmail and Outlook, so month-end depends on the calendar, not on memory.

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistPidgy for bookkeepers