Question 1

Why do QuickBooks and Xero not detect that my dates are in the wrong format?

Accepted Answer

Both platforms validate that a date field contains a plausible date value — they do not validate whether the date represents the user's intended day and month. A date like 01/04/2026 is a valid date in both MM/DD/YYYY and DD/MM/YYYY interpretations. The platform picks the interpretation that matches its regional setting and posts the transaction without a warning. The only defense is pre-import date format verification.

Question 2

How do I tell if my EU bank export uses semicolons before trying to import it?

Accepted Answer

Open the CSV in a plain text editor (Notepad on Windows, TextEdit on Mac in plain text mode). If each row shows the fields separated by semicolons rather than commas, the file uses semicolon delimiters. German, French, Dutch, and Swiss bank exports from SEPA-standard institutions almost always use semicolons. You can also run the file through SplitForge Format Checker — it detects the delimiter automatically.

Question 3

What is the SEPA format and do I need to convert it for QuickBooks?

Accepted Answer

SEPA (Single Euro Payments Area) is the EU payment network for euro-denominated transfers. SEPA CSV exports from European banks typically use semicolon delimiters, DD.MM.YYYY dates, comma decimal separators, and ISO-8859-1 or UTF-8 encoding. Yes — all of these differences require conversion before importing into QuickBooks US or Xero US. The conversion steps are: (1) re-encode to UTF-8, (2) convert delimiter from semicolon to comma, (3) convert dates from DD.MM.YYYY to MM/DD/YYYY, (4) convert decimal separators from comma to period, (5) remove extra columns (Balance, IBAN).

Question 4

Does Xero accept DD/MM/YYYY dates automatically for UK or AU accounts?

Accepted Answer

Xero accepts DD/MM/YYYY dates when the organization's regional setting is configured for UK or Australia. Check your setting at Settings → Organisation → Financial Settings → Date format. If the setting shows MM/DD/YYYY (common if the organization was created by a US-based team), your UK or AU bank export will fail with a date format error even though the dates are in the correct local format. Either change the setting or convert the dates to match the current setting.

Question 5

Can I import Canadian bank exports directly into QuickBooks Online?

Accepted Answer

Most Canadian bank exports (RBC, TD, Scotiabank, BMO) export in ISO 8601 date format (YYYY-MM-DD), which QuickBooks Online does not accept. Convert YYYY-MM-DD dates to MM/DD/YYYY for QuickBooks US using SplitForge Data Cleaner before importing. Also check whether the Canadian export uses CAD Amount as the column header (needs renaming to Amount) and whether amounts include $ currency symbols (needs stripping).

Question 6

What happens to my bank data if I use a cloud-based format converter to fix international CSV issues?

Accepted Answer

Cloud-based format converters that require file upload — such as EasyBankConvert and DocuClipper — receive and store your bank statement data on their servers during processing. International bank exports contain IBAN account numbers, SWIFT codes, and counterparty names that qualify as personal data under GDPR Article 4(1). Uploading this data creates a GDPR Article 28 processor relationship. SplitForge processes your file entirely in your browser with no data transmitted — verifiable in Chrome DevTools Network tab.

Question 7

After converting my international bank CSV, which QuickBooks or Xero errors should I still expect?

Accepted Answer

