Property & Strata,
considered.

PROPSERVA is built by VYROX INTERNATIONAL SDN BHD in Malaysia and powered by VYROX AI — the AI that specializes in business operation management together with IoT. It is purpose-built for property managers, JMB / MC committees, hotel and Airbnb operators who run residential or commercial buildings.

Yes. E-invoicing for LHDN MyInvois is built into the accounting module — including consolidated, recurring and rental invoices, with sandbox and production environments and full credit-note support.

MIFARE-compatible RFID smart-card readers, generic IP cameras (HTTP snapshot & event ingest), brand-agnostic face-recognition cameras (SmartFACE), LPR/ANPR cameras (SmartVE), smart intercoms (SmartINTE), lift relays, parking-lock controllers, smart lighting and power monitoring, smart mirrors with secure access code access requests, and delivery lockers. Device crypto uses the SM4 cipher.

Yes. JMBs, MCs and management firms can run multiple properties under one account with strict data isolation and cross-property reporting at the firm level.

Custom per-property monthly subscription scaled to units and modules. Free demo and trial period; no setup fee for standard SKU. Speak with Patrick on +60 19-688 3338.

Production data is hosted in Singapore with daily off-site backups and point-in-time restore. TLS in transit. Role-based access with full audit trail.

Most properties go live in 4–5 weeks. Week 1 is discovery and data import; week 2 is configuration and training; weeks 3–4 are AIoT pairing and soft launch; week 5+ is full cutover.

Invoices are built as UBL 2.1 JSON payloads and submitted directly from the accounting module to LHDN MyInvois in real time. PROPSERVA validates TIN, applies the MSIC industry-code list, supports consolidated and recurring invoices and credit notes, generates a sharing URL on success, and falls back to a walk-in buyer TIN where required. Validation failures surface back to the operator with the underlying LHDN error code.

Yes — the documented REST endpoint surface is in our developer API reference, covering visitors, EV charging, sub-accounts, announcements, invoices, payments and access events. Bearer-token authentication.

Yes. Bulk imports for customers, units, contracts, opening balances and historical invoices are part of week-1 onboarding. CSV templates are provided; Patrick’s team validates and loads them for you.

Yes. Four role-specific web-based mobile apps (Progressive Web Apps / PWAs, not native): a customer/resident app, a staff app, a security/guard app and a delivery courier app. All read and write the same ledger.

Face templates are stored encrypted with purpose-limitation tags and explicit retention windows. Resident consent is captured at enrolment, and data subjects can request deletion. The platform is PDPA-aligned.

Either. PROPSERVA can be your primary GL, or it can sync to Autocount via the hosted VYROX-AutoCount-Connector middleware (Bearer-token auth) — supporting invoice, payment, cancel and undo flows for firms that already standardise on Autocount.

Both. The pricing bands cover small (<100 units), mid (100–1,000) and large (1,000+) deployments. PROPSERVA scales from a walk-up of a few dozen units to a multi-tower estate of several thousand — the data model is identical; only the property-availability toggles (feature flag[]) differ.

Each unit carries its property number, build-up area in square feet, share unit (which drives the maintenance apportionment), reserved and non-reserved parking lots, and bedroom and bathroom counts. The register is the spine the billing engine reads when it raises maintenance and sinking-fund charges.

The GL statement filters by processing, posted, unposted, customer deposits, customer advances, refund-requested, refund-approved and refunded. Every entry shows debit, credit and a running balance, and the period totals reconcile — the figures are tabular SQL aggregations, not estimates, and export to PDF or Excel.

Yes. The statement of account summarises total billed, total collected, balance outstanding and collection rate for the period, breaks revenue down by service line (maintenance, sinking fund, water, late-payment interest, bookings, access cards) and reports arrears in aging buckets (current, 1–30, 31–60 and over 60 days). It exports to PDF and Excel for the council pack.

Yes — via Xendit. Confirmed payment methods in the codebase are QR, credit/debit card and Direct Debit, with auto-retry, refunds and webhook reconciliation against the originating invoice.

