Import bank statement transactions into Sage
Start with a native CSV, OFX, QBO, QFX, or other statement export from your bank when Sage supports it. Convert a PDF only when the native export is unavailable, then review every proposed transaction before import.
Last updated: August 29, 2026 · Import steps vary by product version
Need to convert a PDF first?
Document quality affects extraction. Digital PDFs are usually easier to process than scans, and password-protected files must be unlocked before upload.
Open the CSV converterA review-first workflow
- 1. Check your bank first. Download a native statement export that Sage accepts if one is available.
- 2. Convert only when necessary. If the bank provides only a PDF, extract dates, descriptions, debits, credits, and balances into a supported format.
- 3. Validate the output. Compare the date range, row count, signed amounts, and opening or closing totals with the source statement. Spot-check several rows.
- 4. Import into the correct account. Confirm the account, currency, column mapping, and date range in Sage before completing the import.
- 5. Reconcile and check duplicates. Look for overlap with feeds or earlier uploads before accepting the imported transactions.
Import into Sage
Open the bank transaction or statement-import area, choose the destination account, upload a format listed by your current Sage documentation, and review the proposed mapping. Product menus and supported formats can change, so confirm the workflow in Sage's official help before importing.
What to verify before import
Confirm the date format and the first and last transaction dates.
Check debit, credit, and signed-amount conventions.
Import into the matching account and currency.
Compare the date range with bank feeds and previous uploads.
Statement converters by bank
These retained bank pages use the same review-first workflow and link to the global export formats.