How to Get Clients to Send Receipts and Invoices (Without Chasing Them Every Month)

To get clients to send receipts and invoices, make the request specific, scheduled, and nearly effortless: one message a month listing the exact transactions that lack a document, a reply-by date, and a channel that takes seconds (a forwarding address or a photo to a bot). Then remove the request where you can, by capturing the client's emailed invoices automatically through a read-only inbox connection.

Why does the monthly receipt chase fail?

The monthly request fails because it is vague, unscheduled, and costly to fulfill, not because clients do not care. Every bookkeeper with more than a few clients knows the pattern. Day 3 of the close, the bank feed shows 40 transactions with no document, and the email goes out: "Hi, could you send me any receipts you have for last month?" Half the clients never reply. The other half send a photo of a crumpled receipt and three forwarded emails, two of which you already had.

The request fails for reasons that have nothing to do with the client's good intentions:

• It is not specific. "Any receipts" is a research project. "The $1,284.50 to Uline on the 14th" is a two-minute task.
• It has no deadline and no consequence. Nothing the client can see breaks when they wait.
• The documents are scattered. Some are in their inbox, some in a vendor portal they log into twice a year, some on paper in a glovebox. Compliance means a scavenger hunt.
• It asks for too much. When the list includes every $6 coffee, the client learns the request is unreasonable and stops reading it.
• It arrives at a different time every month. There is no habit to attach it to.

Fixing the request fixes about half the problem. Removing the request fixes most of the rest.

Step 1: Shorten the list before you send it

Not every transaction needs a document. For US clients, IRS Publication 463, which covers travel, meal, gift, and car expenses, states that documentary evidence is not needed if "your expense, other than lodging, is less than $75," provided the records still show the amount, date, place, and essential character of the expense. That rule does not extend to every purchase: for ordinary expenses such as supplies, IRS Publication 583 asks for supporting documents that show the amount paid and that it was a business expense, and accepts a bank or card statement showing amount, payee, and date as proof of payment. The practical approach is to agree a documentation threshold with the client's CPA (some practices reuse the $75 figure) and, below it, treat the bank line plus a category and a note about business purpose as the support. Asking for every small receipt is overhead for both of you.

What does need a document:

Applying this filter can turn a 40-item list into 12 to 15. Those are the ones the client will actually send.

Step 2: Send one specific request, on a schedule

One message per client per month, the same business day each month, with this structure:

1. A numbered list of the transactions that need a document: date, vendor as it appears on the bank line, amount.
2. A reply-by date, two to three business days out.
3. One way to comply that takes seconds (see Step 3).
4. What happens otherwise: the item is recorded without support and flagged in the month's summary.

A script that works:

Subject: 6 documents needed to close September (reply by Thursday)

Hi Dana, September is nearly closed. Six payments need their invoice or receipt. Forward the email, or photograph the paper copy and send it to the receipts number, and I will match them.

1. Sep 4, ULINE SHIP SUPPLIES, $1,284.50
2. Sep 9, COMCAST BUSINESS, $312.00
3. Sep 12, J ALVAREZ DESIGN, $2,400.00
4. Sep 17, GRAINGER, $418.76
5. Sep 22, MARRIOTT CHICAGO, $389.14 (lodging, receipt required)
6. Sep 26, AMAZON BUSINESS, $606.90

Anything not in by Thursday is recorded as unsupported and listed in your September summary.

Note what the script does not do: it does not ask for "any receipts," it does not apologize, and it does not list the fourteen small card swipes below the threshold that you have already recorded with a category.

Never send the same item twice without acknowledging the first request. If an item carries over, say so: "Carried from last month: Sep 12, J Alvarez Design, $2,400.00."

Step 3: Make compliance a one-step action

The request only works if fulfilling it is nearly free. Three channels do that, and they are the same channels that let you remove the request entirely in Step 4.

A forwarding address. Give each client an address they can forward any invoice email to, and that their vendors can be told to bill directly. No login, no upload form. In Inbox Ledger, each workspace has its own forwarding address; anything sent to it is captured and extracted like any other document.

