XLSX → Xero bank statement (English CSV)
Prepare a five-column Xero English bank-statement CSV from your original Excel XLSX workbook, then import it manually.
Purpose
Upload your unchanged XLSX workbook, inspect the selected sheet and map real columns if needed. Choose a genuine BOOKING or VALUE date, confirm one account and matching ISO 4217 currencies, and review specific information losses. Java validates the original OOXML bytes before producing the Xero CSV.
Workflow fit
For a single-account, single-currency Excel bank statement that needs the Xero English-language five-column bank import profile.
Implementation note
Xero English profile only; up to 50,000 movements subject to channel limits. The browser cannot certify hidden rows/sheets, formulas, numeric account IDs altered by Excel, or ambiguous sheets. Java must validate or reject them. No FX, invented Payee/Reference, automatic Xero import, reconciliation or external import certification.
Xero bank statement EN · Date,Amount,Payee,Description,Reference
The original XLSX/OOXML File bytes are inspected and uploaded unchanged. Java produces a separate CSV with Date,Amount,Payee,Description,Reference, in that exact order, using yyyy/MM/dd dates.
The browser cannot certify those properties. Inspect and choose the source sheet; Java must reject ambiguous or unsafe workbooks instead of silently omitting hidden transactions or trusting calculated cells.
Excel may already have damaged numeric account identifiers. Neither the browser nor Java can invent lost digits, payees or transaction references. Check the source and keep unverified optional output fields empty if the writer permits it.
No. Only one real account and currency per file. Source and receiving ISO 4217 currencies must match. You manually import the resulting CSV into the correct Xero account and check duplicates; external acceptance is not verified.
The Xero profile supports at most 50,000 movements, subject to file size and paid limits. Trial is at most 10,000 movements and 10,000,000 input bytes if eligible; paid conversion uses at least one credit per started 10,000,000 input bytes.
Related converters
Explore other production-ready routes connected to this format.