Export / process
Bulk bank statement conversion: review before batch export
Upload bounded groups of PDFs, review and approve each document, then create a paid workspace batch for a combined CSV, XLSX, or OFX export before the earliest document expires.
Plan the handoff
Check eligibility before a batch export
Fictional batch planning example
| Statement | State | Next action |
|---|---|---|
| A | Approved | Check remaining access time |
| B | Draft | Review and approve first |
| C | Expired | Unavailable for export |
| D | Other workspace | Use the correct workspace |
Step by step.
Prepare a bounded set
Gather the complete PDFs and label their accounts and periods. An upload accepts up to 10 files, each at most 50 MiB and 250 pages.
Extract and review each statement
Check every draft against its source pages, correcting missing or duplicated rows and amount signs document by document.
Approve each saved revision
Have a person approve each document to be included; the batch export cannot use an unapproved draft.
Create a workspace batch
With an active paid entitlement, select 1 to 10 live documents owned by the active workspace for the batch.
Export before the earliest expiry
Choose CSV, XLSX, or OFX for the approved batch and download while all included documents remain available. A combined OFX requires every statement to belong to the same account.
Size the intake and keep periods identifiable
Bulk does not mean unlimited. An upload accepts at most 10 PDFs, and each file is limited to 50 MiB and 250 pages. Group documents deliberately so account and period boundaries stay identifiable during review and after export.
Text, scanned, mixed, and password-protected PDFs can enter the document flow. The extracted transactions are drafts, not a batch of automatically approved records; inspect each statement separately against its source pages.
Build the batch from eligible documents
The workspace batch workflow requires an active paid entitlement. Select 1 to 10 live document IDs owned by the active workspace. A document outside that workspace, or one that has expired, cannot be used as a shortcut into a combined export.
Review and approve the exact saved revision of every included document first. If one statement still contains a questionable row or missing page, address it in that document rather than relying on a combined file to hide the issue.
Respect the shared deadline and output choices
Private statement content expires 24 hours after presign. A batch takes the earliest expiry among its included documents, so adding a newer statement does not extend the older one. Allow time to finish every review, create the batch, and download before that shared deadline.
Batch export accepts CSV, XLSX, or OFX and uses approved documents only. Choose CSV for a flat table, XLSX for a workbook handoff, or OFX when several statements from one account should load into QuickBooks Online or Xero as a single file. Check account and period boundaries before importing the result elsewhere. This workflow does not automatically synchronize an accounting ledger.
Verify each statement before combining a batch
Keep a simple manifest of the source filename, account, currency, period, expected transaction count and closing balance. Review and approve each statement separately before creating a combined output. Compare the final row count with the sum of the approved inputs and investigate overlapping periods.
For OFX, combine statements only when they belong to the same account and currency; mixed-account output is rejected. The one-statement fictional sample is useful for inspecting fields, but it is not a multi-month batch test. Batch UI exports accept up to ten eligible statements, while the documented developer conversion endpoint accepts up to 100 unique IDs with paid entitlement when more than one ID is supplied.
Sample files and references
Questions about this guide
Can I export a batch while one statement is still a draft?
No. Batch export draws from approved documents only. Finish the source-linked review and approve that document before exporting the batch.
Is JSON available as a workspace batch export?
No. The workspace batch export offers CSV, XLSX, or OFX, even though other approved-document workflows can offer JSON.
Does a new document reset the batch lifetime?
No. The earliest expiry among included documents bounds the batch. Each document’s private content expires 24 hours after presign.