Project and unit inventory, a deterministic price build-up, bookings, an installment engine, brokers and a collection desk — sitting directly on double-entry, GST-ready books instead of a spreadsheet beside them.
A development business runs on two records that rarely agree: the sales sheet that says which unit is booked at what price, and the books that say what was actually collected. LekhaPro closes that gap with a property-developer edition on its Cloud Suite — project, tower, floor and unit inventory; a deterministic price build-up so the same unit quotes the same number to every executive; bookings, an installment engine and demand schedules; broker and channel-partner records; and a collection desk that ages every receivable against the unit it belongs to. Because all of it posts into the same double-entry General Ledger that carries GST invoicing, e-invoice IRN and QR, and the full report set, the sales pipeline and the balance sheet stop being two versions of the truth. On the construction side, the same books carry project costing, supplier payables and contractor billing, and where a site needs software that keeps working on a bad line, we build the offline-first field layer around it.
The GST accounting platform behind this stack — its Cloud Suite ships a property-developer edition with unit inventory, price build-up, bookings, installments, brokers and a collection desk over one double-entry ledger.
Everything between listing a unit and banking the last installment — inventory, pricing, bookings, brokers, collections and costing, over one set of books.
Every project, tower, floor and unit in one live register — carpet and saleable area, facing, status and hold, visible to the whole sales floor at once.
A deterministic price build-up — base rate, floor rise, PLC, parking, amenities, statutory charges and taxes — so the same unit quotes the same number to every executive.
Convert a hold into a booking, capture the customer and agreement, and let the installment engine schedule milestone or time-linked demands automatically.
Register channel partners, attribute each booking to the source, and track commission from slab to payout without a parallel reconciliation exercise.
A single desk showing what is due, what is overdue and against which unit — with receipts, follow-up history and ageing that ties straight back to the ledger.
Track project cost heads, supplier payables and contractor billing against the same books, with an offline-first field layer where the site has no reliable connection.
Load the inventory, fix the pricing logic, run bookings and demands, then work the collection desk — with the ledger updating on every step.
Set up the project, tower and floor hierarchy, import the unit schedule with areas and attributes, and open the books.
Configure base rate, floor rise, PLC, parking, amenity and statutory heads with discount approval rules, so every quote is reproducible.
Convert holds into bookings, capture agreements, and let the installment engine schedule milestone or time-linked demand letters.
Work the collection desk against ageing, receipt and reconcile the money, and read margin per project off the same ledger.
The workloads our platforms are engineered to handle — from first deployment through enterprise scale.
Residential Developers
Designed so project, tower, floor and unit status is a single record rather than a shared spreadsheet — holds, blocks and releases visible to every executive at the moment they happen.
Unit-level live statusPlotted & Township Projects
Built around a demand schedule engine that generates time-linked or milestone-linked installments, prints demand letters, and ages what has not arrived against the plot it belongs to.
Scheduled demand generationChannel Sales Operations
Designed to attribute each booking to its channel partner and carry commission from slab rule to payout milestone with TDS handling, instead of a reconciliation months after the sale.
Source-attributed commissionsContractors & Project Builders
Built to post material purchases, supplier payables and contractor billing into the same double-entry ledger as revenue, so budget versus actual is a report rather than a quarterly assembly job.
Budget versus actual by projectCommon questions about our real estate & construction solutions.
Yes — as a property-developer pack on the LekhaPro Cloud Suite. It covers project and unit inventory, a deterministic price build-up, bookings, an installment engine, brokers and a collection desk, all posting into the same double-entry ledger as the rest of the product. The industry packs are a Cloud edition capability; the offline-first Windows Desktop edition carries the accounting, GST and inventory core but not the packs.
The Desktop edition runs fully offline on Windows against a local database — the right choice for a single office that must keep working with the network unplugged. The Cloud edition runs the same GST and accounting engine in a browser with multi-user access, roles, approvals and an audit trail, and it is the edition that carries the real estate and construction packs. For a developer with a sales team, a collection desk and site staff, Cloud is usually the fit.
Both. The installment engine schedules demands either against construction milestones — on excavation, on slab, on possession — or against fixed dates, generates the demand letters, and then ages whatever has not been received against the specific unit and customer on the collection desk.
Channel partners are registered as party records, each booking carries its source attribution, and commission is computed from slab rules with payout milestones and TDS handling. Because it posts into the ledger like any other payable, the commission liability shows up in the books at booking time rather than surfacing at reconciliation.
The GST engine underneath is the same one the rest of LekhaPro uses — CGST/SGST/IGST with CESS, e-invoicing with IRN and QR, e-way bill JSON, and GSTR-1/3B/9 filing with 2B reconciliation. It generates the e-invoice JSON from your own data; pushing it to the portal live needs your own GSP connection, and no return is filed on your behalf. Rate and scheme selection for a given project stays a decision you and your consultant make.
That is a custom build alongside the books. Our desktop and mobile practice is offline-first by default — local storage, full functionality with zero connectivity, and deferred sync that reconciles when the connection returns. For a site office or a field team on an unreliable line, we build the capture layer that way and let it feed the ledger once it is back online.
Tell us how many projects and units you are carrying, how your payment plans are structured, and where the sales sheet and the ledger currently disagree. We will map the rollout from there.