Statements and transaction imports
Prepare CSV and bank exports, extract statements, resolve duplicate rows, and recover interrupted imports.
Articles
120 articles in statements and transaction imports
Choose a statement import or a transaction export import
Use the intake that matches your file before mapping or extraction.
Updated 2026-11-11
Prepare an import for one legal company
Keep source files and financial accounts scoped to the right company.
Updated 2026-11-11
Add a manual source account from the import picker
Create the destination for a statement when no bank connection is available.
Updated 2026-11-11
Leave an unknown source opening balance blank
Avoid recording an unsupported zero when preparing a manual account.
Updated 2026-11-11
Understand why an existing source account’s currency is read only
Use a reviewed source change when currency identity needs correction.
Updated 2026-11-11
Distinguish a source account from its ledger account
Understand the two account identities involved in imported bank activity.
Updated 2026-11-11
Select a connected bank account in an import
Let the picker prepare an eligible connected account before reading rows.
Updated 2026-11-11
Use saved accounts when connected accounts cannot be loaded
Recognize the picker’s partial availability message.
Updated 2026-11-11
Check a source account whose type cannot be changed
Review its ledger mapping before changing the account type.
Updated 2026-11-11
Name bank import files so their source period is clear
Keep separate account and period imports identifiable in history.
Updated 2026-11-11
Prepare the required CSV transaction columns
Provide a date, description and usable amount for every transaction row.
Updated 2026-11-11
Map a CSV with one signed amount column
Set cash direction correctly for a single amount field.
Updated 2026-11-11
Map separate money-in and money-out columns
Use the split-column layout without treating both fields as signed amounts.
Updated 2026-11-11
Fix reversed directions in a card transaction export
Check the positive-is-out convention before changing individual card amounts.
Updated 2026-11-11
Set First line is column names correctly
Prevent a header from becoming a transaction or a real transaction from being skipped.
Updated 2026-11-11
Keep commas inside transaction descriptions intact
Use properly quoted CSV fields so a merchant description stays in one column.
Updated 2026-11-11
Read a semicolon-separated bank export
Choose Semicolon when the columns do not split correctly.
Updated 2026-11-11
Import tab-separated spreadsheet rows
Check pasted columns using the Tab separator.
Updated 2026-11-11
Read a pipe-delimited transaction file
Use Pipe when vertical bars separate the source fields.
Updated 2026-11-11
Fix a preview that places each row in one column
Choose the correct delimiter before remapping the fields.
Updated 2026-11-11
Resolve an ambiguous day and month in an import
Choose the date convention from source evidence when both interpretations are possible.
Updated 2026-11-11
Prepare unambiguous ISO dates for transaction imports
Use YYYY-MM-DD when preparing a working CSV.
Updated 2026-11-11
Fix Date does not match the selected format
Check the mapped date column and date convention before editing source rows.
Updated 2026-11-11
Handle a transaction row with no date
Resolve missing source dates before the row can be imported.
Updated 2026-11-11
Check two-digit years before importing
Prefer full years when a bank export could be misread.
Updated 2026-11-11
Correct an impossible calendar date in an export
Use the bank source to resolve invalid dates such as a nonexistent day of the month.
Updated 2026-11-11
Convert spreadsheet serial dates before CSV import
Replace numeric date codes with verified calendar dates in a working export.
Updated 2026-11-11
Prepare dates that use written month names
Convert unsupported text dates to a consistent verified calendar format.
Updated 2026-11-11
Choose the intended date column in a bank export
Check which source date should define the imported movement.
Updated 2026-11-11
Set an optional start date for a transaction import
Hold earlier activity back while preserving its row-level reason.
Updated 2026-11-11
Still stuck?
Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.