How to Import Credit Card Statements into Sage
Sage doesn't read credit card PDF statements directly. If your bank or credit card issuer sends you PDF statements — and most do — you need to convert them to CSV first, then import the CSV into Sage.
This guide walks through both steps: converting your PDF statement to CSV, and importing that CSV into Sage 50 and Sage Business Cloud (also called Sage Accounting). For a broader overview of the conversion step, see our credit card statement to Excel guide.
Why You Need to Convert First
Sage's bank import function accepts structured data files — CSV, OFX, or QIF. It cannot read PDF statements. PDFs are visual documents, not data files, even though they look like tables.
Your credit card issuer may offer a native CSV download through their online portal, which works well for recent transactions. But native downloads typically cover only the past 60-90 days, don't always match the official statement exactly, and aren't available for older statements.
If you're working with:
- Statements older than 90 days
- Multiple months of history
- PDF statements from a client
- Downloaded PDF statements that don't have a corresponding CSV export option
...then converting from PDF is the right approach.
Step 1: Convert Your PDF Statement to CSV
CreditCardToExcel extracts transactions from credit card PDF statements and outputs a clean, structured CSV file with one row per transaction.
Download Your PDF Statement
Log in to your credit card issuer's website and download the PDF statement for the period you want to import. Most issuers archive statements for at least 12 months; many go back 24 months.
If you're working with multiple months, download all the PDFs before starting the conversion step.
Upload to CreditCardToExcel
Go to creditcardtoexcel.com and upload your PDF. The tool works with statements from all major US and UK issuers — Chase, American Express, Citi, Bank of America, Barclays, Capital One, Discover, and others.
On the Pro and Business plans, you can upload multiple PDFs at once for batch conversion.
Review the Extracted Transactions
After processing, your transactions appear in a preview table. Check the dates, merchant names, and amounts against your PDF statement. This takes about 30 seconds and catches any extraction issues before they get into your books.
Download as CSV
Click download and select CSV. Save the file somewhere you can find it — you'll upload it to Sage in the next step.
Step 2: Import into Sage 50
Sage 50 (formerly Sage 50cloud Accounting or Peachtree) uses a specific import format. The process differs slightly between versions, but the core steps are the same.
Prepare Your CSV for Sage 50
Sage 50 requires a specific column order for bank/credit card imports. Before importing, open your CSV in Excel and verify or rearrange the columns to match what Sage 50 expects:
| Column | What Sage 50 Expects |
|---|---|
| A | Date (MM/DD/YYYY format) |
| B | Reference number (optional — can leave blank) |
| C | Payee / Description |
| D | Amount (negative for charges, positive for payments) |
The CSV exported from CreditCardToExcel already includes Date, Description, and Amount columns. You may need to:
- Reorder columns to match the table above
- Convert date format if your Sage 50 expects MM/DD/YYYY instead of YYYY-MM-DD
- Add an empty Reference column if required
To convert date format in Excel, select the date column, use Format Cells to change the display format, then copy-paste as values to a new column.
Import Steps in Sage 50
Go to File > Import/Export
In Sage 50, go to File in the top menu, then Import/Export.
Select Bank Transactions
From the import options, choose Bank Transactions or General Journal Entries depending on your Sage 50 version and how you want the transactions to post.
For direct bank/credit card reconciliation, Bank Transactions is the right choice.
Choose Your CSV File
Click Browse and select the CSV file you prepared. Sage 50 will show a preview of the mapped columns.
Map the Columns
Sage 50's import wizard will ask you to map the columns from your CSV to Sage's fields. Match:
- Your Date column → Transaction Date
- Your Description column → Description or Payee
- Your Amount column → Amount
Select the Account
Choose the credit card liability account you want the transactions to post to. If you haven't created a credit card account in Sage 50 yet, cancel, create the account in the chart of accounts, then return to import.
Review and Import
Sage 50 will show a summary of how many transactions will be imported and flag any rows it can't read. Review the summary, then click Import to complete.
After Import in Sage 50
Once imported, go to your credit card account in the chart of accounts and review the transactions. You'll need to categorize each transaction to the correct expense account (or Sage 50 can auto-categorize based on rules you set up for recurring merchants).
Run a reconciliation against your original statement to confirm the imported balance matches.
Step 3: Import into Sage Business Cloud (Sage Accounting)
Sage Business Cloud — now often called Sage Accounting — has a more flexible bank import interface than Sage 50. It accepts CSV directly and walks you through column mapping interactively.
Import Steps in Sage Accounting
Go to Banking
In Sage Accounting, click on Banking in the left navigation.
Select Your Credit Card Account
Click on the credit card account you want to import into. If you don't have a credit card account set up yet, click Connect a bank account and choose Import a bank statement — Sage will prompt you to create a new account during this process.
Click Import Statement
Inside the account view, click the Import statement button (or the three-dot menu and then Import).
Upload Your CSV
Choose your converted CSV file and click Upload. Sage Accounting will detect the file format and show a preview.
Map the Columns
Sage Accounting's column mapper lets you drag-and-drop or select which column in your CSV maps to Date, Description, and Amount. The mapper is forgiving — you don't need to pre-format the CSV as strictly as Sage 50.
Set the date format to match your CSV (YYYY-MM-DD or MM/DD/YYYY).
For credit card statements, amounts are typically all negative (charges) with positive entries for payments. Sage Accounting handles this correctly when you set the amount column type.
Review and Import
After mapping, Sage Accounting shows a preview of the transactions. Check a few rows against your original statement. Click Import when satisfied.
After Import in Sage Accounting
Imported transactions appear in your credit card account as unreconciled entries. Sage Accounting will try to auto-match transactions to existing rules or previously imported data. Review the matches, add transaction categories (expense accounts) where needed, and mark as reconciled when you've confirmed the balance matches your statement.
Handling Multiple Months
If you're catching up several months of credit card activity, converting and importing month by month is the most reliable approach. Here's why: if you merge multiple months into a single CSV before importing, duplicate-detection gets harder, and if there's an error, it's more difficult to identify which month is the problem.
The recommended workflow:
- Convert each month's PDF statement to its own CSV
- Import one CSV at a time into Sage
- Reconcile each month before moving to the next
On the Business plan at CreditCardToExcel, you can convert up to 20 files per batch — so the conversion step is fast even for a full year of statements.
Troubleshooting Common Import Issues
"Invalid date format" error
Sage is strict about date formats. If you get a date error, open your CSV in Excel, select the date column, and reformat it to match what Sage expects. Sage 50 typically wants MM/DD/YYYY. Sage Accounting is more flexible but may need YYYY-MM-DD.
Transactions imported with wrong signs (charges showing as credits)
This happens when the amount column sign convention in your CSV doesn't match what Sage expects. Open the CSV in Excel and multiply the amount column by -1 to flip all signs, then re-import.
Duplicate transactions after import
If you import the same CSV twice, Sage Accounting will usually detect duplicates and warn you. Sage 50 is less reliable at this — if you accidentally import a duplicate batch, you'll need to delete the duplicate transactions manually from the account register.
Missing transactions after import
If the imported transaction count is lower than expected, check whether the date range filter in Sage's import wizard excluded some transactions. Also verify the original CSV has the correct number of rows by checking the row count in Excel.
Related Guides
- How to import credit card statements into QuickBooks
- How to import credit card statements into Xero
- How to import credit card statements into FreshBooks
- How to import credit card statements into Wave
- Credit card statement to Excel for accountants
- Credit card reconciliation in small business
Frequently Asked Questions
Does Sage have a direct connection to my credit card account?
Sage Accounting does offer live bank feeds for some banks and credit card issuers. If your issuer is supported, the live feed will automatically pull recent transactions. However, live feeds typically only cover recent activity and don't support historical imports. For anything older than the feed's history, CSV import is the reliable option.
Can I import business and personal transactions into separate Sage accounts?
Yes. If you have a combined statement that includes both business and personal charges, convert the full statement to CSV first, then use Excel to filter out personal transactions before importing into Sage. Keep the original CSV as a record of what was filtered.
What's the difference between Sage 50 and Sage Business Cloud for this purpose?
Sage Business Cloud (Sage Accounting) has a more user-friendly import interface with visual column mapping. Sage 50 requires more manual preparation of the CSV but gives more control over how transactions post. For most small businesses and accountants, Sage Accounting's import process is faster and requires less pre-formatting.
How long does the conversion take?
Most statements convert in under 30 seconds. Longer statements with 100+ transactions may take a minute. Batch conversions of multiple files run in parallel.
Summary
Importing credit card transactions into Sage is a two-step process: convert the PDF statement to CSV, then import the CSV into Sage. The conversion step is the part that usually holds people up — and CreditCardToExcel handles it in under a minute, for statements from any major issuer.
The first five conversions are free. If you're an accountant or bookkeeper working with multiple clients, the Business plan handles up to 100 conversions per month with batch upload support.
Convert your first statement and have it in Sage in the next ten minutes.
Ready to stop manual data entry?
Convert your credit card statements to Excel in seconds. Free, no signup required.
Try CreditCardToExcel Free