How to Import Bank Statements into Sage Pastel

To import bank statements into Sage Pastel, open the relevant cash book, start Pastel Bank Manager and choose the Statement Provider that matches the file you have. Use a native bank export with its named provider, or a three-column Date, Description and Amount file with CSV (Bank Manager). Loading the file is only the first stage: review and allocate the transactions before creating and updating the cash book batches.

The Statement Provider is part of the import contract. It tells Bank Manager how to read that file's layout, not simply which bank holds the account. A native Standard Bank, FNB or Nedbank export may contain fields and control records that its named provider expects. Rearranging three columns from another source does not recreate that bank-specific format.

A CSV can therefore look correct in Excel and still fail in Pastel. The visible rows may be sensible while the selected provider expects a different column order, delimiter, date interpretation or record structure. Match the provider to the file first; troubleshoot individual values only after that pairing is correct.

This workflow applies to Sage 50cloud Pastel Bank Manager in South Africa. Sage Accounting, Sage 200 Evolution and other Sage products have different import contracts, covered in bank-statement import workflows for other Sage products.

Choose among a native export, generic CSV and PDF source

Start with the source that preserves the most reliable transaction data. The three routes are not interchangeable.

Source available	Preparation route	Pastel route
Native bank export supported by a named provider	Keep the downloaded structure intact	Select the matching Statement Provider
Generic transaction file	Prepare Date, Description and Amount in the documented order	Select CSV (Bank Manager)
PDF or image statement only	Extract the transactions, verify them against the statement and export a three-column CSV	Select CSV (Bank Manager)

Prefer a supported native export. It retains the structure the bank supplied and avoids reconstructing transactions from a presentation document. If the client needs help obtaining or converting the source, use the relevant bank guidance to prepare an FNB bank statement for Excel or CSV, convert a Standard Bank statement to Excel or CSV or convert a Nedbank statement to Excel or CSV. These guides help with source preparation; they do not make the banks' Pastel providers interchangeable.

When only a PDF or image is available, Invoice Data Extraction can extract bank statement data into a reviewable spreadsheet. Upload the PDF, JPG or PNG files and request Date, Description and Amount columns in that order. Review the XLSX or CSV output against the statement, then use the approved CSV with the generic provider.

This is a preparation route: the product takes the PDF or image source, not an existing CSV. You review the extracted transaction file, then import and post it in Pastel as separate steps.

Build the three-column CSV that Bank Manager documents

For the generic route, Sage's CSV (Bank Manager) format specifies this layout in row one:

Column	Heading
A	Date
B	Description
C	Amount

Enter the transactions below those headings and save the file as CSV (Comma delimited). Heading spelling and column order matter because CSV (Bank Manager) reads a defined transaction layout. This compact Pastel Bank Manager CSV format is not a recipe for rebuilding a bank's proprietary export.

Inspect the saved CSV itself before import. It should contain one header row, the three intended columns and the transaction rows beneath them. Remove report titles, page headings, opening or closing balance lines, subtotals and notes that are not transactions. If the workbook contains formulas, check the values preserved in the CSV rather than assuming the spreadsheet view is what Pastel will read.

Date and amount interpretation need their own checks after loading. Compare the imported dates with the statement, then find one known incoming payment and one known outgoing payment and confirm that Bank Manager placed them on the correct receipt and payment sides. If either check fails, stop before creating batches and compare the file values, Pastel company context and Windows regional settings. A date can look valid in Excel but still be interpreted differently by the importer, and the correct receipt/payment result is safer than assuming one universal sign convention.

---

Load, allocate and move the transactions into the cash book

The current Sage Bank Manager procedure begins by selecting Process, then Cash Book, then Process Cash Book. Select the cash book you intend to update, open Pastel Bank Manager, choose the matching Statement Provider, browse to the Statement File and select Continue.

Continue loads the transactions into Bank Manager. It does not post them to the cash book. Treat this screen as a staging area: check what loaded, assign each transaction to the correct general ledger, customer or supplier account, and complete any other fields required for the batch. Mappings can reuse allocations for descriptions that recur. A split applies to the current import and must be handled again when it recurs in another import.

Once allocation is complete:

1. Confirm that the correct cash book is selected.
2. Check that every transaction has the required account and fields.
3. Create the payment and receipt batches separately where both types are present.
4. Inspect the resulting cash book batches rather than treating batch creation as approval.
5. Make a backup before updating the batches.
6. Select Update only after the batch review is complete.

Bank Manager classifies transactions into payments and receipts, but loading, allocation, batch creation and updating remain distinct control points. A statement visible in Bank Manager has not yet changed the cash book.

---

Reconcile the import before updating

Reconcile the staged transactions to the source statement before they reach the cash book. Start with the transaction count and covered date range. Then compare receipts and payments, scan conspicuous high-value entries, and check whether the first or last dates overlap a range imported previously. An apparently complete month can still contain duplicated days or omit transactions around the statement boundary.

Review the created receipt and payment batches line by line where the risk warrants it. Check the allocated account, period, transaction date, amount and tax treatment. Compare the batch totals with the reviewed statement data before selecting Update. These checks catch errors at the point where they can still be corrected without reversing a posted batch.

Keep the original bank export or statement, the prepared CSV and the relevant accounting support together. SARS record-keeping requirements state that a person who has submitted a tax return must keep the relevant records for five years from the date of submission. Records may need to be retained longer while an audit, investigation, objection or appeal remains unresolved, so five years is not a universal disposal date for every file.

Diagnose Pastel Bank Manager import errors by layer

Pastel Bank Manager import errors are easier to isolate when you identify which contract is failing.

Symptom or checkpoint	What to inspect
File is rejected immediately	Confirm that the Statement Provider is designed for that exact bank export or generic CSV layout. A different provider may expect different records even when the filename ends in CSV.
Generic CSV will not load	Check the headings Date, Description and Amount in columns A, B and C, with no unrelated report material. Save as CSV (Comma delimited), close the file, then browse to it again.
Date or input-string error appears	Compare the raw date values, the Pastel company context and Windows regional settings. Do not keep reformatting dates until the provider and file contract have been confirmed.
Transactions fall into an unexpected period	Check the company financial year and the transaction dates. Sage notes that transactions outside the financial year can be assigned to Period 99. Resolve the period before Update.
Transactions appear twice	Compare the file's date range and entries with the last successful import. Do not reload the same range merely because the first attempt's posting status is unclear.
Create Batch is unavailable or incomplete	Confirm that every transaction has been allocated and that all required fields are complete. Check payment and receipt sides separately.

Also rule out a file-access problem: another program or user may still have the CSV open, and Bank Manager itself is a one-user-at-a-time module. If a valid-looking file continues to fail, preserve a copy of the original and change one diagnosed layer at a time. Borrowing a date rule or error fix from Sage Accounting or Sage 200 Evolution can produce a file that complies with the wrong product.