The short version
- You say what happened in your own words. There is no form, and no field order to learn.
- Nothing reaches your books until you confirm the card the app shows you. That gate is the whole design.
- The card is the app's own arithmetic, not a summary of it, so the number you approve is the number that gets written.
- Every entry lands in a double-entry ledger where debit must equal credit, enforced by the database rather than by code.
- Corrections are reversals, not edits. Nothing is quietly overwritten and every write keeps an audit trail.
What you say
A sale, an expense, a purchase, an udhaar entry, a payment received. You say it the way you would say it to a person standing next to you:
- “aaj 12 hazaar ki bikri”
- “Rahul ko 500 ka udhaar”
- “design fee 40,000, GST alag se”
- “Mehta Traders ka bill banao”
There is no form behind this, and no order you have to say things in. You can leave out what you do not know and the app will ask for it. If you would rather type, type. The path is identical either way, which matters more than it sounds: the voice version is not a lesser mode with fewer features.
The card you get back
Before anything is recorded, the app shows you a card: who, what, how much, what tax, which date. Two things about that card are worth knowing.
It is the real arithmetic, not a preview of it. The same code that would write the entry computes what you see, and then stops short of writing. So the total on the card is the total that gets booked. A preview that is calculated separately from the thing it previews is a preview that can disagree with it, and that is the bug this design exists to prevent.
It resolves real things, not guesses. If you say a customer's name, the app looks in your own parties, not at a name it invented. If you say an item, it looks in your catalogue and uses your price and your GST rate. Dates are read in Indian business terms, so “kal” is yesterday relative to your day, not to a server somewhere.
What confirming actually writes
You confirm. Now it is recorded, and what gets recorded is more than one line:
| Where | What lands there |
|---|---|
| The journal | A balanced voucher. Debit equals credit, and the database refuses the write if it does not. |
| The khata | The customer-facing record you actually read day to day |
| Stock | Quantities move, where the entry involves goods |
| Tax | The GST split, which is what the month-end summaries are built from |
| The audit log | What was written, when, and from what instruction |
The balance rule is worth dwelling on, because it is unusual in an app built for owners rather than accountants. Debit equals credit is enforced by a constraint in the database that fires when the transaction commits, not by a check in the application. That means no path can write unbalanced books, including an import, including a correction, including a future feature nobody has written yet.
Changing your mind
Before you confirm, edit the card. Change the amount, the party, the rate, the date. The entry is re-costed by the same tool that would have written it, so an edited card is as trustworthy as an unedited one.
After you confirm, a correction is a reversal and a re-post, not an edit in place. Your books then show what happened and what corrected it, which is what an auditor, a lender or your CA will want to see. It also means nothing you recorded can silently change under you.
The five languages
Hinglish, Hindi, English, Kannada and Telugu. One per merchant, and the choice follows you: the chat, the cards, the errors and every screen speak it.
Paper is treated differently on purpose. A document that leaves your shop for a lender, an auditor or your CA is in English, because that is the language its reader works in. The one exception is the tax invoice, which goes to your own buyer, so it follows your language for Hindi, Kannada and Telugu. Hinglish invoices print in English, because “GRAHAK (BILL TO)” on a statutory document reads as informal to everyone downstream.
What it will not do
Being clear about this is more useful than another feature list.
- It does not file your GST returns. It prepares the documents and the numbers: the GSTR-1 portal JSON, the GSTR-3B and GSTR-9 summaries, the registers. Filing is your CA's job, with their credentials.
- It does not write anything you have not confirmed. There is no silent-capture mode and no background bookkeeping.
- It does not do the arithmetic in the language model. Every number is computed in code and SQL. The model's job is understanding what you meant, not adding up.
Starting
Sign in with your phone number and a one-time code. There is no password. Your books are free, and every business gets 50 free AI credits each month for chat, voice and bill scans. Recharges start at ₹199 for 200 credits, and bought credits never expire. Looking at your books, entering something manually, making an invoice and running reports never use credits.
Try saying one day's sales
Record a day the way you would describe it out loud, and see the card before anything is written. Free to start, no password, no card.
Frequently asked questions
Do I have to speak, or can I type?
Either. The same path runs for both: you get the same confirmation card, the same edits and the same entry. Typing is often easier in a noisy shop, and many people switch between the two in one conversation.
What if it mishears me?
You see the card before anything is recorded, so a mishearing shows up as a wrong name or a wrong number on screen rather than as a wrong entry in your books. Edit the card, or say it again.
Which languages does it understand?
Hinglish, Hindi, English, Kannada and Telugu. One is set per merchant and the whole app follows it, including error messages.
Can I undo something after I have confirmed it?
Yes. A correction is recorded as a reversal followed by a fresh entry, so the books show both what happened and what fixed it. Nothing is overwritten in place.
Does it file my GST return?
No. It prepares what a return is filed from: the GSTR-1 portal JSON, the GSTR-3B and GSTR-9 summaries, and the sales and purchase registers. Your CA files, using their own credentials.
Is my data used to train anything?
Your books are yours. Data export and account deletion are both available from inside the app.