Import Format Specifications by Software
Each accounting platform uses a different column format, date standard, and encoding for bank statement imports. Using the wrong spec causes the entire import to fail or worse — silently import with wrong data.
QuickBooks Online
Xero
Sage 50
MYOB AccountRight
Wave Accounting
Zoho Books
How to Import Bank Statements into QuickBooks Online
QuickBooks Online's bank transaction import has changed significantly in 2024-2025. Here are the exact steps using either QBO format (recommended) or CSV.
| Step | QBO Format (Direct) | CSV Format (Manual) |
|---|---|---|
| 1. Navigate | Banking → Upload Transactions | Banking → Upload Transactions |
| 2. Select file | Choose .qbo file | Choose .csv file |
| 3. Select account | Auto-matched from header | Manually select bank account |
| 4. Map columns | Skipped automatically | Map Date, Description, Amount |
| 5. Set date format | Auto-detected | Select MM/DD/YYYY manually |
| 6. Review & import | Review transactions → Import | Review transactions → Import |
| 7. Categorize | AI suggestions pre-applied | Manual categorization required |
| Time required | 2–3 minutes | 10–20 minutes |
5 Most Common Import Errors (and Exact Fixes)
Import failures follow predictable patterns. These are the five errors accountants encounter most often, and the precise fix for each.
Error: "Date format not recognized"
Cause: Your CSV has DD/MM/YYYY but the software expects MM/DD/YYYY (or vice versa).
Fix: Zera Books auto-detects and standardizes date format to match your target software's requirement. No manual reformatting.
Error: "Duplicate transactions already exist"
Cause: The date range overlaps with transactions already imported in a previous session.
Fix: Zera Books duplicate detection flags transactions that already exist in your account before import. Filter to new-only transactions.
Error: "Invalid amount format"
Cause: Amounts have currency symbols ($, £), comma separators (1,234.56), or parentheses for negatives (1,234.56).
Fix: Zera Books strips all formatting and converts to plain decimal (1234.56) in every export.
Error: "Account not found"
Cause: QBO file header references an account number not in QuickBooks.
Fix: Zera Books generates QBO headers that match your connected QuickBooks account. The account number is pulled from your QBO OAuth connection.
Error: "File encoding error"
Cause: The CSV was saved in UTF-16 or ANSI but the software expects UTF-8 (or vice versa), causing special characters to display as garbage.
Fix: Zera Books exports in the correct encoding for each target software automatically.
Import-Ready Files for Every Accounting Platform
Zera Books generates import-ready files for every major accounting software. Zero format errors, zero manual column mapping.
Try for one week →Xero Bank Statement Import: Complete Guide
Xero's import process differs from QuickBooks in a few important ways. Xero uses a bank feed model — imported transactions go into the bank feed for matching, not directly to the ledger.
| Xero Import Column | Required? | Format | Notes |
|---|---|---|---|
Date | Required | DD/MM/YYYY | Xero accepts multiple formats but DD/MM/YYYY is safest |
Amount | Required | Decimal (-100.00) | Negative = money out (debit), positive = money in (credit) |
Payee | Optional | Text | Appears as contact in Xero — useful for matching |
Description | Optional | Text | Bank transaction description |
Reference | Optional | Text | Check number or payment reference |
Balance | Optional | Decimal | Running balance — Xero uses this to verify no missing transactions |