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.
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.
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.
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.
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.
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.
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.
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%.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Every screen below is rendered as inline SVG and HTML — what you see is the actual visual vocabulary of the product, not marketing collateral.
| DESC | QTY | RATE | AMT |
|---|---|---|---|
| Service charge — Apr 2026 | 1 | 340.00 | 340.00 |
| Sinking fund levy | 1 | 68.00 | 68.00 |
| Carpark — bay #B-082 | 1 | 85.00 | 85.00 |
| SST 6% | — | — | 29.58 |
| WHO | GATE | METHOD | TIME | STATE |
|---|---|---|---|---|
| ATAndrew T. | GATE_01 | FACE | 09:14:22 | GRANTED |
| SKSiti K. | LIFT_03 | RFID | 09:14:08 | GRANTED |
| VRVendor R. | GATE_02 | QR | 09:13:51 | GRANTED |
| UNUnknown | GATE_01 | FACE | 09:13:30 | DENIED |
| JLJ. Lim | LIFT_05 | RFID | 09:13:11 | GRANTED |
| HMHafiz M. | GATE_03 | PLATE | 09:12:48 | GRANTED |
| NKN. Kaur | LIFT_02 | RFID | 09:12:19 | GRANTED |
| DVDelivery | GATE_02 | QR | 09:11:55 | GRANTED |
Across the xSERVA platform — the core that powers AUTOSERVA, SMARTSERVA, PROPSERVA, HOMESERVA and SPORTSERVA. Treat as illustrative aggregate, not per-tenant guarantees.
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.
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.
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.
AUTOSERVA ships with first-party connectors. Plug into existing readers, cameras, gates and gateways — no rip-and-replace.
Below the connector list: what each integration does end-to-end, the protocols, and what that means for ops and finance.
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.
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.
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.
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.
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.
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.
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.
A predictable rollout cadence — Patrick runs each phase personally. Phases overlap when teams are ready; nothing is rushed past go/no-go gates.
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.
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.
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.
Old system retired. AUTOSERVA is the source of truth. Quarterly reviews to surface new module adoption opportunities. Patrick stays accessible for ops escalations.
Plug your numbers in. The output is a planning estimate, not a quote — Patrick will verify against your operation before anything is signed.
Operators we serve, anonymised. Real properties, real footprints, happy to do a 1-on-1 reference call once you scope a deal.
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.
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.
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.
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.
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.
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.
Customer data resides in regulated Malaysian cloud regions. Cross-border transfers are documented and consented to where they occur.
Encryption at rest with AES-256. Encryption in transit with TLS 1.3. Per-tenant encryption keys; rotated on schedule.
Role-based access control across every module. Every create / update / delete is logged with user, timestamp and before/after diff.
Encrypted off-site backups daily; point-in-time restore for the last 30 days. Quarterly restore drills.
LHDN-certified data flow. Sandbox and production environments switchable per tenant.
Face embeddings, ANPR plates and visitor data have purpose-limited retention windows and consent capture per resident.
SAML and OIDC supported on enterprise plans. Map your IdP groups to AUTOSERVA roles.
Independent penetration test yearly. Findings remediated within agreed SLAs; report available on request under NDA.
No tier-1 phone tree. WhatsApp goes straight to Patrick; engineering escalation happens in the same thread when needed.
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.
Single property or a small club. Standard module set. No setup fee. Pay-monthly per property.
Multi-block estates and clubs. Full feature set with AIoT bundle option. Predictable monthly subscription.
Multi-property portfolios and enterprise tenants. Dedicated support, SSO, custom integrations, volume tiers.
Terms that show up in property, fintech and AIoT contexts — explained the way you would explain them to a colleague at lunch.
Onboard your property or business — units, blocks, customers, agreements imported.
Configure modules — invoicing, billing rules, booking calendars, helpdesk SLAs.
Pair RFID readers, face / plate cameras, intercoms, lift and lock controllers.
Cut over. Cron jobs run. Dashboards populate. Ops takes the wheel.
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.
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.
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.
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.
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.
Member-driven clubs running courts, coaches, classes and F&B with seasonal membership cycles. Pain: court double-booking, member-charge reconciliation, no-shows.
A racquet club with 12 courts grew booked-court utilisation by 38% while reducing front-desk booking workload by ~70%.
Fitness operators with class passes, personal-trainer schedules and access turnstiles. Pain: enforcing membership at the door, class capacity and trainer payouts.
A 3-branch gym chain eliminated tail-gating losses worth ~RM8,500/month after enforcing face + pass at the turnstile.
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.
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.
Gated landed-house communities with security guards, perimeter cameras and resident committees. Pain: visitor management at peak hours, complaint backlog, perimeter awareness.
A community gate processing 200+ visitors/day cut average visitor approval from ~4 minutes to under 90 seconds — a 60% improvement.
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.
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.
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.
A clubhouse handling ~80 bookings/day moved members to QR-based self-service; front-desk booking workload dropped ~70% with zero member complaints.
Six operators on what changed when their site moved onto AUTOSERVA.
Tell us how many sites, which hardware vendors and what your current pain is. We'll quote, scope and onboard. English / Bahasa / Mandarin.
Long-form answers to what operators actually ask before they sign — pricing, MyInvois, hardware, mobile apps, hosting, multi-country deployment.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Yes. Logo, footer, payment instructions, multi-language remarks and per-customer remarks are configurable. Reports can be exported as PDF, Excel or CSV.
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.
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.
Data is hosted in Malaysian cloud regions, encrypted at rest (AES-256) and in transit (TLS 1.3). Daily off-site backups with point-in-time restore for the last 30 days.
Yes — deployed across Malaysia, Singapore, Indonesia, Thailand, Vietnam and the Philippines. Tax flows are configurable per country; MyInvois is the Malaysia-specific module.
99.9% uptime target. Maintenance windows are scheduled out of business hours and announced via email (PHPMailer) to all tenant administrators. A public status page tracks incidents in real time.
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.
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.
Yes. While AUTOSERVA is built around Malaysian PDPA, the same controls — purpose-of-processing logging, configurable retention, right-to-erasure workflows, audit trails on biometric data — satisfy the operational requirements of GDPR. Hosting region can be selected per tenant where GDPR data residency is required.
Yes. Each customer record carries a base currency; invoices, payments and statements respect it. FX rates are pulled from a configurable source and locked at posting time. Consolidated reports can be presented in MYR, SGD, USD or any base currency you choose.
Yes. The customer/resident-facing PWA mobile apps support full branding — logo, colour palette, app icon, sender names on outbound email — and the dashboard chrome can be skinned for enterprise customers. Source-code white-label / on-prem licensing is available on request.
Yes, for qualifying enterprise customers. We deliver a hardened on-prem build that runs on your infrastructure, with the same module set and an offline-friendly licensing model. Patrick will walk you through the requirements; an on-prem contract typically takes 6-8 weeks from signature to go-live.
Audit log retention defaults to 7 years for financial events and 18 months for operational events, both configurable per tenant. The full log is exportable to CSV, JSON or syslog/SIEM (Splunk, Elastic, Wazuh). Records are append-only and tamper-evident.
Configurable password complexity, rotation and lockout rules per tenant. Two-factor authentication via TOTP (Google Authenticator, Authy, 1Password), email OTP, SMS OTP and passkeys (WebAuthn). Admin and finance roles can be forced to 2FA. SSO via SAML 2.0 and OIDC is available on enterprise plans.
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.
You own your data. We provide a self-service export of all your transactional, member and audit data in CSV/JSON; biometric embeddings can be deleted on request with a signed certificate of destruction. There is no exit fee.
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.