Skip to main content

Glossary

An alphabetical reference for the domain terms used throughout the Vruksha Real Estate ERP. Where a term has a dedicated guide, the entry links to it.

A​

Allocation​

Assigning a quantity of Stock (land or building inventory) to a Project or Subproject. Allocation can be full or partial, and the allocated area can never exceed the available (unallocated) area of the stock. A stock that is fully or partially allocated cannot be deleted. See Allocations and Delete Guardrails.

Amenity​

A feature or facility associated with a subproject — for example a clubhouse, park, road, or unit-level feature. Amenities have a type (Internal, External, Common Area, Unit Feature, or Utility) and can carry custom fields. They may be positioned on an SVG layout as markers.

Audit Log​

A field-level record of who changed what and when. Audit entries capture the action, entity type and ID, old and new values, the acting user, IP address, and timestamp. Create / Update / Delete operations, status changes, holding changes, and sensitive exports are all logged.

B​

Bank Account​

A financial account attached to an entity (party, partner, partnership, organization, and so on). Parties can hold multiple accounts with one designated as the default receipt account. See Bank Accounts.

Buyer​

A Party type representing the purchasing side of a sale. A party can be a Buyer, Seller, and/or Vendor simultaneously.

C​

Custom Fields​

User-defined fields stored as JSONB on certain records (stocks, subprojects, units, documents, and their master types). Each value is an object with a field_name and a value. Supported field types are TEXT, TEXT_AREA, NUMBER, DATE, DROPDOWN, and BOOLEAN.

D​

Discount​

A reduction applied to a sales document's line totals. Discount can be applied per unit or at the order level, and per unit it can never exceed that unit's total rate. Discount is subtracted before tax in the sales calculation.

Document​

A file (PDF, image, Office document, or DWG) attached to an entity, stored centrally with classification by Document Type and optional custom fields. See the Documents guide.

Document Type​

A master classification for documents (for example "Sale Deed", "Encumbrance Certificate"). Document types can define custom fields that apply to documents of that type.

F​

Final Amount​

The net payable on a sales document. Computed as (Grand Total − Discount) + GST − TDS. Paid plus Due always equals the Final Amount. See Sales Calculations.

G​

Grand Total​

The sum of all unit line totals on a sales document, where each line total is rate × area. It is the starting figure for the Final Amount calculation, before discount and tax.

GST (Goods and Services Tax)​

Indian indirect tax added to the taxable amount (Grand Total minus Discount) on a sales document. Stored as a rate and an absolute amount. See Sales Calculations.

H​

Holding​

A partner's ownership percentage in a Partnership, Project, Subproject, Unit, or Stock. Within any single ownership table, all holdings must sum to exactly 100.00%. See Validation Rules.

M​

Managing Partner​

The single partner designated to manage a Partnership. A partnership in Active status requires exactly one managing partner among its active holdings — no more, no less. See Create Partnership.

Masking​

Hiding most of a sensitive value in API responses and on screen, showing only enough to recognize it — for example **** plus the last four characters of a PAN, or •••• plus the last four digits of a bank account number. Sensitive data is masked by default; only users with the right permission can reveal the full value. See Data Security.

Master Data​

Reusable configuration records that other modules reference — location hierarchy, stock categories, amenities, status master, document types, subproject types, unit types, usage tags, and payment schedule types.

Multi-tenant​

The architecture in which every record belongs to an Organization (the tenant), identified by organization_id. Data is isolated per organization so one tenant can never see another's records.

N​

Naming Convention​

An organization-level setting that defines the prefix used to auto-generate identifiers — for example PRJ- for projects, SP- for subprojects, QT- for quotations, SO- for sales orders, SI- for sales invoices. Configured in Settings → Naming Conventions. See Validation Rules.

Notification​

A system-generated alert delivered to users over one or more channels (In-App, Email, SMS, WhatsApp) with a priority of Critical, High, Medium, or Low. See the Notification Catalog and Using Notifications.

O​

Organization​

The root tenant entity. Every user, role, and business record belongs to exactly one organization. Created during sign-up. See Authentication Flows.

Optimistic Locking​

A concurrency-control technique that uses an updatedAt timestamp to detect when a record changed since you opened it. A conflicting save returns a 409 with "This record changed since you opened it." See Validation Rules.

P​

Paid is the net amount received against a sales document — payment receipts minus returns/refunds. Due is the remaining balance, Final Amount − Paid (never below zero). Tracked through the payment timeline. See Sales Calculations.

PII (Personally Identifiable Information)​

Sensitive personal and financial data such as PAN, Aadhaar, GSTIN, email, phone, address, and bank account numbers. PII is masked by default and stored protected; the plaintext is shown only through a permission-gated, audited reveal. See Data Security.

Party​

