Import bank statements and receipts into SQL Account automatically
Krani reads receipts and bank statements, then sends the finished entries into SQL Account. No double entry, no new system to learn.
Retyping SQL Account entries is where the hours go
Every month, someone on the team opens a PDF bank statement and keys it into SQL Account line by line. Receipts arrive from clients over WhatsApp, often crumpled or half-legible, and still need to be read, coded and entered by hand. During peak season this backs up fast, and when a staff member leaves, the process leaves with them.
Krani removes that step. Receipts, invoices and bank statements are read automatically, matched to the client's existing chart of accounts, and sent into SQL Account ready to post.
Three ways to get data into SQL Account
Direct integration
Krani connects directly to SQL Account and pushes finished, categorized entries in automatically. Nothing to export, nothing to re-key.
Flat-file export and import
Prefer to stay in control of what gets posted? Krani produces a file already formatted for SQL Account's import screen, so you review and import it in a few clicks. See SQL Account's own Excel import guide for exactly what that import screen looks like today.
Copy and paste into the entry grid
For a quick batch, copy the rows from Krani's Excel export and paste them straight into SQL Account's entry grid, for example on a payment voucher, without remapping any columns.
In practice, most firms follow this flow:
- Upload receipts and bank statement PDFs, or forward them from the client's WhatsApp chat.
- Krani reads and codes each line, matching it to the client's existing chart of accounts in SQL Account.
- Entries post directly into SQL Account, or export as a ready-to-import file, or as rows you can paste straight into SQL Account's entry grid, if you'd rather review first.
If your firm also has clients on AutoCount, Krani works the same way there.
Which banks are supported
Krani reads statement layouts from Maybank, CIMB, Public Bank, RHB, Hong Leong Bank, AmBank and more. If a client banks somewhere Krani hasn't seen yet, send a sample statement and it gets added. See the full breakdown on how AI Bank Statement Extraction works.
What the SQL Account import file contains
Each line in the file Krani produces carries the date, description, debit or credit amount and the matching chart-of-accounts code, already formatted for SQL Account's own import screen. You open SQL Account, import the file, and review, rather than typing each line by hand.
Chart-of-accounts matching works from the client's own history: Krani looks at the supplier or description on each line and applies the account code that client has used for similar transactions before. Anything it isn't confident about gets a lower confidence score and is flagged for you to check before it posts, rather than posted blind.
This is the same matching Krani uses for the other accounting systems it connects to, including Bukku, Xero and QuickBooks. See pricing plans based on document volume.
SQL Account integration questions
Ready to connect Krani to SQL Account?
Send us a message. We will show you Krani on your own documents.
WhatsApp Us for a Demo Free demo. No commitment.