Property Management

Design: 1) Charge Engine: Each property has a charge schedule derived from the lease. Base rent + recurring charges (CAM, parking, utilities) are auto-generated monthly. Support different frequencies (monthly, quarterly, annual). Handle escalation types: fixed amount, percentage, CPI-linked. Multi-currency support for international portfolios — store amounts in base currency with exchange rate at invoice date. 2) Payment Processing: Accept multiple methods: ACH/bank transfer (lowest cost, 2-3 day settlement), credit card (2.5-3% fee — landlord decision whether to absorb or pass through), UPI/NEFT in India (instant settlement). Payment matching: auto-match by amount and tenant reference. Partial payment handling: apply to oldest charges first (legally important). Overpayment creates credit on account. 3) Data Model: Lease → ChargeSchedule → [MonthlyCharge]. MonthlyCharge = {leaseId, chargeType, amount, currency, dueDate, status}. Payment = {tenantId, amount, method, referenceNo, receivedDate}. PaymentAllocation = {paymentId, chargeId, allocatedAmount}. Each property has its own GL and bank account for reconciliation. 4) Late Fee Logic: Configurable per lease/property: grace period (typically 5 days), flat fee or percentage, maximum cap, waiver rules. Some jurisdictions limit late fees (e.g., California: 6% of rent). Store jurisdiction rules as configuration. 5) Reconciliation: Daily bank feed import. Auto-match payments by amount + reference. Exception queue for unmatched items. Monthly close: verify all charges posted, payments allocated, late fees assessed. 6) Scale: For 10,000+ units: batch charge generation overnight (cron job at 12 AM on 1st). Payment processing via message queue (SQS/Kafka) for reliability. Idempotency keys prevent duplicate charges. Audit trail for every financial transaction.

Architecture: 1) Sensor Layer: HVAC sensors (temperature, humidity per zone), occupancy sensors (PIR, desk sensors), energy meters (per floor/tenant), water meters, elevator status, parking sensors, air quality (CO2, PM2.5). Protocols: BACnet (HVAC), Modbus (energy meters), Zigbee/BLE (occupancy). Edge gateway in each building aggregates and normalizes data. 2) IoT Platform: MQTT broker (Eclipse Mosquitto or AWS IoT Core) for sensor data ingestion. Time-series database (InfluxDB or TimescaleDB) for storage — handles 10,000+ data points per minute per building. Stream processing (Apache Kafka Streams) for real-time alerts: temperature out of range, water leak detected, elevator fault. 3) Integration with PMS: Auto-create maintenance work orders when anomaly detected (e.g., HVAC compressor vibration abnormal → preventive maintenance WO). Occupancy data feeds into space utilization reporting — show landlord which floors are underutilized. Energy consumption data drives tenant utility billing (submetering). Access control events update visitor logs in tenant portal. 4) Tenant Benefits: Real-time temperature control via app (tenant adjusts their zone). Meeting room booking with actual occupancy validation (no phantom bookings). Indoor air quality dashboard. Energy consumption visibility (gamification: 'Your floor used 10% less energy this month'). 5) Analytics: Predictive maintenance: ML model trained on equipment sensor data predicts failure 7-14 days in advance. Energy optimization: AI learns occupancy patterns and pre-cools/heats based on predicted demand. Space utilization: heat maps showing desk/floor usage patterns — inform lease decisions. 6) Cost-Benefit: Smart building systems reduce energy costs 15-30%. Predictive maintenance prevents 40% of emergency repairs. Tenant satisfaction (NPS) improves by 20+ points. Premium rent justification: 10-15% rent premium for smart buildings.