After format conversion (date, delimiter, decimal, encoding), the remaining common failures are column header mismatches and extra columns. QuickBooks requires Date, Description, Amount (case-sensitive) and rejects any additional columns. Xero requires Date, Amount, Payee, Description, Reference. EU bank exports often include Balance, IBAN Reference, and Creditor/Debtor Name columns that must be removed. For a complete QuickBooks column mapping walkthrough after international format conversion, see the QuickBooks bank feed CSV column mapping guide.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Why do QuickBooks and Xero not detect that my dates are in the wrong format?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Both platforms validate that a date field contains a plausible date value — they do not validate whether the date represents the user's intended day and month. A date like 01/04/2026 is a valid date in both MM/DD/YYYY and DD/MM/YYYY interpretations. The platform picks the interpretation that matches its regional setting and posts the transaction without a warning. The only defense is pre-import date format verification."
      }
    },
    {
      "@type": "Question",
      "name": "How do I tell if my EU bank export uses semicolons before trying to import it?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Open the CSV in a plain text editor (Notepad on Windows, TextEdit on Mac in plain text mode). If each row shows the fields separated by semicolons rather than commas, the file uses semicolon delimiters. German, French, Dutch, and Swiss bank exports from SEPA-standard institutions almost always use semicolons. You can also run the file through SplitForge Format Checker at https://splitforge.app/tools/format-checker — it detects the delimiter automatically."
      }
    },
    {
      "@type": "Question",
      "name": "What is the SEPA format and do I need to convert it for QuickBooks?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "SEPA (Single Euro Payments Area) is the EU payment network for euro-denominated transfers. SEPA CSV exports from European banks typically use semicolon delimiters, DD.MM.YYYY dates, comma decimal separators, and ISO-8859-1 or UTF-8 encoding. All of these differences require conversion before importing into QuickBooks US or Xero US. The conversion steps are: re-encode to UTF-8, convert delimiter from semicolon to comma, convert dates from DD.MM.YYYY to MM/DD/YYYY, convert decimal separators from comma to period, and remove extra columns such as Balance and IBAN."
      }
    },
    {
      "@type": "Question",
      "name": "Does Xero accept DD/MM/YYYY dates automatically for UK or AU accounts?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Xero accepts DD/MM/YYYY dates when the organisation's regional setting is configured for UK or Australia. Check at Settings → Organisation → Financial Settings → Date format. If the setting shows MM/DD/YYYY, your UK or AU bank export will fail with a date format error even though the dates are in the correct local format. Either change the setting or convert the dates to match the current setting before importing."
      }
    },
    {
      "@type": "Question",
      "name": "Can I import Canadian bank exports directly into QuickBooks Online?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most Canadian bank exports (RBC, TD, Scotiabank, BMO) export in ISO 8601 date format (YYYY-MM-DD), which QuickBooks Online does not accept. Convert YYYY-MM-DD dates to MM/DD/YYYY for QuickBooks US using SplitForge Data Cleaner at https://splitforge.app/tools/data-cleaner before importing. Also check whether the Canadian export uses CAD Amount as the column header (needs renaming to Amount) and whether amounts include dollar currency symbols (needs stripping)."
      }
    },
    {
      "@type": "Question",
      "name": "What happens to my bank data if I use a cloud-based format converter to fix international CSV issues?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Cloud-based format converters that require file upload receive and store your bank statement data on their servers during processing. International bank exports contain IBAN account numbers, SWIFT codes, and counterparty names that qualify as personal data under GDPR Article 4(1). Uploading this data creates a GDPR Article 28 processor relationship. SplitForge processes your file entirely in your browser with no data transmitted — verifiable in Chrome DevTools Network tab."
      }
    },
    {
      "@type": "Question",
      "name": "After converting my international bank CSV, which QuickBooks or Xero errors should I still expect?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "After format conversion (date, delimiter, decimal, encoding), the remaining common failures are column header mismatches and extra columns. QuickBooks requires Date, Description, Amount (case-sensitive) and rejects additional columns. Xero requires Date, Amount, Payee, Description, Reference. EU bank exports often include Balance, IBAN Reference, and Creditor/Debtor Name columns that must be removed. For a complete QuickBooks column mapping walkthrough after international format conversion, see the QuickBooks bank feed CSV column mapping guide at https://splitforge.app/blog/quickbooks-bank-feed-csv-column-mapping."
      }
    }
  ]
}

Error / Symptom	Root Cause	Fix
Wrong month on imported transactions (no error)	DD/MM/YYYY date silently read as MM/DD/YYYY	Convert date format before import; verify platform regional setting
"This file contains errors" / import fails entirely	Semicolon-delimited EU export — platform expects comma	Convert delimiter from semicolon to comma
"Invalid amount" / amount field blank after import	Comma decimal separator (`1.250,00`) read as text	Convert to period-decimal format (`1250.00`)
Garbled description text after import	Non-ASCII characters (ä, ü, é) in Windows-1252 or ISO-8859-1 encoding	Re-encode to UTF-8; replace non-ASCII characters
"File could not be imported" / no further detail	ISO 8601 date (YYYY-MM-DD) from Canadian banks — platform expects MM/DD/YYYY	Convert YYYY-MM-DD to MM/DD/YYYY before import
Import appears successful but transaction count is wrong	Silent row drop for dates with day > 12 in MM/DD/YYYY context	Audit imported row count; re-import with correct date format
"File too large" / import freezes	QuickBooks ~350 KB / ~1,000 row limit exceeded on large international exports	Split file by date range using CSV Splitter

