The structured transaction-export workflow accepts files and pasted text up to 5 MB. If the source is larger, split it by a clear period such as month and import each part separately.
- Keep an unchanged copy of the full original export.
- Create smaller files containing complete transaction rows, one account and one currency per file. Preserve the appropriate header in each file.
- Check the boundary dates and total rows across the parts so no movement is lost or unintentionally repeated.
Do not split a quoted CSV field in the middle or divide an OFX transaction record manually. Prefer period-specific exports from the bank or a tool that preserves the format.
Track the finished batches
Use recognizable filenames and compare each batch’s results with its source period. Keep a list of any rejected or held rows that still need resolution.
A small file can still exceed the separate row limit, and an OFX conversion can become larger after its fields are normalized. Follow the displayed limit message for the current stage. Reducing filename length or changing the extension does not reduce the underlying source data that must be checked.
Was this article helpful?
Tell us whether this answered the question you came with.