How to Convert a Month of Invoices at Once
One bill is a small job. Thirty bills is a pile. If you convert them one by one, the pile eats your day in small bites. The fix is to batch convert invoice PDF to Excel files in one run: one upload, one sheet per bill, one round of checks.
Our invoice to Excel converter takes a set of files at once and works through them in order. This guide shows the craft around the tool: how to sort the pile first, how to run the batch, and how to check a batch without reading every row of every bill.
A batch is not a bigger risk. Done right, it is a smaller one: the same checks, run the same way, on each bill, with the flags lined up where you can see them. The craft below is short. Most of it is habit, and the habit pays from the first run.
Why a batch beats one by one
Each single convert has fixed costs: find the file, open the tool, wait, save the sheet with a clear name. Those costs are small once. Times thirty, they are the day. A batch pays them once. You set the files up in order, start the run, and do other work while it runs.
A batch also makes your checks even. Bills done one by one on tired days get tired checks. Bills done in one run get the same steps, in the same order, with the same care. If you have not yet done a single convert, learn that craft first in our guide on how to convert an invoice PDF to Excel — a batch is that same craft, run at scale.
There is a mind shift in it too. One-by-one work feels like help: each bill is a small favor you do the books. Batch work feels like a system: the month has a shape, a day, and an end. Systems beat favors at scale, since a system does not depend on your mood or your week. When the pile is a system, a staff change or a sick day does not stop it — the next person runs the same steps.
Sort the pile before you start
Five minutes of sorting saves an hour of hunting later. Before you upload a thing:
- Put the month's bills in one folder. Bills left in email or on a desk are bills that miss the run.
- Name each file with the vendor and the bill number, like “acme-1042.pdf”. Names you can read make the check fast.
- Pull out any bill you have already paid or already converted. A batch will not know it is a twin.
- Mark the scans. A file name that starts with “scan-” tells you which sheets will need the closer row check.
- Note the odd ones: credit notes, part bills, and bills in a second currency. Set them at the end of the run, where you can give them their own care.
That is the whole prep. It feels slow the first time. By the third month it is a reflex, and the reflex is worth more than the run itself: a sorted pile is half checked before the tool starts.
Sort with the check in mind. Put the bills you most doubt at the top of the folder, not buried in the pack: the new vendor, the odd layout, the thick scan. Batch day then starts with the hard ones while your eyes are fresh, and the plain bills flow after. Order is a free form of care.
Run the batch
Upload the folder's files in one go and start the run. The tool works through the files in order. Text PDFs read fast. Scans take longer, since each page must be read as an image first. A mixed month of thirty bills is a good task to start and then leave: make tea, clear the inbox, come back to a set of sheets.
Each bill gets its own sheet, with its own totals check. The batch does not merge bills into one blob. That split is what makes the check sane: a flag on one bill points at one PDF, one sheet, one fix. Save the sheets in the same folder as the PDFs, with the same names. PDF and sheet side by side is the record.
Keep the run's order the same as the folder's order. If the sheets come out in the order you sorted — vendor by vendor, say — your sample check walks the same path your eyes walked in the sort. Small thing, real help: when sheet nine flags, you know just where its PDF sits, since you put it there an hour before.
One batch, timed
Here is a real shape of run, with the names changed. A small trade firm gets 26 bills in a month: 19 text PDFs, 5 scans, 2 photos from a site phone. The sort takes six minutes — one twin found and pulled, the scans marked, one credit note set at the end. The upload takes a minute. The run itself takes a while for the scans, but no one waits on it; it runs while the mail gets read.
The check takes twelve minutes. Three bills are flagged: one scan lost a row (found, fixed in the sheet), one text bill has a fee line at its foot (real, added), one photo is too bent to trust (re-shot by the site tech the same day). The top three bills by size all pass. Four random bills pass. The note goes in the folder: “26 bills, 3 flags, all closed.”
Total hands-on time: about twenty minutes, for a month of bills, checked. The old way — one by one, typed and checked — ran this firm most of a day, and the checks still slipped when the day got long. Your counts will differ. Your shape will not: sort, run, sample, note. Four verbs, one short slot in the month.
Check the batch by sample
You do not need to read every row of every bill. You need a check plan that catches the real risks. Work in this order:
| What to check | How many | Why |
|---|---|---|
| Bills the tool flagged | All of them | A gap means a row or a digit needs you |
| The biggest bills | Top three by total | Where the money risk sits |
| A random sample | Three to five | A fair test of the whole run |
| All scans | Rows only, with care | Rows are the weak part of a scan read |
When a sample bill fails, widen the net. If one scan lost rows, check the other scans from the same source. If one vendor's bills all flag, look at that vendor's layout — it may print rows in a way that needs a closer look. The craft of the row check itself is in our guide on how to get line items out of an invoice PDF.
Keep a one-line note per batch: the date, the count of bills, the flags, and what you did about them. That note is dull gold. Three months of notes show you which vendors send hard bills, which scans read clean, and how long the job takes. You plan next month from facts, not from dread.
If the flags cluster — say, half the batch flags — stop and think before you fix sheet after sheet. A cluster has one cause most of the time: a new bill layout from a big vendor, a bad scan source, or a sort flaw that let last month's bills in. Fix the cause once and the cluster clears. Fix each flag one by one and you do the same work ten times, and learn nothing for next month.
Know your pages
Plans count pages, not bills. A month of short bills is a light month. A month with a few thick packs is a heavy one. Count your pages before you pick a plan:
| Plan | Pages a month | Fits |
|---|---|---|
| Free | 10 pages | A first test, or a few bills |
| Starter | 100 pages | A small team's month |
| Pro | 500 pages | Busy teams and thick packs |
If a month runs hot — a big project lands, say — the pages you need most are the flagged and the big ones. Convert those first. The rest can wait for the new month if they must. For the plans in full, see the pricing plans.
Thick files are the page eaters. One 20-page pack counts as 20 pages, not one bill. If your pile has a few of those each month, count them first when you plan. A month that looks like 30 bills can be 200 pages. The count takes a minute in the folder view, and it stops the rude shock of a cap hit mid-run.
Batch mistakes that cost time
- Running the same month twice. Mark a batch as done the moment it is done, or the twin bills will find you at pay time.
- Mixing months in one folder. A bill from last month in this month's run will land in the wrong books.
- Checking nothing because the run “looked fine”. The sample check is ten minutes. Skip it and you pay for it at month end.
- Saving sheets with tool names like “output-1.xlsx”. A name you can not read is a sheet you can not find.
- Letting the pile grow for a quarter. A month is a batch. A quarter is a project. Run monthly and the job stays small.
Each of these is a habit flaw, not a tool flaw. The run is the easy part. The craft is the sort before and the check after — and that craft is short, fixed, and quick to learn.
One more, the worst of the set: no slot at all. A batch with no set day drifts to the worst day — the last day of the month, when the books must close and time is short. Short time makes short checks, and short checks are how gaps get through. Pick the day while you are calm — the first work day of the new month, say — and guard it. Batch day held is month end saved.
Your next step
Take last month's bills — the whole pile — and run them as one batch. Sort first, check by sample, note the flags. Then set the same day each month as batch day. If you want the case for why this beats typing in full, read why typing invoices by hand costs you money.
The first batch teaches you your pile: which vendors send clean text, which send scans, where the flags cluster. Each batch after that is shorter. By the third, batch day is just a slot in the month — and a short one.
Write batch day on the shared calendar, with the folder path in the note. Then the habit does not live in one head. Whoever is in that day can run it: sort, run, sample, note. A system any of the team can run is a system that survives holidays, sick days, and growth — which is the whole point of a batch.
Sources and further reading
- Import bills and credit notes — Xero's guide to bringing many bills in from one file — the natural next step once a batch of sheets is ready.
- Common questions about importing data to QuickBooks Online — Intuit on file size and row caps for imports, which is why this guide keeps batches in small, checked lots.