The bahi khata, kept by the app: every bill and every payment against the party who owes it, with the balance always standing at the bottom.
A paper khata answers one question well — what does this person owe me — and nothing else. The entries are written by hand, so they drift from the bills, and the total is only as good as the last time somebody added it up.
Here the ledger is a consequence rather than a chore: raising a bill writes to it, recording a payment writes to it, and a return corrects it. The party page shows the running balance, the statement behind it can be shared as it stands, and nothing has to be added up twice.
The invoice posts to their ledger as it is saved.
Record it against one bill or several; the balance moves.
The party page carries the running figure, not a total to compute.
Share the ledger as it stands when they ask what is outstanding.
The money side of the business: what has been billed, what has been collected, what is still owed, and what the tax on all of it comes to. Party ledgers sit at the centre — every bill and every payment lands on somebody’s khata, and the balance there is the number you act on.
Most of this area runs on its own once bills are being raised: ledgers update as you bill, reminders go out on their due dates, and the GST reports are built from what is already recorded.
The parties themselves, the money moving against them, and the chasing that follows.
Party-wise ledger · Parties statements · Party-wise outstanding · Receivable ageing · Party-wise profit and loss
Every feature, by plan →No. Bills and payments post to the party’s ledger as they are saved, so the khata is a result of billing rather than a second job.
Yes — the statement can be shared from the party’s page as it stands.
Yes. Purchases post against the supplier the same way, so what you owe sits beside what you are owed.
The balance is right because the bills wrote it, not because somebody remembered to.
