How to Format Wise CSV Exports for Xero Import
Bookkeepers and accountants often receive bank statements from Wise as CSV files, but Xero’s bank‑feeds import tool expects a very specific layout. If the columns, dates, or amounts are not arranged exactly as Xero requires, the upload will be rejected and the reconciliation process stalls. This article walks through the steps needed to format wise csv for xero import so the file passes Xero’s validation without manual trial and error.
---
Why Xero’s CSV Import Has Strict Requirements
Xero’s import wizard reads a CSV file line by line and maps each column to an internal transaction field. The platform only accepts the following columns, in this order:
DD/MM/YYYY (or the locale you have set in Xero). If any column is missing, extra columns are present, or the date format does not match Xero’s expectation, the upload will fail with an error such as “Invalid date format” or “Column mismatch”. Understanding these constraints up front saves time and reduces the need for repeated uploads.
---
Step‑by‑step Guide to Format Wise CSV for Xero Import
1. Export the CSV from Wise
When you download a statement from Wise, the default CSV typically contains:
| Transaction ID | Date | Description | Amount (GBP) | Amount (EUR) | Balance | … |
The column names and order vary depending on the account type and the date range you select. Most importantly, Wise provides separate columns for each currency and includes a running balance column that Xero does not use. Keep the raw export unchanged for a moment; you will need it as the source data for the transformation.
2. Create a Working Copy and Remove Unneeded Columns
Open the CSV in a spreadsheet program (Excel, Google Sheets, or LibreOffice Calc). Delete any columns that Xero will ignore:
* Transaction ID – Xero generates its own reference.
* Balance – not needed for import.
* Currency‑specific amount columns – you should consolidate to a single Amount column in the base currency you plan to import (usually the primary currency of the Xero organization).
After removal, you should have at least these columns left: Date, Description, Amount, Payee. If a Payee column does not exist, you can create it and copy the relevant text from the description or a separate “Recipient” column.
3. Standardise the Date Format
Wise often exports dates in YYYY-MM-DD or DD MMM YYYY format. Xero expects DD/MM/YYYY. To convert:
`excel
=TEXT(A2,"dd/mm/yyyy")
`
Replace A2 with the cell that holds the original date.
Now every row displays dates exactly as Xero expects.
4. Consolidate Amounts and Apply Correct Sign
Wise lists amounts as positive numbers and indicates debit or credit with a separate “Type” column (e.g., Debit or Credit). Xero requires a single Amount column where debits are negative.
`excel
=IF(C2="Debit", -D2, D2)
`
Here C2 holds the transaction type, and D2 holds the absolute amount.
The amount column now contains signed numbers ready for Xero.
5. Arrange Columns in Xero’s Required Order
Select the entire sheet and reorder the columns to match Xero’s import template:
Delete any leftover empty columns. Save the file as CSV UTF‑8 (Comma delimited) to preserve special characters.
6. Run a Quick Validation Before Upload
Even after careful reformatting, small issues such as stray commas, hidden characters, or duplicate rows can cause Xero to reject the file. Perform these checks:
* Comma safety – Ensure no field contains an unescaped comma. If a description contains a comma, enclose the entire field in double quotes.
* Duplicate detection – Xero will import duplicate transactions unless you filter them out. Sort by Date and Amount, then remove any rows that appear identical.
* Numeric consistency – Verify that the Amount column contains only numbers and a leading minus sign for debits.
If you have a large file (hundreds or thousands of rows), manual checks become time‑consuming. This is where an automated file‑health tool can help.
---
Validate the Format Wise CSV for Xero Import with a Health Check
A dedicated file‑repair service can automatically perform the steps above and flag any remaining problems. The tool offered at the Korrali Data platform specializes in converting, validating, and repairing business files for accounting systems, including Xero. Its features relevant to the format wise csv for xero import workflow are:
* CSV health checks – scans the file for malformed rows, missing required columns, and incorrect date formats.
* Duplicate‑row finding – highlights exact matches on date, amount, and description so you can decide which rows to keep.
* Platform‑specific fixers – applies Xero‑specific column ordering, date reformatting, and amount sign adjustments with a single click.
You can upload your Wise CSV, let the service run a preview, and see a side‑by‑side comparison of the original and the corrected version. If the preview meets your expectations, you can finalize the conversion and download the Xero‑ready CSV. The service works on a per‑file pay‑as‑you‑go basis or through a monthly plan for frequent users, and it offers a free preview so you can verify the outcome before committing.
---
Common Pitfalls and How to Avoid Them
Incorrect Locale Settings
If your Xero organization is set to a locale that uses a different date separator (e.g., MM-DD-YYYY), the same CSV that works for a UK‑based organization will be rejected. Always check Xero’s Organisation Settings → General Settings → Locale before finalising the date format.
Hidden Characters from Export
Wise sometimes embeds non‑printing characters (e.g., zero‑width spaces) in the description field. These characters survive the CSV export and can break the import. Open the CSV in a plain‑text editor (Notepad++ or VS Code) and use the “Show All Characters” view to locate and delete them, or rely on the Korrali health‑check to clean them automatically.
Multi‑Currency Transactions
If your Wise statement contains transactions in several currencies, Xero expects each import file to be in a single currency. Split the CSV into separate files per currency, convert each amount to the base currency, or use Xero’s multi‑currency bank feed for direct integration. Attempting to import a mixed‑currency file will cause “Invalid amount” errors.
---
Automating Repeated Imports
For businesses that receive Wise statements weekly or monthly, manual reformatting becomes a bottleneck. Consider building a simple macro or using a script (Python’s pandas library works well) that performs the column removal, date conversion, amount sign adjustment, and reordering automatically. The script can read the raw Wise CSV, apply the transformation logic, and write the Xero‑compatible file in one step.
When you combine a custom script with the Korrali Data health‑check, you get both speed and confidence: the script handles routine restructuring, while the health‑check catches edge‑case errors that a script might miss, such as unexpected extra columns or hidden characters introduced by a new Wise export template.
---
Conclusion
Getting a Wise statement into Xero requires a disciplined approach: export the raw CSV, strip unnecessary columns, reformat dates to DD/MM/YYYY, apply correct sign to amounts, arrange columns in Xero’s prescribed order, and run a final validation. By following the steps outlined above, you can reliably format wise csv for xero import and avoid the frustrating upload errors that disrupt bookkeeping workflows.
If you prefer an automated solution that handles conversion, validation, duplicate detection, and platform‑specific fixes in one place, try the free preview at Korrali Data. Convert or check your file free at [data.korrali.com](https://data.korrali.com/tools/wise-to-xero).