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
Avoid mapping a running balance as the transaction amount
Use the movement value rather than the account balance after each row.
Updated 2026-11-11
Resolve a row with both money in and money out
Check split-column mappings when two nonzero amounts appear on one row.
Updated 2026-11-11
Handle a zero-amount row in a transaction export
Separate nontransaction lines from real movements before importing.
Updated 2026-11-11
Read amounts shown in parentheses
Confirm the direction of parenthesized amounts in a signed-column export.
Updated 2026-11-11
Read a bank amount with a trailing minus sign
Check how the parser interprets a minus after the number.
Updated 2026-11-11
Check CR and DR suffixes on imported amounts
Review suffix direction and column meaning before accepting parsed values.
Updated 2026-11-11
Prepare decimal-comma amounts for the structured importer
Convert numeric representation without changing the underlying amounts.
Updated 2026-11-11
Handle an amount with more than two decimal places
Resolve source precision instead of silently rounding an import value.
Updated 2026-11-11
Resolve a currency symbol that conflicts with the selected account
Check account identity and amount markers before importing.
Updated 2026-11-11
Fix an amount with conflicting sign markers
Remove formatting ambiguity only after confirming the source direction.
Updated 2026-11-11
Repair a CSV field with a missing closing quote
Use the reported line to locate incomplete quoted text.
Updated 2026-11-11
Fix unexpected text after a closing CSV quote
Check delimiter and quoting when a field ends incorrectly.
Updated 2026-11-11
Keep a multiline description within one CSV transaction
Use quoted fields when a description contains a line break.
Updated 2026-11-11
Understand how blank lines affect imported row counts
Separate empty lines from informational rows that still contain text.
Updated 2026-11-11
Resolve a description longer than 500 characters
Check whether several fields or rows were combined into the description.
Updated 2026-11-11
Check a payee that exceeds the import field length
Preserve the vendor identity without placing a whole narrative in Payee.
Updated 2026-11-11
Resolve an oversized bank reference field
Check that Bank reference contains the transaction identifier.
Updated 2026-11-11
Use a three-letter currency code in CSV imports
Keep source currency explicit and consistent with the selected account.
Updated 2026-11-11
Review beyond the first ten preview rows
Use the next validation step to check every row in a larger import.
Updated 2026-11-11
Understand preview totals when some rows have problems
Compare valid-row totals separately from the full source totals.
Updated 2026-11-11
Understand Ready in checked import rows
Review an eligible row before committing it to Transactions.
Updated 2026-11-11
Understand Already imported in an import check
Avoid adding another copy of recognized source activity.
Updated 2026-11-11
Decide whether a possible duplicate should be imported
Compare source evidence when an existing row shares the date and amount.
Updated 2026-11-11
Keep two genuine purchases with the same date and amount
Use receipts and bank references to distinguish repeated-looking movements.
Updated 2026-11-11
Skip a valid row you do not intend to import
Exclude a ready row through the batch decision without altering its source values.
Updated 2026-11-11
Use Skip all for a reviewed set of possible duplicates
Apply a broad exclusion only when every candidate represents existing activity.
Updated 2026-11-11
Use Import all only for distinct source movements
Review every possible duplicate before applying a broad inclusion decision.
Updated 2026-11-11
Recover an import decision that was not confirmed
Reload the same saved import before repeating an uncertain decision.
Updated 2026-11-11
Review rows marked Before start date
Check the intended boundary instead of changing genuine transaction dates.
Updated 2026-11-11
Handle source rows marked Closed period
Respect locked accounting history while reviewing an import.
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.