The unified master for external entities. A party is either Individual or Organization in category, and may carry one or more types: Buyer, Seller, Vendor. Holds PAN, Aadhaar, GSTIN, contact details, bank accounts, and communication preferences. See Parties overview.

Partner​

A business stakeholder (Individual or Organization) who can hold ownership in partnerships, projects, subprojects, units, and stock. Organization partners have a stakeholder breakdown of individual partners with holding percentages. See Partners overview.

Partnership​

A business entity defined by a set of partners and their holdings (which must sum to 100.00%), with a Managing Partner, effective dates, and a status (Draft, Active, Suspended, Closed). See Partnerships overview.

Payment Schedule​

The plan for how a Sales Order is paid. Schedule types include Standard EMI, On Booking, On Agreement, On Registration, On Full Payment, and Manual; the type drives how installments are generated.

Payment Timeline​

The chronological ledger of payments (and returns) recorded against a sales order, stock, or unit. It is the source of truth for the Paid / Due figures.

Project​

A container that maps a Partnership or joint venture to a location and a set of Subprojects and Stock allocations. Identified by a code (default prefix PRJ-). A project with subprojects, units, or allocations cannot be deleted. See Projects overview.

Q​

Quotation​

A pre-sale price offer for one or more Units, with discount, GST, and TDS computed using the standard sales formula. Statuses: Draft, Quoted, Cancelled, Converted. A quotation can be converted into a Sales Order. See Quotations.

R​

RBAC (Role-Based Access Control)​

The two-layer permission model: Organization Roles (exactly one per user, defining system-wide authority) and Subproject Roles (multiple per user, scoped to a subproject). Subproject roles can only add permissions, never restrict them. See the RBAC Matrix.

Return / Refund​

Money paid back against a sales order (a cancellation refund or overpayment return). Returns reduce the net Paid amount and therefore increase the Due. See Sales Calculations.

Reveal​

The permission-gated action of unmasking a sensitive value (or downloading a sensitive file) to see its full plaintext. Triggered by an eye/reveal control; every reveal is recorded in the Audit Log. Only roles holding the matching *_view_sensitive (or file-download) permission can reveal. See Data Security.

Role​

A named set of permissions. Organization Roles include Admin, Partner, Finance Manager, Sales Head, Sales Staff, Project Manager, and People Manager (HR). Subproject Roles include Sales Head, Sales Staff, and Project Manager scoped to a specific subproject. See the RBAC Matrix.

S​

Sales Invoice​

The tax invoice generated from a Sales Order (default prefix SI-), carrying buyer and unit mappings, status and payment timelines, and using the same sales formula. See Sales Invoices.

Sales Order​

The confirmed sale (default prefix SO-). Supports multi-buyer (joint purchases) and multi-unit lines, a payment schedule, and statuses Draft, Active, Completed, Cancelled/Forfeited, Shifted, Split. See Sales Orders.

Seller​

A Party type representing the selling side (typically of stock/land). Seller details on a stock include bank accounts and a payment timeline.

Soft Delete​

The deletion strategy used everywhere in the system: records are not physically removed but marked with a deleted_at timestamp and hidden from normal views. This makes deletions recoverable by an administrator and preserves audit history. See Delete Guardrails and Validation Rules.

Stock​

Land or building inventory tracked through a lifecycle (Wishlist → In Negotiation → Under PO → Advanced → Registered → Partially Sold → Completely Sold), with seller details, area measurements, partner holdings, and custom fields. See Stock Management overview and Stock Lifecycle.

Subproject​

A child of a Project of a given type (for example Layout, Apartment, Villa) with location, partner holdings, area split (saleable / non-saleable), amenities, SVG layouts, and the Units it contains. Default prefix SP-. See Subprojects overview.

Survey Entry​

A stock survey record capturing land survey details — survey number, optional sub-division number, and the mandatory guideline value (the government-notified land value used as a valuation reference). Captured as part of stock data. See Create Stock.

SVG Layout​

A vector floor plan or site map uploaded to a Subproject. Unit boundaries are drawn as polygons and amenities as markers, enabling an interactive, clickable plan. See Layouts and SVG.

T​

TDS (Tax Deducted at Source)​

A tax amount withheld (subtracted) from a sales document's net. Stored as a rate and an absolute amount, and deducted in the sales calculation after GST is added.

U​

Unit​

A saleable item within a Subproject — a plot, flat, villa, shop, or parking space. Has a number (unique within its subproject), type, area, cost, status, shareholder holdings, and boundaries. Unit statuses: Draft, Available, Blocked, Booked, Registered, Cancelled, Frozen. See Units overview and Unit Lifecycle.

Usage Tag​

A label classifying records by lifecycle stage — Planned, Active, or Historical/Closed — used for filtering and reporting.

V​

Vendor​

A Party type representing a supplier of goods or services (relevant to procurement and purchase orders).