Normalize bank CSV files
Prepare existing CSV transactions directly for Bank CSV without PDF extraction or OCR.
Drop CSV or XLSX files here
One CSV shows a transaction preview. Multiple CSV/XLSX files form a batch with a file list, verified transaction counts and total credits. Successful exports can be downloaded together as a ZIP. MT940/CAMT.053 require account details and balances per file.
What data does the CSV need?
A transaction date and amount must be identifiable. Description/reference is recommended; separate debit and credit columns are supported.
- Date / booking date
- Amount or debit/credit
- Description / reference
Bank CSV
Prepare existing CSV transactions directly for Bank CSV without PDF extraction or OCR.
- Consistent transaction layout
- CSV source – no OCR
- Bank and payment data
Move directly from CSV to the target format
Export CSV from the bank, card or payment provider.
Upload the CSV and review the target profile.
Review the generated file before importing it.
Frequently asked questions
Does the CSV need one exact column layout?
A transaction date and amount must be identifiable. Description/reference is recommended; separate debit and credit columns are supported.
How is CSV to Bank CSV billed?
1–50 transactions = 1 credit, 51–100 = 2 credits, and so on. CSV input is billed by transaction count rather than PDF pages.