Every rupee accounted for.
Client receipts, vendor payouts, transport, labour, materials — one ledger that your team uses daily and your CA can hand to anyone.
Everything the ledger module ships with.
Append-only by design
Entries are never edited in place. Reverse + re-create, with the reversal link visible in the audit trail.
Decimal128 storage
Money lives as Decimal128, not float. Aggregates over ten lakh entries reconcile to the paisa.
Client receipts
Per-stage, per-add-on receipt capture with reference + payment mode + payer name. Branded receipts for the client.
Vendor payouts
Record payments out with FIFO allocation across outstanding vendor bills, all from one screen.
Per-site, per-stage P&L
Live profit/loss at the site, stage, or add-on level — no spreadsheet stitching required.
CSV export
Export the full ledger to CSV any time. Rate-limited (10/hr) so abuse doesn't affect everyone.
What this looks like on a real site.
Your CA asks for the books and you send a folder of Excel files
One ledger covers client receipts, vendor payouts, transport, labour and materials, and it exports to CSV whenever your accountant asks. Because entries are append-only — reversed and re-created rather than edited in place, with the reversal link visible — there is no version of the books that quietly differs from the one you showed someone last month.
The totals are off by a few rupees and nobody can find why
Money is stored as exact decimals rather than floating-point numbers, which is the unglamorous reason aggregates over hundreds of thousands of entries still reconcile to the paisa. Most spreadsheet drift comes from rounding that accumulates invisibly; here the arithmetic is the same on entry one and entry ten lakh.
You want to know if a project actually made money
Profit and loss is live at the site, stage and add-on level, built from the same entries your team is recording daily. Client receipts against each stage roll up as value; bills, labour payroll and material issues tagged to the site roll up as cost. No month-end stitching exercise, and no separate spreadsheet that stops being updated in June.
Ledger, answered.
Can I delete or edit a ledger entry?
Not in place — and that is the point. Reverse the entry and create a corrected one; both stay visible with the reversal link between them. Books you can silently edit are books nobody can rely on, including you when a dispute is about something that happened eight months ago.
Do I still need Tally?
For statutory filing and formal accounting, your CA will most likely keep using it, and that is fine. This is the operational layer they file from — the daily record of what came in and went out, tied to sites and vendors — exported to CSV whenever they need it. See the honest comparison on our Tally page.
Can I export everything?
Yes. The full ledger exports to CSV at any time, in a format your CA can re-import into whatever they use. Exports are rate-limited to ten per hour so one heavy user cannot degrade the system for everyone else, which in practice nobody notices.
Does payroll post to the ledger automatically?
It does. Finalising a payroll run posts one labour-expense entry per person, attributed to that employee and paid from cash or bank. Voiding the run reverses those postings. The same applies to vendor payments and client receipts — the ledger is a consequence of the work, not a second place to type it.