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

Bank reconciliation in AutoCount, step by step

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 bank statement line to a posted ledger entry until both sides agree, then investigating and resolving whatever doesn't match. AutoCount's built-in PDF import handles statement extraction for four banks, but the actual matching against receipts and invoices is still manual. This walks through the process step by step and where automation like Krani removes the matching work entirely.

What bank reconciliation actually means

Bank reconciliation is the process of checking that the transactions recorded in the ledger match what actually happened in the bank account, line by line, until every entry on one side has a matching entry on the other, or an explanation for why it doesn't. It's the step that catches missing entries, duplicate postings, and the timing differences that are completely normal in any account, like a cheque that's been issued but hasn't cleared yet.

The general process, step by step

  1. Get the bank statement for the period. A PDF statement, or the transaction export from online banking, 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 AutoCount for that period, so you have both sides in front of you.
  3. Match each statement line to a ledger entry. Work through the statement and tick off every line that has a corresponding entry already posted.
  4. Investigate what's left unmatched. Anything on the statement without a ledger match usually needs a new entry (a bank charge, interest, or a transaction that was never keyed in). Anything in the ledger without a statement match needs checking too, since it may be a timing difference or a genuine error.
  5. Post the adjustments and confirm the closing balance. Once every line is accounted for, the reconciled balance in AutoCount should match the statement's closing balance for the period.

Where the time actually goes

The matching step is where reconciliation gets slow, not the concept itself. For a client with a handful of transactions a month, this is quick. For a client running hundreds of transactions, matching each statement line against the ledger by eye, then chasing down every unmatched item, is where an afternoon disappears. Multiply that across a full book of clients at month-end, and reconciliation becomes one of the largest blocks of manual time in a practice's calendar.

Where AutoCount's own tools help, and where they stop

AutoCount's built-in PDF bank statement import can pull statement lines in automatically for CIMB, RHB, BSN and Public Bank, which removes the retyping step for those banks. It doesn't, on its own, match those lines against receipts and invoices already on file, or extend to other Malaysian banks. That matching step is still manual.

How Krani automates the whole flow

Krani extracts the statement (for Maybank, CIMB, Public Bank, RHB, Hong Leong Bank, AmBank and more, not just the four AutoCount covers natively), reads the receipts and invoices for the same period, and matches them against each other automatically. Anything it isn't confident about is flagged with a confidence score for a quick check, rather than posted blindly. The reconciled result, plus a P&L and Balance Sheet, posts directly into AutoCount. 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 SQL Account, or how Krani's AutoCount integration works end to end.

Ready to automate reconciliation for AutoCount?

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

WhatsApp Us for a Demo Free demo. No commitment.