How to Sort Phone Photos of Receipts by Client

To sort phone photos of receipts, first put every photo under the right client, then group them by month and vendor, the order bookkeepers use to match them to bank and card lines. Split any photo that shows several receipts into one record each, keep the sharpest of each set of repeats, and set aside photos that are not receipts.

Why phone photos of receipts are harder to sort than scans

Phone photos of receipts are harder to sort than scans because they arrive with no structure. A scanned PDF is usually one session, in page order, with a name someone chose. A camera-roll dump is dozens of images named by the phone, in the order they were taken, mixed with retakes, screenshots and the odd photo of the client's dog.

File names carry no meaning. A phone names images by sequence, so IMG_4471 tells you nothing about the vendor, the date or even the client. When three clients text photos on the same afternoon, the names alone cannot keep them apart.

Order follows the camera, not the calendar. A client who photographs a month of receipts on the 30th produces images dated the 30th, whatever the purchase date. The photo's timestamp is when it was taken; the receipt's date is printed on the paper and has to be read.

Quality varies photo by photo. Some are flat and sharp, others are curled, shadowed or cut off at the total. What makes a receipt photo readable to software and to a person is covered in receipt photo quality for OCR.

Repeats are common. Clients take a second shot when the first looks dim, hold the shutter and get a burst, or send the same photo by text and again by email. A scan rarely contains copies of itself; a photo batch almost always does.

How should receipt photos be sorted by client, month and vendor?

Receipt photos should be sorted by client first, then by month of the receipt date, then by vendor within each month. Client keeps files apart. Month matches how bank and card statements are issued. Vendor groups the repeat purchases, such as weekly fuel, that are easiest to tick off against a statement in a run.

Client. Assign each photo to a client the moment it arrives, using the sender, not the image. A text from a known number or an email from a known address settles it. Photos forwarded from a third party, such as a spouse or an office manager, need a note so they land in the right file.

Month. Read the date printed on the receipt and file the photo under that month. Ignore the photo's own timestamp for this. A receipt from 28 February photographed on 3 March belongs to February, because that is where it will appear on the statement.

Vendor. Within each month, group by the merchant name printed at the top. Normalize obvious variants so "Ridge Hardware #12" and "RIDGE HARDWARE" sit together.

Rename files once they are sorted. A name like 2026-03_Ridge-Hardware_139.88.jpg can be read without opening it, and it sorts correctly in any folder view. Keep the original file name in a column or the image's metadata in case the client refers to it.

Reading the amount and date off each receipt into a spreadsheet is the next job after sorting; the post on receipt to Excel covers it.

What should you do with one photo of several receipts?

One photo of several receipts should become one record per receipt. Crop or mark each receipt as its own item, give each its own date, vendor and amount, and keep a link back to the original photo. Filing the photo as one receipt loses all but one purchase, and the missing ones show up later as unexplained statement lines.

Clients take these group shots to save time. Five receipts laid out on a table and photographed once is faster for them and harder for the firm. The receipts may span several days, vendors and even months.

There are two ways to split one. The first is to crop the image into separate files, one per receipt, each named as above. The second is to keep the single image and log several rows against it, each with a note such as "receipt 2 of 4, top right". Cropping makes each receipt stand alone; logging keeps the file count down. Either works if every receipt gets its own row.

Check the group shot for receipts that are partly covered. A receipt tucked under another may show its vendor but hide its total. Ask the client for that one again rather than guessing.

HEIC files, screenshots and other receipt photo formats

Receipt photos arrive in a handful of formats: JPEG, HEIC from iPhones, PNG screenshots, PDFs from phone scanner apps, and images pasted into email. Most tools open JPEG and PDF without trouble. HEIC and screenshots are the two that cause friction, and both are worth handling on arrival.

Photos from iPhones sometimes arrive as .heic files that not every computer or tool in a firm opens. Apple's support page on HEIF and HEVC describes HEIF, the High Efficiency Image File Format, as compressing better than JPEG, and says an iPhone can switch to JPEG by opening Settings, tapping Camera, tapping Formats and choosing Most Compatible. The same page says media imported to a Mac or PC "might be converted to JPEG". A client who sends many receipts can be asked to make that change, or the firm can convert HEIC files to JPEG on arrival so every machine and tool opens them.

Screenshots are a different kind of evidence. A screenshot of a banking app or a payment confirmation shows that money moved, not what was bought. Keep them, but label them as payment screenshots, not receipts, so they are not counted as itemized purchases.

PDFs from phone scanner apps are usually the cleanest format, because the app has already cropped and flattened the receipt. Encourage clients who send many receipts to use one, and treat each PDF page as one receipt unless it shows several.

Burst shots and blurry retakes among receipt photos

Burst shots and blurry retakes among receipt photos should be reduced to one readable copy per receipt. Group images of the same receipt together, keep the sharpest one where every digit of the total and date is clear, and set the rest aside linked to the keeper. Do not count each retake as a purchase.

Burst repeats are easy to spot because they sit next to each other with timestamps a second apart and nearly identical content. Retakes are harder: the second shot may come minutes later from a different angle. Compare vendor, date and total, not the image.

Resends are the third kind of repeat. The same photo texted on Monday and emailed on Friday is one receipt, even though it arrives twice in two channels. Catching it means comparing across everything the client sent, not within one message. How duplicates get into a client file in the first place, and why a resend is the commonest case, is covered in how duplicate documents get into a client file.

On the client's side, Photos on a Mac can merge exact duplicates. Apple's guide to finding and merging duplicates in Photos says to click Duplicates below Utilities in the sidebar, select the sets and click Merge, and that removed copies go to Recently Deleted, where they can be recovered within 30 days. It helps a client tidy a library before sending, but it will not catch a retake from a new angle.

When not to sort receipt photos at all

Some receipt photos do not need sorting because a statement already covers what they show. A screenshot of a card transaction, a payment confirmation, or a photo of something that is not a receipt adds nothing a bank or card statement does not. Set these aside in one batch instead of filing each one by vendor.

Itemized receipts are different. IRS Publication 583 says a credit card statement used to prove payment must show the amount charged, the payee's name and the transaction date, but also that "proof of payment of an amount, by itself, does not establish you are entitled to a tax deduction." It lists credit card sales slips and invoices among the documents to keep. Whether a client needs a particular receipt is the preparer's call; the sorting routine only decides which photos are receipts and which are not.

A useful split is three piles: itemized receipts, which get the full sort; payment evidence, such as screenshots, which gets matched to the statement line and noted; and non-receipts, which get set aside with a note to the client.

Worked example: 30 receipt photos from one client

Tidewater Landscaping, a fictional client, texts and emails 30 photos covering February to May. All names and amounts are examples. The photos are named IMG_0101 to IMG_0130. After sorting, 23 photos are kept, one of which (IMG_0112) shows four receipts, giving 26 receipts.

IMG_0112 is the multi-receipt shot: four receipts on a tabletop, two from February and two from March, logged as (a) to (d). Without the split, three purchases would be missing from the table.

Seven photos are set aside, each linked to the reason:

The table is now ready to tick against the February to May card statements, one month at a time.

Sorting by hand is one stage of a longer chain; the post on accounting document automation sets out which stages a firm can hand to software. Reading a photo is not the same as understanding it, and OCR vs intelligent document processing explains the difference. Schema CPA takes phone photos through the same upload link as PDFs and email attachments, reads each receipt, and flags the resent copy rather than counting it twice; the client tracker demo shows a folder after that pass.