Ringbook uses AI to do the tedious part of bookkeeping for you: reading a receipt, drafting a balanced journal entry, matching a document to the right transaction, and answering questions about your books in plain language. You stay in control — the AI proposes, you review and post.
This page explains where AI shows up, how to get the best results from it, how to teach it your own booking conventions so it gets better over time, and how to tell us when something's off.
This page is English-only for now. The Ringbook app itself is available in English, Japanese, Russian, Thai, Simplified Chinese, and Traditional Chinese.
AI is woven through the everyday flow rather than bolted on as a separate mode:
AI-powered actions consume AI credits. Manual data entry is always free; you only spend credits when you ask the AI to read, draft, or match something. See Pricing for how credits work.
For the bookkeeping fundamentals these features sit on top of — rings, journals, the Shoebox, reconciliation — see the main Documentation.
The AI is good, but a few habits make it noticeably better and save you credits by getting a clean draft on the first try.
The single biggest factor in extraction quality is the background behind the receipt. A receipt shot flat on a plain white (or other light, solid) surface, in even light, gives the AI crisp edges and clean text. The same receipt on a cluttered desk — wood grain, other papers, coffee rings, hard shadows — forces the AI to guess where the receipt ends and the desk begins, and it reads less reliably.
A few seconds of setup pays off:
This applies to receipts sent via WhatsApp and to drag-and-drop uploads alike.
iPhone photos often save as
.heic, which isn't supported on direct upload. Sending the photo via WhatsApp converts it automatically; for drag-and-drop, convert to.jpgfirst. See the docs for how.
AI generation is probabilistic. Occasionally a draft will stall, time out, or come back looking off. It's completely fine to generate again — just trigger the generation a second time. A retry usually succeeds, and because each run is independent, the second attempt often produces a cleaner entry than the first.
This is true everywhere AI generates: the Ring composer's Generate with AI, the inline Generate Journal action on an existing ring, the Ledger's AI entry, and reconciliation suggestions. If something looks wrong, regenerate before fixing it by hand — it's faster.
A common source of errors: the currency on your document doesn't match the currency the chosen account allows. For example, if you attach a receipt in HKD but the account the AI picks (or that you select) is restricted to a different currency, posting can fail with an error.
When that happens, you have two clean fixes:
If you genuinely need to book a foreign-currency receipt against a base-currency account, that's a multi-currency entry — Ringbook stores both the original and base amounts and can add the FX gain/loss leg for you. See Multi-Currency and FX in the docs.
The AI reads both your text and the attached document. A photo on its own usually produces a workable draft; a photo plus a handful of words — "Lunch with David, paid on the Amex" — produces a noticeably cleaner one, because the AI knows the context (which card, what it was for). You don't need a sentence; a few words is plenty.
Some transactions recur in exactly the same shape every month: the same rent, the same software subscription, the same payout from a marketplace split across fee and net. Rather than re-checking the AI's guess each time, you can capture how you book it once and have Ringbook follow that recipe on every similar ring afterwards.
Make a rule when you find yourself correcting the AI the same way repeatedly, or when a transaction has a non-obvious split the AI can't infer (for example, a gross payout that needs to be broken into platform fees and net cash). The more idiosyncratic your booking, the more a rule helps.
You refer to accounts by name in the instructions — the rule is a plain-language recipe, not code.
Before saving, you can tighten the rule:
Saved rules can be edited, toggled on or off, or deleted later from Settings (next section).
Every rule you create with Make rule is managed in one place: Settings → Ringer to Journal (the Ring → journal rules card).
Rules saved from a ring's 3-dot menu ("Make rule"). When the AI generates a journal on a similar future ring, it follows the matching rule's accounts and structure instead of guessing.
The page lists each rule with:
For each rule you can edit it (name, match hint, instructions), toggle it on or off without deleting it, or delete it outright. Disable a rule when a vendor changes their invoice format and the rule starts misfiring — you can re-enable it after fixing the instructions.
When you next generate a journal on a ring that matches an enabled rule, Ringbook follows that rule's accounts and structure instead of drafting from scratch. This is how the system gets more accurate the more you use it: every correction you turn into a rule is one the AI won't get wrong again.
The Companion is a floating chat assistant — tap the message-circle button in the bottom-right corner of the dashboard. It can run as a compact bubble or dock as a resizable sidebar, and it keeps a history of your past conversations (which you can rename, delete, or start fresh). You can attach files (images and PDFs) to a message.
Using the Companion spends AI credits; you'll be prompted to top up if your balance is too low.
The Companion has read access to your organization's books, so you can ask things like:
When you open a fresh chat it suggests starting points: Create a ring about…, Record a transaction for…, Find documents for…, and Show recent transactions.
Beyond answering, the Companion can take a couple of actions on request:
As always, these are proposals you can review on the Ring or Ledger afterwards.
Querying your books from WhatsApp isn't supported — that lives in the Companion in the web app. WhatsApp is for capturing rings and dropping documents into the Shoebox.
When a receipt or invoice lands in your Shoebox, Ringbook tries to figure out which transaction it belongs to — so the paperwork ends up attached to the right journal entry without you hunting for it.
Open a document's preview and you'll see a Match Suggestions panel (✨). If the document is already linked, it shows the Linked Transaction with a green badge. Otherwise it lists the potential matches the AI found.
Each suggestion comes with a confidence level — High, Medium, or Low — backed by a breakdown of how it scored:
Each candidate card shows the transaction's description, date, total, and the first couple of accounts involved, so you can judge it at a glance.
Matching is automatic — there's nothing to configure. You're only ever confirming or dismissing what the AI proposes, which keeps a clean trail of which document supports which entry. For more on documents and the Shoebox, see the docs.
Reconciliation is where Ringbook's AI does its heaviest lifting. You give it a bank statement; it reads every line, matches what it can against your ledger, and shows you exactly what's missing — so closing the month is a quick review instead of a manual tick-and-tie. It works on real-world statements from any bank, in any format (PDF, CSV, or OFX/QIF) and any language.
Open Reconciliation from the sidebar (the 💵 statement icon). The screen is split: Statement Documents on the left, your Ledger Transactions on the right. Pick the account you're reconciling from the selector at the top (here, Pineapple Bank). Then follow four steps.
Click Upload (or the + Upload Document button in the empty state) and drop in your bank statement. Once Ringbook recognizes the file as a statement, it appears in the Statement Documents list, ready to open.

