krani
WhatsApp Us
Home / Blog / AutoCount PDF Import Guide
Guide

AutoCount PDF bank statement import: what it covers and where it stops

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

AutoCount has a built-in feature for importing bank statements from a PDF, but per AutoCount's own documentation, it only reads CIMB, RHB, BSN and Public Bank statements, and doesn't handle receipts, invoices or WhatsApp-captured documents. Firms with clients on other banks, or that want receipts automated too, need a separate tool to fill the gap.

What AutoCount's built-in PDF bank statement import actually does

AutoCount ships with a built-in feature for importing bank statements directly from a PDF, saving firms from manually keying in every line of a client's monthly statement. According to AutoCount's own support documentation, the feature reads the PDF, extracts the transaction lines, and lets you review and post them into the ledger without retyping each entry by hand.

Which banks it actually supports

This is the detail that catches firms out: the built-in import doesn't read every Malaysian bank's statement format. Per AutoCount's own documentation, it covers CIMB, RHB, BSN and Public Bank statements only. If a client banks with Maybank, Hong Leong Bank, AmBank, or any bank outside that list, the built-in tool won't read the PDF correctly, and the firm is back to manual entry for that client.

Where the built-in tool stops

When the built-in import is enough

If every client a firm handles banks exclusively with CIMB, RHB, BSN or Public Bank, and the firm isn't trying to automate receipt and invoice entry as well, AutoCount's built-in import covers the core use case well enough on its own, at no extra cost beyond the AutoCount licence already in place.

Why the bank-coverage gap matters more than it looks

A single unsupported bank doesn't sound like much until you count how many clients it actually touches. A firm running 40 clients, even a handful on Maybank or Hong Leong Bank alongside the CIMB and Public Bank accounts the built-in import handles, still ends up with a manual entry process for that subset every single month. The built-in import doesn't fail loudly when it hits an unsupported format; it simply can't read the statement in the first place, so the workaround has always been retyping it by hand.

What to do about the banks it doesn't cover

For everything outside that list, and for receipts and invoices, a firm needs either manual entry or a separate tool. Krani's AutoCount integration is built to pick up exactly where the built-in import stops: it reads Maybank, CIMB, Public Bank, RHB, Hong Leong Bank, AmBank and more, plus receipts and invoices via OCR, and posts the result directly into AutoCount or exports a file formatted for AutoCount's own import screen.

AutoCount built-in importKrani
Bank coverageCIMB, RHB, BSN, Public BankMaybank, CIMB, Public Bank, RHB, Hong Leong Bank, AmBank and more
Receipts and invoicesNot coveredRead with OCR, coded automatically
WhatsApp captureNot coveredClients send receipts by WhatsApp, no credits used
Multiple clients at onceOne file at a timeBuilt for firms running many clients, no per-client limit
Chart-of-accounts mappingManualMatched automatically before posting

See the full AutoCount integration page for how the setup works, or WhatsApp us for a demo on your own statements.

FAQ

Frequently asked questions

Related reading

See the full AutoCount integration page, or how the same idea applies to SQL Account.

Ready to cover the banks AutoCount's import doesn't?

Send us a message. We will show you Krani on your own client's statements.

WhatsApp Us for a Demo Free demo. No commitment.