Reconcile your bank statement with AI — statement day, step by step

Baca panduan amali ini dalam Bahasa Malaysia →

Statement day is the reconciliation clerk’s whole job: read the statement, decide what every line was, tick it off. This playbook hands the reading and the proposing to your own AI, and leaves you the deciding. Seven steps. Nothing posts to your ledger without your tap.

The short version

Assumes the setup playbook is done — the connector is on and your AI can see your books.
You download the statement from your bank. Your AI imports it, and every row lands in Banking → Review, unposted.
Your AI proposes a category for the rows it can read, with its reason on each one. It can never confirm or post.
You clear the obvious rows from two batch panels — Taokeh’s own suggestions, and your AI’s proposals — then post.
Your AI reads the tie-out back to you. When the statement carries no closing balance it says “unknown”, not “balanced”.

What do you need before statement day?

The spine from the setup playbook: the add-on on, https://taokeh.my/mcp added as a connector, your AI able to list its Taokeh tools. Do that once, and this playbook is seven steps.

You also need your bank account set up in Taokeh (Banking → Accounts) and this month’s statement downloaded as a PDF or CSV.

How does the statement get into your books? (steps 1–4)

Save the statement anywhere on your computer, then paste the block below into a new chat with the folder path changed to yours. This is the wording we ran ourselves.

1. Download the statement from your bank and save it — PDF or CSV, whichever your bank gives you.
2. Paste the instruction block into a new chat.
3. Read the report. It should say how many rows were staged and give you the link into Taokeh. Our run staged nine rows and named the account and the period back.
The server checks that opening balance plus the rows equals the printed closing balance, and rejects the import with the exact difference if they disagree. Your AI cannot quietly drop a row to make it balance.

The instruction block — paste this, changing the statement’s path

It is statement day. The bank statement for this month is at ~/Documents/Taokeh/Statements/maybank-aug-2026.pdf.

1. Read the statement yourself, then call Taokeh's intake_contract with doc_type 'statement' to see my accounts and the arithmetic rule.
2. Import it with import_bank_statement: the printed opening and closing balances, and EVERY row, signed (+ money in, − money out). Never invent or drop a row to make it balance — if it will not tie, stop and tell me the difference.
3. Call bank_review_queue and read me the rows Taokeh is least sure about first.
4. Before you propose anything on a row I would have to guess at, call payer_history on the name printed on that line.
5. Propose with draft_bank_classification, and put your reason on every row — I read them before I accept.
6. Finish with bank_reconciliation_status and tell me two things: does the statement tie out, and how many rows are still waiting for me.

Do not confirm and do not post. Proposals only — I accept and post in Taokeh.

What does Taokeh already know about the rows?

More than you would expect, and your AI reads it before proposing anything. Each row comes back with Taokeh’s own suggested category, a confidence score and a plain reason — the same ones the review screen computes.

Our nine-row run came back sorted worst-first: two rows mechanical at 90% or better, two mid, five needing eyes. Those five are the job.

On a real payer name, payer_history returns what you decided before — category, contact, GL account, how many times. On a line reading TRANSFER 5527819 it returns nothing and says so: Taokeh never learns precedent from a generic memo, so it will not invent one.

How do you clear the queue? (steps 4–5)

Open Banking → Review. Two batch panels sit above the rows, and they are deliberately separate — they carry different opinions.

4. “Accept AI suggestions” is Taokeh’s own classifier, gated by a confidence you choose: 80%, 90% or 95%, defaulting to 90%. It shows what it would accept, grouped by category, before you tap.
5. “Proposals from your AI” is your assistant’s own list, with its reason on every row. No percentages here — a proposal from your AI carries no score, and we will not invent one for it.
Accepting sets the category and the contact. It does not post. In our run the two panels cleared four of nine rows between them, and the ledger was still untouched.
A row where your AI disagrees with Taokeh’s classifier drops out of the first panel on purpose. Two opinions is a reason to read it, not to batch it.
Then post — row by row, or a whole supplier’s group with “Post all”.

What if your AI is wrong about a row?

You override it, and it costs one dropdown. We had our AI file a deliberately wrong proposal: a RM1,388.60 payment to a marketing agency, proposed as a bank charge, with a confident-sounding reason.

It read wrong on the screen, so the fix was to pick the right category on that row and press Post. Nothing had to be undone first, and the wrong proposal never reached the ledger — because a proposal cannot.

This is why the reasons matter. Read them, and the ones that are wrong announce themselves.

How do you know it actually ties out? (step 6)

Ask. bank_reconciliation_status gives your AI the same figures the Bank Reconciliation page shows you.

6. Ask for the tie-out. Ours reported opening RM13,185.60 plus RM3,247.60 of movement against a printed closing of RM16,433.20, and tied.
It also reports what is left: the unreviewed backlog per account, so “how much of statement day is still mine?” has a number.
And when a statement carries no closing balance — a CSV export with no balance column — the tie-out comes back unknown, not false. There was nothing to check against, and saying “balanced” would be a lie.

How do you make it monthly? (step 7)

Statement day already has a date. Attach the run to it.

7a. If your plan offers a scheduled or recurring task, create one for the day after your statement lands and point it at the block above.
7b. If it does not, save the block as a saved prompt and run it on the day you already open the bank app. A habit on a date beats an automation you never set up.
7c. Either way it proposes and reports. It cannot post, so a run you did not watch cannot hurt your books.

What still needs you?

Reading the rows your AI was unsure about, and posting. Everything above that line is sorting — and sorting is what you just handed over.

Frequently asked questions

Can my AI post the bank rows for me?

Taokeh reads your live books freely and files drafts. It can never post, edit or delete — a human approves every entry before it hits the ledger. On bank rows specifically: it can import a statement and propose categories, and that is the end of its reach. Confirming and posting are clicks in Taokeh.

Does the AI import keep a copy of my statement?

Yes, if you hand it the file. Ask your AI to attach the statement PDF when it imports: Taokeh archives that original on the statement, downloadable from the statement page exactly as a web upload is. Imported without one? Ask it to run the same import again with the file attached: the file lands on the statement you already have, and no row is staged twice. Send no file and nothing is archived, and the tool says so plainly.

What if the statement does not balance?

The import is rejected with the exact difference, and nothing is staged. That is deliberate: a statement that will not tie is a reading error to fix, not a row to quietly drop.

What happens if I import the same statement twice?

Nothing doubles. An exact re-import stages nothing new, and an overlapping period is blocked until you confirm it is genuinely a separate statement.

Do I have to accept a whole batch at once?

No. The panels are a shortcut for the obvious rows, not a requirement. You can ignore both and work down the list one row at a time — same screen, same categories.

Updated August 2026

This playbook is general information for Malaysian SMEs, not tax, legal or accounting advice. Screens in third-party AI apps change — the steps here are as at August 2026; confirm against your app if a screen looks different.

The Ask Taokeh connector — what it reads, what it can file, what it can never do

Your own AI runs your back office; Taokeh keeps the books — and you approve every entry.

See the connector → Start your free trial