krani
WhatsApp Us
Home / Blog / Bank Reconciliation in SQL Account
How-to

How to do bank reconciliation in SQL Account

Vincent · COO of Krani.ai · Ex-PwC, EY · 10+ years in accounting & audit
Published 27 Sep 2026 · 6 min read
TL;DR

Bank reconciliation means matching every statement line to a posted ledger entry until both sides agree, then resolving whatever doesn't match. This walks through that process for SQL Account step by step, what a Krani-produced import file actually contains, and how automating the matching step removes the slowest part of month-end.

What bank reconciliation actually means

Bank reconciliation is the process of checking that what's recorded in the ledger matches what actually happened in the bank account, until every statement line has a matching ledger entry, or a clear explanation for why it doesn't. It catches missing entries, duplicate postings, and the ordinary timing differences that show up in any account, like a payment that's been issued but hasn't cleared the bank yet.

The general process, step by step

  1. Get the bank statement for the period. A PDF statement or online banking export covering the same period as the ledger you're reconciling.
  2. Get the ledger entries for the same period. Pull up the client's posted bank transactions in SQL Account for that period.
  3. Match each statement line to a ledger entry. Work through the statement, ticking off every line with a corresponding posted entry.
  4. Investigate what's left unmatched. A statement line with no ledger match usually needs a new entry. A ledger entry with no statement match needs checking too, since it could be timing or a genuine error.
  5. Post the adjustments and confirm the closing balance. Once everything is accounted for, the reconciled balance in SQL Account should match the statement's closing balance.

Where the time actually goes

The concept is simple; the matching is what takes time. A client with a short, simple statement reconciles quickly. A client running hundreds of transactions a month means matching each line against the ledger by eye, then chasing down every item that doesn't line up cleanly, which is where an afternoon disappears. Across a full book of clients at month-end, that matching step becomes one of the biggest blocks of manual work in the calendar.

What Krani extracts for SQL Account

Krani produces an import file with the date, description, debit or credit amount and the matching chart-of-accounts code for every line, formatted for SQL Account's own import screen, so the accountant reviews and confirms rather than typing each line by hand. Chart-of-accounts matching works from the client's own transaction history, and anything Krani isn't confident about is flagged with a lower confidence score for a check before it posts.

How Krani automates the whole flow

Krani extracts the statement (Maybank, CIMB, Public Bank, RHB, Hong Leong Bank, AmBank and more), reads the receipts and invoices for the same period, and matches them against each other automatically, rather than leaving that matching step to be done by eye. The reconciled result, plus a P&L and Balance Sheet, posts directly into SQL Account or exports as a ready-to-import file. See the full flow on the bank reconciliation page.

WhatsApp us for a demo and we'll walk through reconciliation on your own client's statement.

FAQ

Frequently asked questions

Related reading

See the same process for AutoCount, or how Krani's SQL Account integration works end to end.

Ready to automate reconciliation for SQL Account?

Send us a message. We will show you Krani reconciling your own client's data.

WhatsApp Us for a Demo Free demo. No commitment.