The platform queues the invoice, surfaces the LHDN error code with a plain-English description, and allows the operator to fix the underlying record (TIN, classification, item code) and resubmit without re-issuing the invoice number.

Yes. Invoice templates support estate branding, multiple footers and JMB/MC particulars. Reports are exportable to PDF and Excel; custom report development is available on enterprise plans.

A resident pre-registers a guest from the app, picking arrival window and vehicle plate. The platform issues a QR pass to the guest by email (our email service). At the gate, the guard scans the QR — the guest is cleared in seconds.

Yes. PROPSERVA exposes a REST API for customers, units, invoices, payments and access events.

It is a single auditable workspace: a left sidebar (Operation Insights, Security Monitor, Customer Accounts, Cash Book, a General Ledger group with Customer Advances / Deposits / Payments / Refunds / Invoice Adjustments / Revenues, then Reports and Suppliers), a title bar with a date-range selector and a New Invoice action, an Invoices ledger showing No., Issued On, Due Date, Document No., the charge item, Payable, Paid and Balance, filter tabs for Unpaid / Paid / Overdue / Outstanding / Deposits, and a Things-to-Do queue summarising current balance, overdue and outstanding invoices, opening deposits, payments pending verification and deposit-refund requests. Every list exports to PDF and Excel. The figures are computed by tabular SQL (balance = payable minus paid), not predicted.

Yes. PROPSERVA serves Malaysia, Singapore, Indonesia, Thailand, Vietnam and the Philippines. MyInvois compliance is Malaysia-specific; the rest of the platform is region-neutral.

Best-effort availability monitored internally 24/7. Maintenance windows are announced in advance and run in low-traffic hours. Incident communications go via email (our email service). To reach Patrick directly, WhatsApp him on +60 19-688 3338.

Onboarding includes 2–3 hands-on training sessions for staff. Resident rollout uses a templated launch kit (notices, QR posters, app-download cards). Patrick remains on WhatsApp throughout.

Yes. We have run migrations from at least nine common Malaysian property and JMB platforms. Export your customer master, unit register, contracts, opening balances and outstanding invoices in CSV; we map the columns to PROPSERVA, run a parallel reconciliation for one billing cycle, and only switch the master record once the numbers tie out exactly.

PROPSERVA is engineered around PDPA (Malaysia) but uses the same purpose-limitation, retention-window and right-to-erasure machinery that GDPR requires. For European data subjects we can document the lawful basis, run subject-access requests through a published workflow, and execute deletion within 30 days. Cross-border transfers are off by default.

Audit logs are retained for the life of the contract. They are queryable in-app and exportable to CSV or JSON on demand.

Hardware procurement (cameras, readers, locks); on-site installation labour; bespoke integration development; and on-site Patrick visits beyond the 4-week rollout. Each is available as a clearly priced add-on. The software, hosting, support and standard integrations are all in the base subscription.

Yes — at any time, with no exit fee. Customer master, units, contracts, the GL, all invoices, payments, audit logs and uploaded documents export to CSV, JSON and PDF on demand. We also publish a one-page data-portability brief to help your next system ingest the export cleanly.

The close board surfaces the metrics the platform already computes from your operational data: collection rate, total arrears, occupancy, the segregated sinking-fund balance and open tickets. Arrears are aged into current, 1–30, 31–60 and 60+ day buckets, and occupancy is shown as units let against total. Change the date preset and the figures re-settle for that period.

No — and we are deliberate about this. PROPSERVA does tabular reporting with SQL aggregation and PDF/Excel export. The dashboards visualize the numbers your reports already produce; there is no machine-learning prediction or forecasting model in the loop. The “powered by VYROX AI” line refers to the AIoT device intelligence, not to financial forecasting. Decisions stay with your council and manager.

Each invoice’s balance is computed as amount minus paid minus unposted, then aged by days overdue into four buckets. Those buckets feed the dunning cascade: an overdue reminder fires seven days before the due date, the first letter on day 1 overdue, the second on day 31 and the third on day 61. A treasurer reads the board and chases the oldest balances first, where bad debt crystallises.

