Operations dashboard
Sidebar pillars, four cosy stat tiles and a soft trend curve — all calm, all yours.
Whether you run a condo, a clubhouse, or a community — HOMESERVA keeps everyone happy. Pay fees from your phone. Book the BBQ pit. Pre-register Raya guests with a QR. Walk into the lobby with a smile (it unlocks with your face).
Free to explore. No credit card. We'll set it up with you.
Less paper. Less waiting at the guard house. Less awkward group-chat reminders. Just a calm app that handles the boring stuff so your community can enjoy the fun stuff.
FPX, card, e-wallet — straight from the app. Receipt auto-sent.
Lobby, lift, your floor. No card to fumble — your kids and parents will love it.
A real picture, real time. No more "did it actually arrive?" panic.
Send a QR before they arrive. Guard scans, gate opens, you stay in your slippers.
We're not asking you to take our word for it. Here's how HOMESERVA compares to WhatsApp-and-spreadsheets and to off-the-shelf community-app vendors you might already be using.
| What you need | HOMESERVA | WhatsApp + spreadsheets | Off-the-shelf community-app vendor |
|---|---|---|---|
| e-Invoice (MyInvois) compliance | Built in, real-time validated | Manual upload, error-prone | Add-on or unsupported |
| Automation (cron + rule engine) | Minute-level cron, configurable | Manual reminders | Limited to one domain |
| AIoT / access control | Native: face, plate, RFID, lift | None | Vendor-locked |
| Multi-property management | One operator, many properties | Separate files per property | Per-license, separate logins |
| Mobile app for residents/customers | Friendly, branded per property | Not available | Often desktop-only |
| Real-time dashboards | Live ops console | Static spreadsheets | Daily exports |
| Audit trail of every change | Yes, time-stamped | Whoever last saved | Limited |
| Payment automation | FPX, card, e-wallets via Xendit | Bank-in slips | Single gateway |
| Integrations (AutoCount middleware, MyInvois, Xendit, public REST API) | All native | Manual re-entry | Pick one |
| Support response | 24/7 WhatsApp · P1 in 1h | You email yourself | Email tickets, days |
Not a perfect fit for every property — talk to Patrick and we'll tell you straight if HOMESERVA isn't right for yours.
Six soft-cornered glimpses of the actual product, drawn in the same friendly palette as the rest of HOMESERVA.
Sidebar pillars, four cosy stat tiles and a soft trend curve — all calm, all yours.
A sage-trimmed invoice with the green MyInvois Validated sticker right where the eye lands.
Three friendly cards: pay invoice, book BBQ pit, send a visitor QR. That is the whole app.
Last eight swipes with little face circles, timestamps and a status sticker beside each one.
A week × hour calendar where free is sage, taken is peach and your slot is highlighted in cream.
Eight devices — cameras, lifts, locks, lighting — each with a calm online / syncing pill.
Interactive HOMESERVA community operations dashboard. It shows five live KPIs — fees collected as a percentage, bookings this week, visitors today, open complaints and parcels waiting — together with a seven-day bookings-by-day bar chart and a fees-collected donut. Date-preset buttons (Today, This week, This month, Last month) re-scope every number. The figures are computed by HOMESERVA's reporting from collections, bookings, visitor and complaint records.
Saturday is the peak — the BBQ pit and function room fill first. The utilisation report turns this into cut-off and deposit rules.
The collection-rate ring drives your cashflow and sinking-fund view. Anything below target feeds the dunning cascade.
A live activity ticker cycling through recent community events: a maintenance fee paid by FPX, a guest pre-registered with a QR pass, a BBQ pit booked, a parcel delivered to a locker, a complaint resolved, and a face-recognition access event at the lobby.
Resident app home screen titled "Things to do" for Aisha at Block A Unit 12-3: a maintenance-fee balance of RM 564.50 due in 5 days, one overdue carpark invoice, a confirmed BBQ booking on Saturday at 7 PM, and a parcel waiting in locker B-12.
Visitor QR pass card. Property: Lake View Residences. Visitor ID VIS-2026-1184. Valid from 21-MAY-2026 6:00 PM to 21-MAY-2026 11:30 PM. A QR code is shown. Access points: Lobby A turnstile and Visitor Carpark boom gate, with Lift access to Level 12. Linked booking ID BKG-0042.
BBQ and facility booking grid for one week. Columns are days Wednesday to Sunday; rows are time slots from 4 PM to 8 PM. Each cell is a slot you can tap to cycle through free, tentatively-held and booked. Saturday 7 PM is already booked, and Sunday 6 PM is held by another resident.
Tap a free slot to hold it, tap again to confirm. Booked slots are locked. Cut-off, deposit and max-per-month rules enforce themselves at the database layer.
Fee payment screen. Invoice INV-2026-0042 for RM 564.50 (maintenance fee plus sinking fund) is MyInvois validated. The resident chooses a payment method — FPX online banking, credit or debit card, or e-wallet such as Touch n Go, Boost, GrabPay or ShopeePay — then sees a green confirmed tick: Paid, receipt emailed.
Interactive clubhouse facility booking grid. Columns are the seven days of the week; rows are the hourly slots from 5 PM to 10 PM. Tap a free slot to tentatively hold it, tap again to confirm a booking, and tap once more to release it. Slots already taken by other residents are locked. The Saturday 8 PM and 9 PM slots and the Friday 7 PM slot are pre-booked.
Every confirmed slot writes an immutable change-history record (bookings.php, bookings_chg.php), so a disputed booking is settled on evidence — not on who shouted loudest in the group chat. Public-holiday rules and per-resident monthly caps apply automatically.
Interactive mockup of the HOMESERVA resident mobile app. A phone frame shows five screens swapped by a bottom navigation bar with five buttons: Home, Pay, Book, Visitor and Parcel. The Home screen lists the current account balance of RM 286.00, an unpaid maintenance-fee invoice, a parcel waiting for pickup, and an upcoming BBQ booking. The Pay screen shows the maintenance-fee invoice for RM 286.00 with a choice of FPX, card or e-wallet payment and a Pay button that confirms with a Paid tick. The Book screen lets the resident pick a clubhouse facility time slot. The Visitor screen pre-registers a guest and shows a QR pass valid for a time window. The Parcel screen shows a parcel held in locker B-14 with a one-tap collect action. Illustrative data.
Tap a green slot to hold it, tap again to confirm. Cut-off & deposit rules apply automatically.
The same machinery your management office runs — invoicing, bookings, visitor passes, lockers — wrapped in a friendly app residents actually open. Tap Pay and watch a fee clear; the receipt is e-mailed and the invoice is MyInvois-validated in the same pass.
app.php, cus_dashboard.php).Illustrative data — your real numbers come from your own ledger.
Animated four-step visitor pre-registration flow. Step one: a resident fills in the guest name and arrival time window. Step two: a QR visitor pass is issued, valid for the chosen window with named access points. Step three: the guard scans the QR at the gate and the pass is verified. Step four: the boom gate lifts and the guest is admitted. The animation auto-advances and can be replayed.
qrcode_check.php) validated against its time window and access points — so a peak-day wave of guests still flows through the gate cleanly. Illustrative.Interactive parcel locker wall mockup. A grid of fifteen lockers, each labelled, shows their state: most are empty, some hold parcels for other residents. When a parcel arrives, locker B-14 pulses to signal it is waiting for you. Tapping the pulsing locker opens its door with an animation and a notification confirms you have collected your parcel from locker B-14; the locker then returns to empty for the next delivery.
delivery_lockers.php, delivery_lockers_config.php); the resident gets an in-app notification with an arrival photo and a one-tap pickup code. Tap the glowing B-14 to collect — or press "Simulate a delivery" to watch a fresh parcel arrive. Illustrative.HOMESERVA e-invoice flow, five stages: Draft, MyInvois validate, Submit to LHDN, Cleared, and Paid. Each invoice is built as a UBL 2.1 JSON document, validated against the MyInvois portal, submitted to LHDN, and on clearance returns a UUID and QR before the resident pays. Walk-in residents without a tax identification number use the LHDN-prescribed walk-in TIN EI00000000010. The connector runs in sandbox first, then production.
Each charge is assembled into the UBL 2.1 JSON payload LHDN expects — line items, taxes (SST), the buyer's TIN, your company TIN and the matching MSIC industry code — and validated against MyInvois before it is issued. Nothing leaves your books in an invalid state.
A resident or guest without a tax number uses the LHDN-prescribed walk-in TIN EI00000000010, so a one-off facility charge or deposit still clears cleanly. The connector runs in sandbox while you onboard, then flips to production on go-live.
On a validation failure, the invoice waits in a "needs attention" queue with the exact LHDN message attached — you fix the data and resubmit in one click.
Every committee meeting opens with the same question: who owes us, and how long have they owed it? HOMESERVA buckets each outstanding balance into current, 1–30, 31–60 and 60-plus days, because the right action depends entirely on the age. A resident two weeks late needs a gentle nudge; a unit sixty days overdue needs a formal letter. The platform turns those buckets into an automatic dunning cascade — the invoice and PDF go out immediately, an overdue reminder fires seven days before the due date, a first letter on day one overdue, a second on day thirty-one and a third on day sixty-one, with a card-expiry warning seven days before a saved card lapses. The committee chases only the genuine exceptions, not the whole book, and the AGM sees a clean aging table instead of a shoebox of bank-in slips.
The fees-collected percentage is the single most important number a community tracks, because it feeds straight into liquidity. HOMESERVA reports the collection rate by period and projects the resulting cashflow by day, month and year, separating operating maintenance fees from the sinking fund reserved for major repairs. When the rate dips, the committee can see immediately whether the shortfall threatens this month's contractor payments or next year's lift refurbishment — and decide whether to tighten the dunning cascade, defer discretionary spend, or both. The decision is grounded in the ledger, not in a guess.
The facility-utilisation report breaks every booking down by facility and by hour, so the committee can see exactly when the BBQ pit, function room and courts fill up. Saturday evenings booking out weeks ahead is a signal: it justifies a deposit, a tighter cut-off window, a sensible cap of bookings per household per month, and — where the community agrees — gentle peak pricing so the busiest slots are shared fairly. Idle weekday slots, equally, are a prompt to promote a facility rather than let it sit empty. None of this is a forecast; it is a clear read of bookings that already happened, turned into rules everyone understands.
Visitor frequency, first and last visit, overstays and vehicle plates all flow into one analytics view. If Friday and Saturday evenings consistently generate the heaviest visitor waves, the committee can roster an extra guard for those windows instead of paying for round-the-clock cover that the data does not support. Repeat-visitor patterns and overstay flags help the guard house separate the regular grandchildren from the genuinely unexpected — so security attention lands where it actually matters.
Because every complaint carries a status, a priority and a timestamped trail, the committee can finally measure service rather than argue about it. Median resolution time, the share of tickets breaching their target, and the recurring categories (lifts, lighting, leaks) become visible — so the longest-waiting items surface to the top and the recurring ones justify a capital fix instead of an endless string of patch jobs. Every figure on this page is computed by HOMESERVA's reporting with plain SQL aggregation and date presets, exportable to PDF or Excel for the AGM pack. The intelligence is in the decision the committee makes; the platform simply makes the number impossible to miss.
Six code-verifiable facts about HOMESERVA — derivable from the source, not marketing telemetry.
Architectural constants from the HOMESERVA codebase — not per-property telemetry. Patrick will share specifics for your case.
Your chairman, treasurer and manager open the same board and stop arguing about which spreadsheet is right.
| Bucket | Units | Amount | Next action |
|---|---|---|---|
| Current | — | RM 5,840 | On track |
| 1–30 days | 9 | RM 3,420 | Reminder sent |
| 31–60 days | 4 | RM 2,460 | 2nd letter |
| 60+ days | 2 | RM 1,380 | 3rd letter |
Pick a date range, scan the gate log, export to your committee — all in one calm place.
| No. | Checked-In | Visitor Pass No. | Visiting Property | Visitor | Mobile No. | Vehicle Plate No. | Valid Until | Checked By | |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 22-May-2026 6:12 PM | VP-2026-04418 | A-12-04 | Lim Wei Sheng | +60 12-345 6789 | WXY 8842 | 22-May-2026 11:00 PM | Guard Rosli | ⋯ |
| 2 | 22-May-2026 5:48 PM | VP-2026-04417 | B-08-11 | Nurul Ain binti Hassan | +60 13-882 1190 | No Vehicle | 22-May-2026 9:00 PM | Guard Rosli | ⋯ |
| 3 | 22-May-2026 3:30 PM | VP-2026-04415 | C-03-02 | CoolAir Aircond (contractor) | +60 16-771 4023 | VBA 1209 | 22-May-2026 6:00 PM | Guard Devan | ⋯ |
| 4 | 22-May-2026 1:05 PM | VP-2026-04412 | A-05-09 | Tan Mei Ling | +60 17-204 9981 | PKL 5570 | 22-May-2026 5:00 PM | Guard Devan | ⋯ |
| 5 | 22-May-2026 12:40 PM | VP-2026-04410 | D-15-03 | GrabFood courier | +60 11-2098 3344 | JKL 7781 | 22-May-2026 1:10 PM | Guard Rosli | ⋯ |
| 6 | 22-May-2026 11:18 AM | VP-2026-04408 | B-21-07 | Siti & family (4) | +60 19-660 2215 | WWA 3320 | 22-May-2026 4:00 PM | Guard Meena | ⋯ |
| 7 | 22-May-2026 10:02 AM | VP-2026-04405 | A-18-02 | Pos Laju despatch | +60 12-908 6677 | No Vehicle | 22-May-2026 10:30 AM | Guard Meena | ⋯ |
| 8 | 22-May-2026 8:55 AM | VP-2026-04401 | C-09-12 | Raj Kumar | +60 14-339 5512 | BNN 1042 | 22-May-2026 12:00 PM | Guard Meena | ⋯ |
Auto-hides any task that reads zero — just like the real dashboard.
Each row mirrors the real dashboard’s phrasing and only appears when its count is above zero — so the office sees exactly what still needs a hand today.
The QR changes over time, so a screenshot won’t open your gate tomorrow. Re-skinned warm, faithful to the software.
Every pass carries a dynamic Access Control QR-Key that rotates on a timer — the card shows the live “Expire in mm:ss” countdown. A guest can’t forward yesterday’s screenshot to a friend and waltz in; the gate checks the current key against the valid time window before it opens.
Face-unlock at the lobby is matched on the device itself, not in the platform — HOMESERVA records the access event and the entitlement. Powered by VYROX AI.
Maintenance, sinking fund, water, booking deposits — the invoice list HOMESERVA keeps for each home, with filter tabs for what is paid, unpaid or overdue. Click a row's filter to narrow the list right here.
| No. | Issued On | Due Date | Document No. | Invoice | Payable | Paid | Balance | ||
|---|---|---|---|---|---|---|---|---|---|
| 1 | 01-May-2026 | 15-May-2026 | INV-00041 | Maintenance ChargeMay 2026 · RM 0.33/sq ft | 320.00 | 320.00 | 0.00 | ⋯ | |
| 2 | 01-May-2026 | 15-May-2026 | INV-00042 | Sinking FundMay 2026 · statutory 10% | 32.00 | 32.00 | 0.00 | ⋯ | |
| 3 | 01-May-2026 | 15-May-2026 | INV-00043 | Water ChargeApr read · 14 m³ | 41.20 | 0.00 | 41.20 | ⋯ | |
| 4 | 03-May-2026 | 10-May-2026 | INV-00051 | Facility Booking DepositFunction Hall · 17-May | 150.00 | 150.00 | 0.00 | ⋯ | |
| 5 | 01-Apr-2026 | 15-Apr-2026 | INV-00029 | Maintenance ChargeApr 2026 · carried forward | 320.00 | 0.00 | 320.00 | ⋯ | |
| 6 | 16-Apr-2026 | 30-Apr-2026 | INV-00037 | Late Payment Interest1.5% on overdue balance | 4.80 | 0.00 | 4.80 | ⋯ | |
| 7 | 01-May-2026 | 15-May-2026 | INV-00044 | Water Chargepart-paid · balance left | 38.60 | 20.00 | 18.60 | ⋯ | |
| 8 | 02-Apr-2026 | 16-Apr-2026 | INV-00031 | Sinking FundApr 2026 · statutory 10% | 32.00 | 32.00 | 0.00 | ⋯ | |
| 9 | 05-May-2026 | 19-May-2026 | INV-00057 | Facility Booking DepositBBQ Pit · 24-May | 80.00 | 0.00 | 80.00 | ⋯ |
Balance is computed as Payable minus Paid — the same SQL aggregation the software runs for every statement. Paid in green, money owing in your alert tone. Powered by VYROX AI.
The same availability grid your management uses — facilities down the side, time slots across the top. Tap a free cell to hold it, tap again to confirm, tap once more to release. Booked and past slots stay locked.
| Facility | 8 AM | 9 AM | 10 AM | 11 AM | 12 PM | 1 PM | 2 PM | 3 PM | 4 PM | 5 PM | 6 PM | 7 PM | 8 PM |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| BBQ Pit | |||||||||||||
| Function Hall | |||||||||||||
| Pool | |||||||||||||
| Gym | |||||||||||||
| Tennis Court |
Held slots become a booking deposit invoice; the calendar releases them automatically if payment lapses. No double-bookings, no awkward phone calls. Powered by VYROX AI.
The members register your committee already keeps — who joined, which plan, days remaining, deposit and fee — laid out the same way the software lists it, just dressed in HOMESERVA colours.
| No. | First Joined | Customer Account ID | Membership ID | Member | Subscribed Membership Plan | Days Remaining | Deposit | Membership Fee | Start Date | Expiry Date | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 12-Jan-2024 | CA-100412 | MB-0412 | Lim Wei ShengA-12-04 | Resident Standard | 235 | 320.00 | 120.00 | 13-Jan-2026 | 12-Jan-2027 | ⋯ |
| 2 | 03-Mar-2023 | CA-100388 | MB-0388 | Nurul AinaB-08-11 | Resident Premium | 12 | 500.00 | 240.00 | 04-Mar-2026 | 03-Mar-2027 | ⋯ |
| 3 | 21-Sep-2022 | CA-100201 | MB-0201 | Tan Mei LingC-03-02 | Resident Standard | 312 | 320.00 | 120.00 | 22-Sep-2025 | 21-Sep-2026 | ⋯ |
| 4 | 07-Jul-2025 | CA-100590 | MB-0590 | Rajesh KumarA-05-09 · tenant | Tenant | 47 | 650.00 | 0.00 | 08-Jul-2025 | 07-Jul-2026 | ⋯ |
| 5 | 15-Nov-2024 | CA-100503 | MB-0503 | Goh Jia HuiD-14-07 | Resident Premium | 178 | 500.00 | 240.00 | 16-Nov-2025 | 15-Nov-2026 | ⋯ |
| 6 | 29-Feb-2024 | CA-100456 | MB-0456 | Faridah HassanB-02-03 | Resident Standard | 283 | 320.00 | 120.00 | 01-Mar-2026 | 28-Feb-2027 | ⋯ |
Days Remaining counts down to expiry so renewals never sneak up — the platform can nudge a reminder seven days before. Powered by VYROX AI.
Cosy summary tiles up top, then a plain collections report that buckets every balance by age — current, 1–30, 31–60 and 60+ days — ready to export as PDF or Excel.
| Fee Type | Current | 1–30 days | 31–60 days | 60+ days | Total Owing |
|---|---|---|---|---|---|
| Maintenance Charge | 1,920.00 | 640.00 | 320.00 | 640.00 | 3,520.00 |
| Sinking Fund | 192.00 | 64.00 | 32.00 | 64.00 | 352.00 |
| Water Charge | 288.40 | 82.40 | 41.20 | 18.60 | 430.60 |
| Facility Deposit | 230.00 | 0.00 | 0.00 | 0.00 | 230.00 |
| Late Payment Interest | 0.00 | 4.80 | 4.80 | 9.60 | 19.20 |
| Total | 2,630.40 | 791.20 | 398.20 | 732.20 | 4,551.80 |
Aging buckets are simple SQL date-difference grouping — the report tells your committee exactly who to chase first, in plain ringgit. Powered by VYROX AI.
The HOMESERVA resident home screen lays out a friendly To Do List, a little Water Usage chart so the bill never surprises anyone, and four big quick actions — the same layout the app already ships, dressed in warm colours.
The empty-state line is the real one: “No pending tasks for today. Good habits are the beginning of success!” The water chart is plain month-by-month usage from your meter reads — tabular numbers, not a prediction. Powered by VYROX AI.
The same complaints & suggestions list your committee already works, with the real filter tabs — Pending Acknowledgement, Processing and Resolved — an outstanding-days counter, and the little neighbour Like widget so popular issues float to the top.
| No. | Submitted | Unit | Complainant | Category | Title | Outstanding (Day) | Neighbours | |
|---|---|---|---|---|---|---|---|---|
| 1 | 20-May-2026 | A-12-04 | Lim Wei Sheng | Plumbing | Lobby tap drippingNew | 2 | ||
| 2 | 19-May-2026 | C-03-02 | Tan Mei Ling | Lift | Block C lift jerkyNew | 3 | ||
| 3 | 19-May-2026 | B-08-11 | Nurul Aina | Cleanliness | Rubbish chute smell L8New | 2 | ||
| 4 | 18-May-2026 | D-14-07 | Goh Jia Hui | Lighting | Car park L2 lamp outNew | 4 | ||
| 5 | 16-May-2026 | A-05-09 | Rajesh Kumar | Security | Gate barrier slow at peakProcessing | 2 | ||
| 6 | 15-May-2026 | B-02-03 | Faridah Hassan | Facilities | Gym treadmill #2 faultProcessing | 1 | ||
| 7 | 10-May-2026 | C-09-05 | Wong Kah Meng | Plumbing | Pool pump leakCompleted | 0 | Resolved | |
| 8 | 08-May-2026 | A-03-12 | Siti Aishah | Noise | Renovation past hoursCompleted | 0 | Resolved |
Status maps to the real labels New, Processing and Completed; Acknowledge moves a new complaint into Processing, Resolved closes it — every step lands in the audit trail. Powered by VYROX AI.
A resident taps SOS and picks the help they need — Security Guard, Ambulance, Police or Fire Fighter. The guard sees it instantly, Acknowledges, then marks Completed, with the response time captured for the record.
The flow is the real one: status 0 shows Acknowledge, status 1 shows Completed, and response time is measured from raised to attended — the dashboard also counts SOS in progress. Powered by VYROX AI.
A live grid of every locker door, coloured by the real statuses — Pending pickup in peach, Done in green, empty doors dashed and quiet — with the delivery list your team works from underneath.
| No. | Created | Door No. | To Unit | Customer Name | Customer Mobile No. | Rider/Driver Mobile No. | Status |
|---|---|---|---|---|---|---|---|
| 1 | 22-May-2026 | 01 | A-12-04 | Lim Wei Sheng | 012-345 6789 | 011-222 3344 | Pending |
| 2 | 22-May-2026 | 04 | C-03-02 | Tan Mei Ling | 017-888 1212 | 011-555 9090 | Pending |
| 3 | 21-May-2026 | 07 | D-14-07 | Goh Jia Hui | 019-440 7766 | 013-200 4455 | Pending |
| 4 | 21-May-2026 | 10 | A-05-09 | Rajesh Kumar | 016-901 3322 | 011-808 7711 | Pending |
| 5 | 20-May-2026 | 02 | B-08-11 | Nurul Aina | 014-330 9988 | 012-770 6655 | Done |
| 6 | 19-May-2026 | 15 | C-09-05 | Wong Kah Meng | 018-220 1100 | 013-660 4433 | Done |
When a courier drops a parcel the resident gets a tap-to-open notification; an uncollected parcel shows in the resident To Do List until it is picked up. Powered by VYROX AI.
Real announcement cards — thumbnail, timestamp, title, body and “Published by” line, each with a read-receipt count — next to a friendly composer where the committee picks recipients and posts straight to every app.
| No. | Uploaded | Title | Uploader | Attachment |
|---|---|---|---|---|
| 1 | 16-May-2026 | Committee meeting — May 2026 | JMB Secretary | minutes-may.pdf |
| 2 | 18-Apr-2026 | Committee meeting — Apr 2026 | JMB Secretary | minutes-apr.pdf |
Announcements and meeting minutes publish into the resident app and the lobby display together — one post, every screen. Powered by VYROX AI.
Scan a QR, wave a patrol checkpoint, acknowledge an SOS — without juggling four apps and a paper book.
| Visitor | Host unit | Valid window | Status |
|---|---|---|---|
| Lim & family (4) | A-12-04 | 22-MAY 18:00–23:00 | QR validated |
| GrabFood courier | B-08-11 | 22-MAY 19:10–19:40 | At gate |
| Aircond contractor | C-03-02 | 22-MAY 09:00–12:00 | Permit check |
| Unknown vehicle WXY-1234 | — | — | Hold · verify |
No active emergencies.
Management posts once; residents see it in the app, and the committee sees exactly how many actually read it.
Supply to Blocks A & B will pause briefly. Please store water in advance.
Agenda, last year’s minutes and the audited accounts are attached in Files.
RSVP in the events tab — 96 neighbours already going.
Stroller (lightly used) · Home-baked kuih orders · Tuition for SPM Add-Maths.
Resident-to-residentTap a question. The answer is built straight from the numbers your reports compute — honest, friendly, and exportable.
| Unit | Days | Balance | Cascade |
|---|---|---|---|
| D-05-09 | 74 | RM 760 | 3rd letter sent |
| D-11-03 | 63 | RM 620 | 3rd letter sent |
Source: arrears aging buckets + dunning cascade log. Export to PDF for the committee.
BBQ pit and function room are fully booked Sat 6–10pm; courts have idle weekday mornings worth promoting. Utilisation comes from the facility-utilisation report (by facility, by hour).
Suggest a Saturday deposit rule| Ticket | Category | Age | Status |
|---|---|---|---|
| #2041 | Lift B noise | 3d | SLA breach |
| #2048 | Corridor light | 2d | In progress |
| #2052 | Leak · L3 | 9h | Assigned |
Source: complaints + helpdesk SLA queue, ordered by oldest-waiting.
The cron run drafts each invoice; functions_einv.php submits the UBL 2.1 JSON to LHDN; any rejection lands in a “needs attention” queue with the error attached. Nothing leaves your books in an invalid state.
VYROX AI is the AI that specialises in business operation management together with IoT. Here it reads and automates the operational reports HOMESERVA already produces — it is operational intelligence over your real data, not a predictive model.
No machine learning, no magic — just dependable scheduled jobs you can switch on and off.
Generates management-fee, sinking-fund and rental invoices in batch, then submits each to MyInvois.
generate_ma.php · generate_sink.php · generate_rentals.php
Friendly nudge fires 7 days before the invoice due date so residents pay on time.
reminder.php
First overdue letter the day after a missed due date.
reminder.php
Escalating letters at day 31 and day 61 — the committee only handles the residual exceptions.
reminder.php
Renewal invoice drafts ~30 days before a paid plan lapses.
auto_renew_mem()
Time-limited amenities (laundry, BBQ) stop and bill automatically when the window ends.
cron_minute_work.php
Unpaid or lapsed bookings are auto-cancelled so the calendar frees up.
cron_minute_work.php
AIoT devices are pinged for uptime; intrusion-photo files are purged on a schedule.
check_iot_up.php
One platform, many spokes — no rip-and-replace, no walled garden.
National e-invoice — UBL 2.1 JSON, real-time validation, walk-in TIN fallback, MSIC code list. Sandbox & production.
FPX, credit / debit card, Direct Debit, DuitNow QR and e-wallets (Touch ’n Go, Boost, GrabPay, ShopeePay) with webhook reconciliation.
Bidirectional middleware sync (Bearer-token) — invoice, payment, cancel and undo flow end-to-end to your accountant’s ledger.
Brand-agnostic IP cameras, MIFARE RFID, face & plate cameras, intercoms, lift controllers, parking locks and TCP delivery lockers — SM4-encrypted device traffic.
Geolocation and routing for the delivery-courier and staff PWAs, so parcels reach the right block.
Documented surface at /api_doc.php — visitors, EV charging, sub-accounts, announcements and bookings. Bring your own BI dashboards.
Integration and ecosystem hub: HOMESERVA at the centre connects out to six third-party spokes — MyInvois/LHDN e-invoicing, the Xendit payment gateway, the AutoCount accounting connector, brand-agnostic access and IoT hardware with SM4-encrypted traffic, HERE Maps for courier routing, and a documented REST API with webhooks. No sister-product or shared-core relationships are implied; the only common thread across VYROX products is that they are powered by VYROX AI.
Tighter than the main dashboard, made for the monthly committee glance.
We map how your community runs today — fees, facilities, gates, lockers, complaints — onto HOMESERVA modules. No assumptions, just your real workflow.
Owners, units, contracts and outstanding balances come in from CSV/Excel. A dry-run import lets you review every row before we commit the real one — nothing gets lost.
Rates, fees, MyInvois TIN, the Xendit gateway, branding and role-based accounts for office, committee and security are all set up and tested.
Cameras, face and plate readers, lift controllers, parking locks and TCP delivery lockers are paired and their heartbeats verified.
The resident app rolls out alongside your old system. We hand you ready-to-send email templates and printable QR posters for the lobby.
The old system retires. Quarterly reviews keep things tidy, and new modules switch on as the community grows.
HOMESERVA implementation journey: a six-stage onboarding rail — Discovery (Week 1, map operations to modules), Data import (Week 1, CSV/Excel of owners, units, contracts and balances with a reviewable dry run), Configuration (Week 2, rates, fees, MyInvois TIN, Xendit, branding and role-based accounts), AIoT pairing (Week 3, cameras, face and plate readers, lifts, parking locks and lockers), Soft-launch (Week 3–4, resident app parallel-run with email templates and lobby QR posters) and Cutover (Week 5 onward, retire the old system with quarterly reviews). Most communities complete it in about four weeks.
HOMESERVA day-in-the-life playbooks: a tabbed walkthrough of three real scenarios. Month-end close — the cron run drafts management-account and sinking-fund invoices, validates them against MyInvois, emails PDFs with FPX/e-wallet links, and runs the dunning cascade. Festive parcel rush — a courier drops a parcel into a smart locker, the resident receives a tap-to-open notification and one-time QR, collects it, and any uncollected parcel is flagged as an overstay. A 2am incident — a resident SOS reaches the guard PWA, the access feed shows the matching face, plate and lift events for the timestamp, the guard logs a patrol round and closes the incident, and every step is written to the audit trail. All steps are grounded in real platform behaviour, not a forecast.
in_syslog. Real device and system state, not predictive analytics.check_iot_up.php
22 / 24 online
in_syslog
14-day
Live audit feed drawn from the in_syslog table with a 14-day retention window: who did what, when and from which device — incident closures, posted payments, the month-end invoice batch, MyInvois validation, booking approvals and sub-account changes.
Try it — tap Approve or Reject on any row below.
HOMESERVA unified approvals queue: four pending sign-offs — a new-tenant move-in for unit A-08-03 with lease and IC uploaded, a payment proof of RM 720.00 for B-12-01, a function-room booking request with deposit paid, and a BBQ booking-change request. Each row offers Approve and Reject actions; the decision posts to the ledger or booking record (via files such as sub_account_changes.php, bookings.php and bookings_chg.php) and is written to the audit trail, so the committee reviews only the exceptions rather than every transaction.
Pulled straight from functions.php → property_ava() — no marketing fluff.
Each toggle maps 1:1 to a row in tg_prop_ava[*] — flip it on per property, leave the rest off. You only pay for what you turn on.
You shouldn't have to think about most of this — and you won't. It runs every minute, all year, while you sleep.
On the 1st of every month, invoices generate themselves and validate against MyInvois before anyone opens the office
Cron jobs run every minute — auto-stop laundry timers, expire stale bookings, retry failed payments, clean up intrusion photos
IoT heartbeats check every camera, lock, lift and sensor — if one quiets down, the system notices before residents do
Auto-billing schedules recurring fees, sinking fund, late-interest and rental invoices — the office only intervenes for exceptions
Cash book and bank-account records keep payments tied to statements — month-end takes minutes, not days
AutoCount middleware syncs invoice / payment / cancel / undo flows in the background
The audit log (debugv_access) quietly records every change — who, what, when, from where
Failed e-invoices land in a "needs attention" queue with the LHDN error attached — your books never sit in an invalid state
Expired memberships, departed sub-users and orphaned bookings are tidied up by housekeeping cron — no manual purge needed
PDF generation respects paper sizes — your accountant gets A4, your printer gets what it expects
The SM4 cipher quietly encrypts device traffic between the platform and AIoT hardware
Notification mute toggles, public-holiday calendars and cut-off times all enforce themselves so staff don't have to remember
A short, honest list — what we connect to today, no buzzwords.
Real-time validation, UBL 2.1 JSON, walk-in TIN fallback, MSIC code list.
FPX, card, Direct Debit, Touch 'n Go, Boost, GrabPay, ShopeePay, DuitNow QR.
Bidirectional sync via our hosted middleware — invoice, payment, cancel, undo.
HTTP snapshot + event ingest. Camera-brand agnostic.
Face, plate and intercom families — pair what you already own.
Tap cards and fobs from any compatible supplier.
One-tap handyman link-out for ad-hoc home repairs.
The AI that specialises in business operation management together with IoT — quietly powering HOMESERVA under the hood.
/api_doc.php for the developer-minded committee.
Most residents will never open this drawer — and that's fine. But if your committee has a developer who likes to tinker, HOMESERVA exposes a documented REST endpoint surface at /api_doc.php (visitors, EV charging, sub-accounts, announcements and more), Xendit webhooks, the AutoCount sync middleware, an audit-log table (debugv_access), a paper-size-aware PDF engine, and TCP-controlled delivery lockers (delivery_lockers_config.php). The dlcsp.php landing page is a printable property-QR surface, not a hardware protocol. It's all there if you want it. Ask Patrick for the API doc page.
HOMESERVA is the one app your community actually uses — residents pay fees, book BBQ, pre-register guests, unlock with face. Security and management see the other side of the same screen. Tap a card to peek inside.
From morning kopi to lights-out — here's how it weaves through a normal day.
You unlock the lift with your face — coffee in one hand, gym bag in the other.
You pay this month's maintenance fee from the train. Receipt lands in your inbox.
Cousin's coming over — a tap sends her a visitor QR. Guard waves her in.
Notification + photo: your Shopee order is in Locker B-12. Pick up after work.
You book the BBQ pit for Saturday. Calendar shows it's yours, no calls needed.
Lights set themselves. Lobby logs your evening jog. Everyone's home, all's well.
Residents see the friendly app. JMB / MC sees a calm operations console — collections, occupancy, security events, MyInvois status, IoT health — all in one tab. No spreadsheets emailed at midnight.
No rip-and-replace. We connect to most cameras, controllers and gateways.
HOMESERVA is wired into Malaysia's national e-invoice scheme. Every B2B invoice is built as a UBL 2.1 JSON payload, validated in real time, returned with a sharing URL, and supports walk-in buyer fallback (TIN EI00000000010), the full MSIC code list, credit notes, consolidated invoices and corrections. Sandbox and production environments are both supported, so you can test end-to-end before flipping the switch.
Multi-method payment gateway. Confirmed methods in code: QR payment, credit / debit card, and Direct Debit. Built-in failover, refunds and webhook reconciliation mean your accounts stay in sync without manual matching.
Bidirectional sync via the hosted VYROX-AutoCount-Connector middleware (Bearer-token auth) — invoice, payment, cancel and undo flows are pushed end-to-end. Run HOMESERVA accounting on its own, or keep your accountant on AutoCount and let HOMESERVA push transactions across.
Invoices, statements, payment receipts, password resets and one-time codes are emailed via PHPMailer from your own domain. (WhatsApp is how you reach Patrick — it is a sales channel, not a system feature.)
Generic IP cameras (HTTP snapshot and event ingest, brand-agnostic), MIFARE-compatible RFID smart-card readers, face cameras, ANPR / license-plate cameras and SIP-style intercoms — all glued together by the SmartFACE / SmartVE / SmartINTE modules.
Relay-based and IP-controlled hardware on both low-voltage and high-voltage paths. Brand-agnostic — we integrate lift controllers, parking-lock controllers, smart lighting, smart mirrors (micode access codes) and TCP-controlled delivery lockers (delivery_lockers_config.php). The dlcsp.php / dlcsp_qr.php pages are a printable property-QR landing surface, not a hardware protocol — door and locker tokens are issued through the standard QR-key system (qr_keys.php).
Documented at /api_doc.php — visitor management, EV charging deposit and session, sub-account, announcements, bookings and more. Bring your own dashboards, BI tools or integrations.
Device-protocol traffic between HOMESERVA and the AIoT layer is encrypted with SM4, a 32-round Chinese block cipher — the same cipher class used in industrial smart-locks and access controllers.
Four friendly journey moments along a calm path. Patrick walks the whole way with you.
Patrick on-site or via video. We map your operations to HOMESERVA modules and bulk-import customers, units, contracts and outstanding balances.
Set rates, fees, MyInvois TIN, payment gateway, branding and role-based accounts. Hands-on training across 2–3 sessions.
Pair access devices, cameras and lifts. Roll out the resident/customer app. Parallel-run alongside the old system.
Old system retired. Quarterly reviews. New modules added as the community grows.
Eight typical operations we serve. Pick yours and see exactly which modules help most.
JMBs and MCs juggle owners, tenants, contractors and a budget that gets scrutinised every AGM. Their biggest pain is fee collection and visitor jams at the boom gate.
Capability: pre-registered QR passes (visitor_pass.php) cut the guard-house step to a single scan; auto-billing (auto_payments.php) plus dunning reminders chase arrears without human intervention.
Residential towers above a retail podium share access, parking and security, but each tenant type has different rules. Coordinating them by hand is a nightmare.
Capability: one access policy spans residential, retail and podium tenants — tg_prop_ava[] gates per-property module visibility while mypriv[] enforces role capability page-by-page.
Member dues, court bookings, coach schedules and a clubhouse F&B usually live in 4 separate tools. Members hate the friction; managers hate the reconciliation.
Capability: bookings move from phone calls to a real-time calendar (bookings.php) with cut-off, deposit and max-per-month rules — utilisation reports surface idle slots so committees can re-price them.
Class passes, recurring memberships, locker access and PT bookings need one consistent member ID. Manual sign-ins kill front-desk time.
Capability: SmartFACE entry (smartface.php) and amenity QR self-check-in (amenities_qr.php) replace manual sign-in books — the front desk handles exceptions, not the queue.
EV bays, visitor lots and reserved parking each have different rules. Without a system, you get charger squatters and angry residents.
Capability: EV-bay billing (ev_parking_lots.php with `is_ev=2` on parking_lot_type) plus paid-parking overstay rules (paid_parking.php) plus wheel-clamp release (clamp.php) capture revenue that previously walked out of the carpark.
Landed communities want the same convenience as condos — visitor QR, fee collection, security — without a giant guard-house budget.
Capability: complaints.php tickets carry priority, status and routing fields; helpdesk.php surfaces SLA breaches as a queue so the longest-waiting items are visible rather than buried in a phone log.
Tenants in a podium need to bill rent, utilities and CAM, take member promotions, and reconcile their till with the building's accounts.
Capability: member-charge from the resident app (sales.php) settles against the household statement via `acc_bal` — F&B accepts charges without a separate till reconciliation.
Clubhouses run BBQ pits, function rooms, courts, kids rooms and a café — all of which compete for the same calendar.
Capability: bookings.php enforces overlap rules at the database layer; the booking-change request flow (bookings_chg.php) records every amendment with an audit trail rather than living in a group chat.
Operators we serve, anonymised — happy to introduce on request when there's a good fit.
Auto-billing plus face access for residents and a calm guard-house console.
Anonymised customerOnline booking with rate cards — peak hours clear without a phone call.
Anonymised customerPOS, amenities and visitor management glued onto one friendly member ID.
Anonymised customerLift access tied to face and floor entitlement plus smart-parking enforcement.
Anonymised customerRecurring class bookings settled through Xendit in five clicks or fewer.
Anonymised customerConcierge requests and a cheerful helpdesk that families can read on the app.
Anonymised customerLPR entry, paid parking and EV-bay billing in one calm gateway flow.
Anonymised customerJMB billing, sinking-fund auto-generation and a 1-page chairman cashflow.
Anonymised customerClass passes, coach scheduling and a member app that finally feels modern.
Anonymised customerSub-account billing and per-tenant statements — handy for landlords too.
Anonymised customerPOS, membership plans and friendly leaderboards on the lobby screen.
Anonymised customerMulti-facility bookings with auto-reminders that cut no-shows almost in half.
Anonymised customerWant a reference call? Patrick will pair you with a similar operator — with their consent, naturally.
Wherever your community keeps its records today, the move to HOMESERVA is a soft slope — not a cliff.
We import customers, units, contracts, fees and outstanding balances from CSV or Excel during Week 1. Patrick reads the file with you, fixes the small mismatches (extra columns, weird date formats, mixed currency), and runs a dry import you can review before the real one. The classic pain points — duplicated owners, missing TINs, balances that no longer reconcile — surface in a friendly issues list, not in midnight panic.
Paper records become a calm digital onboarding workflow. Past invoices and contracts can be photographed and OCR-extracted into structured rows; new residents self-register through the app with optional management approval. The first month runs softly — guards still keep the paper book while the system shadows them — so nothing slips while everyone learns the new rhythm.
Bridges keep the old system live during cutover. We mirror customers, invoices and payments across, run a parallel period of two to four weeks, and only retire the old tool after a quiet weekend reconciliation. You never face the cliff-edge of "everyone migrate by Monday" — it is a gentle slope with a known landing spot.
We work with your developer to map and export, then normalise your data against the HOMESERVA schema. Anything we cannot model cleanly stays archived in original form for audit. Where you have webhooks or APIs, we wire them straight in so the rest of your stack — accountant, payment gateway, BI dashboard — keeps humming throughout.
Move four sliders. Get a friendly estimate. Then talk to Patrick to verify with your real operation.
Estimate only — Patrick will confirm for your specific operation.
We take security as seriously as residents take their parking lot. Here's the plain-English version.
Your data lives in Singapore. No surprise transfers to faraway data centres.
TLS over the wire so data moves safely between app, browser and server.
Roles, permissions and a full audit trail of every change. You always know who did what.
Automatic daily backups — weeks of safety net.
Validated, real-time data flow with LHDN. Your tax compliance is literally built in.
Face, ANPR and visitor data with explicit consent capture, purpose limits and retention windows.
Every action — who, what, when, from which device — recorded via in_syslog.
HOMESERVA’s AI and IoT integration was developed under the consultation of Ts. Dr. Leong Yee Rock (Alex), in line with industry best practices and ISO-aligned methodologies.
No call queues. No press 1 for English. Just Patrick on +60 19-688 3338, with a proper team behind him.
Patrick on +60 19-688 3338. Onboarding training included for every community.
Maintenance is announced ahead on WhatsApp and scheduled outside office hours where possible.
Two to three hands-on sessions during Week 2, with templates and printable QR posters for resident rollout.
Reviewed quarterly. If multiple communities need the same thing, it usually ships in the next release.
Larger communities get a named contact who knows your property. No tier-1 ping-pong.
Free demo. Free trial. Custom monthly subscription per property. No setup fee for the standard SKU.
For boutique communities, single clubhouses or starter gyms.
Most condos, sports clubs and mid-size properties land here.
Mixed-use developments, multi-property operators and enterprise.
Six stories we hear over and over from residents using HOMESERVA.
"Capability: the resident PWA (app.php) and online customer-payment portal let residents settle invoices via FPX, card or e-wallet through Xendit — the PHPMailer receipt arrives in the same flow."
"Capability: SmartFACE biometric (smartface.php / face_rec.php) replaces lost-card rituals — residents walk up and the door opens, with the access event logged for audit."
"Capability: the courier PWA (delivery_app.php) writes parcel + locker bay against the household; the parcel-camera event hits cam_rece_log.php and the resident app receives a push notification with the photo."
"Capability: residents pre-register guests in bulk from the customer app; each pass carries a hashed QR (qrcode_check.php) that the guard scans on arrival. Visitor type rules (visitors_type.php) carry capacity, grace-period and bulk-booking flags so peak-day waves of guests still flow."
"Capability: bookings.php enforces overlap rules at the database layer — the booking status lifecycle (functions.php:4314, :31085) blocks doubles and records every amendment with an audit trail."
"Capability: SmartFACE (lobby), access_devices_lift.php (lift per-floor entitlement) and check_auto_lighting.php (corridor lighting) all react on the same authenticated access event — no card, no fumbling."
Every industry has its alphabet soup. Here's ours, decoded — no jargon hiding the meaning.
Click any question to expand. If yours isn't here, just WhatsApp Patrick.
Just a direct conversation about whether HOMESERVA fits your community. WhatsApp or email — whichever you prefer.
The HOMESERVA security app is the lean two-tab tool a guard carries on patrol — check a visitor in by scanning their QR, tap each patrol checkpoint as you walk it, and see resident SOS alerts the moment they're raised. Tap a tab below to switch screens.
Every check-in, checkpoint and SOS acknowledgement writes to the same audit trail the committee reads — nothing lives on paper. Face-unlock matching happens on the device at the lobby, not in the app. Powered by VYROX AI.
SOS types match the real model: Security Guard, Ambulance, Police, Fire Fighter, Other. Acknowledge → Completed; response time is captured.
A resident requests a concierge service from the app — key handover, laundry pick-up, pram loan — and the front desk works it from one list. Every request shows the unit, the resident, the service, any deposit held and the charge.
| No. | Created | Unit | User | Concierge Service | Deposit (RM) | Charge (RM) | |
|---|---|---|---|---|---|---|---|
| 1 | 22-May-2026 | A-12-04 | Wei Sheng | Key handover to cleaner | 50.00 | 10.00 | Pending |
| 2 | 22-May-2026 | B-08-11 | Nurul A. | Laundry & dry-clean pick-up | 0.00 | 25.00 | In progress |
| 3 | 21-May-2026 | C-03-02 | Rajesh K. | Baby pram loan (weekend) | 80.00 | 0.00 | Completed |
| 4 | 21-May-2026 | D-14-07 | Mandy T. | Parcel forwarding to office | 0.00 | 15.00 | In progress |
| 5 | 20-May-2026 | A-09-03 | Faizal R. | Floral arrangement on arrival | 0.00 | 120.00 | Completed |
| 6 | 20-May-2026 | B-15-09 | Grace L. | Airport limousine booking | 100.00 | 45.00 | Pending |
Deposits and charges flow straight into the same ledger as everything else, so the month-end concierge revenue line is computed by SQL aggregation — no side spreadsheet. Powered by VYROX AI.
The committee curates an emergency directory once and every resident sees it in the app — with the real, slightly unusual touch the software keeps: the distance from your building, so the nearest help is obvious in a hurry.
Curated once by the committee, distance-sorted so the nearest help shows first — a plain directory, no machine learning. Powered by VYROX AI.
The Apps tab is the home of the whole community in one tidy grid — bookings, visitors, smart access, the marketplace, lockers, EV charging, the help desk and more. Each tile only appears for residents whose community has switched that module on, and a red badge shows when something needs a hand.
These are the real tile labels the app ships. Residents see a friendly subset; staff and committee see the management tiles too. Powered by VYROX AI.
Resident EV bays bill per minute, and the management list shows every session live — a still-charging session keeps ticking until the car is unplugged, with the bill accruing on screen. The same columns the software keeps.
| No. | Customer | Parking Lot | Start Time | End Time | Rate | Billing Amount | Status | |
|---|---|---|---|---|---|---|---|---|
| 1 | Wei Sheng (A-12-04) | EV-01 | 20:46 | Still charging… | RM 0.30 / minute | RM 13.80 | Charging | |
| 2 | Nurul A. (B-08-11) | EV-02 | 19:10 | 20:02 · 52 min | RM 0.30 / minute | RM 15.60 | Completed | |
| 3 | Rajesh K. (C-03-02) | EV-01 | 16:30 | 18:12 · 102 min | RM 0.30 / minute | RM 30.60 | Completed | |
| 4 | Mandy T. (D-14-07) | EV-03 | 14:05 | 14:48 · 43 min | RM 0.30 / minute | RM 12.90 | Deleted |
Rate is set per charger; the bill is simply rate times minutes elapsed — the same arithmetic the software runs, posted straight to the resident's invoice. Powered by VYROX AI.