GuideNovember 5, 20269 min read

AutoCount and SQL Accounting: How to Import a Malaysian Bank Statement PDF as CSV

Prepare Malaysian bank statement PDFs for AutoCount and SQL Accounting, check CSV column mapping and avoid reversing deposits and withdrawals.

AutoCount and SQL Accounting: How to Import a Malaysian Bank Statement PDF as CSV

Introduction

A client sends a month of Maybank, CIMB, Public Bank, RHB, Hong Leong or AmBank statements as PDFs. You need those transactions in AutoCount Accounting or SQL Accounting for bank reconciliation, without typing every payment and receipt.

The practical route is to extract the PDF into transaction rows, review them, then prepare a CSV for the import function available in your software. The critical check is what Debit and Credit mean on each side. A bank statement credit is money received, but that same receipt is a debit to the company's bank ledger account.

This guide covers the CSV preparation, the two software workflows and a small test that catches reversed amounts before a full month's import. Features and file requirements differ by edition and version, so check your own installation first.

Understand the debit/credit perspective trap

A bank statement shows movements from the bank's perspective. Money held for your company is a liability in the bank's books: a deposit increases that liability with a credit. A withdrawal reduces it with a debit.

In your company's books, the bank account is an asset. A deposit increases that asset with a debit; a withdrawal reduces it with a credit.

The following examples are illustrative transactions for the fictional ABC Trading Sdn Bhd.

| Transaction | Bank statement perspective | Company's bank ledger perspective | | --- | --- | --- | | Customer pays RM250.00 into the account | Credit: deposit, money in | Debit bank RM250.00 | | Company pays supplier RM80.00 | Debit: withdrawal, money out | Credit bank RM80.00 | | Bank deducts RM5.00 charges | Debit: withdrawal, money out | Credit bank RM5.00 |

This reversal does not mean you should swap the CSV columns immediately. A statement importer may expect the bank's perspective, while a ledger-entry importer may expect the company's perspective. Map by deposits and withdrawals, not by matching column names alone.

Before the first full import, use a couple of known transactions: one customer receipt and one supplier payment. Confirm which destination column in your AutoCount or SQL Accounting import screen represents deposits and which represents withdrawals. Where the importer uses a fixed template instead of manual mapping, check the same distinction in its preview or test result.

Prepare the PDF and review the extracted rows

Start with one account and one statement period

Keep each bank account and currency separate. Confirm the account, statement period, opening balance and closing balance against the client's records before conversion. Check whether any of the dates have already been imported.

If the PDF is password-protected, open it using the password you know and save an unprotected copy before uploading. SEA Bank OCR rejects protected PDFs; the upload message may say the file “may be corrupted or password-protected”.

Extract, then check against the PDF

SEA Bank OCR converts Malaysian and Singaporean bank statement PDFs to Excel, CSV or JSON. It is an independent Malaysian service, not affiliated with SeaBank or any bank.

Upload the unprotected PDF, then review the extracted rows on the results page. Individual cells can be edited before export. Compare dates, descriptions, references and amounts with the source, particularly around page breaks and descriptions that continue onto another line.

Check that each transaction appears once and that page headings or balance summaries have not become transactions. A correct closing balance alone does not prove every row is correct: offsetting errors can still leave the total unchanged.

For Maybank-specific preparation, see the Maybank statement to CSV guide. The remaining steps focus on getting reviewed rows into AutoCount and SQL Accounting.

Choose the accounting preset and keep a control file

SEA Bank OCR's export menu includes accounting presets that arrange the columns for subsequent import preparation. They do not connect directly to either accounting package. Check the mapping and your version's required template on the first import.

| Export | Exact CSV columns, in order | File ending | | --- | --- | --- | | AutoCount preset | Date, Description, Ref No, Debit, Credit | -autocount.csv | | SQL Accounting preset | Date, Description, Reference, DR, CR | -sql-accounting.csv |

Both presets use dates in DD/MM/YYYY format and amounts as plain numbers with two decimal places and no thousands separators, such as 250.00.

In both files, the amounts retain the bank statement perspective:

  • AutoCount Debit and SQL Accounting DR mean withdrawal, money out.
  • AutoCount Credit and SQL Accounting CR mean deposit, money in.

The SQL header DR does not turn a withdrawal into a ledger debit. These labels describe the exported statement data; the destination importer determines how those values must be mapped.

Neither preset includes a Balance column. Also save the generic CSV or Excel export as your review and control file. Its columns are Date, Description, Reference, Debit, Credit, Balance and Category. Keep that file alongside the original PDF and the final import CSV. The Excel bank reconciliation guide provides a useful framework for checking the balances separately.

Import into AutoCount Accounting

Check whether you use desktop or Cloud

AutoCount's desktop Bank Reconciliation help documents G/L > Bank Reconciliation, selecting a bank account and adding a reconciliation with a statement date. That page describes reconciliation against recorded transactions; it does not establish a universal desktop CSV import wizard.