Yes. The facility-utilisation report aggregates bookings by facility type and facility, on a minute or hour basis, with peak detection. When a court runs at 90%+ on Saturday evenings and 15% on weekday mornings, you have a concrete basis to introduce peak and off-peak rates, schedule maintenance in the quiet windows, or open under-used slots to coached programmes.

Yes — every report behind the dashboards exports to PDF and Excel, including the aging analysis, occupancy, facility utilisation, cashflow and revenue-by-service-line summaries. The boards are the on-screen visualization; the export is the council-facing pack.

All production data — including the figures behind the dashboards — is hosted in Singapore with daily off-site backups and point-in-time restore, encrypted in transit with TLS, and access-controlled with a full audit trail. MyInvois, SST and MSIC compliance remain Malaysia-specific while the data residency is Singapore.

Yes. A management firm runs its whole book from a single account: each property’s ledger is isolated (every transactional query is scoped by property id), while the portfolio command roll-up reads across the book to show units, occupancy, collection rate, arrears and open tickets per property, with a firm-level total. The roll-up exports to PDF and Excel for the directors’ pack.

It ages every outstanding balance — computed as amount minus paid minus unposted — into current, 1-30, 31-60 and 60+ day buckets, then drives the dunning cascade: a courtesy reminder seven days before due, a first letter on day 1 overdue, a second on day 31 and a third with interest advice on day 61. The treasurer works the oldest balances first, where bad debt crystallises. Every notice is written to the audit log.

It is an operational-intelligence shortcut to reports the platform already computes by SQL aggregation: who is 60+ days overdue, which units are vacant and for how long, the segregated sinking-fund balance, and the status of this month’s MyInvois batch. It surfaces and automates real reports and points you at the next action; it does not forecast the future or invent confidence percentages. The truth stays in your ledger.

MyInvois (LHDN) for e-invoice clearance; Xendit for FPX, card, Direct Debit, DuitNow QR and e-wallets; the VYROX-AutoCount-Connector middleware for AutoCount sync; brand-agnostic IoT hardware families (RFID, face, LPR, intercom, lift, parking-lock) encrypted with SM4; HERE Maps for delivery and patrol routing; our email service for email; and a documented REST API with webhooks for your own integrations.

Yes. Meeting minutes, the resolutions register and statutory documents — audited accounts, the sinking-fund statement, by-laws, insurance and fire certificates, the council register — are filed in a document vault against the property. Each resolution links to the budget line, rate change or GL posting it authorises, so the council and the auditor can open the whole governance pack in one click.

The close board reads one building in depth; the executive wall reads the whole estate at a glance. It is a denser one-page board of small multiples — trend tiles, sparklines, mini-bars and rings — covering collection rate, arrears, occupancy, sinking-fund balance, open tickets, weekly bookings, average daily revenue, e-invoices cleared, visitor passes, device health, complaint SLA and cashflow. Each tile is a number the reports already compute by SQL aggregation; the trend arrows are last-period deltas, not forecasts, and the wall exports to PDF and Excel for the directors’ pack.

Most properties go live in four to five weeks across six phases: discovery (week 1) maps your operations to modules and agrees the chart of accounts; data import (weeks 1–2) loads owners, units, contracts and opening balances by CSV; configuration (week 2) sets fees, SST, the MyInvois TIN and MSIC code, Xendit keys, branding and role-based accounts with hands-on training; AIoT pairing (week 3) pairs door, face, lift and plate readers under one policy; soft-launch (weeks 3–4) rolls out the apps and parallel-runs the old system for one billing cycle; and cutover (week 5+) retires the old system once the parallel run reconciles exactly.

Yes. The monitoring console gives the operations manager a single pane: system status and device heartbeat (MyInvois clearance, Xendit webhooks, the per-minute automation engine, door, face, lift and plate readers, parcel lockers and the nightly Singapore backup) on one side, and the approval queue plus a live audit feed on the other. The queue mirrors the unposted-payment, booking, move-in and refund workflows; the feed mirrors the append-only log written by the audit log, so every action reads back exactly as it happened.

