Tally is excellent at books. The question is whether you need a second system beside it, or whether one system that does both is now the better arrangement — and that answer has changed.
Tally is a genuinely good accounting and GST compliance tool, and it is deeply embedded in how Indian SMBs handle books, invoicing and tax filing — construction contractors included. Nothing below is a criticism of it. The question is what it was scoped to do, and what it was not.
An update, because this page used to say otherwise. For a long time the honest answer here was "keep Tally for books and add Rebota beside it for the site". That is no longer the arrangement Rebota requires: it now carries its own general ledger, chart of accounts, vouchers and day book, AR and AP, banking, GST return preparation, e-invoicing and a statutory audit trail. The comparison below reflects that, including the one place it still stops short — submitting the return to the GST portal.
Tally has no native concept of a BOQ, a site log, planned-vs-executed quantities, material reconciliation against work done, equipment utilization, or a measurement book. A contractor entering purchase invoices in Tally has accurate books — and zero visibility into whether the cement bought against those invoices matches what the site should have consumed for the work completed.
The two tools solve different layers of the same business: Tally for statutory books, GST returns and financial statements; a construction-specific system for the operational layer — site progress, material and labour cost control, BOQ tracking — that ultimately feeds accurate numbers back into the books. Most contractors running both find the construction layer is what was missing, not a replacement for their accounting system.
| Feature | Rebota | Tally |
|---|---|---|
| General ledger & chart of accounts | Built in | Purpose-built, industry standard |
| GSTR-1 / 3B preparation & 2B reconciliation | Built in | Built in |
| Submitting the return to the GST portal | Prepares and records the ARN; you file on the portal | Direct filing workflow |
| E-invoicing (IRP / IRN) | Built in | Built in |
| Rule 3(1) audit trail | Hash-chained, cannot be disabled | Compliant |
| Your CA already knows the system | Rarely | Universally — a real advantage |
| Works offline / on a local machine | Cloud only | Yes |
| Imports your existing Tally data | XML masters + vouchers, preview then commit | — |
| BOQ tracking | Built in | No native concept |
| Site-level material reconciliation | Built in | No native concept |
| Daily site progress logs | Built in | No native concept |
| Equipment cost & utilization tracking | Built in | No native concept |
| Measurement book (MB) | Built in | No native concept |
| Mobile, field-friendly usage | Designed for site use | Desktop-oriented workflow |
Contractors already running Tally for accounting who have no structured way to track BOQ consumption, site progress, or material reconciliation against what was purchased — i.e., the books are fine, but nobody can answer "what actually happened on site" without calling someone.
A contractor with a single small project, or one whose Tally usage is already minimal (a bookkeeper handles it monthly), likely doesn't have enough operational complexity yet to justify a second system — the reconciliation pain has to actually be felt before the switching effort is worth it.
Tally wins when books are genuinely the whole requirement — no site, no production, no project profitability question you cannot answer. It also wins on two things Rebota cannot match today: your CA already knows it, and it runs locally, which matters where connectivity is unreliable. If all you need is books and filing, Tally alone is the right and sufficient tool and you should not move.
A single project with a small team and low material value can often be tracked in a well-maintained spreadsheet alongside Tally — the case for a dedicated system strengthens with project count and value, not as a universal starting point.
This used to be an "add a layer beside Tally" decision. It is now a genuine either/or: Rebota carries a full ledger, GST return preparation, e-invoicing and a Rule 3(1) audit trail of its own, and imports your Tally data to get there. Whether you should move is a different question from whether you can. If your books work and you cannot name a decision you are unable to make, stay. If the thing you cannot see happens on site, one system that holds both the operations and the ledger is worth more than two that reconcile monthly.
Contractors who run both tools well keep a clean boundary: Tally owns the statutory ledger (GST returns, vouchers, financial statements), and the construction-specific system owns the operational ledger (BOQ, site progress, retention, cash flow timing) that feeds accurate numbers back into Tally rather than being reconstructed from it after the fact. The failure mode to avoid is treating Tally as the source of truth for project profitability — it can only show what was invoiced and paid, not what retention is currently locked up, what a payment delay is costing in financing terms, or whether material purchases match BOQ consumption.