Mixed-use properties (e.g., a complex with office floors, residential apartments, and ground-floor retail) require a flexible data model: 1) Property Hierarchy: Portfolio → Property → Building → Floor → Unit. Each unit has: type (commercial, residential, retail), area (carpet, built-up, super built-up), status (vacant, occupied, under renovation). Building can have mixed types — floor 1-2 retail, 3-10 office, 11-20 residential. 2) Lease Differences by Type: Commercial: longer term (3-9 years), rent per sq ft, CAM charges, fit-out period, lock-in period, rent-free period, escalation clause (typically 15% every 3 years). Residential: shorter term (11 months in India — to avoid registration), security deposit (2-10 months), maintenance charges, society rules. Retail: base rent + percentage rent (% of tenant's revenue above threshold), footfall data sharing, signage rights, exclusive use clause (no competing tenant). Each type needs different lease templates and charge calculations. 3) Common Area Management: Shared spaces (lobby, parking, elevators, gardens). CAM allocation formula: proportional to leased area, or fixed by unit, or tiered by type. Commercial tenants may pay higher CAM rate (24/7 AC, dedicated lifts). Retail CAM includes marketing fund contribution. 4) Accounting Separation: Each property type may have separate P&L for investor reporting. Revenue recognition differs: commercial (straight-line rent), retail (variable rent). GST/tax treatment varies by type in India. REIT regulations require segmented reporting. 5) Unified Tenant Experience: Single portal for all tenant types but different features: commercial tenants see office booking, visitor management, parking. Residential tenants see maintenance requests, society notices, amenity booking. Retail tenants see footfall analytics, revenue reporting. 6) Example Schema: Property {id, name, address, type: MIXED_USE, totalArea}. Unit {id, propertyId, floor, unitNo, type: COMMERCIAL|RESIDENTIAL|RETAIL, area, status}. Lease {id, unitId, tenantId, type, startDate, endDate, terms: JSON (flexible per type)}. ChargeSchedule {leaseId, chargeType, amount, frequency, escalation}.

Indian housing societies have unique requirements: 1) Society Structure: Under state Cooperative Societies Act or RERA. Managing Committee (elected annually). Members (flat owners), tenants (if owner rents out). Society has its own bank account, auditors, AGM requirements. 2) Key Modules: a) Member Management: Owner directory with unit details, family members, vehicles, staff (domestic help). Tenant NOC (No Objection Certificate) workflow — owner requests, committee approves. RERA registration and compliance tracking. b) Billing: Monthly maintenance = fixed charge + area-based charge + sinking fund + parking + water. Support for different billing slabs (different rate for different flat sizes). Interest on late payment (per bye-laws). Special assessments for one-time expenses (painting, lift replacement). c) Accounting: Society-level accounting with proper books (cash book, ledger, trial balance). Fixed deposit management (sinking fund typically in FD). Audit-ready reports per state Cooperative Act requirements. GST if society maintenance exceeds ₹7,500/month per member. d) Communication: Notice board (digital), circular distribution via app. AGM notice (mandatory 14 days before), voting (proxy voting support). Complaint management and resolution tracking. e) Facility Management: Amenity booking (clubhouse, guest room). Visitor/delivery management with OTP-based entry. Domestic staff in/out tracking. Parking allocation and enforcement. 3) Compliance: RERA registration number displayed. Maintain proper books per state cooperative act. Annual audit and filing. GST registration and monthly filing if applicable. Property tax payment tracking. Fire safety and lift inspection compliance. 4) Tech Stack: Mobile-first (most society members use phone). WhatsApp integration (meeting notifications, payment reminders). UPI payment (BBPS for society maintenance). Digital signature for NOCs and resolutions. 5) Platforms: myGate (visitor management + billing), ApnaComplex (full society ERP), ADDA (Asia-Pacific society management), NoBrokerHood (society management).

ASC 842 (US GAAP) and IFRS 16 (international) fundamentally changed how leases appear on balance sheets. Property management systems must handle both sides — landlord (lessor) and tenant (lessee): 1) Key Change: Previously, operating leases were off-balance-sheet (just expense in P&L). Now, lessees must recognize a Right-of-Use (ROU) asset and lease liability for virtually all leases > 12 months. 2) Lessee Accounting: At lease commencement: ROU Asset = Present Value of future lease payments. Lease Liability = Same PV amount. Discount rate: incremental borrowing rate (IBR) or rate implicit in lease. Monthly: amortize ROU asset (straight-line), reduce lease liability (effective interest method). For variable payments (CAM, % rent): expense as incurred (not in ROU/liability). Modifications: remeasure liability if terms change (rent increase, extension, early termination). 3) Lessor Accounting: Less change than lessee side. Classify as operating or finance lease. Operating lease: recognize rent income straight-line. Finance lease: derecognize asset, recognize net investment. Most commercial property leases are operating leases for lessor. 4) PMS Impact: a) Lease Data: System must capture all lease terms precisely — base rent, escalations, options (renewal, termination, purchase), variable components, tenant improvement allowances, lease incentives. b) Calculations: Present value engine with configurable discount rates. Handle complex escalation patterns (fixed, CPI-linked, market reset). Modification accounting (partial termination, blending). Transition calculations (on adoption date, grandfather existing leases). c) Reporting: Balance sheet: ROU asset schedule, lease liability roll-forward. P&L: lease expense (amortization + interest), variable lease cost. Cash flow: separate principal (financing) vs interest (operating or financing). Disclosure: maturity analysis of lease liabilities by year. d) Volume: A large corporate tenant may have 10,000+ leases globally. Each with different terms, currencies, modification history. Portfolio-level reports for auditors. 5) Data Model: Lease → LeaseComponent (separate land, building, equipment). Component → PaymentSchedule (base rent, escalation, options). LeaseAccounting {componentId, commencementDate, rou_asset, lease_liability, discount_rate, classification}. MonthlyJournal {date, dr_account, cr_account, amount, type: AMORTIZATION|INTEREST|VARIABLE}.