For a builder with three live projects, Excel stops being the cheaper option once more than one person updates the same sheets, once demands depend on construction progress recorded somewhere else, and once receipts have to be matched to the bank every month. At that point an ERP costs less than the errors, rework and late demands that spreadsheets cause.
Excel is not the problem. It is a superb calculator. The trouble is using it as the record of who bought which flat, what they owe and what they paid, across several projects and teams.
When does Excel still work?
Excel is a reasonable choice when all of these are true:
- one project, or one at a time, with under about 100 units;
- one person owns the sales and collection sheets, and nobody else edits them;
- the payment plan has few stages and demands go out on fixed dates;
- the CA reconciles receipts in Tally at the end of each month.
If that describes you, spend the money on construction, not software.
Six signs you have outgrown it
| Sign | What it costs you |
|---|---|
| Two people hold different “latest” versions of the unit list | A flat sold twice, or a buyer told a sold flat is free |
| Demands wait for someone to email the site’s progress | Days of interest-free credit to every buyer |
| Receipts are matched to the bank only at month end | Bounced cheques counted as collected for weeks |
| Interest on late payment is worked out by hand, if at all | Interest you were owed and never asked for |
| Each project’s sheet has its own columns and formulas | Group-level reports take days and disagree |
| Approvals happen on WhatsApp | No record of who allowed a discount or a cancellation |
What one sign can cost (sample figures)
Say a 7th-slab demand on a sample 120-flat project totals ₹4 crore, and it goes out 15 days after the slab was certified because the progress update sat in someone’s inbox. At a 10% annual cost of funds, those 15 days cost about ₹1.6 lakh: 4,00,00,000 × 10% × 15 ÷ 365. With 15 or so stage demands per project and three projects, a habit of late demands can cost more each year than a software licence. Use your own figures; these are illustrative.
What an ERP changes, and what it does not
An ERP keeps one record of each unit, booking, demand and receipt, shared by sales, accounts and site. A demand goes out when the stage is certified, a receipt updates the buyer’s balance as soon as it is entered, and the interest, ageing and statements come from the same data.
It does not remove work you have not defined. Someone still has to agree the payment plans, the interest rules and the approval limits, and somebody has to clean the existing sheets before they are imported. Budget a few weeks of your team’s time for that, separately from the software.
How to move without stopping sales
- Pick one project to start, ideally one that is mid-construction with live demands.
- Clean the unit list: one row per unit, with tower, floor, carpet area and status.
- Import inventory and bookings, then check totals against the sheet: units sold, booking value, amounts received.
- Set up payment plans and raise the next demand from the system, while keeping the sheet as a check for one cycle.
- Move receipts and bank reconciliation, then stop updating the sheet.
- Repeat for the other projects, which goes faster once the first is done.
Where LoftRay fits
LoftRay imports units from Excel with a preview before anything is saved, keeps inventory, holds, cost sheets, bookings and payment plans in one place, and raises demands from certified construction milestones. Receipts, bounces, interest on late payment and bank reconciliation (CSV, Excel or MT940 statements) feed buyer statements and ageing. Accounts can still be exported to Tally, so your CA keeps working the way they do today.