A photo to a bot. For paper receipts, the client photographs the receipt and sends it to a Telegram or WhatsApp bot linked to their workspace. The image goes through the same extraction, and the bot replies with what it read, including a warning if the extraction was low-confidence. A client at a trade show can clear three receipts before leaving the booth.

A read-only inbox connection. The client authorizes a connection to their business mailbox through Gmail's or Microsoft's standard consent screen (or IMAP for other providers). The connection is read-only: it finds invoices and receipts, and it cannot send, delete, or move anything. This is the channel that makes most of the monthly list disappear, because most supplier invoices for a small business arrive by email. Our overview of invoice processing automation explains what happens to a document after capture, and how to organize business receipts covers the conventions for the ones that still arrive by hand.

Step 4: Remove the request where you can

Once a client's inbox is connected, their emailed supplier invoices and receipts are captured as they arrive, the vendor, date, and amount are extracted, duplicates (the same invoice forwarded twice, or sent once as a PDF and once as a reminder) are flagged, and once you upload the month's bank statement, each document is matched to the bank transaction that paid it. On Day 1 of the close, you open the client's workspace and see which transactions already have a document. The monthly request shrinks to the portal-only items and the paper receipts.

Inbox Ledger connects to Gmail, Outlook, or IMAP with read-only access, finds invoices and receipts, extracts the data with AI, matches them to bank statement transactions, and pushes bills to QuickBooks Online or Xero. For the bookkeeper-client relationship, the pieces that matter:

• The client stays in control of their mailbox. They authorize the connection; you never hold their credentials.
• Two ways to connect the relationship. A client who already uses Inbox Ledger can invite their accountant from their own workspace with a link, and the accountant sees that client's documents alongside their other clients. A firm can also add a client business from its own workspace and send the owner a claim link; the firm's Clients tab shows the invite as pending until the owner claims it. Either way, the client's documents appear in the firm's view and the client can disconnect the accountant at any time.
• A backlog is handled the same way. For a new client with months of uncollected invoices, a retroactive scan over a chosen window (presets run up to the last 12 months) captures what is already in the mailbox, which is usually the bulk of a catch-up engagement's missing documents. Our guide on how to catch up on bookkeeping sequences the rest of that work.
• Rules do the recurring sorting. A rule can tag every document from a given sender, set a consistent vendor name for a supplier whose invoices vary, or exclude a sender that should never enter the books.

For a practice-level view of the multi-client workspace, see the accountants page. For the wider question of how firms collect client documents and which tools do what, see our guide to client document collection for accountants. If a client asks how to get their invoices to you without doing anything, send invoices to your accountant automatically is written for them.

Step 5: Record what never arrives, visibly

Some documents will not come. Handle them so the books stay honest and the client sees the consequence.

• Below the threshold, not lodging: record the amount, date, payee, and business purpose from the bank line and your knowledge of the client. No flag needed.
• Above the threshold, first month missing: record the transaction with the best description, mark it unsupported, and list it in the month's summary to the client.
• Above the threshold, second month missing: carry it forward in the request, and escalate in writing. For a supplier invoice on terms, request a copy directly from the vendor if the client has authorized you to do so.
• Never arrives: leave it recorded and flagged. An unsupported expense that is visibly flagged is a judgment call the client made; a guessed category with no note looks like the bookkeeper's error.

Photographed and scanned copies are acceptable records; our guide on scanning receipts for taxes covers the IRS position on electronic copies, which is worth sharing with clients who think the paper original is the only valid one.

The monthly summary to the client should have a standing section: "Recorded without support." When clients see the list grow, they send documents. When they see it empty, they trust the books.

Start for free and extract your first 10 invoices without a credit card.

A worked example: before and after

The figures are illustrative. A bookkeeper closes a logistics client with about 180 bank and card transactions a month.

The difference is not the client. It is that 53 of the 62 gaps were emailed invoices that a read-only connection captured without anyone being asked, and the remaining request was short enough to answer between meetings.

The bookkeeper's monthly document routine

Chasing receipts is not a client-management problem. It is a capture problem that has been handed to the client because the bookkeeper had no other way to get the documents. Give them a channel that takes seconds, capture what arrives by email without asking, and reserve the monthly request for the few items that genuinely need a human to go and find them.