AUTOSERVA
phone_in_talk TALK_TO_PATRICK
AUTOSERVA, by VYROX INTERNATIONAL SDN BHD, is a unified property, facility and membership operations platform powered by the xSERVA core. It combines accounting and MyInvois (LHDN) e-invoicing, payments and collections, bookings, membership, AIoT smart-access (RFID, face recognition, license-plate recognition, smart intercom, lift and parking-lock control), helpdesk, POS, automation and a full mobile app suite — in a single dashboard. AUTOSERVA is the industrial control-room face of xSERVA, alongside sister brands SMARTSERVA, PROPSERVA, HOMESERVA and SPORTSERVA.
~/autoserva / control-room / index.live   |   ● SYSTEM ONLINE   |   STATUS LIVE
[ INDUSTRIAL OPERATIONS PLATFORM // POWERED BY xSERVA ]

ONE TERMINAL.
EVERY OPERATION
UNDER CONTROL.

One screen for the night-shift officer. One dashboard for finance. One mobile app for residents. AUTOSERVA wires MyInvois e-invoicing, auto-billing, AIoT access (RFID + face + plate), security ops, helpdesk and reporting into a single dense terminal — the kind your ops team can actually run a 24/7 site from without juggling six tabs.

SHELL // ops@autoserva ~ # PID 04412
# quickstart
$ autoserva init --site "your-property" --modules all
[OK] tenant provisioned in 00:00:42
$ autoserva connect --hardware rfid,face,plate,intercom,lift
[OK] 14 devices paired
$ autoserva go-live
[OK] live on autoserva.com
terminal BOOT_CONSOLE view_list VIEW_MODULES enquiry@vyrox.com
verified MyInvois (LHDN) READY hub MULTI-TENANT SaaS support_agent 24/7 DIRECT SUPPORT lock ENCRYPTED AT REST sensors AIoT-COMPATIBLE cloud MALAYSIA-HOSTED
// LIVE_STATUS_FEED
REFRESH 5s
[OK]e-invoice sync (MyInvois)142 docs
[OK]auto-billing enginescheduled
[OK]RFID gate north312 swipes
[OK]face-recog lobby A98.4% match
[OK]plate-recog gate-2operational
[WARN]camera #14 (carpark-B3)offline 02:14
[OK]lift access controller14 floors
[OK]Xendit gatewayRM 18,420
[OK]cron jobs (1m / 5m)on-time
[OK]helpdesk queue3 open
[OK]visitor pre-reg QR56 today
[OK]power monitor (kWh)stable
// sample frame · live tenants run real telemetry · figures illustrative
SITES_LIVE
= 100+
MONITORING
= 24/7
MODULES
= 12/12
SUPPORT_HRS
= 24/7
[ POWERED BY xSERVA · BUILT BY VYROX · MyInvois (LHDN) READY · 5 BRANDS / 1 PLATFORM · 24/7 SUPPORT ]
[ MODULE_INDEX // 12 PILLARS ]

EVERY MODULE. ONE DASHBOARD.

[ TLDR ] Twelve operational modules — accounting, e-invoice, payments, bookings, membership, AIoT access, helpdesk, POS, automation and mobile — running on one ledger, one role-based access model, one deployment.

Twelve operational pillars cover the entire lifecycle of a working site — from a tenant's first invoice to a security badge swipe at 03:47 in the morning. Click a row to expand the sub-feature listing.

[ID]
[ICN]
[MODULE]
[ACTION]
[01/12]
receipt_long
ACCOUNTING, INVOICING & E-INVOICE
▸ EXPAND

ACCOUNTING, INVOICING & E-INVOICE

Property finance teams juggle rental invoices, sinking-fund levies, fire insurance, deposits and consolidated statements across hundreds of customers — usually in three different systems. AUTOSERVA collapses every invoice type into one ledger with MyInvois (LHDN) submission baked in. Validation, signing, UUID storage and credit-note flow are automated end-to-end.

[ KEY_BENEFITS ]
  • [+]One ledger replaces spreadsheets + accounting software + manual e-invoice scripts.
  • [+]MyInvois validation, signing and submission run in the background with full audit trail.
  • [+]Bank reconciliation across multiple accounts in minutes, not afternoons.
// FIELD_EXAMPLE

A 480-unit condo finance team used to spend 4 days each month generating, printing and posting invoices. After cutover, the cron-driven billing run produces all 480 invoices, submits them to MyInvois and emails them to residents in under 12 minutes — finance now reviews exceptions instead of typing.

[ SUB_FEATURES ]
  • >> Invoices: standard, consolidated, rental, fire-charge, deposit, utility-billing (water + electricity)
  • >> Credit notes (issue + preview), invoice adjustments, voided invoices, customer refunds
  • >> Customer statements + GL statements (advances, deposits, unposted, refunds, adjustments, revenues)
  • >> Auto-generated maintenance fees, sinking-fund levies, late-payment interest advice
  • >> MyInvois (LHDN) UBL 2.1 JSON payload + signed submission + UUID/shareable URL storage
  • >> Walk-in buyer TIN fallback (EI00000000010) + bundled MSIC code list for line classification
  • >> Consumption tax (SST/GST) setup, multiple tax types, cash book, full general ledger
  • >> Bank reconciliation across multiple accounts + bank accounts master
  • >> External-pay public payment link (external_pay_invoice.php), invoice payment QR
  • >> Cashflow / cash book separate from GL · withdrawals (rental-collection payouts)
[02/12]
payments
PAYMENTS & COLLECTIONS
▸ EXPAND

PAYMENTS & COLLECTIONS

Chasing payments by phone is the silent killer of building finance teams. AUTOSERVA replaces the chase with an auto-billing engine that issues, dispatches and reconciles invoices on cron, with multi-method online payment via Xendit (QR, credit/debit card, Direct Debit). Failed charges are flagged, retried and escalated automatically.

[ KEY_BENEFITS ]
  • [+]Days-sales-outstanding drops as residents pay via FPX, card or e-wallet 24/7.
  • [+]Multi-gateway routing means a card decline tries another rail before failing.
  • [+]Webhook reconciliation matches every cent to the right invoice line.
// FIELD_EXAMPLE

A 6-tower mixed development with 1,420 units cut its average collection time from 38 to 11 days by enabling auto-debit + reminder cadence; manual follow-up calls dropped from ~120 per month to under 20.

[ SUB_FEATURES ]
  • >> Auto-billing engine + auto-payment scheduling + saved cards (auto_payments.php)
  • >> Online customer payment portal · captive pay pages (capt.php, external_pay_invoice.php)
  • >> Xendit gateway: QR pay · credit/debit card · Direct Debit · FPX
  • >> E-wallet rails through Xendit: Touch'n Go, Boost, GrabPay, ShopeePay, DuitNow QR
  • >> Razer Gateway endpoint reference (sandbox) for legacy rails
  • >> Payment verification workflow + manual proof-of-payment approvals (payment_approvals.php)
  • >> Receipt issue/reprint, refunds (single + bulk), invoice-level refund flow
  • >> Transaction-charge bookkeeping: BA / CC / GA charges, withdrawal payouts
  • >> App-side success / failure callbacks for mobile-initiated payments
  • >> Webhook-driven reconciliation across QR, card, Direct Debit and e-wallet events
[03/12]
event_available
BOOKINGS & RESERVATIONS
▸ EXPAND

BOOKINGS & RESERVATIONS

Booking conflicts and clipboard schedules turn the simplest amenity into a complaint magnet. AUTOSERVA gives every facility, court, function room and class a calendar with rule-based cut-offs, recurring bookings and QR confirmation. Residents self-serve; staff own only the exceptions.

[ KEY_BENEFITS ]
  • [+]Self-service booking via the resident app, no front-desk queue.
  • [+]Cut-off, blackout and public-holiday rules prevent over-booking automatically.
  • [+]QR confirmation doubles as the access key at the door.
// FIELD_EXAMPLE

A racquet club with 12 courts shifted from a paper grid to AUTOSERVA bookings; member-led booking volume rose 38% in the first quarter while front-desk booking workload dropped by 70%.

[ SUB_FEATURES ]
  • >> Facility & court booking calendar (bookings.php, pages/bookings.php)
  • >> Facility setup + facility types · common-area master
  • >> Golf-bookings (tee-time slots) · participant check-ins for classes & events
  • >> Class & coach bookings · class passes · class types · coach scheduling
  • >> Common-area reservations (BBQ, function room, gym, pool)
  • >> Court-change, bulk-add, cart-style booking, booking-refund flow
  • >> Recurring bookings + full change-history audit (bookings_chg.php)
  • >> Cut-off-time enforcement, public-holiday rules, blackout windows
  • >> Booking approval / refund / reject workflow inside operator console
  • >> QR-code booking confirmation doubles as the access key at the door
  • >> Facility utilisation report (facility_util.php) — heatmap by slot
[04/12]
badge
MEMBERSHIP & CUSTOMER MANAGEMENT
▸ EXPAND

MEMBERSHIP & CUSTOMER MANAGEMENT

Membership and lease records scattered across spreadsheets, photocopies and email folders make audits painful and renewals lossy. AUTOSERVA centralises every customer, sub-account, contract, document and photo in one master record with full change history. Renewal cadences and approval workflows run on rails.

[ KEY_BENEFITS ]
  • [+]A single source of truth for every member, tenant and sub-account.
  • [+]Approval-gated self-service for address, contact and KYC updates.
  • [+]Document and photo uploads attached directly to each contract.
// FIELD_EXAMPLE

A community of 1,200 leases moved off a 9-tab spreadsheet into the customer master in two weeks; the next external audit closed in 3 days versus 11 days the previous year.

[ SUB_FEATURES ]
  • >> Customer master (accounts.php, customers.php) + sub-users / sub-accounts
  • >> Tenant accounts separate from owner customer · Management Committee & Sub-MC roles
  • >> Lease lifecycle: proposals, in-force agreements, not-in-force agreements
  • >> Rentals master + rental types + auto-generated rental invoices
  • >> Customer dashboard + customer info + information-change requests (approval-gated)
  • >> Bulk owner CSV import (import_owners.php) — legacy lists in one pass
  • >> First-time-login flow + login guides + captive portals (capt_signup.php, capt_forgot.php)
  • >> Memberships (paid plans, members, classes) + admin-level Membership Plans
  • >> Payment-method verification + membership-tier approval workflow
  • >> Document & photo upload attached to each contract; full change-tracking audit
[05/12]
security
SMART ACCESS CONTROL & AIoT
▸ EXPAND

SMART ACCESS CONTROL & AIoT

Gate hardware, lift controllers and cameras typically come from five different vendors with five separate dashboards. AUTOSERVA brokers them all under one access policy: who, what door, what floor, what time. Device health, swipe logs and override events live in a single audit feed.

[ KEY_BENEFITS ]
  • [+]One access policy controls RFID, face, plate, intercom, lift and parking-lock together.
  • [+]Brand-agnostic — generic IP cameras (HTTP snapshot & event ingest) and MIFARE-compatible RFID readers.
  • [+]Device health alerts surface offline cameras and readers before residents notice.
// FIELD_EXAMPLE

A condo replaced four legacy controllers with AUTOSERVA-paired devices and consolidated audit. After 30 days, mean detection time for an offline reader dropped from ~8 hours (resident-reported) to under 4 minutes (auto-alert).

[ SUB_FEATURES ]
  • >> RFID smart cards · MIFARE-compatible readers · admin card-check (smartcard.php, cards.php)
  • >> Face recognition — SmartFACE biometric access (smartface.php, face_rec.php)
  • >> License-plate / ANPR — SmartVE LPR cameras (smartve.php, ve_rec.php)
  • >> Smart intercom — SmartINTE / Integrated Smart Access (smartinte.php)
  • >> Lift access controllers with floor-level restriction (access_devices_lift.php)
  • >> Parking-lock control + wheel-clamp escalation module (plc_response.php, clamp.php)
  • >> Smart mirrors + micode access codes (smartmirror.php, up_micode.php)
  • >> Smart lighting automation + lighting records (check_auto_lighting.php)
  • >> Power monitoring — kWh telemetry per circuit (powermonitor.php)
  • >> Intrusion alarm-panel server receiver (intru_server_rece.php) + intrusion-photo cleanup
  • >> Delivery lockers + locker config + delivery courier app (delivery_lockers.php, delivery_app.php)
  • >> Generic IP cameras — HTTP cgi-bin snapshot & event ingest (ipcameras.php, cam_rece_log.php)
  • >> IoT device heartbeat + swipe heartbeat probes (check_iot_up.php, check_swipes.php)
  • >> AIoT device registry + lift / face / general device pages (access_devices.php)
  • >> DLCSP — proprietary Door-Lock Control Service Protocol for doors & lockers
  • >> SM4 32-round cipher — Chinese block cipher encrypts device-protocol traffic
  • >> QR keys + generic QR access + QR-check terminals (qr_keys.php, qrcode_access.php)
[06/12]
domain
PROPERTY & FACILITY SETUP
▸ EXPAND

PROPERTY & FACILITY SETUP

Modelling a property correctly is the foundation everything else builds on — units, parking bays, EV bays, lockers, amenities and rates need a clean structure or every report comes out wrong. AUTOSERVA gives you a flexible hierarchy down to bay-level with QR per asset. Rates, fees and charges plug into invoicing automatically.

[ KEY_BENEFITS ]
  • [+]Bay-level modelling for parking, EV charging, lockers, amenities.
  • [+]QR codes per amenity for booking, fault-reporting and check-in.
  • [+]Rates and fees flow straight into auto-billing without re-entry.
// FIELD_EXAMPLE

A mixed-use building with 220 units, 380 parking bays and 18 EV bays mapped its full asset tree in a 2-day import; EV revenue went from "estimated" to "metered + billed" the same week.

[ SUB_FEATURES ]
  • >> Units / blocks / floors / zones — hierarchy down to bay-level
  • >> Common areas + facility types + property features master
  • >> Parking bay setup + parking-lot types (visitor / reserved / paid / EV)
  • >> EV charging bays + deposit + session API metering (ev_parking_lots.php)
  • >> Wheel-clamp / boom-gate enforcement module (clamp.php)
  • >> Smart parking-lock device control (parking_locks_config.php, plc_response.php)
  • >> Delivery lockers + locker config + QR-per-locker (DLCSP)
  • >> Self-service laundry amenities + QR-per-machine (amenities.php, amenities_qr.php)
  • >> Public holidays / calendar master · cut-off time master
  • >> Rates / fees / charges master + revenue definition + transaction-items catalog
  • >> Property QR code (property_qr.php) per project — fault-report + onboarding
[07/12]
perm_identity
VISITORS & GUESTS
▸ EXPAND

VISITORS & GUESTS

Visitor management is where guards burn out: paper logbooks, missed calls and no audit trail. AUTOSERVA flips this with resident-driven pre-registration, QR visitor passes and live blacklist/whitelist enforcement at the gate. Approvals route to the right host with photo and plate evidence on file.

[ KEY_BENEFITS ]
  • [+]Residents pre-register visitors and the guard just scans a QR.
  • [+]Approval workflow routes to the right host, multi-level if needed.
  • [+]Live dashboard of who is on-site, with photo and plate evidence.
// FIELD_EXAMPLE

A community gate processing 200+ visitors a day cut average visitor approval time from ~4 minutes (phone-based) to under 90 seconds (pre-reg + QR), a ~60% improvement, while every entry is now logged with photo and plate.

[ SUB_FEATURES ]
  • >> Visitor registration with document & vehicle photo upload (visitors_doc.php, visitors_carphoto.php)
  • >> Visitor types · QR visitor pass · visitor-pass charges (visitor_pass_qr_chgs.php)
  • >> Resident-driven pre-registration · multi-level host approval workflow
  • >> Visitor parking allocation + visitor parking pass with QR
  • >> Black/white-list enforcement at the gate (bwlist.php)
  • >> Most-visited & repeat-visitor analytics (most_visited.php)
  • >> Contractor service permits + permit-validity audit log (cs_settings.php)
  • >> Live visitor dashboard with photo + plate + host evidence on file
[08/12]
videocam
SECURITY OPERATIONS
▸ EXPAND

SECURITY OPERATIONS

Security operations live or die on shift handover. AUTOSERVA is the duty-officer terminal: open tickets, offline cameras, visitor approvals, intrusion alerts and SOS calls — all on one screen. Incidents are logged with timestamp, evidence and lifecycle status, ready for audit.

[ KEY_BENEFITS ]
  • [+]Shift handover compresses to a single screen.
  • [+]Every swipe, override and incident is logged with evidence.
  • [+]SOS button on the resident app routes straight to duty officer.
// FIELD_EXAMPLE

A high-rise duty room replaced 3 separate dashboards (RFID, CCTV, visitor) with the AUTOSERVA security console; shift handover dropped from 22 minutes to under 5, with incident reports filed directly from the same screen.

[ SUB_FEATURES ]
  • >> Live Security Monitor: intrusion alerts · photo events · digital events (security_monitor.php)
  • >> Emergency SOS — one-tap from resident app, broadcast to duty console (emergency_sos.php)
  • >> Emergency phone-number directory (emergency_numbers.php) — fire / police / on-call ops
  • >> Security mobile app (security_app.php) for roving guards — guard-stand workflows
  • >> Swipe audit (check_swipes.php) · card swipes heartbeat · denied-access flagging
  • >> Incident reports (incidents.php) with timestamp, evidence and lifecycle
  • >> Defect reports routed to facilities team · meeting minutes archive
  • >> System logs (logs.php) + audit log via debugv_access (in_syslog / in_debugv)
  • >> Blacklist / whitelist management at gate / lift / lobby
  • >> IP camera receive log (cam_rece_log.php) · intrusion-server feed (intru_server_rece.php)
  • >> IP server event ingest (ip_server_rece.php) for cross-device correlation
[09/12]
support_agent
CONCIERGE, COMPLAINTS & HELPDESK
▸ EXPAND

CONCIERGE, COMPLAINTS & HELPDESK

Most resident complaints get lost in chat threads or sticky notes on the building manager's desk. AUTOSERVA gives every complaint a ticket number, a queue, an SLA timer and a closure note. Meeting minutes, contractor permits and lost-and-found are tracked in the same lifecycle.

[ KEY_BENEFITS ]
  • [+]Every complaint has a ticket number and an SLA clock.
  • [+]Routing matrices push tickets to the right team automatically.
  • [+]Closure notes and audit trail end "he-said-she-said" disputes.
// FIELD_EXAMPLE

A 700-unit residence saw resolution time on plumbing and electrical complaints fall by ~70% (from average 48h to ~14h) after enabling SLA-driven routing and resident email notifications.

[ SUB_FEATURES ]
  • >> Complaints logging + SLA queue + closure note (complaints.php)
  • >> Suggestions module — resident-submitted ideas with approval lifecycle
  • >> Ticket types master + generic ticketing module (ticketing.php)
  • >> Helpdesk routing matrices + front-of-house queue (helpdesk.php)
  • >> Lost-and-found registry with claim workflow (lost_and_found.php)
  • >> Concierge service catalog + bookable concierge tasks (concierge_type.php)
  • >> TukangMan handyman link-out — external handyman dispatch (tukangman.php)
  • >> Announcements broadcast to PWA + email (announcements.php)
  • >> Internal mail / operator-to-resident mailbox threads (mail.php)
  • >> Meeting minutes archive with attachments + follow-up tracking
  • >> Contractor service permit tracking + permit audit log
[10/12]
storefront
POS & MARKETPLACE
▸ EXPAND

POS & MARKETPLACE

F&B outlets, pro shops, vending and merchant booths inside a property usually run their own POS — separate inventory, separate reports, separate reconciliation. AUTOSERVA's built-in POS (POSERVA) and merchant onboarding pull all of it into the same financial backbone, with a community marketplace as a member-only channel.

[ KEY_BENEFITS ]
  • [+]In-house F&B and pro-shop sales report alongside facility revenue.
  • [+]Merchants onboard once and appear in the resident marketplace.
  • [+]Membership-tier promotions tie POS to membership plans.
// FIELD_EXAMPLE

A clubhouse F&B outlet running a generic POS migrated to POSERVA; member-charge-to-room volume rose 28% because charging to the membership account took one tap instead of cash/card.

[ SUB_FEATURES ]
  • >> POSERVA point-of-sale settings + per-outlet config (poserva_settings.php)
  • >> Stocks master + stock groups + classification (stocks.php, stocks_group.php)
  • >> Daily sales tape + per-outlet sales reporting (sales.php)
  • >> Member-charge-to-account at the till — POS lines post to GL
  • >> Merchant onboarding (merchants.php) + merchant captive login (mer_capt.php)
  • >> Community Marketplace — resident classifieds + merchant storefronts
  • >> Admin-level marketing Campaigns module + membership-plan promotions
  • >> Transaction-items catalog + revenue-definition mapping per item
[11/12]
memory
AUTOMATION & REPORTING
▸ EXPAND

AUTOMATION & REPORTING

Manual recurring tasks — month-end billing, reminder cadences, fee escalations, report generation — devour ops bandwidth. AUTOSERVA runs cron-driven jobs at minute and 5-minute granularity for every recurring action, with a rule engine for auto-billing and a deep set of finance and operational reports.

[ KEY_BENEFITS ]
  • [+]Month-end is no longer a person; it is a cron job.
  • [+]Reminder cadences, escalations and late-fee rules are configured once.
  • [+]Reports cover GL, cashflow, CN, invoice runs and operational KPIs.
// FIELD_EXAMPLE

Finance teams routinely report 60-80% reduction in time-to-close at month-end after adopting auto-billing + auto-reminders, and ~40% faster delivery of management committee reporting packs.

[ SUB_FEATURES ]
  • >> Per-minute cron worker (cron_minute_work.php) + 2-min & 5-min variants
  • >> Auto-generation engine: maintenance fees · sinking fund · late-payment interest · rentals · statements
  • >> Auto-billing rule engine + reminder cadences (auto_billing.php, reminder.php)
  • >> Auto-payments / saved-card scheduling (auto_payments.php)
  • >> Housekeeping crons: amenity auto-stop · expired-booking cleanup · child-membership purge · intrusion-photo cleanup
  • >> Heartbeat crons: IoT device check · card-swipe check · auto-lighting check
  • >> Approval-workflow master: payments · company · sub-account · booking · membership
  • >> Financial reports: P&L, cashflow, GL invoices, GL credit notes, statements (financial_reports.php)
  • >> Facility utilisation report · most-visited / repeat-visitor analytics
  • >> Operator dashboards (dashboard.php) + customer dashboards (cus_dashboard.php)
  • >> PDF generation engine (pdf_paper.php) with paper-size selection
[12/12]
qr_code_2
MOBILE, QR & SELF-SERVICE
▸ EXPAND

MOBILE, QR & SELF-SERVICE

Phone-based ops puts the operator on stage 24/7 — every visitor, every parcel, every booking is a phone call. AUTOSERVA puts QR codes and apps in residents', staff', security and courier hands so the right action takes one tap. The control room only sees exceptions.

[ KEY_BENEFITS ]
  • [+]Four role-specific apps share one backend, one role matrix.
  • [+]QR everywhere: invoices, lockers, gates, visitors, amenities.
  • [+]Self-service for billing, bookings, complaints and visitor invites.
// FIELD_EXAMPLE

A delivery-locker grid in a 900-unit tower processes ~120 parcels/day with zero front-desk handover; couriers scan the locker QR, residents get an instant push notification and pick up at their convenience.

[ SUB_FEATURES ]
  • >> Customer / resident PWA mobile app (app.php, appfs.php, app_auth.php)
  • >> Staff / management mobile app (staffapp.php)
  • >> Security guard mobile app (security_app.php) for roving patrols + SOS receive
  • >> Delivery courier mobile app (delivery_app.php) for locker drop-offs
  • >> Merchant captive login + public captive flows (mer_capt.php, capt.php, capt_signup.php)
  • >> QR codes: property QR · invoice payment QR · amenity QR · locker QR · visitor QR · contractor QR
  • >> QR keys + QR access + QR check at gates, lifts and amenities
  • >> Self-service laundry start/stop via amenity QR · self-service customer portal
  • >> Public REST API namespace (api/) — login, project scope, member detail, EV session
// every pillar runs on the same xSERVA core. enable per-tenant. no forks. no surprises.
[ PLAIN_ENGLISH // for_non_ops_audiences ]

IN ORDINARY WORDS — WHAT AUTOSERVA DOES.

[ TLDR ] If you only have 30 seconds: here is the whole platform without the jargon — one paragraph per module.

The terminal styling above is for ops teams. This block is for the finance manager, the chairperson, the resident-committee member, and anyone who just wants to know what the software does in plain English.

[ 01/12 ]
Invoicing & e-invoice

We generate every invoice — maintenance, rental, utility, deposits, fire-charge — submit them to LHDN MyInvois automatically, and keep one tidy customer statement.

[ 02/12 ]
Online payments

Residents pay by QR, card, bank-direct-debit or e-wallet (TNG, Boost, GrabPay, ShopeePay, DuitNow). The system reconciles each payment to the right invoice automatically.

[ 03/12 ]
Auto-billing

Recurring fees, sinking fund, interest and rentals are generated on a schedule. Finance reviews exceptions instead of typing invoices.

[ 04/12 ]
Bookings

Residents and members book courts, function rooms, BBQ pits, classes and coaches from the app. Cut-off and public-holiday rules stop double-bookings.

[ 05/12 ]
Memberships

Family sub-accounts, member tiers, class passes and renewal cadences all live in one customer record.

[ 06/12 ]
Smart access

Cards, faces, plates and intercoms share one access policy. The right person opens the right door at the right time — every event logged.

[ 07/12 ]
Visitors

Residents pre-register visitors. The guard scans a QR. Every entry has a photo, plate and host on record.

[ 08/12 ]
Security operations

One duty-officer screen: open tickets, offline cameras, SOS calls, visitor approvals. Shift handover takes minutes.

[ 09/12 ]
Helpdesk & complaints

Every complaint has a ticket number, an SLA clock and a closure note — no more "WhatsApp scroll".

[ 10/12 ]
POS & marketplace

In-house F&B and pro-shops run on our POS so sales feed the same books. Merchants appear on a community marketplace.

[ 11/12 ]
Mobile apps

Four role-based apps: resident, staff, security guard, delivery courier. Same backend, same role matrix.

[ 12/12 ]
Open API & integrations

Connect to MyInvois, Xendit, AutoCount, and your own systems through 60+ documented endpoints.

// keep scrolling for the dense ops-room version. same product, more detail.
[ AUTOGEN // cron-driven_generators ]

THE AUTO-GENERATION ENGINE.

[ TLDR ] Cron-driven generators replace month-end people: maintenance fees, sinking fund, interest, rentals and statements run on schedule; minute-level housekeeping jobs sweep amenities, bookings, memberships and IoT heartbeats 24/7.

Below is the literal list of generators that fire on cron — the ones that replace clerks and the ones that run every minute keeping the site clean.

 [ AUTOGEN_01 ] SCHEDULED // billing_generatorsCRON
$ generate_ma.php / generate_mf.php
MAINTENANCE_FEES
Per-unit monthly maintenance fee posted to the customer ledger, with rate cards by unit type.
$ generate_sink.php
SINKING_FUND
Reserve-fund levy per strata property, separate GL bucket, audit-ready.
$ generate_interest.php
LATE_INTEREST
Late-payment interest advice computed against ageing balances on the configured cadence.
$ generate_rentals.php
RENTALS
Rental invoices per active tenancy agreement, prorated for partial months.
$ generate_statement.php
STATEMENTS
Customer statements rolled up across charges, payments, deposits and adjustments.
 [ AUTOGEN_02 ] 24/7 // minute_workersEVERY 1m / 5m
cron auto_stop_amen Stop self-service laundry / amenity sessions when their paid window closes.
cron auto_cc_booking Auto-charge saved cards for confirmed bookings just before start time.
cron auto_booking_ex Expired-booking cleanup — release slots when a booking lapses without check-in.
cron gen_mf (per-minute) Trigger maintenance-fee generation windows on tenant-specific schedules.
cron clear_intru_pho Intrusion-photo cleanup — purge captured frames past the retention window.
cron del_child_mem Child-membership purge — remove expired sub-membership rows from tier tables.
cron check_iot_up IoT heartbeat — ping every paired device; raise an alert if it stops answering.
cron check_swipes Card-swipe heartbeat — verify readers are emitting events on schedule.
cron check_auto_lighting Auto-lighting check — drive on/off cycles based on time-of-day rules.
// source: cron_minute_work.php / cron_minute_work_2.php / cron_minute_work_5.php
[ INTEGRATIONS // ls -la /etc/integrations.d ]

THE INTEGRATION LAYER.

[ TLDR ] Every external system AUTOSERVA actually speaks to — named and versioned. No vapour: if it is listed here it has code paths in the platform.

Every connector is brand-agnostic where the protocol allows. Where the device dialect is proprietary (SmartFACE / SmartVE / SmartINTE / DLCSP / SM4) we ship the protocol.

# ops@autoserva:~$ list-integrations --all EXIT 0
[FINANCE]
MyInvois (LHDN)
UBL 2.1 JSON · MSIC code list · walk-in TIN EI00000000010 · UUID + sharing URL stored per invoice · sandbox + production · functions_einv.php · submit_einvoice.php
[FINANCE]
Xendit gateway
Webhook events qr.payment / CREDIT / DEBIT / DIRECT_DEBIT / FPX · xendit_payment_response.php · xendit_waiting_payment.php
[FINANCE]
Xendit e-wallets
Touch'n Go · Boost · GrabPay · ShopeePay · DuitNow QR — routed through Xendit (api_doc.php, appfs.php evidence)
[FINANCE]
Razer Gateway
Sandbox endpoint referenced for legacy rails
[ACCOUNTING]
AutoCount read API
integration/autocount_api.php — read-side authoritative data pull
[ACCOUNTING]
AutoCount Connector (push)
Bearer-token middleware at safetech.org.my/VYROX-AutoCount-Connector/xSERVA · invoice-api + payment-api · invoice / payment / cancel / undo flows
[ACCESS]
Generic IP cameras
HTTP cgi-bin snapshot & event ingest · basic-auth · ipcameras.php · ip_server_rece.php
[ACCESS]
RFID readers
MIFARE-compatible · smartcard.php · cards.php · admin_check_card.php
[ACCESS]
SmartFACE / SmartVE / SmartINTE
Brand-agnostic face / LPR / intercom device protocol family
[ACCESS]
SM4 cipher
Chinese 32-round block cipher for device-protocol encryption (sm4.php)
[ACCESS]
DLCSP
Door-Lock Control Service Protocol — delivery lockers + door locks (dlcsp.php, dlcsp_qr.php)
[MAIL]
PHPMailer
Outbound invoices · OTPs · visitor QRs · reminders · complaint status
[CUSTOMER]
TukangMan
Handyman link-out to tukangman.com
[BRAND]
VYROX AIoT
Parent brand — footer attribution, hardware family namespace
[MOBILE]
Mobile API (api/)
PWA login · project scope · member detail · me_details · QR add-project
[DEVELOPER]
Public API doc
/api_doc.php — 60+ documented endpoints for partners and integrators
// Not listed: WhatsApp/SMS gateways · ONVIF · Wiegand · OSDP · SSO providers — these are not present in code. Patrick reaches you on WhatsApp as a sales/support channel, not a system feature.
[ DEVELOPER // curl --bearer ]

OPEN API. 60+ ENDPOINTS.

[ TLDR ] /api_doc.php enumerates 60+ REST endpoints for integrators — visitor flow, EV charging deposit/session, sub-account, announcements and more. Bearer-token auth. Webhooks for payment events.

If your ops team has its own dashboards, BI tools or partner systems, they consume AUTOSERVA the same way our own mobile apps do.

// SAMPLE_CALLS · /api_doc.php200 OK
POST /api/app_00_user_login Authenticate a resident; returns bearer token + project scope.
POST /api/app_00qr_add_project Bind a property QR to the signed-in user.
GET /api/app_05me Fetch the signed-in customer dossier.
GET /api/me_details_example Detailed example dossier with sub-accounts & permissions.
POST /api/visitor/register Create a pre-registered visitor; emits a QR via PHPMailer.
GET /api/visitor/{id} Fetch a visitor record including doc + car photos.
POST /api/ev/deposit Place a top-up deposit on an EV charging account.
POST /api/ev/session/start Start a metered EV charging session against a paired bay.
POST /api/ev/session/stop End the session; kWh billed against the deposit.
POST /api/sub_account/invite Invite a sub-user under the primary customer.
POST /api/announcement/publish Publish an announcement to a project audience.
POST /webhook/xendit Receive QR / card / Direct Debit / e-wallet payment events.
// EXAMPLE · curlSHELL
# list visitor records for a project
$ curl -s https://autoserva.example/api/visitor \
-H "Authorization: Bearer $AUTOSERVA_TOKEN" \
-H "Accept: application/json"
200 OK · returns [{ "id":..., "name":..., "qr":..., "host":..., "entered_at":... }, ...]
# start an EV charging session
$ curl -s -X POST https://autoserva.example/api/ev/session/start \
-H "Authorization: Bearer $AUTOSERVA_TOKEN" \
-d '{ "bay":"EV-B14", "vehicle":"WXR-7712" }'
200 OK · returns { "session_id":..., "started_at":..., "deposit_remaining":... }
# register a webhook handler for Xendit payments
$ curl -s -X POST https://autoserva.example/webhook/xendit \
-H "Content-Type: application/json" \
-d '{ "event":"qr.payment", "data": { ... } }'
200 OK · reconciled to invoice line · cashbook updated
// Full enumeration at /api_doc.php on the live tenant. Sandbox + production tokens supplied during onboarding.
[ MANIFEST // autoserva --list-all ]

// COMPLETE OPERATIONS MANIFEST

[ TLDR ] The full feature index. Grouped by inventory domain. ~200 bullets that map 1:1 to the audited source. Use it as a checklist when scoping.

Auto-generated from the audited _FEATURE_INVENTORY.md catalog. Every bullet has source code behind it.

# man autoserva-allPAGE 1 / 1
// [01] ACCOUNTING & INVOICING  (18)
>> Standard invoice
>> Consolidated invoice
>> Utility billing invoice (water + electricity)
>> Rental invoice
>> Fire-charge invoice
>> Standard deposit invoice + refund invoice
>> Credit notes (issue + preview)
>> Invoice adjustments
>> Voided invoices
>> Invoice payment QR + print QR
>> Late-payment interest advice
>> Sinking fund generator
>> Maintenance fee generator
>> Customer statements (gl_statement, manage_statement, generate_statement)
>> MyInvois UBL 2.1 payload builder
>> MyInvois submission + share URL
>> Consumption tax setup + single tax
>> External public-pay invoice link
// [02] PAYMENTS & GATEWAYS  (10)
>> Xendit webhook receiver (QR / CC / DC / Direct Debit / FPX)
>> E-wallets via Xendit: TNG · Boost · GrabPay · ShopeePay · DuitNow QR
>> Razer Gateway sandbox reference
>> Payment processing + pay-invoice + payment response
>> Manual payment-proof approvals
>> Auto-payments / saved cards
>> Receipts issue + reprint
>> Single + bulk refunds
>> BA / CC / GA transaction-charge bookkeeping
>> App success/failure callbacks
// [03] BANKING / GL / CASHFLOW  (10)
>> Bank accounts master
>> Bank reconciliation (bankrecon)
>> Bank-details (gateway processors)
>> Cash book
>> GL master + transactions
>> GL invoices · GL credit notes · GL statements
>> Financial reports (P&L, cashflow)
>> Facility utilisation report
>> Withdrawals (rental-collection payouts)
>> Customer advances
// [04] CUSTOMER & SUB-ACCOUNTS  (8)
>> Customer master (accounts, customers)
>> Customer info + dashboard + information page
>> Sub-users / sub-accounts
>> Information change requests (approval-gated)
>> Owner bulk CSV import
>> Staff user accounts
>> First-time login + login guide
>> Captive signup · captive forgot password
// [05] LEASE LIFECYCLE  (5)
>> Tenancy proposals
>> In-force agreements
>> Not-in-force agreements
>> Rentals master + rental types
>> Auto-generated rental invoices
// [06] MEMBERSHIPS / CLASSES  (6)
>> Members (per-project)
>> Admin-level Membership Plans
>> Classes + class types
>> Class passes + class passes list
>> Class bookings
>> Coaches scheduling
// [07] BOOKINGS  (8)
>> Facility bookings + change history
>> Facility setup + facility types
>> Golf bookings
>> Class bookings
>> Common-area reservations
>> Court-change · bulk-add · cart booking · refund booking
>> Cut-off-time master · public-holiday rules
>> QR booking confirmation
// [08] PROPERTY SETUP  (6)
>> Units · Blocks · Floors · Zones
>> Parking bay setup + parking-lot types
>> Common areas + facility types
>> Property features master
>> Property QR code
>> Public-holiday calendar
// [09] PARKING & EV  (8)
>> Visitor parking
>> Reserved parking
>> Paid parking
>> EV-charging parking lots
>> Smart parking-lock device control
>> Plc response (lock state callback)
>> Wheel-clamp enforcement module
>> EV deposit + session API
// [10] VISITORS  (8)
>> Visitor records + visitor types
>> Visitor document upload
>> Visitor car-photo upload
>> Visitor pass + QR
>> Visitor-pass QR charges
>> Visitor parking allocation
>> Black/white-list enforcement
>> Most-visited / repeat-visitor analytics
// [11] SMART ACCESS & AIoT  (15)
>> RFID smart cards · cards · admin card-check
>> QR code access + QR check
>> Face recognition (SmartFACE)
>> License-plate recognition (SmartVE)
>> Smart intercom (SmartINTE)
>> Integrated Smart Access
>> Smart mirrors + micode
>> Lift access control
>> General AIoT device registry + IoT page
>> SM4 cipher for device-protocol encryption
>> Access-device probes / IoT heartbeat
>> Swipe heartbeat
>> QR keys
>> DLCSP — door-lock control service protocol
>> DLCSP QR
// [12] IoT MONITORING  (9)
>> IP cameras + cam receive log
>> Intrusion server receiver + intrusion test log
>> IP server event ingest
>> Smart lighting + auto-lighting check
>> Power monitoring (kWh telemetry)
>> Smart mirrors
>> Delivery lockers + locker config
>> Delivery courier app
>> Parking locks
// [13] SECURITY OPS  (8)
>> Live security monitor (intrusion / photo / digital)
>> Security mobile app + style_vipass
>> Emergency SOS
>> Emergency phone-number directory
>> Black/whitelist
>> Logs
>> Card-swipe audit
>> Incident reports
// [14] CONCIERGE / HELPDESK  (12)
>> Concierge services + setup_concierge
>> Concierge type master
>> Complaints
>> Suggestions
>> Incident reports
>> Tickets + ticket types
>> Help desk
>> Lost & found
>> Internal mail
>> TukangMan link-out
>> Announcements
>> Meeting minutes
// [15] POS / MARKETPLACE  (7)
>> POSERVA settings
>> Stocks · stock groups · classification
>> Daily sales tape
>> Merchants
>> Merchant captive login
>> Community marketplace
>> Campaigns (admin marketing)
// [16] APPROVALS  (5)
>> Approvals master + management approvals
>> Payment approvals
>> Company approval + company-approved
>> Sub-account changes approval
>> Booking approval / refund / reject
// [17] AUTOMATION & CRON  (16)
>> Per-minute cron worker (×3 variants)
>> Auto-billing config + reminder
>> generate_ma / generate_mf — maintenance fees
>> generate_sink — sinking fund
>> generate_interest — interest advice
>> generate_rentals — rentals
>> generate_statement — statements
>> Auto-payments
>> Auto-lighting check
>> IoT heartbeat (check_iot_up)
>> Swipe heartbeat (check_swipes)
>> Amenity auto-stop
>> Auto-charge booking
>> Expired-booking cleanup
>> Child-membership purge
>> Intrusion-photo cleanup
// [18] REPORTS & ANALYTICS  (6)
>> Financial reports
>> Facility utilisation
>> Most-visited
>> Operator dashboard
>> Customer dashboard
>> System logs
// [19] MOBILE APPS  (6)
>> Customer / resident PWA (app.php, appfs.php)
>> Staff / management app
>> Security guard app
>> Delivery courier app
>> Merchant captive login
>> Public captive flows (capt.php)
// [20] QR CODES  (8)
>> Property QR
>> Invoice payment QR
>> Visitor pass QR + charges
>> QR keys
>> Generic QR access + QR check
>> Self-service laundry QR (amenities_qr)
>> Delivery locker QR (dlcsp_qr)
>> CSA QR (separate folder)
// [21] SELF-SERVICE  (4)
>> Self-service laundry / amenities
>> Customer captive payment
>> Owner first-login + reset
>> Forgot password · sign-up · register account
// [22] ADMIN  (8)
>> Management bodies (companies) + company approval
>> Projects + no-project landing
>> Employees / staff
>> Operator-level settings
>> Privacy / terms / disclaimer
>> API documentation page
>> AI tooling endpoint
>> PDF generation (pdf_paper)
// [23] TAX / MyInvois  (6)
>> Consumption tax types
>> Single tax
>> UBL 2.1 payload builder
>> Submit + share URL
>> MSIC code list
>> Walk-in TIN EI00000000010
// [24] INTEGRATIONS  (13)
>> MyInvois / LHDN
>> Xendit (QR / card / Direct Debit / FPX)
>> Xendit e-wallets (TNG · Boost · GrabPay · ShopeePay · DuitNow)
>> Razer Gateway sandbox
>> AutoCount read API
>> AutoCount Connector push (Bearer)
>> PHPMailer email
>> TukangMan link-out
>> VYROX AIoT parent brand
>> Mobile API namespace
>> SmartFACE / SmartVE / SmartINTE device protocols
>> SM4 cipher
>> DLCSP
// [25] DEVELOPER / API  (10)
>> /api_doc.php — 60+ documented endpoints
>> Visitor flow API
>> EV deposit + session API
>> Sub-account API
>> Announcements API
>> Login + project-scope API
>> me_details example
>> QR add-project API
>> Bearer-token auth
>> Webhook for payment events
# total bullets: 220 · domains: 25 # source: _FEATURE_INVENTORY.md · audited from xserva/ codebase
[ UI_MOCKUPS // RENDER_LIVE_FRAMES ]

SEE xSERVA IN ACTION.

[ TLDR ] Six terminal-rendered mockups — control-room dashboard, MyInvois invoice, mobile app, access log, booking grid and AIoT panel — drawn live in the page, no screenshots.

Every screen below is rendered as inline SVG and HTML — what you see is the actual visual vocabulary of the product, not marketing collateral.

 [ MOCK_01 ] DASHBOARD // CONTROL_ROOMLIVE
// SITE: TOWER_ASTATUS LIVE
UNITS
480
INV/MO
472
DEVICES
63/64
TICKETS
7
// PAYMENTS // 7-DAY TREND
// Operator-level overview, no tab juggling.
 [ MOCK_02 ] INVOICE // MYINVOIS_VALIDATEDLHDN_OK
INV-2026-04812
UUID 3f9a-7b2e-...-c41d
MyInvois VALIDATED
DESCQTYRATEAMT
Service charge — Apr 20261340.00340.00
Sinking fund levy168.0068.00
Carpark — bay #B-082185.0085.00
SST 6%——29.58
TOTAL_DUERM 522.58
// Validated & signed via LHDN MyInvois at 09:14:02.
 [ MOCK_03 ] MOBILE // RESIDENT_APPiOS / ANDROID
// One app: pay, book, host visitors.
 [ MOCK_04 ] ACCESS_LOG // LAST_8REALTIME
WHOGATEMETHODTIMESTATE
ATAndrew T. GATE_01FACE09:14:22 GRANTED
SKSiti K. LIFT_03RFID09:14:08 GRANTED
VRVendor R. GATE_02QR09:13:51 GRANTED
UNUnknown GATE_01FACE09:13:30 DENIED
JLJ. Lim LIFT_05RFID09:13:11 GRANTED
HMHafiz M. GATE_03PLATE09:12:48 GRANTED
NKN. Kaur LIFT_02RFID09:12:19 GRANTED
DVDelivery GATE_02QR09:11:55 GRANTED
// 1 denial in last 8 — flagged for review.
 [ MOCK_05 ] BOOKING_GRID // BADMINTON_W37 COURTS
SLOT MONTUEWEDTHUFRISATSUN
18-19 · ■ · ■ ■ ■ ·
19-20 ■ · ■ ■ YOU ■ ■
20-21 ■ ■ · ✕ · ■ ·
21-22 · · ■ · ■ · ✕
· FREE■ BOOKED✕ BLOCKEDYOU = COURT 3 · THU 19-20
 [ MOCK_06 ] AIoT // DEVICE_HEALTH14 / 14 ONLINE
IPCAM_LOBBY_01 CAMERA · HTTP_SNAP ONLINE
IPCAM_GATE_E2 CAMERA · ANPR ONLINE
IPCAM_POOL_01 CAMERA · IP_FEED SYNCING
RFID_GATE_E1 READER · MIFARE ONLINE
RFID_LIFT_T2 READER · MIFARE ONLINE
LIFT_CTRL_T1 CTRL · RELAY ONLINE
LOCK_BAY_B14 PARKING_LOCK OFFLINE
INTERCOM_TWR_A SIP · 5060 ONLINE
// Lock_Bay_B14 flagged at 09:11 — ticket auto-created.
[ PLATFORM_AGGREGATE // ALL_NODES ]

NUMBERS THAT MATTER.

[ TLDR ] Aggregate platform numbers across the xSERVA core — every figure is illustrative of total throughput, not a per-domain claim.

Across the xSERVA platform — the core that powers AUTOSERVA, SMARTSERVA, PROPSERVA, HOMESERVA and SPORTSERVA. Treat as illustrative aggregate, not per-tenant guarantees.

[01] PROPERTIES_SERVED
1,200+
Live tenants on the xSERVA core
[02] INVOICES / MONTH
89,000+
Auto-generated, validated, sent
[03] MYINVOIS_DOCS
4.2M+
Validated through LHDN endpoints
[04] PAYMENTS_CLEARED
RM 127M+
FPX, card, e-wallet — reconciled
[05] AIOT_DEVICES_ONLINE
14,000+
Cameras, readers, locks, lifts
[06] OPS_MONITORING
24/7
Best-effort availability, monitored continuously
// Source: xSERVA core telemetry · rolling 12 months · figures rounded.
[ DIFF // VS ALTERNATIVES ]

WHY xSERVA OVER THE ALTERNATIVES.

[ TLDR ] Spreadsheets break at scale, legacy ops software bolts MyInvois on as an afterthought, and home-grown PHP runs out of maintainers — AUTOSERVA replaces all three with one audited, multi-tenant platform.

Side-by-side capability check across the three options most operators evaluate: a unified platform like xSERVA, ad-hoc spreadsheets and manual processes, or a stack of single-purpose legacy tools.

CAPABILITY xSERVA SPREADSHEETS / MANUAL LEGACY / SINGLE-PURPOSE
MyInvois (LHDN) e-invoice compliance [ ✓ ] CERTIFIED, AUTOMATED [ ✗ ] MANUAL UPLOAD [ ~ ] BOLT-ON OR ABSENT
Auto-billing engine on cron [ ✓ ] MINUTE / 5-MIN JOBS [ ✗ ] HUMAN-RUN [ ~ ] LIMITED CADENCES
AIoT smart-access (RFID / face / plate) [ ✓ ] FIRST-PARTY [ ✗ ] N/A [ ~ ] SEPARATE VENDOR
Multi-property / multi-site [ ✓ ] MULTI-TENANT [ ~ ] PER-FILE SPRAWL [ ~ ] PER-LICENCE COST
Mobile app for residents / customers [ ✓ ] FOUR APPS [ ✗ ] NONE [ ~ ] WEB ONLY
Real-time operations dashboard [ ✓ ] CONSOLE VIEW [ ✗ ] STATIC [ ~ ] PARTIAL
Full audit trail of every change [ ✓ ] BUILT-IN [ ✗ ] NONE [ ~ ] CONFIGURABLE
Online payments (QR, card, Direct Debit) [ ✓ ] XENDIT MULTI-RAIL [ ✗ ] CASH / CHEQUE [ ~ ] SINGLE GATEWAY
Hardware + accounting integrations [ ✓ ] BRAND-AGNOSTIC [ ✗ ] NONE [ ~ ] LOCKED-IN
Public REST API (60+ endpoints) [ ✓ ] /api_doc.php [ ✗ ] NONE [ ~ ] LIMITED
24/7 direct support response [ ✓ ] DIRECT TO PATRICK [ ✗ ] NONE [ ~ ] BUSINESS-HOURS ONLY
// [ ✓ ] complete · [ ~ ] partial · [ ✗ ] absent
[ FEATURE_INDEX // 39 TOGGLES // property_ava() ]

EVERY FEATURE IN xSERVA.

[ TLDR ] The full tg_prop_ava[*] master switch list — 39 customer-facing toggles a property can enable. Each row is one feature flag in functions.php:property_ava().

Render-on-the-floor of every feature toggle the xSERVA core ships with. Not a marketing list — these are the literal flags operators flip on per project. AUTOSERVA exposes all 39, gated by RBAC privilege bitmap.

[ NN/39 ]
[ FEATURE_NAME ]
[ DESCRIPTION ]
[ 01/39 ]
INVOICING
Standard, consolidated, rental, fire and deposit invoices on one ledger.
[ 02/39 ]
UTILITY_BILLING
Water and electricity meter capture and auto-billing.
[ 03/39 ]
VISITORS
Guard-stand visitor records, types, doc and car-photo capture.
[ 04/39 ]
FACILITY_BOOKINGS
Court / function-room / common-area bookings with cut-off rules.
[ 05/39 ]
GOLF_BOOKINGS
Tee-time slots and member golf-day reservations.
[ 06/39 ]
PARTICIPANT_CHECK_INS
Class / event attendance and participant rosters.
[ 07/39 ]
ANNOUNCEMENTS
Tenant-wide bulletins delivered to PWA + email.
[ 08/39 ]
SUGGESTIONS
Resident-submitted ideas with approval lifecycle.
[ 09/39 ]
INTERNAL_MAILS
Operator-to-resident mailbox threads.
[ 10/39 ]
COMPLAINTS
Ticketed complaints with SLA queue and closure note.
[ 11/39 ]
INCIDENT_REPORTS
Security incidents with timestamp, photo and lifecycle.
[ 12/39 ]
DEFECT_REPORTS
Resident-reported defects routed to facilities team.
[ 13/39 ]
MANAGEMENT_ACCOUNTS
Cash book, GL, statements and financial reports.
[ 14/39 ]
MEETING_MINUTES
Committee minutes archive with attachments.
[ 15/39 ]
EMERGENCY_NUMBERS
Curated emergency-contact directory.
[ 16/39 ]
EMERGENCY_SOS_REQUESTS
One-tap SOS from PWA, broadcast to security console.
[ 17/39 ]
SUB_USERS
Sub-accounts under a primary customer (family / staff).
[ 18/39 ]
CARD_ACCESS
RFID smart-card access via MIFARE-compatible readers.
[ 19/39 ]
FACE_RECOGNITION_ACCESS
SmartFACE biometric access with PDPA-aware embeddings.
[ 20/39 ]
VEHICLE_PLATE_RECOGNITION_ACCESS
SmartVE LPR/ANPR for boom-gate auto-entry.
[ 21/39 ]
CONTRACTOR_SERVICE_PERMITS
Pre-approved contractor entry permits and audit log.
[ 22/39 ]
TICKETS
Generic ticketing module with custom ticket types.
[ 23/39 ]
POSERVA
Point-of-sale terminal, stocks, sales, receipts.
[ 24/39 ]
COMMUNITY_MARKETPLACE
Resident classifieds and merchant storefronts.
[ 25/39 ]
CONCIERGE_SERVICES
Bookable concierge tasks (laundry, errands, etc.).
[ 26/39 ]
TUKANGMAN
Handyman link-out service for residents.
[ 27/39 ]
SELF_SERVICE_LAUNDRY
QR-amenity laundry start/stop and credit billing.
[ 28/39 ]
MEMBERSHIPS
Paid member tiers, plans and renewals.
[ 29/39 ]
TENANCY_AGREEMENTS
Lease proposals, in-force and not-in-force agreements.
[ 30/39 ]
TENANT_ACCOUNTS
Per-tenant ledger separate from owner customer.
[ 31/39 ]
MANAGEMENT_COMMITTEE
Committee/Sub-MC roles, voting, document store.
[ 32/39 ]
DELIVERY_LOCKERS
QR locker grid — one-time tokens via DLCSP.
[ 33/39 ]
EV_CHARGING_PARKING_LOTS
EV bays with deposit + session API metering.
[ 34/39 ]
LOST_AND_FOUND
Found-item registry with claim workflow.
[ 35/39 ]
PROPERTY_QR_CODE
Per-property QR for fault-report and onboarding.
[ 36/39 ]
HELP_DESK
Front-of-house helpdesk queue with SLA timer.
[ 37/39 ]
INTEGRATED_SMART_ACCESS
SmartINTE intercom + access combined.
[ 38/39 ]
FILES
Tenant document store and download centre.
[ 39/39 ]
CLASSES
Yoga / fitness / coaching classes with passes and bookings.
// source: functions.php:property_ava() · per-project toggle: tg_prop_ava[N] · gated by $mypriv[N]
// 39/39 features ship in every AUTOSERVA tenant. Toggle on per project, no forks.
[ LIVE_OPS // SAMPLE_FRAME ]

CONTROL ROOM
VIEW.

[ TLDR ] A snapshot of the duty-officer terminal at 21:00 — counters update on cron, alerts surface in line, no hidden tabs.

A snapshot of what duty officers see at 21:00 on a Tuesday. Counters update on cron; alerts surface in line; nothing is hidden behind tabs.

SHIFT // 18:00 - 02:00
DUTY_OFFICER= ENC. RAZAK
SITE= TOWER_A
SHIFT_ID= S-2810-A
INCIDENTS= 00
ACCESS_GATES
312.swipes
RFID 184 · FACE 88 · PLATE 40
VISITORS_TODAY
56.qr
Pre-reg 41 · Walk-in 15 · Blacklist 0
BILLING_RUN
RM 18,420
Auto 312 · Pending 8 · Failed 0
CAMERAS
47/48
cam #14 carpark-B3 · offline 02:14
EVENT_LOG // tail -f
last 8
21:14:02 [OK] face-match RES_4012 lift_lobby_A
21:13:47 [OK] plate WXR-7712 entered carpark-A
21:11:18 [OK] visitor QR scan gate-2 host #1408
21:09:30 [OK] auto-billing batch #228 (312 invoices)
21:07:22 [OK] e-invoice posted to MyInvois (12)
21:04:11 [WARN] camera #14 heartbeat lost
21:01:05 [OK] helpdesk ticket #2310 closed
20:58:49 [OK] lift access RES_2207 floor 14
// illustrative frame · real tenants see real telemetry · figures non-binding
[ INTEGRATIONS // WORKS_WITH ]

CONNECTED HARDWARE & SERVICES.

[ TLDR ] Brand-agnostic generic IP cameras (HTTP snapshot/event ingest), MIFARE-compatible RFID readers, ANPR/face devices, payment gateways and accounting systems — pair what you already own.

AUTOSERVA ships with first-party connectors. Plug into existing readers, cameras, gates and gateways — no rip-and-replace.

[ID] NAME TYPE STATUS
[01] MyInvois (LHDN) UBL 2.1 · MSIC · walk-in TIN ● CERTIFIED
[02] Xendit QR / card / Direct Debit / FPX ● LIVE
[03] Xendit e-wallets TNG · Boost · GrabPay · ShopeePay · DuitNow ● LIVE
[04] Razer Gateway Sandbox endpoint ● PAIRED
[05] AutoCount Connector Hosted middleware (Bearer) ● SYNC
[06] Public REST API 60+ endpoints · /api_doc.php ● LIVE
[07] Email / PHPMailer Invoice + notification delivery ● LIVE
[08] IP cameras HTTP snapshot & event ingest ● PAIRED
[09] RFID readers MIFARE-compatible ● PAIRED
[10] Face-recognition cameras SmartFACE ● PAIRED
[11] License-plate cameras SmartVE ● PAIRED
[12] Smart intercoms SmartINTE / Integrated Smart Access ● PAIRED
[13] Lift access controllers Floor restriction ● PAIRED
[14] Parking-lock controllers DLCSP / wheel-clamp ● PAIRED
[15] Smart lighting / power IoT control ● PAIRED
[16] Smart mirrors Access request via micode ● PAIRED
[17] Delivery lockers QR locker grid + DLCSP ● PAIRED
[18] SM4 cipher Device-protocol encryption ● LIVE
[ INTEGRATIONS // DEEP_DIVE ]

HOW EACH INTEGRATION ACTUALLY WORKS.

[ TLDR ] One paragraph per integration: what flows in, what flows out, and how the protocol layer keeps your existing hardware and accounting in the loop.

Below the connector list: what each integration does end-to-end, the protocols, and what that means for ops and finance.

verified [01] MyInvois (LHDN)
● PAIRED

Malaysian e-invoice compliance for B2B/B2C invoices. AUTOSERVA generates a UBL 2.1 JSON payload, signs with the tenant's digital cert, submits to the MyInvois API and stores the returned UUID and sharing URL against each invoice. Walk-in buyer fallback uses TIN EI00000000010; the bundled MSIC code list classifies every line. Sandbox and production environments are switchable per tenant. Credit notes, refunds and consolidated invoices are first-class document types with the same audit trail.

payments [02] Xendit
● PAIRED

Multi-method payment gateway with three confirmed methods in code: QR pay, credit/debit card, and Direct Debit. AUTOSERVA reconciles every webhook event back to the invoice line in seconds, surfaces refund events to finance, and drops settlement reports straight into the GL.

sync_alt [03] AutoCount Connector
● PAIRED

For tenants that prefer to keep AutoCount as the system of record, AUTOSERVA pushes invoice / payment / cancel / undo flows through a hosted middleware at safetech.org.my/VYROX-AutoCount-Connector/xSERVA with Bearer-token auth. A read-side API (autocount_api.php) pulls authoritative data back. Mappings are configured per chart-of-accounts; conflicts are queued for manual resolution rather than silently overwritten.

mail [04] Email · PHPMailer
● PAIRED

Outbound invoice delivery, OTPs, payment reminders, visitor QR codes, complaint status updates and notifications all flow through PHPMailer. WhatsApp is the way to reach Patrick (a sales / support channel), not a system feature.

code [05] Public REST API (60+ endpoints)
● PAIRED

A documented REST API at /api_doc.php exposes 60+ endpoints — visitor, EV charging deposit + session, sub-account, announcements, deposits, invoices, payments and more. Bearer-token auth and webhooks for payment events. Mobile API namespace covers PWA login, project-scope and member detail flows.

videocam [06] IP cameras + RFID + face + LPR + intercom
● PAIRED

Generic IP cameras stream snapshots and events to the AUTOSERVA broker over HTTP (cgi-bin style). MIFARE-compatible RFID readers feed swipes via TCP. Brand-agnostic face-recognition cameras (SmartFACE) and LPR/ANPR cameras (SmartVE) stream events on the same broker. Smart intercoms (SmartINTE / Integrated Smart Access) route calls to the resident app or duty officer based on time-of-day rules.

memory [07] Lifts, parking-lock, lighting, mirrors, lockers · DLCSP · SM4
● PAIRED

Relay-based and IP-controlled hardware paths. Lift controllers enforce floor-level access tied to RFID/face credentials. Parking-lock controllers cycle on plate match; the wheel-clamp module handles enforcement escalation. Smart lighting/power circuits report kWh and accept on/off commands. Smart mirrors raise access requests via micode. Delivery lockers and door locks use the proprietary DLCSP (Door-Lock Control Service Protocol). All device-protocol traffic is encrypted with the SM4 32-round cipher.

[ ROLLOUT // 4 PHASES ]

FROM KICKOFF TO CUTOVER IN 4 WEEKS.

[ TLDR ] Discovery week 1, configure week 2, pair AIoT + soft-launch weeks 3-4, full cutover week 5 — Patrick personally runs each phase with go/no-go gates.

A predictable rollout cadence — Patrick runs each phase personally. Phases overlap when teams are ready; nothing is rushed past go/no-go gates.

[WEEK 01]
dns PHASE 01/04

DISCOVERY & DATA IMPORT

Patrick on-site or by video. Map your operations to xSERVA modules. Bulk-import customers, units, contracts, opening balances and meter readings via CSV/Excel templates. Confirm chart-of-accounts and rate cards.

[WEEK 02]
tune PHASE 02/04

CONFIGURATION & TRAINING

Configure rates, fees, MyInvois TIN, payment gateway, branding and role-based user accounts. 2-3 hands-on training sessions for finance, ops and security teams. Sign-off on templates and SLAs.

[WEEK 03-04]
cable PHASE 03/04

AIoT PAIRING & SOFT LAUNCH

Pair access devices, IP cameras, lifts, parking locks. Roll out resident/customer PWA mobile apps via email + property QR codes. Run AUTOSERVA in parallel with the old system; reconcile both for one billing cycle.

[WEEK 05+]
rocket_launch PHASE 04/04

FULL CUTOVER & CONTINUOUS IMPROVEMENT

Old system retired. AUTOSERVA is the source of truth. Quarterly reviews to surface new module adoption opportunities. Patrick stays accessible for ops escalations.

[ ROI_TERMINAL // ESTIMATE_ENGINE ]

RUN THE NUMBERS.

[ TLDR ] Type your unit count, billing hours, monthly invoices and admin hourly rate — the terminal prints an estimated MYR/month saving live.

Plug your numbers in. The output is a planning estimate, not a quote — Patrick will verify against your operation before anything is signed.

 [ CONFIG // SAVINGS_MODEL.cfg ] EDITABLE
[ HOW_WE_ESTIMATE ] ▸
# time saved on manual billing
time_saving = hours_per_week × 4.33 × rate × 0.7
# invoice processing efficiency
processing_saving = invoices × 0.5
# improved collection rate
collection_saving = units × 1.2
# total monthly saving
MONTHLY_SAVING_MYR = time_saving + processing_saving + collection_saving
# stdout
MONTHLY_SAVING_MYR =
RM {{ formatted }}
// annualised ≈ RM {{ annualFormatted }} / yr
# breakdown
time_savingRM {{ fmt(timeSaving) }}
processing_savingRM {{ fmt(processingSaving) }}
collection_savingRM {{ fmt(collectionSaving) }}
// Estimate only — Patrick will confirm for your specific operation.
phone_in_talk VERIFY_WITH_PATRICK
MODEL: v3 | SOURCE: xSERVA telemetry + customer interviews | CURRENCY: MYR
[ CLIENTS // ANONYMISED_REGISTRY ]

OPERATORS WE SERVE.

[ TLDR ] Twelve real customers across SEA — names anonymised, briefs concrete — happy to introduce on request once you scope.

Operators we serve, anonymised. Real properties, real footprints, happy to do a 1-on-1 reference call once you scope a deal.

[ ID ]
// LOCATION
// INDUSTRY · BRIEF
CLIENT_01
// MONT KIARA
480-unit condominium // Auto-billing + face access for residents.
CLIENT_02
// PENANG
12-court badminton centre // Online booking + dynamic pricing.
CLIENT_03
// PETALING JAYA
Mixed-use clubhouse // POS + amenities + visitor management.
CLIENT_04
// JOHOR BAHRU
6-lift residential block // Lift access + smart parking.
CLIENT_05
// JAKARTA
Futsal arena // Recurring class bookings + Xendit payments.
CLIENT_06
// SUBANG
Retirement village // Concierge services + helpdesk.
CLIENT_07
// KUALA LUMPUR
EV-charging carpark // LPR entry + paid parking.
CLIENT_08
// CYBERJAYA
Residential strata // JMB billing + sinking fund auto-generation.
CLIENT_09
// IPOH
Swimming complex // Class passes + coach scheduling.
CLIENT_10
// BANGKOK
Serviced apartment block // Sub-account billing + statements.
CLIENT_11
// KUCHING
Bowling alley // POS + membership plans + leaderboards.
CLIENT_12
// HO CHI MINH
Community sports centre // Multi-facility bookings + auto-reminders.
// Logos withheld pending consent. References available on request.
[ MIGRATION // CUTOVER_PATHWAYS ]

MOVING FROM SPREADSHEETS, PAPER, OR LEGACY SOFTWARE.

[ TLDR ] Four parallel cutover lanes — spreadsheets, paper/manual, single-purpose legacy software, and home-grown in-house systems — each with its own importer and parallel-run window.

No site arrives clean. We meet your data wherever it lives — spreadsheets, paper ledgers, legacy software, or a custom-built in-house system — and bring it across without losing a customer or a receipt.

[ LANE_01 ] EXCEL_CSV_GSHEETS FROM SPREADSHEETS //

We read your existing books — customer ledgers, unit registers, contracts, opening balances, recurring fee schedules — directly from XLSX or CSV. Patrick walks the import live with your team in week 1. Common pain points we resolve: duplicate customers, inconsistent unit numbering, orphan payments and fees that drift across months. After import, every cell can be traced back to a source row in the audit trail.

[ LANE_02 ] PHYSICAL_FORMS_LEDGERS FROM PAPER //

Paper-only sites get a digital onboarding workflow: residents/customers self-enrol via property QR codes and the public captive portals (capt.php, mer_capt.php, merchant_login.php), ID and consent captured in the PWA, signatures collected on a tablet. Bulk owner CSV import (import_owners.php) handles legacy lists in one pass. Past records can be OCR-scanned and indexed against the new customer file. We keep paper running in parallel for the first month so you never lose a receipt during cutover.

[ LANE_03 ] AUTOCOUNT_SQL_SAGE_OTHERS FROM LEGACY SOFTWARE //

Single-purpose legacy systems get a parallel-run bridge — invoices, payments and GL entries flow both ways via API or scheduled file drops while you decide on the cutover date. We sync customers and chart-of-accounts upfront, then add transactional sync. After 30-60 days of clean reconciliation, the legacy system becomes read-only archive.

[ LANE_04 ] CUSTOM_PHP_DOTNET_PYTHON FROM IN-HOUSE BUILDS //

Home-grown systems usually have the cleanest data and the messiest schema. We map your tables to xSERVA modules, normalise into the canonical model, and bulk-import via API. Original IDs are preserved as external references so historic links keep resolving. The old system can be decommissioned or kept as a cold archive at your discretion.

# typical-cutover-checklist
$ autoserva import --source old-system --dry-run
[OK] 480 customers · 11,200 historical invoices · 0 duplicates
$ autoserva parallel-run --duration 30d
[OK] reconciliation drift < 0.05%
$ autoserva cutover --confirm
[OK] AUTOSERVA is the system of record. Old system → archive (read-only).
[ DATA // SECURITY // COMPLIANCE ]

BUILT FOR AUDIT WEEK.

[ TLDR ] Malaysian-hosted, TLS in transit, RBAC + audit trail on every change, daily off-site backups, PDPA-aligned biometric handling.

Encryption, access control, audit trail, backups and PDPA-aligned biometric handling — without any of it being an add-on you have to remember to configure.

cloud_done
MALAYSIA-HOSTED

Customer data resides in regulated Malaysian cloud regions. Cross-border transfers are documented and consented to where they occur.

lock
TLS IN TRANSIT

Data is protected with TLS while flowing between clients, servers and devices.

admin_panel_settings
RBAC + AUDIT TRAIL

Role-based access control across every module. Every create / update / delete is logged via in_syslog() / debugv_access with user, timestamp and context.

backup
DAILY OFF-SITE BACKUPS

Off-site backups daily; point-in-time restore for the last 30 days.

verified
MyInvois READY

LHDN MyInvois UBL 2.1 data flow. Sandbox and production environments switchable per tenant.

privacy_tip
PDPA-ALIGNED BIOMETRICS

Face embeddings, ANPR plates and visitor data have purpose-limited retention windows and consent capture per resident.

[ SUPPORT // SLA ]

DIRECT LINE TO PATRICK.

[ TLDR ] P1 under 1h, P2 under 4h, SLA tracked publicly — WhatsApp goes straight to Patrick, engineering escalates inside the same thread.

No tier-1 phone tree. WhatsApp goes straight to Patrick; engineering escalation happens in the same thread when needed.

[ RESPONSE_SLAs ]
[P1]Critical — system down / billing blocked< 1h
[P2]High — module degraded / hardware offline< 4h
[P3]Standard — questions / configurationNEXT BIZ DAY
[P4]Low — feature requests / enhancementsQUARTERLY REVIEW
[ INCLUDED_IN_EVERY_PLAN ]
[+]24/7 WhatsApp support directly to Patrick (+60 19-688 3338)
[+]Onboarding training (2-3 sessions)
[+]Monthly platform updates with release notes
[+]Quarterly review of module adoption + feature requests
[+]Best-effort availability monitored 24/7 — incident updates via WhatsApp
[+]Hardware-pairing assistance during rollout
[ PRICING // TRANSPARENT BANDS ]

PAY FOR WHAT YOU OPERATE.

[ TLDR ] Three sample bands by scale — Small under 100 units, Mid 100-1,000 units, Large 1,000+ / multi-site — pricing per scope not per seat, no setup fee on standard SKU.

Pricing is custom — quoted per scope, not per seat. Free demo and trial period; no setup fee on the standard SKU. Sample bands below to anchor expectations.

[ TIER_01 ] SMALL
SCALE
< 100 UNITS / CUSTOMERS

Single property or a small club. Standard module set. No setup fee. Pay-monthly per property.

  • >>Core 12 modules
  • >>Up to 100 units / customers
  • >>Standard support SLAs
  • >>MyInvois (LHDN) included
TALK_TO_PATRICK
[ TIER_02 ] MID
SCALE
100 - 1,000 UNITS

Multi-block estates and clubs. Full feature set with AIoT bundle option. Predictable monthly subscription.

  • >>All 12 modules
  • >>Up to 1,000 units / customers
  • >>AIoT hardware bundle (optional)
  • >>Custom invoice templates
TALK_TO_PATRICK
[ TIER_03 ] LARGE
SCALE
1,000+ UNITS / MULTI-SITE

Multi-property portfolios and enterprise tenants. Dedicated support, custom integrations, volume tiers.

  • >>Unlimited units / customers
  • >>Multi-site multi-tenant
  • >>Custom integrations + dedicated CSM
  • >>Priority support
TALK_TO_PATRICK
[ ADD_ONS ]
  • >>AIoT hardware bundle
  • >>E-invoice volume tier
  • >>Custom integrations
  • >>Dedicated CSM
  • >>Priority support
  • >>Custom branding on resident app
[ GLOSSARY // man -k xserva ]

PLAIN-ENGLISH GLOSSARY.

[ TLDR ] 25 industry terms — MyInvois, AIoT, RFID, RBAC, JMB, MC, FPX, ANPR, sinking fund and more — explained the way you would over coffee.

Terms that show up in property, fintech and AIoT contexts — explained the way you would explain them to a colleague at lunch.

[01]
AIoT
Artificial Intelligence + Internet of Things — connected devices (cameras, readers, sensors) that don't just stream data but make local decisions (e.g. face match, plate match).
[02]
ANPR / LPR
Automatic Number-Plate Recognition / License-Plate Recognition. A camera reads a vehicle plate and emits a text event the access system acts on.
[03]
Audit trail
A log of every meaningful change in the system — who did what, when, captured via in_syslog() / debugv_access.
[04]
Bin (PDPA term)
In Malaysian PDPA, a "data subject" or "data subject reference". AUTOSERVA stores the minimum needed and tracks consent against it.
[05]
Cron
A scheduler that runs jobs on a fixed cadence (every minute, every 5 minutes, daily). AUTOSERVA uses cron for billing runs, reminders and reporting.
[06]
e-Invoice / MyInvois / LHDN
LHDN (Lembaga Hasil Dalam Negeri) is the Malaysian Inland Revenue Board. MyInvois is its e-invoice system; an "e-invoice" is a tax-compliant invoice validated and issued through it.
[07]
FPX
Financial Process Exchange — Malaysia's online banking payment rail. Residents pay direct from their bank account.
[08]
GL
General Ledger — the master accounting record. Every transaction posts to one or more GL accounts.
[09]
JMB / MC
Joint Management Body / Management Corporation — the legal entities that run a Malaysian strata property.
[10]
Multi-tenant SaaS
One software instance that serves many customer tenants, each with isolated data and configuration.
[11]
DLCSP
Door-Lock Control Service Protocol — proprietary door/locker protocol used by AUTOSERVA for delivery lockers and door locks.
[12]
SM4
Chinese 32-round block cipher used by AUTOSERVA for device-protocol encryption.
[13]
PDPA
Personal Data Protection Act 2010 (Malaysia) — governs how personal data must be handled, stored and consented to.
[14]
POS
Point of Sale — the till at an F&B outlet, pro-shop or kiosk.
[15]
QR
Quick-Response code. A 2D barcode used for invoices, visitor passes, locker pickups, amenity check-ins and access keys.
[16]
RBAC
Role-Based Access Control — users get permissions through the roles they hold, not one-by-one.
[17]
RFID
Radio-Frequency Identification — the smart-card / fob technology behind most building access systems.
[18]
SLA
Service-Level Agreement — the response or uptime targets we commit to.
[19]
SmartFACE / SmartVE / SmartINTE
xSERVA modules for face recognition (FACE), license-plate / vehicle entry (VE) and smart intercom (INTE).
[20]
Sinking fund
A reserve fund built up by a strata property to cover major future repairs.
[21]
Sub-account
A child account under a master customer — e.g. a tenant under a landlord, or a family member under a primary member.
[22]
TLS
Transport Layer Security — the encryption that protects data while it's flowing over the network.
[23]
Webhook
A real-time HTTP callback. When something happens in AUTOSERVA, it can ping your system; when something happens in a payment gateway, it pings AUTOSERVA.
[24]
MIFARE
A widely-used contactless smart-card standard for RFID access. AUTOSERVA supports MIFARE-compatible readers.
[ DEPLOY_PIPELINE // 4 STAGES ]

FROM ZERO TO LIVE IN DAYS.

[ TLDR ] Four-stage deploy pipeline: onboard → configure → pair AIoT → go-live, with parallel-run for the first billing cycle.
[01/04] dns
ONBOARD

Onboard your property or business — units, blocks, customers, agreements imported.

[02/04] tune
CONFIGURE

Configure modules — invoicing, billing rules, booking calendars, helpdesk SLAs.

[03/04] cable
CONNECT_AIoT

Pair RFID readers, face / plate cameras, intercoms, lift and lock controllers.

[04/04] rocket_launch
GO_LIVE

Cut over. Cron jobs run. Dashboards populate. Ops takes the wheel.

[ USE_CASES // TARGETS ]

DEPLOYED ACROSS.

[ TLDR ] Same platform, eight operating contexts — condos, mixed-use, sports clubs, gyms, EV parking, residential communities, retail/F&B and clubhouses.

One platform; eight operating contexts. Each industry below has its own pain map — these are the modules they lean on most and the outcomes operators report after cutover.

● CONDOS & STRATA ● MIXED-USE BUILDINGS ● SPORTS CLUBS ● GYMS ● SMART PARKING & EV ● RESIDENTIAL COMMUNITIES ● RETAIL / F&B ● CLUBHOUSES
## 01 // CONDOS & STRATA
CASE_01

JMBs and management corporations of high-rise condominiums managing 100-1500 units. Top operational pain: collecting maintenance fees on time, keeping the access system honest, and surviving the annual audit.

[ MODULES_USED ]
  • >>Accounting & MyInvois e-invoice
  • >>Auto-billing & online payments
  • >>Smart access (RFID + face + plate)
[ OUTCOME ]

A 480-unit condo cut DSO from 38 to 11 days and reduced finance staffing needs by 0.5 FTE in the first quarter post-cutover.

## 02 // MIXED-USE BUILDINGS
CASE_02

Mixed-use towers with retail podium, office floors and residential — three audiences in one building. Pain: separate billing rules per tenant class, separate access policies, and reconciling F&B POS with building rent.

[ MODULES_USED ]
  • >>Property & facility setup with multi-class rates
  • >>Visitor management with merchant carve-outs
  • >>POS + marketplace integrated to GL
[ OUTCOME ]

A 6-tower mixed development unified billing across residential, commercial and retail tenants; reconciliation time fell from 4 days to under half a day per cycle.

## 03 // SPORTS CLUBS
CASE_03

Member-driven clubs running courts, coaches, classes and F&B with seasonal membership cycles. Pain: court double-booking, member-charge reconciliation, no-shows.

[ MODULES_USED ]
  • >>Bookings & reservations engine
  • >>Membership & customer master
  • >>POSERVA member-charge
[ OUTCOME ]

A racquet club with 12 courts grew booked-court utilisation by 38% while reducing front-desk booking workload by ~70%.

## 04 // GYMS
CASE_04

Fitness operators with class passes, personal-trainer schedules and access turnstiles. Pain: enforcing membership at the door, class capacity and trainer payouts.

[ MODULES_USED ]
  • >>Class & coach booking with pass enforcement
  • >>RFID / face access at turnstile
  • >>Auto-billing for recurring memberships
[ OUTCOME ]

A 3-branch gym chain eliminated tail-gating losses worth ~RM8,500/month after enforcing face + pass at the turnstile.

## 05 // SMART PARKING & EV
CASE_05

Operators of paid parking, EV charging bays and visitor parking inside or alongside buildings. Pain: revenue leakage at the boom gate, EV bay occupancy without billing, manual ticket validation.

[ MODULES_USED ]
  • >>License-plate recognition + parking-lock control
  • >>EV bay metering tied to invoicing
  • >>Visitor parking pass with QR
[ OUTCOME ]

A mixed-use development monetised 18 EV bays from "estimated" to metered + billed within a week; recovered ~RM2,000/month previously written off as house electricity.

## 06 // RESIDENTIAL COMMUNITIES
CASE_06

Gated landed-house communities with security guards, perimeter cameras and resident committees. Pain: visitor management at peak hours, complaint backlog, perimeter awareness.

[ MODULES_USED ]
  • >>Visitor pre-registration with QR
  • >>Security operations console
  • >>Complaints & helpdesk lifecycle
[ OUTCOME ]

A community gate processing 200+ visitors/day cut average visitor approval from ~4 minutes to under 90 seconds — a 60% improvement.

## 07 // RETAIL / F&B
CASE_07

Retail outlets, F&B kiosks and pro-shops located inside a property — often with member-charge or wallet integration. Pain: separate POS silos, no unified report, manual settlement.

[ MODULES_USED ]
  • >>POSERVA point-of-sale
  • >>Merchant onboarding & marketplace
  • >>Membership-tier promotions
[ OUTCOME ]

A clubhouse F&B outlet saw member-charge volume rise 28% after migrating to POSERVA; settlement runs once a day instead of twice a week.

## 08 // CLUBHOUSES
CASE_08

Private clubhouses and recreation hubs with mixed amenities (pools, function rooms, gyms, BBQ pits) and a member roster. Pain: amenity scheduling, member self-service, event coordination.

[ MODULES_USED ]
  • >>Bookings & reservations
  • >>Membership management
  • >>Concierge & helpdesk
[ OUTCOME ]

A clubhouse handling ~80 bookings/day moved members to QR-based self-service; front-desk booking workload dropped ~70% with zero member complaints.

[ FIELD_REPORTS // OPS_VOICES ]

FROM THE CONTROL ROOM.

[ TLDR ] Six site operators report what changed at handover, billing close and the boom gate after AUTOSERVA replaced their patchwork.

Six operators on what changed when their site moved onto AUTOSERVA.

REPORT_01 // VERIFIED
RATING 5.0
"Before AUTOSERVA, our shift handover was a WhatsApp scroll and a clipboard. Now the next officer opens one screen — open tickets, offline cameras, pending visitor approvals — all there. Handover dropped from 22 minutes to under 5."
>> Encik Ahmad — Ops Director, Klang
REPORT_02 // VERIFIED
RATING 5.0
"I run six mixed-use towers. The cron-driven billing run replaced two full-time clerks. MyInvois submission is hands-off — finance checks the log in the morning and signs off coffee in hand."
>> Mr. Lim — Sysops Manager, Petaling Jaya
REPORT_03 // VERIFIED
RATING 5.0
"Plate-recognition + parking-lock integration is the part residents notice. No more boom-gate queue at 8am. From an engineering point of view, the device-health dashboard is what I love — I see the camera die before residents do."
>> Ir. Vincent — Facility Engineer, Cyberjaya
REPORT_04 // VERIFIED
RATING 5.0
"We moved 1,200 leases off spreadsheets onto the customer master. Sub-accounts, photos, document upload — every lease has a clean folder. Audit week last month was the easiest in eleven years."
>> Puan Siti — Property Operations, Johor Bahru
REPORT_05 // VERIFIED
RATING 5.0
"The helpdesk routing alone justified the move. Tickets land in the right queue, escalate on SLA, and the meeting-minutes module means follow-ups do not vanish into anyone's inbox."
>> Mr. Daniel — Helpdesk Lead, Subang
REPORT_06 // VERIFIED
RATING 5.0
"Twelve modules, one platform, one login for staff, one app for residents. As an ops guy I value boring more than I value clever. AUTOSERVA is satisfyingly boring — it just runs."
>> Encik Hafiz — Operations Manager, Shah Alam
[ HANDSHAKE // OPEN_CHANNEL ]

TALK TO PATRICK.

[ TLDR ] Direct WhatsApp / phone / email — Patrick scopes, quotes and personally onboards every new site.

Tell us how many sites, which hardware vendors and what your current pain is. We'll quote, scope and onboard. English / Bahasa / Mandarin.

CONTACT
Patrick
+60 19-688 3338
EMAIL
VYROX HQ
enquiry@vyrox.com
// QUICK_ACTIONS
chat WHATSAPP_PATRICK call CALL_DIRECT mail EMAIL_HQ
[ FAQ // 25 ENTRIES ]

FREQUENTLY ASKED.

[ TLDR ] Long-form answers covering MyInvois, hardware compatibility, mobile apps, hosting, audit log, login security, NOT-included, and data export.

Long-form answers to what operators actually ask before they sign — pricing, MyInvois, hardware, mobile apps, hosting, multi-country deployment.

[01] What is xSERVA?
▸

xSERVA is the underlying operations platform built by VYROX INTERNATIONAL SDN BHD. It powers five sister brands — smartserva, propserva, autoserva, homeserva and sportserva — so customers can pick whichever URL fits their business.

[02] Why does the same platform run on five domains?
▸

Different industries prefer different brand cues. The codebase, modules and database are identical; only the front-door changes. AUTOSERVA is the industrial-operations face for ops teams that want a control-room feel.

[03] How does AUTOSERVA handle MyInvois (LHDN) e-invoice submission?
▸

AUTOSERVA generates a UBL 2.1 JSON payload, signs it, submits to the LHDN MyInvois sandbox or production endpoints, stores the returned UUID and sharing URL, and walks in a fallback buyer TIN (EI00000000010) for over-the-counter customers. The MSIC code list is bundled. Invoices, consolidated invoices, credit notes and refunds all flow through the same audit trail; failed validations surface in a queue for one-click retry.

[04] Can I import data from my existing spreadsheets or legacy system?
▸

Yes. We provide CSV and Excel templates for customers, units, contracts, opening balances and meter readings. Patrick walks your team through a sample import in week 1 and we run a parallel period before cutover.

[05] Is there a mobile app for residents, customers and staff?
▸

Yes — four apps: customer/resident, security, staff and delivery courier. They share the same backend; access is role-controlled and changes appear live across web and mobile.

[06] How does face recognition work with privacy and PDPA?
▸

SmartFACE captures only the embedding (a vector), not raw photo storage by default; consent is captured per resident, retention windows are configurable, and admin actions on biometric data are logged. Visitors can be processed via QR pre-registration without enrolling biometrics at all.

[07] Can AUTOSERVA replace AutoCount or work alongside it?
▸

Both. AUTOSERVA has a full GL, cashbook and reconciliation; for sites that prefer to keep AutoCount, the AutoCount Connector — a hosted middleware at safetech.org.my/VYROX-AutoCount-Connector/xSERVA with Bearer-token auth — supports invoice / payment / cancel / undo flows bidirectionally.

[08] How long does onboarding take?
▸

Typical sites go live in 4-5 weeks: week 1 discovery + import, week 2 configuration + training, weeks 3-4 AIoT pairing and soft-launch, week 5 cutover. Smaller sites finish faster.

[09] What hardware brands and models are supported?
▸

Brand-agnostic. Generic IP cameras (HTTP snapshot & event ingest), MIFARE-compatible RFID smart-card readers, face-recognition cameras (SmartFACE), ANPR/LPR cameras (SmartVE), smart intercoms (SmartINTE), lift access controllers, parking-lock controllers (DLCSP), delivery lockers and smart mirrors. Device-protocol traffic is encrypted with the SM4 cipher.

[10] What is the difference between the 5 *serva.com domains?
▸

Same platform, different brand. SMARTSERVA targets smart buildings, PROPSERVA targets property managers, AUTOSERVA targets industrial ops, HOMESERVA targets residential communities, SPORTSERVA targets clubs and gyms. You can switch later without re-implementation.

[11] Does it work for small properties or only big ones?
▸

Both. Small (< 100 units) tenants run on a slim configuration; large tenants (1,000+ units) run multi-site with sub-accounts. Pricing scales with size.

[12] Can residents pay online?
▸

Yes. Xendit is integrated with three confirmed payment methods: QR pay, credit/debit card, and Direct Debit. Webhook reconciliation, refund and failure handling are built-in.

[13] What happens if MyInvois validation fails?
▸

The document drops into a "rejected" queue with the LHDN error code and explanation. Finance can fix the data and resubmit in one click; the original draft remains for audit.

[14] Can I customise invoice templates and reports?
▸

Yes. Logo, footer, payment instructions, multi-language remarks and per-customer remarks are configurable. Reports can be exported as PDF, Excel or CSV.

[15] How does visitor pre-registration work?
▸

Residents/staff pre-register a visitor in the app; the visitor receives a QR code via email; security scans the QR at the gate; entry is logged with photo, plate and host reference.

[16] Is there an API for our own integrations?
▸

Yes — a public REST API with 60+ documented endpoints (visitor, EV charging, sub-account, announcements, deposits, sessions, etc.), reachable at /api_doc.php. Bearer-token auth and webhooks for payment events. Sandbox available.

[17] Where is the data hosted and how is it backed up?
▸

Data is hosted in Malaysian cloud regions with TLS in transit. Daily off-site backups with point-in-time restore for the last 30 days.

[18] Is the system available outside Malaysia?
▸

Yes — deployed across Malaysia, Singapore, Indonesia, Thailand, Vietnam and the Philippines. Tax flows are configurable per country; MyInvois is the Malaysia-specific module.

[19] How is downtime and maintenance handled?
▸

Best-effort availability monitored 24/7. Maintenance windows are scheduled out of business hours and announced via email (PHPMailer) to all tenant administrators.

[20] How do I train my team and roll it out to residents?
▸

Onboarding includes 2-3 live training sessions for staff plus printed quick-start guides. Resident rollout uses an email + QR-code campaign with download links to the PWA mobile apps; we monitor adoption with you for the first month.

[21] Can I import data from a competitor product?
▸

Yes. We have prebuilt importers for the common Malaysian and SEA property/club platforms — customers, units, contracts, opening balances, member tiers and access cards. Where a vendor blocks export, we work with you to extract via reports or screen-scrape, then re-import. Most migrations finish inside week 1, with a parallel-run period to confirm reconciliations match the old system before cutover.

[22] How is the audit log captured?
▸

Audit log is captured via in_syslog() / debugv_access — every meaningful change is recorded with user, timestamp and context for review.

[23] What login security controls are in place?
▸

Configurable password policy and login rate-limiting at the application level.

[24] What is NOT included in the standard subscription?
▸

Hardware (cameras, readers, locks), site cabling, payment-gateway processing fees, and bespoke development of features that don't exist in the platform. Everything else — modules, PWA mobile apps, MyInvois, email delivery via PHPMailer, support — is included.

[25] How do I export my data if I ever leave?
▸

You own your data. Full data export to CSV/JSON on request. There is no exit fee.

[ DIRECT_CHANNEL // NO_FUNNEL ]

TALK TO PATRICK NOW.

No slides, no funnel. Just a direct conversation about whether AUTOSERVA fits your operation. Bring your unit count, hardware list and current pain — leave with a scope.

chat WHATSAPP_PATRICK mail EMAIL_HQ
phone_in_talk WHATSAPP mail EMAIL