How to Speed Up SQL Accounting Bank Reconciliation (Step-by-Step)

Published: June 2026 · 6 min read

If you're an accountant in Malaysia using SQL Accounting, bank reconciliation is probably one of the most time-consuming tasks on your monthly checklist. You download the bank statement, cross-check every transaction against your SQL entries, and manually key in anything that doesn't match.

For a firm handling 10–20 clients, that's easily 30–50 hours a month just on reconciliation.

This guide walks through how the reconciliation process works in SQL Accounting, where most of the time gets wasted, and how to cut that time down significantly.

What Is Bank Reconciliation in SQL Accounting?

Bank reconciliation in SQL Accounting means matching your bank ledger entries (inside SQL Account) against your actual bank statement (from Maybank, CIMB, RHB, or wherever your client banks).

The goal: ensure every deposit, withdrawal, and transfer recorded in SQL matches what actually happened in the bank — and flag anything that doesn't.

In SQL Accounting, you do this under: General Ledger → Bank Reconciliation

You select the bank account, the statement date, and enter the closing balance from the bank statement. SQL then shows you all unreconciled transactions. You tick the ones that match, and any outstanding items remain for follow-up.

Where Time Gets Wasted

The reconciliation form in SQL Accounting works well once your data is inside the system. The bottleneck isn't the reconciliation itself — it's getting the bank statement data into a format you can work with.

Here's what the typical workflow looks like:

  1. Download bank statement PDF from the bank's online portal
  2. Manually read through every transaction
  3. Cross-reference each one with SQL entries
  4. Key in missing transactions (payments received via DuitNow, TNG QR, etc.)
  5. Investigate mismatches

Steps 1–4 are where most time disappears, especially for:

  • TNG eWallet and DuitNow QR payments — these show up on bank statements but clients rarely record them in SQL
  • Multiple daily transactions — active businesses can have 50–100+ transactions per month
  • Maybank's PDF format — Maybank statements can be tricky to read, especially older PDF versions

The Manual Approach vs Automated Extraction

Manual approach

You open the PDF, scroll through transactions, and copy numbers by hand into SQL or an intermediate spreadsheet. For a 3-month bank statement with 200 transactions, this takes 2–3 hours per client.

Automated approach

You use a tool that reads the PDF bank statement and extracts all transactions into a structured format (Excel or CSV) — date, description, debit, credit, balance. You then import this into SQL Accounting or compare side-by-side.

The difference is dramatic: what takes 2–3 hours manually takes about 5–10 minutes with extraction.

Supported Malaysian Banks

Any extraction tool worth using should handle the major Malaysian banks that SQL Accounting clients typically use:

  • Maybank (most common)
  • CIMB Bank
  • Public Bank
  • RHB Bank
  • Hong Leong Bank
  • Ambank
  • BSN

Each bank uses slightly different PDF formats, column layouts, and date formats. A tool built specifically for Malaysian banks handles these differences automatically.

Step-by-Step: Fast Bank Reconciliation with SQL Accounting

Here's the workflow we recommend for accounting firms handling multiple SQL Accounting clients:

Step 1: Download the bank statement PDF Log into your client's banking portal and download the PDF statement for the period you're reconciling.

Step 2: Extract transactions automatically Upload the PDF to ScanLedge. The AI reads every transaction — including DuitNow transfers, TNG QR receipts, and IBFT payments — and outputs a clean Excel file with columns: Date, Description, Reference, Debit, Credit, Balance.

Step 3: Import into SQL Accounting or reconcile side-by-side Use the extracted Excel file to:

  • Import missing transactions into SQL Accounting
  • Cross-reference your SQL entries against the extracted list to spot discrepancies fast

Step 4: Run Bank Reconciliation in SQL With your transactions already entered, the bank reconciliation form in SQL Accounting becomes a quick tick-box exercise rather than a data entry marathon.

Common Issues and How to Fix Them

Problem: TNG QR and DuitNow transactions not in SQL These show up on Maybank or CIMB statements as bulk credits, but clients often don't record the individual payers. Extracted bank statements show each transaction clearly — you can then enter them into SQL with proper descriptions.

Problem: Mismatched amounts Often caused by bank charges, forex conversion fees, or rounded amounts. Having the full transaction list extracted makes it easy to spot and investigate.

Problem: Statement format changed Banks occasionally update their PDF formats. A good extraction tool updates to match — you don't need to adjust your process.

How Much Time Can You Save?

A typical accounting firm handling 15 clients with monthly reconciliation:

| Task | Manual | With extraction | |------|--------|-----------------| | Per-client reconciliation | 2–3 hours | 20–30 minutes | | 15 clients/month | 30–45 hours | 5–8 hours |

That's roughly 35–40 hours saved per month — time that goes back into higher-value work or taking on more clients without adding headcount.

Try It Free

ScanLedge extracts Malaysian bank statements into clean Excel files ready for SQL Accounting reconciliation. It handles Maybank, CIMB, Public Bank, RHB, and other major Malaysian banks — including DuitNow and TNG transactions.

7-day free trial. No credit card needed.

Start your free trial →