Platform	Regional setting	Required date format
QuickBooks US	United States	MM/DD/YYYY
QuickBooks UK	United Kingdom	DD/MM/YYYY
QuickBooks AU	Australia	DD/MM/YYYY
Xero AU/UK	Follows organisation setting	DD/MM/YYYY (default)
Xero US	Follows organisation setting	MM/DD/YYYY
NetSuite	Follows user locale	Depends on locale

Bank system	Region	Date format	Decimal sep	Thousands sep	Delimiter	Typical encoding
SEPA Credit Transfer	EU (DE/FR/NL/AT/BE)	DD.MM.YYYY	, (comma)	. (period)	; (semicolon)	ISO-8859-1 or UTF-8
BACS / Faster Payments	UK	DD/MM/YYYY	. (period)	, (comma)	, (comma)	UTF-8
OSKO / PayID / NPP	AU	DD/MM/YYYY	. (period)	, (comma)	, (comma)	UTF-8
Interac e-Transfer	CA	YYYY-MM-DD	. (period)	, (comma)	, (comma)	UTF-8
Most other EU banks	EU	DD/MM/YYYY	, (comma)	. (period)	; or ,	Windows-1252 or UTF-8

Bank system	QuickBooks US fix required	Xero US fix required	Xero AU fix required
SEPA (EU)	Date, delimiter, decimal, encoding	Date, delimiter, decimal	Delimiter, decimal, encoding
BACS (UK)	Date format only	None (if Xero AU)	None
OSKO (AU)	Date format only	Date format	None
Interac (CA)	Date format only	Date format	Date format

International Bank CSV: Fix Format Errors for QuickBooks and Xero

💡 Quick Answer

⏰ FAST FIX (90 seconds)

What International CSV Format Errors Actually Mean

📋 Table of Contents

Error 1: Date Format Mismatch

Error 2: Semicolon Delimiter

Error 3: Comma Decimal Separators

Error 4: Non-ASCII Characters in Transaction Descriptions

Error 5: ISO 8601 Dates from Canadian Bank Exports

International Format Reference Tables

Why International Bank CSV Data Should Never Leave Your Browser

Additional Resources

FAQ

Why do QuickBooks and Xero not detect that my dates are in the wrong format?

How do I tell if my EU bank export uses semicolons before trying to import it?

What is the SEPA format and do I need to convert it for QuickBooks?

Does Xero accept DD/MM/YYYY dates automatically for UK or AU accounts?

Can I import Canadian bank exports directly into QuickBooks Online?

What happens to my bank data if I use a cloud-based format converter to fix international CSV issues?

After converting my international bank CSV, which QuickBooks or Xero errors should I still expect?

Fix Your International Bank CSV Without Uploading It

💡 Quick Answer

⏰ FAST FIX (90 seconds)

What International CSV Format Errors Actually Mean

📋 Table of Contents

Error 1: Date Format Mismatch

Error 2: Semicolon Delimiter

Error 3: Comma Decimal Separators

Error 4: Non-ASCII Characters in Transaction Descriptions

Error 5: ISO 8601 Dates from Canadian Bank Exports

International Format Reference Tables

Why International Bank CSV Data Should Never Leave Your Browser

Additional Resources

FAQ

Why do QuickBooks and Xero not detect that my dates are in the wrong format?

How do I tell if my EU bank export uses semicolons before trying to import it?

What is the SEPA format and do I need to convert it for QuickBooks?

Does Xero accept DD/MM/YYYY dates automatically for UK or AU accounts?

Can I import Canadian bank exports directly into QuickBooks Online?

What happens to my bank data if I use a cloud-based format converter to fix international CSV issues?

After converting my international bank CSV, which QuickBooks or Xero errors should I still expect?

Fix Your International Bank CSV Without Uploading It

Continue Reading

Fix Accounting CSV Encoding Errors: UTF-8, Windows-1252, and BOM

Bank Statement CSV Formatting Guide for QuickBooks, Xero, and Wave

Fix Currency Symbols in Accounting CSV Files for QuickBooks and Xero