For desktop, open the bank reconciliation or import function in your version and check the available statement-import facility. Menus and supported files can differ by edition, version and installed components. Obtain its sample file or instructions before treating the preset as ready to load. If your installation has no suitable importer, use the reviewed export as a reconciliation workpaper and confirm the supported import route with your software provider.

Follow the documented Cloud CSV route where available

AutoCount Cloud's official CSV bank statement instructions document this sequence:

  • Select the bank account to reconcile.
  • Choose +Import > Import From File.
  • Select CSV, choose the file through Select File, then open it.
  • Click Import.

The same guide says that if the importer cannot identify transaction date and amount columns, use Download Template and rename the CSV headers to match the template. Start from the AutoCount preset, but adapt a separate copy to that template where necessary. A preset name does not guarantee that every AutoCount import function accepts those headers unchanged.

For your first test, confirm that the known RM250.00 receipt appears as money in and the RM80.00 supplier payment as money out. Review the mapping or test result before proceeding with the full period.

Import into SQL Accounting

SQL Accounting by E Stream documents a statement-loading workflow in its official General Ledger FAQ:

  • Go to GL > Bank Reconciliation > New.
  • Select the Bank Statement Date and Account.
  • Check Show Current Recon Transactions, then click Apply.
  • Click Load Statement and select a PDF or CSV statement.

The documented workflow includes bank-name confirmation and matching against existing transactions. Check that this facility is available in your edition and version; do not assume every installation accepts every bank layout or arbitrary CSV header set.

Export the SQL Accounting preset as a starting file. If your importer offers column mapping, map Date, Description and Reference to the corresponding fields, then explicitly check which destination fields mean deposits and withdrawals. Remember that source DR is a withdrawal and source CR is a deposit. If there is no mapping option, follow your version's required statement format rather than guessing.

Test the same known receipt and payment before loading the complete period. Because the preset omits Balance, keep the PDF closing balance available and verify the reconciliation balance against it.

Run the checks before completing reconciliation

Use this checklist for each client account, even after a previous month's mapping worked.

| Check | What to confirm | | --- | --- | | Account and period | Correct client bank account, currency and statement dates | | Dates and references | DD/MM/YYYY remains intact; leading zeros in references are preserved | | Direction | Known deposit is money in; known withdrawal is money out | | Completeness | Every PDF transaction is represented once; summary rows are excluded | | Totals | Deposits and withdrawals agree with statement totals where provided | | Balance | Opening balance + deposits − withdrawals = closing balance | | Import history | No overlap with previously imported dates or the test batch |

If you open the CSV in a spreadsheet, check it again after saving. Automatic formatting can change dates or remove leading zeros from references.

Before the full import, establish how you will handle the test rows: use a test company where available, or ensure the production batch excludes rows already loaded. Do not rely on duplicate detection without checking your version's behaviour.

After import, match statement lines to existing receipts and payments before creating anything new. A loaded statement is evidence for reconciliation, not proof that each item has already been posted correctly. Investigate bank charges, transfers between company accounts, outstanding cheques and unmatched receipts individually. Keep a note of the final mapping with the client workpapers; the accounting software import guide can support a consistent team procedure.

Frequently Asked Questions

Can I import a bank statement PDF directly into AutoCount or SQL Accounting? Some documented workflows offer PDF loading, including SQL Accounting's Load Statement function. Availability and supported layouts depend on your software. This guide uses reviewed CSV rows when you need to inspect or adapt the data before import; check your version's official instructions first.

Do the AutoCount and SQL Accounting presets work without changes? They arrange the columns as listed above. Your import function may require different headers, a fixed template or manual mapping. Check the first import with a known deposit and withdrawal before processing a full statement.

Why does the SQL Accounting CSV show a payment under DR? SEA Bank OCR's SQL Accounting preset uses the bank statement perspective: DR means withdrawal and CR means deposit. The company's bank ledger uses the opposite debit/credit treatment, so confirm the destination fields by their meaning rather than their initials.

Should I import the Balance and Category columns? The accounting presets contain neither column. Keep the generic export for review, particularly the running Balance. Follow the destination template for import fields and assess the correct ledger allocation separately when completing the bookkeeping.

What should I do when a CSV is rejected? Compare its headers, date format and amount fields with your version's template. AutoCount Cloud specifically advises downloading its template when date and amount columns cannot be identified. Preserve the reviewed original, adapt a copy, then repeat the deposit-and-withdrawal check.

Conclusion

For AutoCount and SQL Accounting, a usable CSV starts with reviewed statement rows and ends with a verified mapping. Keep the Balance column in a separate control file, test one known deposit and withdrawal, and reconcile against existing records before creating new entries.

Try one client statement with SEA Bank OCR's free Starter plan, which includes five pages per month. Export the appropriate preset, check your software's template and confirm the direction of the first two transactions before importing the rest.

Try it on a real statement

Five free pages every month. No credit card required to start.