The same receipts go into expenses.xlsx and a CSV, one row each, and the pack is fitted under an email attachment limit where it can be, with the real size shown. Before anything is written, every receipt sits in a grid where clicking a cell shows the box on the receipt it was read from, and a row whose amounts do not add up to its total turns red, so a misread total is caught before it reaches the report. Add the card statement and the charges with no receipt come out as their own list. Photo receipts use the free OCR pages, 5 a day, the whole report counts as one job, and nothing is uploaded.
How it works
- Drop the receipt photos and PDFs — each one is read on your device
- Check the grid: click a cell to see the box it was read from, and fix any value that is wrong
- Download expense-pack.pdf, with expenses.xlsx and the CSV if the report wants them
Questions people ask
Why not simply merge the receipts?
You can — Merge and JPG to PDF do exactly that. What a plain merge does not give whoever approves the report is a way from a line of the report to its receipt. Here each page carries a stamp such as R-003 with the receipt’s date and total, the summary page lists them all, and a bookmark jumps to each one.
Will the PDF be small enough to email?
Bindery fits it under an email attachment limit where it can be, with the size search Compress uses, and shows the real size of the file. A long report of large photos may not fit; the size shown tells you, and splitting the report into two periods is the usual way out. Check your expense system’s own upload limit too.
Can it read several receipts in one photo?
Not yet. Each photo is read as one receipt, so photograph them one at a time, flat, with each receipt filling most of the frame. A long receipt can be photographed whole. On the free plan, photo receipts use the 5 free OCR pages a day; receipts that arrive as PDFs with text use none.