Skip to main content
Skip to content
FREE TOOL — BROWSER-BASED

Convert Bank CSV to Sage Format Instantly

Bank CSV not importing into Sage? Reformat to Sage's 3-column or 4-column structure. Works with Sage 50, Sage Business Cloud, and Sage Intacct.

100% PrivateInstant3-Col & 4-Col

FAQ

Convert to
Sage
Questions

Can't find what you're looking for? Reach out to our support team.

Contact Support

It converts bank statement files from multiple formats — QBO, OFX, QFX, IIF, QIF, CSV, MT940, CAMT.053, and XLSX — into a Sage Accounting-compatible CSV file that you can import directly into Sage 50, Sage Business Cloud, or Sage Intacct via their bank statement import feature.

Why Your Bank CSV Won't Import Into Sage

CSV is the most common bank export format, but there is no universal CSV standard. Every bank uses its own column layout, date format, and amount conventions. Sage Accounting expects a very specific CSV structure for bank statement imports — either a 3-column format (Date, Description, Amount) or a 4-column format (Date, Description, Money In, Money Out). If your bank CSV has extra columns, different headers, or an incompatible date format, Sage will reject the import or misinterpret the data.

PrimeConnect's free CSV to Sage converter fixes this problem. Upload your bank CSV and the tool lets you map your bank's specific columns to Sage's expected structure. It handles date reformatting, amount sign conventions, extra column removal, header standardization, and CSV escaping — all the details that cause import failures when done manually. Everything runs in your browser with zero server involvement, keeping your financial data 100% private.

Sage CSV Import Format Requirements

Understanding Sage's exact CSV requirements is critical for successful imports. Here are the two supported layouts:

3-Column Format (Date, Description, Amount)

The simplest and most widely supported format across all Sage editions:

  • Column 1: Date — Transaction date in a consistent format. Sage supports DD/MM/YYYY, MM/DD/YYYY, and YYYY-MM-DD. You must use the same format for every row and confirm it during the Sage import wizard.
  • Column 2: Description — Transaction description or payee name. Quoted if it contains commas.
  • Column 3: Amount — Signed numeric value. Positive numbers represent money in (deposits), negative numbers represent money out (payments). No currency symbols, no thousands separators.

4-Column Format (Date, Description, Money In, Money Out)

The alternative format preferred by many users because it eliminates ambiguity around positive/negative amounts:

  • Column 1: Date — Same as 3-column format.
  • Column 2: Description — Same as 3-column format.
  • Column 3: Money In — Deposit amount. Empty for payments.
  • Column 4: Money Out — Payment amount (positive value). Empty for deposits.

Both formats require a header row as the first line of the CSV file. Our converter always includes the correct header row for your chosen format.

Common Bank CSV Layouts vs Sage Requirements

Here are some typical mismatches between bank CSV exports and what Sage expects:

  • Extra columns — Most bank CSVs include columns like Account Number, Transaction Type, Check Number, Running Balance, Category, and Reference. Sage only wants Date, Description, and Amount. Our converter strips all extra columns automatically.
  • Date format variations — Banks may use M/D/YY, YYYY-MM-DD, DD-Mon-YYYY (e.g., 15-Jan-2024), or other non-standard formats. The converter normalizes all dates to your chosen Sage-compatible format.
  • Separate debit/credit columns — Some banks split amounts into separate “Debit” and “Credit” columns instead of a single signed amount. The converter can map these to either Sage's 3-column (combined signed amount) or 4-column (Money In / Money Out) format.
  • Currency symbols and formatting — Bank CSVs often include dollar signs ($), pound signs, euro symbols, commas as thousands separators, or parentheses for negative values. Sage needs plain numbers. The converter strips all formatting automatically.
  • Summary/total rows — Some banks include summary lines, opening balance rows, or totals at the end of the CSV. These must be removed before Sage import. The converter's preview table lets you verify no junk rows are included.

Configuring the Right Date Format for Sage

Date format mismatches are the single most common cause of Sage CSV import failures. Here is how to avoid them:

  1. Check your Sage regional settings — In Sage Business Cloud, go to Settings → Financial Settings → Regional to see your configured date format. In Sage 50, check Tools → Settings → Company Preferences.
  2. Select the matching format in the converter — Choose DD/MM/YYYY for UK/EU Sage installations, MM/DD/YYYY for US, or YYYY-MM-DD for ISO format.
  3. Confirm during Sage import — Sage displays a date format confirmation dialog during CSV upload. Make sure the format shown matches what you selected in the converter.

If dates appear swapped after import (e.g., January 3 showing as March 1), the date format was mismatched. Re-convert the file with the correct format and re-import.

Tips for Successful Sage CSV Import

  • Import in date order — Sage processes transactions sequentially. Importing files in chronological order ensures running balances are calculated correctly.
  • Avoid overlapping date ranges — If you import multiple CSV files, ensure their date ranges do not overlap. Use our Duplicate Transaction Detector to check for duplicates before importing.
  • Clean your bank CSV first — If your bank CSV has merged cells, embedded headers, or other formatting issues, use our Bank CSV Cleaner before converting to Sage format.
  • Test with a small file first — Before importing a full year of transactions, test with a single month to verify the date format, amount signs, and description mapping are all correct in Sage.

Related Free Accounting Tools

The CSV to Sage converter is part of PrimeConnect's complete suite of free financial file conversion and utility tools: