How to get clients to send you coded receipts

Month-end for many bookkeepers still looks like this: a photo dump in email, a shoebox of faded thermal paper, or a card statement with no images. You then spend hours re-coding every line because the client never chose a GL account when they spent the money. That work is billable, but it is also the least leverageable part of the engagement. This guide is a practical onboarding system so clients send you coded receipts on a schedule — date, vendor, amount, your codes, payment method, and the photo — instead of raw evidence you have to interpret cold.

This is a workflow article for bookkeepers and small accounting firms. It is not tax, legal or accounting advice. Confirm categories and treatment with your own practice standards and each client's engagement letter.

The problem you are solving

Uncoded receipts force you to answer questions the client already knew at the counter: Was that Home Depot ticket job materials or shop tools? Was the restaurant meal client entertainment or personal? Which card paid it? Without a photo, you cannot verify the total against the bank feed. Without a code, every line becomes a research ticket.

• Shoebox / email dump: images arrive with no structure. You rename, sort and guess.
• Statement-only: vendor and amount appear, but not what was bought or why.
• OCR without shared COA: software may read the total well, then suggest a generic category that is not on your chart. You recode at month-end anyway.
• Month-end batching: clients wait until the books close, then cannot remember splits. Accuracy drops and your review time goes up.

The fix is not "nag harder." It is to remove friction: give them your chart of accounts, one capture habit, and one handoff day with a fixed file format.

What you want back, in one sentence

For every business expense: date, vendor, total (or split amounts), how it was paid, your account code(s), and a readable photo — delivered weekly or monthly as one CSV plus a ZIP of images, same columns every time.

That matches what clients need on their side too; see how to organize receipts for your bookkeeper if you want a client-facing companion article to send them.

Why clients do not do it (until you design for it)

• Friction at the counter. If coding means opening a spreadsheet later, it does not happen. Capture has to take about 20 seconds while they still hold the receipt.
• No shared chart of accounts. Clients invent "supplies" and "misc." You then map those labels to real accounts. Give them your codes first.
• Waiting until month-end. Memory fades. Mixed tickets get dumped into one bucket. Set a weekly handoff so the pile never gets large.
• Unclear "good enough." Clients do not know whether you want PDF, JPG, Google Drive folders or QuickBooks attachments. Spec the export once.

Onboarding script (about 10 minutes per client)

1. Give them your chart of accounts for their type of business. Export a short expense list (Code, Name, Active, Note). For freelancers and general small service businesses, start from a simple small-business chart of accounts. For trades and job-costing clients, use the contractor version (job costs vs overhead). Trim it to what you actually use for that engagement — 25–40 expense accounts is enough for most.
2. Pick one capture habit. One app, one note template, or one shared folder — not three. The habit is: photo before the receipt hits the pocket, then total + code + vendor + payment method immediately.
3. Set a weekly handoff day. Example: every Monday they send last week's ZIP. Monthly is fine for very low volume, but weekly prevents the shoebox.
4. Show one split example. A hardware-store ticket that is part job materials and part office supplies. If they cannot split, your job costs will be wrong. Point them at how to split one receipt across multiple categories.
5. Agree what "done" looks like. Same CSV columns, same image naming, no duplicate exports of the same receipt.

Spec: CSV columns + receipt images ZIP

Ask for one ZIP named something like ClientName_2026-10-06_to_2026-10-12.zip containing:

• expenses.csv (UTF-8) with these columns:

• receipts/ folder of images. Preferred names: YYYY-MM-DD_Vendor_Total.jpg (or .png / .pdf). Split lines may share one image filename.
• No duplicates: each purchase appears once in the CSV for that period. If they re-export, they replace the prior file for that week rather than attaching a second copy.
• Amounts: lines for one receipt must add up to the receipt total (tax allocation per your preference — state it in the onboarding email).

You can import that CSV into your practice software or use it as a review checklist against the bank feed. Test one sample import before you standardize a client on Xero/QBO-specific formats.

Sample client email (paste and adapt)

Optional checklist to attach or paste into a shared doc:

• ☐ COA CSV imported / printed and in the glove box or phone
• ☐ Capture tool chosen (app or agreed template)
• ☐ First week ZIP sent on schedule
• ☐ One split receipt practiced successfully
• ☐ Payment methods labeled the way they appear on the bank feed

When cloud OCR or expense platforms make sense

Manual coding at capture is not always the right answer. Balanced trade-offs:

• Prefer a shared capture + your COA for freelancers, sole props and small contractors with a modest receipt volume, lots of mixed tickets, and a bookkeeper who wants specific GL codes. The person who bought the item chooses the code while they still remember. See receipt app vs OCR apps for the longer comparison.
• Prefer OCR / expense platforms when volume is high, several employees submit expenses that need approval and reimbursement, or you already run the practice on a platform that matches receipts to bank feeds and you want clients on the same rails.
• Combining both is fine: employees on an expense platform, owner mixed receipts on a simple coded-capture app — as long as you know which source feeds which entries so nothing posts twice.

Either way, the onboarding rule stays the same: clients use your codes, hand off on a schedule, and you still review.

What to measure after 30 days

• Share of expenses that arrive with a valid code from your COA (target: nearly all recurring spend).
• Number of "what was this?" emails you still send.
• Whether the weekly ZIP arrives without renaming or rework on your side.

If coding compliance is low, shorten the COA, move the handoff to weekly, or sit with the client for one live capture session. Tools do not fix a list of 200 unused accounts.

Related: How to organize receipts for your bookkeeper · Receipt app vs OCR apps · Ledgerlite for bookkeepers · Small business COA · Contractor COA