Frequently Asked Questions
Common questions about multi-tenancy, data isolation, billing, and onboarding.
Strictly No. Every society is an isolated tenant. All database records (residents, properties, bills, payments, complaints, and documents) are bounded by foreign keys to
society_id and verified through server-side authenticated user memberships. Client-supplied IDs in URLs or form parameters cannot breach tenant isolation.
When paying for their SaaS software subscription, society administrators can select Bank Transfer, view our bank credentials (Meezan Bank Ltd), enter the deposit reference number, and upload their payment slip. The transaction remains in a Pending Verification state until a Platform Super Admin reviews the proof and formally approves it. Only then is the SaaS invoice marked as Paid.
Yes! Each housing society can configure their primary, secondary, and accent colors, upload an official emblem logo, and customize official invoice/receipt headers and footer notices. These brand styles appear dynamically in the admin dashboard, resident portal, and printable PDF documents.
Yes, they are completely separate financial systems. SaaS subscription billing is the software license fee paid by the housing society to the SaaS platform owner. Resident maintenance billing is the monthly charge collected by the society from its own residents for security, clean water, and upkeep. They use separate database models, separate sequential numbering, and distinct accounting ledgers.