Capture anything
A photo, a Drive folder, a bank CSV or a call to the API.
Bangladesh and Australia, built first
Bookkeeping, done
A receipt becomes a balanced ledger entry in five seconds. Nothing posts without your confirm. Your accountant sees lender-grade books, every day of the year.
Sold by demo. A person shows you the product, then prices it with you.
Built on rules, not promises
Not a customer count. Four properties the software enforces, every build, whether anyone is watching.
The whole thing
Capture, confirm and report. Every tile below is a real surface in the product, not an illustration of one. Submitting the return is still yours: nothing here files anything on your behalf.
A photo, a Drive folder, a bank CSV or a call to the API.
In and out on the surface. Debit and credit one tap deeper.
VAT and GST accrue as you confirm, so the figures are ready before the deadline.
Rules are dated configuration. A 2026 entry is judged by 2026 rules.
The public API and an MCP server post to the same engine.
Hash-chained, append-only, and yours to export any day.
The moment it earns its keep
Every other ledger either makes you type it or quietly guesses for you. Violet means a machine read it and it is outside your totals. Green means you said yes. That line is the whole product, and nothing crosses it on its own.
Drafted, scored, and out of every total until confirmed.
One tap. Recorded under your name, in a trail nobody can rewrite.
Corrections are reversing entries. Nothing is ever hard deleted.
The problem
Every small business already knows what it earns and what it spends. The work is writing it down, in order, forever.
A drawer of paper, a phone full of photos and a bank app in another tab. Nothing adds up until someone sits down and types it all in.
By the time the ledger is current the decision has already been made. You run the business on a feeling, then find out in April whether the feeling was right.
VAT and GST get worked out at the deadline, from paperwork that was never sorted for it. The number is a shock and the evidence is a scramble.
A lender or an auditor asks where a figure came from. The trail is a spreadsheet, a WhatsApp thread and a memory.
How it works
Photograph the receipt, connect a Drive folder or drop in the bank CSV. The amount, the party and the tax are read for you.
The draft arrives violet. Check it, tap once and it settles green. Nothing reaches your books without a person saying yes.
Balances, tax owed and every report move the moment you confirm. Month end is a page you open, not a week you lose.
Confirmation
Every machine-drafted entry stays violet until you confirm it. One tap and it settles green in your books. There are no silent guesses and no cleanup mornings.
Undo beats confirm. Corrections are written as reversing entries, so nothing is ever hard deleted and every number keeps its history.
What has landed
Each card is tied to the product map in the repository. It says landed only when every row behind it is ticked with its evidence and reviews. Until then it says coming and counts what is in.
The Mushak registers and returns print from confirmed postings, a treasury challan is prepared from the books and recorded by its number once you have paid it, the filings hub shows due, prepared, deposited and filed for every period and the deduction certificates print with the deposit behind them.
A cash book for every drawer and wallet with opening, receipts, payments and closing by day, a petty cash tin with a float and a custodian, a count by denomination whose difference posts to cash over and short and a reconcile screen that proposes matches against your bank lines for a person to confirm.
Lock a month or a year from settings, close the year into retained earnings in one entry, bring opening balances in from a CSV and hand an auditor one bundle with every report, voucher, invoice, bill and deposit, its source documents and the audit chain verified.
Tags on every posting, budgets with approvals and a variance report, management adjustments that stay out of every statutory report and a bridge that shows exactly how the two views differ. One journal, never a second set of books.
Every figure you are asked to act on shows the evidence it was read from, the rule that decided it and a method line a shopkeeper can read. Tax sources are watched, so a change in the law becomes a proposal a person accepts and never a silent update.
What your books use is metered and your billing screen shows the month's lines before anything is charged, so a figure you are asked to pay is one you can check against what happened. What the product costs is agreed with you when it is sold and never changed quietly.
Invoices, quotations, receipts and supplier bills on your own letterhead, each numbered from its own series, a PDF beside every print button and a payables view that says who you owe and since when.
Capture from the camera, the share sheet or a bank SMS, then review, invoices, cash, reports and filings from a pocket, on a device paired to a person so every action names who did it. It arrives as an app in the stores.
Employees, salary structures and monthly pay runs that will post one balanced entry, tax deducted at source by the method the Act prescribes, payslips on your letterhead and the salary deduction certificate with its deposit attached.
How it is sold
LedgIQ is a full bookkeeping product for a business, not a tool you pick a tier for. So there is nothing to buy on this site and no plan to choose. You ask for a demo, a person shows you the product on the kind of books you keep, and what it costs is settled with you afterwards on what you actually need.
Questions
No. The screens show money in and money out, in your own currency. The double-entry is underneath, correct and ready for your accountant, and it is always one tap away if you want to look.
You catch it before it counts. Machine-drafted entries stay violet and stay out of your totals until you confirm them. If a mistake does get through, the fix is a reversing entry, so the original stays visible and the history stays honest.
No. Nothing in your books is used to train a model. Retention is a separate question and the answer differs by path, so both are stated: a photographed receipt is read inside the same account that already stores it and no copy is kept anywhere else, while a question you type into the chat goes to OpenAI, which retains request content for abuse monitoring under its standard terms because we hold no zero-retention agreement with them. Phone numbers, email addresses, tax ids and the party names your books already know are replaced with placeholders before either call. The trust page sets out the whole of it.
Bangladesh and Australia today, each with its own chart of accounts, tax rules and filing calendar. Rules are versioned and dated, so a 2026 transaction is judged by 2026 rules even after the rates change.
Yes. Invite them with an accountant role and they get the books and the review queue without your billing or your business settings. Every confirmation is recorded under the name of whoever made it.
Any day, without asking us. One API request returns your entries, your document records and your audit trail. The document files themselves are not in the bundle yet and the trust page says so plainly. Books you cannot leave with are not really yours.
Then the capture has to wait. We would rather say so than let a receipt go missing between the shop and the books. The offline queue that holds an entry on the phone and posts it when the network returns is designed and not built, so today a capture needs a signal.
The one way in
Ask for a demo and a person walks you through the product on the kind of books you keep, with your country rules already loaded. You are not buying anything on this page: nothing is charged, no card is asked for and no account is created.
Request a demo