Statements and transaction imports

Find a saved transaction import in Import history

Return to the existing batch to review or resume its recorded work.

Updated 2026-11-11

Start an import from copied spreadsheet rows

Read pasted transaction data without uploading a separate file.

Updated 2026-11-11

Import a bank export already saved in Documents

Reuse a saved source document while checking its account and period.

Updated 2026-11-11

Read one transaction export at a time

Keep each checked batch tied to one source account and file.

Updated 2026-11-11

Split a transaction export that exceeds 5 MB

Create smaller source periods while preserving complete transaction rows.

Updated 2026-11-11

Split an export with more than 5,000 transactions

Keep each transaction import within the checked row limit.

Updated 2026-11-11

Resume a transaction import that stopped partway through

Continue the saved batch while preserving rows already added.

Updated 2026-11-11

Read the finished import Results log

Confirm which source rows were added and why others were excluded.

Updated 2026-11-11

Discard an import before its rows are added

Keep the checked history while stopping an uncommitted batch.

Updated 2026-11-11

Roll back an import while preserving protected work

Understand why some imported rows may remain after rollback.

Updated 2026-11-11

Import a bank or card OFX or QFX file

Read a structured bank export and review its normalized transactions.

Updated 2026-11-11

Resolve an OFX export that belongs to another account

Match the file’s account identifier to the selected financial account.

Updated 2026-11-11

Resolve an OFX currency that does not match the account

Keep structured bank exports in their actual account currency.

Updated 2026-11-11

Split an OFX file that contains several accounts

Export each bank or card account separately for review.

Updated 2026-11-11

Replace an incomplete OFX or QFX export

Obtain a complete file when required statement or transaction structure is missing.

Updated 2026-11-11

Investigate repeated transaction references in OFX

Resolve duplicate FITID values before importing structured bank records.

Updated 2026-11-11

Handle an OFX file containing a bank correction

Resolve source corrections before importing ordinary transaction rows.

Updated 2026-11-11

Check an OFX export that contains no bank transactions

Confirm the exported period and account type before retrying.

Updated 2026-11-11

Understand the date used from an OFX bank transaction

Use the bank-reported posting date without a time-zone shift.

Updated 2026-11-11

Recover a bank export whose text encoding cannot be read

Obtain a valid text export instead of importing replacement characters.

Updated 2026-11-11

Check PDF statement size and page limits

Prepare a complete bank statement within the supported extraction limits.

Updated 2026-11-11

Prepare a statement PDF that can be opened

Use an unlocked original file for statement extraction.

Updated 2026-11-11

Choose a readable PDF statement source

Use selectable text or a clear scan with complete transaction details.

Updated 2026-11-11

Include opening and closing balance pages in a statement

Keep the evidence needed to check extracted movement totals.

Updated 2026-11-11

Separate statement files that contain several accounts

Keep account matching clear during extraction.

Updated 2026-11-11

Separate statements containing more than one currency

Keep extracted amounts tied to the correct account currency.

Updated 2026-11-11

Investigate a statement with missing pages

Restore complete source evidence before relying on extraction totals.

Updated 2026-11-11

Replace a scan with unreadable amounts

Use clear source evidence before accepting uncertain extracted numbers.

Updated 2026-11-11

Use an XLS or XLSX bank statement

Choose the statement workflow for spreadsheet statement files.

Updated 2026-11-11

Find a statement uploaded earlier

Use the statement list or Documents to reopen its extraction status.

Updated 2026-11-11