Import bank statements into Sage Accounting UK

For Sage Accounting in the UK, import a bank CSV from the chosen account's Actions → Import statement menu, review the dates and amounts, then process the imported entries. Sage 50 Accounts has different bank-feed and audit-trail routes; do not treat them as interchangeable CSV uploads.

Check the account and import scope first

Sage's Accounting statement-import instructions cover gaps in a bank feed and historical transactions. They exclude foreign-currency bank statements and transactions before your Accounts Start Date. Check those conditions before preparing a file; changing a CSV date does not make an earlier transaction eligible.

Prefer a suitable bank-native download. When working from a PDF, first extract and verify the transaction data using the shared CSV preparation method. Keep the account, currency and statement period in your working notes, separate from transaction rows.

Use the Accounting statement template

The current UK format guide offers two clean layouts:

For a simple statement import, start with Sage's linked template and preserve its order. Use slash-separated dates, a nonempty single-line description and numeric amounts. Select the file's actual date order during import; Do not assume every source file uses the same day/month order.

Here is synthetic teaching data, not a bank record or an import-tested template. It represents two invented GBP current-account entries in March 2026, with day/month/year dates:

Date,Description,Amount
02/03/2026,Sample customer receipt,125.00
05/03/2026,Sample office payment,-18.50

These rows show incoming 125.00 and outgoing 18.50. If preparing the four-column layout, put 18.50 in Money out and leave Money in empty for that payment. Do not carry the negative sign from the three-column example into both amount columns.

LocalExtract's CSV headers are date,description,amount. Prepare a separate import copy using the destination template; it does not supply account references, nominal codes, tax decisions or missing counterparties automatically. Sage's file-size figures for other formats are not a verified CSV-wide limit.

Review the Accounting import before confirming

Follow the Accounting import procedure:

1. In Banking, open the intended account and choose Actions → Import statement.
2. Select or drop the file, then choose Review transactions.
3. Select the date format used by that file and continue.
4. Inspect the review and any errors, then choose Confirm import when the entries are correct.

Sage retains import settings and offers a later Import without review option. For a changed export layout, use Import settings and inspect the result instead of assuming the earlier mapping still fits.

If Sage reports File not imported, inspect the Reason column, correct a working copy and retry. Its statement-file troubleshooting includes line breaks in descriptions and unexpected blank rows or columns. Do not borrow contact-import limits or errors for this bank-statement task.

Process entries, then reconcile separately

Processing an imported statement is the next stage: Match connects to an existing record, Create adds a transaction when needed, and Transfer handles movement between bank accounts. Inspect existing entries and feed overlap before creating anything new.

The separate reconciliation workflow uses Banking → account → Reconcile and the actual statement date and closing balance. Confirm the appropriate entries and investigate any difference; do not manufacture a transaction merely to make a total balance. Use the import review sheet to record unresolved rows. It is a manual aid, not a Sage import file.

Which Sage 50 Accounts route do you need?

For UK Sage 50 Accounts v30.1 and above, Sage documents manual statement import through Bank Feeds. An automatic bank feed is not required for this manual-import setup:

In the wizard, continue to Upload your file → Select a file from your device, then choose Review transactions. If prompted, select the file’s actual date order. Check money-in/money-out direction and the reviewed rows before Confirm import. Do not use a type-switch option merely to hide an unexplained sign difference.

Confirmed entries appear in To be matched, ready to match with Sage transactions. This is staging for further work, not proof the ledger or statement reconciliation is complete. Check overlap with an existing feed before importing a missing period.

The Bank Feeds source lists supported file types, including CSV, but does not list PDF. Use its own format guidance rather than assuming a Sage Accounting CSV also fits Sage 50. The linked general Sage 50 import-format rules are broader data-import guidance; they do not establish that any three-column PDF extraction is a tested Bank Feeds template. The synthetic route comparison keeps the three Sage stages distinct and is not an import file.

The separate File → Import procedure can import audit-trail transactions, requiring accounting information such as transaction types and existing nominal codes. Follow Sage's backup and data-import instructions; this creates accounting data rather than merely staging statement lines. For that File → Import route, Sage requires other users to leave the relevant area and a backup before import; the import cannot simply be reversed, and recovery requires restoring a backup. Do not transfer those route-specific instructions to Bank Feeds as if the two processes were identical. Three extracted PDF fields are not a complete coded audit trail.

LocalExtract processes one PDF at a time locally, including OCR, and exports CSV. XLSX requires opening the CSV in Excel and saving a workbook. Uploading prepared rows to Sage is a separate online step; account and periodic Pro checks also require a network. Download and inspect your own PDF.

Official UK instructions checked October 16, 2026.

Correction, October 15, 2026: distinguished UK Accounting statement import from Sage 50 Accounts Bank Feeds (v30.1+) and audit-trail imports; revised date-format guidance.

Update, October 16, 2026: expanded both Sage 50 Bank Feeds entry points and clarified staging, format scope and audit-trail recovery limits.