Open the uploaded statement to preview it — the Original tab shows the document as-is, and you can confirm it's the right bank, account, and period. When you're ready, click Extract. The AI reads the statement and pulls every line into a structured list, regardless of how the bank laid it out.

The Text tab now shows the extracted result: a Statement Info header (bank, account, and the currency — if the statement doesn't state one, Ringbook falls back to your org base currency) and the full list of Extracted Transactions with date, description, amount, and running balance, plus Opening, Incoming, Outgoing, and Closing totals at the bottom.
Give it a quick check before matching:
When it looks right, click Run Reconciliation. Ringbook matches each statement line against your existing ledger entries by date, amount, and description.

The right panel fills in with the outcome. Lines that matched an existing entry are paired up; lines on the statement that aren't in your books yet are grouped under Missing from ledger and tagged Bank Only. For each of those, click + Add: Ringbook drafts the journal with the AI's suggested other leg — the bank side is already known, so it proposes the account to book against. Check that other leg, then post. (You can instead match a line manually against an existing entry that's worded differently, or skip it with a note — e.g. a transfer already booked on the other side.)
Work down the list until nothing is left unexplained: the header flips to Completed and the Net difference reads HK$0.00, meaning your books now agree with the bank. You can Reset to re-run at any time if you need to start the matching over.

The same workflow handles statements with multiple accounts in one PDF, foreign-currency accounts, and personal cards used for company spend. For those odd cases and the bookkeeping detail behind each step, see Bank Reconciliation in the docs.
Always tell us what you think. A wrong journal entry, a match that missed, a confusing screen, or a feature you wish existed — we want to hear all of it. AI features in particular get better the more we learn about where they fall short, so a quick note when something's off is one of the most useful things you can send us.
Open the Report issue / feedback option (the 💬 message icon) from the user menu in the top-right — and from the More menu in the bottom bar on mobile. It opens a short form titled "Report an issue or send feedback" where you pick a category and write a message:
The form quietly includes the page you were on and a bit of technical context so we can reproduce the issue and follow up — you don't have to describe your setup. Tell us what you were doing, what you expected, and what happened instead; a sentence is plenty.
You can also always reach us at samyip@ringbook.io.