Batch parse invoices and receipts: a monthly workflow for solo consultants

The monthly ritual: folder, parse, download, archive

Put a date on the calendar. The first weekday after the month ends is enough. The job is the same every time, which is why it survives a busy week.

• During the month, drop invoice PDFs and receipt photos into one folder. Email attachments and the camera roll both count.
• On close day, upload that folder as one batch.
• Download the CSV. Skim the rows. Fix categories that are wrong.
• Move the originals into an archive folder named for the month, next to a copy of the CSV.

“Monthly invoice folder to spreadsheet” is that sequence. A consultant expense CSV is the file at the end of it. Opening each PDF in a chat window is the sequence this replaces.

Name source files so source_file stays useful

The source_file column stores the name you uploaded. If the camera called it IMG_4402, that is what the spreadsheet will say, and future you will not know which lunch it was. Rename before the batch.

Vendor and date is enough: 2026-03-03-figma.pdf, 2026-03-12-northwind-lunch.jpg. You are not building a filing system. You are making the breadcrumb readable when a row looks wrong in June.

Review categories in minutes, not a typing session

The slow part of expenses used to be the typing. After a batch, the slow part should be a pass over the category column. Software, hosting, travel, meals, contractor — change the ones that are wrong, leave the rest. Ten minutes is a realistic skim of a solo month. Two hours is what retyping the same month costs.

Notes are the same pass. If a row will be obvious later, leave it. If it will not — a meal, a reimbursable client cost — write the note now. You are editing a sheet, not reconstructing one.

Currency checks for international work

Consultants get paid and spend in more than one currency. Before you archive the CSV, sort or filter the currency column. Every row should have a currency. Amounts should be plain numbers. A total only means something inside one currency.

Do not “fix” a mixed file by deleting the currency and summing the amount column. Add a home-currency column in the sheet later if you need one total, and keep the original amount beside it. The Sheets guide covers that import without breaking the columns you just checked.

Keep the schema identical from January through December

The header row does not get a redesign in July because a new tool seemed smarter. These columns stay the columns: date | vendor | amount | currency | category | notes | source_file. Same order. A pivot, a filter, and a SUMIF you wrote in February still describe December.

That lock is the point of a fixed-schema export. A generic PDF chat can describe an invoice. It will not promise you the same file shape on the twelfth run. The fixed-schema guide is the argument for keeping the header boring. ParseKit is the batch and the CSV, not a wrapper that pastes your folder into a conversation.

A checklist you can copy

Tape this to the month-end note. The order matters more than the tooling.

• Folder for the month contains every invoice PDF and receipt photo.
• Files are named so you would recognize them in source_file.
• One batch, not one upload per vendor.
• CSV downloaded. Categories and notes skimmed.
• Currency column checked before any total.
• Header row still matches last month.
• CSV and originals archived together.
• Sheet updated, or the file sent on — see the accountant handoff.

Where ParseKit sits in the ritual

ParseKit is the middle step: the folder goes in, the CSV comes out, with those seven columns. It does not store your archive, file your taxes, or run an accounts-payable desk. Freelancers and tiny agencies use it so the rest of the ritual stays short.

Free is 3 batches a month, no card — a solo close, plus a little room if a folder needs a second pass. Pro is $39/mo when the month is a shared drive and 8 files is not enough. Lemon Squeezy is the checkout when it is open. Until then, start free and run the ritual on a real folder.