A structured transaction import is limited to 5,000 rows. Split a larger export into smaller account-period files before attempting to commit it.
- Choose a natural boundary, such as calendar month, that keeps every file below the limit.
- Preserve complete rows, required columns and the original date and amount values.
- Compare the combined parts with the original row count and source totals.
The file-size limit is separate. A file under 5 MB can still contain too many rows, while a file with fewer than 5,000 rows can be too large because of long text fields.
Check boundary transactions
Inspect the last date in one part and the first date in the next. If several transactions share the boundary date, ensure every movement appears in exactly the intended part.
Keep each saved batch identifiable in Import history. If an individual batch pauses, resume it before recreating the same period elsewhere. After all parts finish, compare imported, skipped and blocked totals with the full source so an omitted rejected row is not mistaken for a complete historical import.
Was this article helpful?
Tell us whether this answered the question you came with.