Real estate ERP glossary.
B
BBA (builder buyer agreement)
The contract between a developer and a buyer that sets out the unit, its price, the payment plan, possession terms and each party’s obligations.
Under RERA the document is formally called the agreement for sale, and it must be registered before the developer accepts more than ten per cent of the unit cost as an advance. It typically records the unit and its area, the total consideration and charges, the payment plan, the possession timeline and the penalties for delay on either side. Because it fixes the commercial terms, it is the reference point for every later payment and demand.
Related module: Post Sales CRM
D
Demand letter
A formal letter asking a buyer to pay an instalment that has fallen due under their payment plan.
A demand letter typically states the milestone or date that triggered the instalment, the amount due with applicable taxes, the due date and the account details for payment. Under a construction-linked plan, demand letters go out as each construction stage is reached. In Proprite, demand letters are generated from the booking’s payment schedule as downloadable PDFs and are visible to the buyer in the customer portal.
Related module: Post Sales CRM
I
Internal indent
A request for material to be supplied from within the company’s own stock rather than bought from a supplier.
Internal indents move material between the company’s own stores or sites — for example from a central store to a project site. They are tracked separately from purchase indents because no new money is committed, but the stock still has to be accounted for at both ends. Proprite’s MIS includes an internal indents report.
Related module: Material Inventory
M
Maker-checker
A control in which one person enters a transaction and a different person approves it.
Maker-checker, also called four-eyes approval, reduces both errors and misuse because no single person can create and approve the same entry. It is common in purchasing, bill processing and payments. In Proprite, purchases, bills and contractor work are approved by someone other than the person who entered them — for example, the store enters supplier bills and the purchase manager approves them.
Related module: Purchase Management
Material indent
A request raised by site for material it needs from the store, with the quantity and the date it is required.
An indent is how site tells the store what it needs and when. The store issues against it from available stock, and any quantity it cannot cover becomes a requirement for purchase. In Proprite, site engineers raise indents with material, quantity, required date and priority, and the store cannot issue more than was requested or more than is available.
Related module: Material Inventory
MIS (management information system)
The set of reports management uses to see sales, collections, cost, stock and cash across projects.
Good MIS is built from the records teams already keep, not from spreadsheets assembled at month end. For a developer, it typically covers what has been sold, what is due, what the build is costing against plan, what has been ordered and issued, and cash in hand. Proprite includes sixteen MIS reports drawn from bookings, payments, activities, NMR, indents, purchase orders, bills and petty cash.
Related module: MIS
N
NMR (nominal muster roll)
A daily record of the labour present on site, used to calculate daily labour cost.
NMR records headcount by category — typically male workers, female workers and masons — for each day. Labour cost for the day is the headcount multiplied by the labour rate for each category. In Proprite, NMR is recorded in Project Scheduling and MIS compares NMR actual against expense.
Related module: Project Scheduling
P
Payment plan
The schedule on which a buyer pays for a unit, set out as instalments against milestones or dates.
In a construction-linked plan, instalments fall due as construction reaches stages such as foundation or each slab. In a down payment plan, most of the price is paid upfront, often in return for a lower rate. In a time-linked plan, instalments fall due on fixed dates regardless of construction progress. In Proprite, each booking carries its own payment schedule generated from the chosen payment plan.
Related module: Post Sales CRM
Petty cash
A small cash float issued to a person on site or in the office to pay for minor day-to-day expenses.
Petty cash covers small, frequent costs such as local transport, minor repairs or consumables that do not justify a purchase order. It needs to be issued against a named person and every expense recorded against the float. In Proprite, Accounts issues cash to a cash manager who records expenses against it, and the petty cash balance cannot become negative.
Related module: Accounts
PLC (preferential location charges)
An extra charge added to a unit’s price for a location buyers value more, such as a higher floor, a park or road facing, or a corner position.
PLC is usually quoted per square foot or as a fixed amount, and it is added on top of the base rate. Developers often define several PLC types for a project — for floor, for facing and for corner units — and apply whichever fit a given unit. In Proprite, PLC for floor and facing is defined at project level alongside rate plans and payment plans.
Related module: Post Sales CRM
Post-sales CRM
The part of customer relationship management that begins once a buyer is ready to block or book a unit.
Post-sales CRM covers inventory, pricing, bookings, payment schedules, receipts, demand letters, customisations, documents and buyer support up to possession. It is different from pre-sales CRM, which deals with leads, enquiries and site visits. Proprite’s Post Sales CRM starts at blocking and booking; it does not include lead management.
Related module: Post Sales CRM
Project-level access
Access control in which staff are granted access to specific projects, not only to functions.
Role-based access decides what a person can do; project-level access decides where they can do it. Together they mean a site engineer on one development cannot see the store or collections of another. In Proprite, staff are assigned to specific projects, and people who work across several use a project switcher to move between them.
Related module: Administration
Purchase order
A formal order issued to a supplier that commits the buyer to the items, quantities, rates and terms agreed.
The purchase order, or PO, is the reference against which delivery, inspection, the supplier’s bill and payment are all checked. For that reason its values should not change quietly after it is issued. In Proprite, a PO is raised from the selected quotation and its values are locked once issued.
Related module: Purchase Management
Q
QC gate
A point in the workflow that work or material cannot pass until its quality inspection has been approved.
A QC gate turns an inspection from a record into a control. If a required check fails, the next step stays closed until the problem is corrected and re-inspected. In Proprite, a failed required check blocks approval with no override, dependent activities wait for QC to pass, and delivered material becomes stock only after QC passes.
Related module: Quality Control
Quantity of work
The measured amount of work executed on site, such as cubic metres of concrete or square metres of plaster.
Quantity of work is how progress is measured in physical terms rather than as a percentage estimate. Comparing executed quantities with planned quantities shows whether an activity is on track, and measured quantities are the usual basis for paying contractors. Proprite tracks quantity of work in Project Scheduling and reports it in MIS.
Related module: Project Scheduling
R
Real estate ERP
Software that runs the operations of a property development — sales, procurement, site, stores, accounts and reporting — in one connected system.
ERP stands for enterprise resource planning. In real estate, the resources are units, money, material, labour and contractors, and the output is a building. A real estate ERP links the departments that manage them so that each team works from the same records rather than its own spreadsheet. It usually sits alongside, not in place of, statutory accounting software.
RFQ (request for quotation)
A request sent to suppliers asking them to price a defined quantity of material or service on stated terms.
A clear RFQ names the item and specification, quantity and unit, delivery location and date, and the terms expected — such as credit period, freight and how taxes are shown. Sending the same RFQ to several suppliers makes their quotations comparable. In Proprite, RFQs are raised from purchase requirements and supplier quotations are compared side by side, with the supplier selected by a person on your team.
Related module: Purchase Management
U
Unit blocking
Holding a unit for a prospective buyer for a limited period so that it cannot be sold to anyone else in the meantime.
Blocking gives a buyer time to arrange a booking amount or finalise a decision without the unit being booked by someone else. A block should always carry an expiry, otherwise units sit unavailable long after interest has gone. In Proprite, a block has an expiry date and the unit returns to available automatically if it is not booked in time.
Related module: Post Sales CRM
See how Proprite fits your project workflow.
Walk through Proprite using the workflows your team already manages — your towers, your payment plans, your approval chain.