Yes. PROPSERVA is one shared ledger with composable modules, and per-property availability toggles (feature flag) decide what each building sees. A walk-up of forty units and a multi-tower estate run the identical data model and core; only the toggles differ, so you switch on accounting, payments, MyInvois, bookings, visitors, AIoT access, parking, governance, delivery, marketplace, mobile apps and the automation engine as each building is ready.

Every complaint moves through three states — New, Processing and Completed — surfaced as the Pending Acknowledgement, Processing and Resolved queues. The list carries the submitted date, unit, complainant, category, title and an outstanding-days counter (a tabular date difference, not a prediction), and residents can Like a complaint to signal it affects them too. A manager acknowledges it, marks it Processing, then Completed, and every transition is written to the audit log so the council can see how responsive the helpdesk has been.

A booking moves through the real lifecycle: Pending Booking Approval, Pending Customer Payment, Confirmed, Pending Changes Approval, Changed Confirmed, Rejected and Expired. The bookings list shows the facility, who booked it, the booking window, the charge and any deposit, and the manager approves, rejects or lets a booking expire. The same engine powers auto-approved facilities and deposit handling, all reconciled back to the ledger.

It aggregates every booking by facility into the real fourteen-column analytics table: booking count, average duration in hours, average rate, average charge, total charge, total bookable hours, non-member and member booked hours, total booked hours, and non-member, member and total utilisation percentages, with peak detection. It is a measurement of what actually happened by SQL aggregation — the basis for a peak-pricing or scheduling decision, not a forecast — and exports to Excel and PDF.

The cash book aggregates cash actually received by month and by method — cash receipts, online payment gateway and per-bank-account movement — into a stacked view with total inflow, total outflow and net cashflow per period. It visualizes the cash you have already taken so a treasurer can see liquidity at a glance; it is tabular SQL aggregation with PDF and Excel export, not a machine-learning prediction.

They sit in an In / Out / running-balance ledger with the real general-ledger states: Pending Refund Approval, Pending Refund, Refunded, Customer Advances and Deposits On Hand. Each movement records the transacted date, property number, customer account ID, document number and description, and a refund only leaves the account after management approval — so the auditor can trace every ringgit in and out, and the figures export to PDF and Excel.

In the governance pack. Meeting minutes and management-account reports are filed with their uploaded date, title, remark, uploader and attachment, against the property. The announcement composer lets the manager choose a recipient, write a title and body, attach a PDF or image, and publish to the same noticeboard card residents read in the app — so the council’s governance record and the residents’ communications run off one dated, defensible source.

The payment-processor and bank registry records each processor — bank account, payment gateway or cash — with its GL account number, processor type and name, the payment-method label residents see in the app and staff see at the counter, and the account holder. When a receipt is posted, it lands against the correct GL account. This is a routing registry, not a statement-matching reconciliation tool; reconciliation is read off the General Ledger statement’s running balance, which exports to PDF and Excel.

The suppliers register lists each supplier by type and name; the service-permit book records every contractor permit with its property number, applicant, permit type, start and expiry dates, deposit and status (Pending, Approved, Expired). Each permit draws its deposit and rate from a service-type catalog, where a type can be marked auto-approved so a routine job clears without a manager. The contractor scans the property QR pass at the gate. Everything exports to PDF and Excel.

Yes. The stores inventory holds each item’s code, description, product group, cost and selling price, remark and status, with stock groups that link a class of items to its sales GL so a kiosk sale posts to the right revenue line. Separately, the community marketplace lets residents and onboarded merchants list items by type, title and price, while the merchant register tracks the business name, person in charge, contact numbers, username and live item count. These are tabular registers with Excel export — not demand forecasting.

Yes. The concierge desk logs each resident request — the unit, the user, the concierge service, and the deposit and charge in ringgit — drawn from a concierge-service catalog where each service carries its own deposit, charge and description. Raising a request bills the resident’s account, so the charge flows into the same statement of account as the maintenance fee, and the desk exports to PDF and Excel.