Bulk conversion
How to Organize Multi-Month Bank Statements Before Conversion
Build a complete, deduplicated statement inventory by entity, account, and month before running a bulk Excel or CSV conversion.
- For
- People preparing a quarter or year of statements for conversion
- Read
- 7 min
- Updated
TL;DR
- Inventory statements by entity, account, currency, and statement period before uploading anything.
- Use a consistent filename and a manifest that exposes missing or overlapping periods.
- Process one logical batch at a time and keep original PDFs, raw outputs, and reviewed files separate.
Create a statement inventory
Start with a manifest rather than a folder full of downloads. One row per statement should record entity, bank, masked account label, currency, period start, period end, filename, and readiness. Confirm every file meets the supported document conditions before marking it ready.
| Manifest field | Example | Purpose |
|---|---|---|
| Entity | North Shop LLC | Prevents client or company mixing |
| Account | Operating-4821 | Separates accounts without exposing a full number |
| Period | 2026-01-01 to 2026-01-31 | Reveals gaps and overlaps |
| Currency | USD | Prevents accidental mixed-currency totals |
| Status | Ready / missing / duplicate / blocked | Makes exceptions visible before conversion |
Use names that sort correctly
A useful pattern is entity-account-YYYY-MM-period-end.pdf. Put the year before the month, avoid generic names such as statement (12).pdf, and never put full account numbers in shared filenames. Keep bank downloads unchanged in an originals folder; rename a working copy if preserving the downloaded name matters.
- 01-original-pdfs: immutable source documents.
- 02-raw-conversions: untouched Excel or CSV downloads.
- 03-reviewed: corrected working copies and exception notes.
- 04-handoff: only the files the final recipient needs.
Resolve gaps, overlaps, and duplicates
- 1
Sort the manifest by account and start date
The next period should begin where the previous coverage ends.
- 2
Mark missing coverage
Do not substitute transaction exports for a missing statement without documenting the source difference.
- 3
Compare duplicate candidates
File size, period, account, and page count can identify repeat downloads.
- 4
Keep overlapping periods visible
Do not delete an overlap before checking how posted and pending transactions appear.
- 5
Freeze the final input list
Count files and record the batch name before upload so output completeness can be measured.
If your output will become one table, read when to merge statement results before dropping file boundaries.
Convert by logical batch, not maximum capacity
A useful batch has one owner and one review context. Twelve months for one account may be easier to control than every statement available. Use the bulk bank statement converter, then compare input count, success count, and failure count before moving the batch to reviewed status.
Limitations to keep visible
- A folder structure cannot recover a missing statement or make an unsupported layout convertible.
- The workflow assumes native PDF statements and excludes scanned or image-only files.
- Statement periods vary by bank and may not align with calendar months, so use printed start and end dates.
Put the workflow into practice
Upload a clean batch after completing the inventory below.
Convert the prepared statement set