KAI Hospitality

KAI Hospitality Intelligence

Every night audited.
Every number sealed.

KAI reads the reports your PMS already prints, checks every figure against Malaysian statute and your own baselines, and seals the verified record into a tamper-evident vault kept for seven years.

Built for Malaysian hospitality · In live hotel operations since 2026

The compliance clock is running

LHDN’s e-invoice mandate reached businesses above RM1 million turnover in 2026, and Tourism Tax, SST and PDPA each carry filing rules of their own. Every one of them is checkable from the reports your hotel already produces — if something checks them nightly.

1 January 2028

E-invoice penalties begin for the RM1 to RM5 million band. The mandate itself started 1 January 2026, so the obligation is live now. LHDN's penalty-free relaxation runs to 31 December 2027, and only while you are issuing consolidated e-invoices every month.

LHDN e-Invoice Guideline v4.7
RM 10,000

A single transaction at or above this amount cannot ride a consolidated e-invoice; it needs its own, and that rule applies during the relaxation too. KAI surfaces every night that reaches the threshold so you can check the folios behind it.

LHDN e-Invoice Guideline v4.7
RM 10 / room / night

Tourism Tax owed for every foreign-tourist room night. KAI classifies every guest and reconciles the tax listing against the night audit.

Tourism Tax Act 2017

Statutory dates as at August 2026. LHDN has revised the e-invoice timetable more than once; check the current guideline before relying on a date here.

  • Tourism Tax Act 2017
  • Service Tax Act 2018
  • LHDN e-Invoice Guideline
  • Personal Data Protection Act

Three steps, nightly

How a night moves through KAIThree stages. First, the reports your PMS already prints are uploaded, and guest names, passports and identity card numbers are stopped at the parser so they never reach the statutory record. Second, every figure is checked against Tourism Tax rules A to G, SST at eight percent on net room revenue and the RM10,000 e-invoice rule, and each flag cites the rule it came from. Third, a manager verifies and the record seals: SHA-256 hashed and kept for seven years.NamePassportICstopped at the parserTourism Tax A to GSST 8% on netRM10,000 watchflagged, rule citedSHA-256sealed, 7 yearsUpload what your PMSalready printsEvery figureis checkedA manager verifies.The record seals.Night audit, Tourism Taxlisting, amendmentsEach flag cites the ruleit came fromNothing seals withoutan explicit verify
  1. 01

    Upload the reports your PMS already prints

    Night audit, Tourism Tax listing, amendment listing, OTA statements. No integration project and no workflow change. Onboarding typically takes under a week.

  2. 02

    Every figure is checked

    Tourism Tax rules A to G. SST at 8% on net room revenue, never on service charge. The RM10,000 e-invoice rule. Rate spikes, missing amendment reasons, unpaired rate drops. Each flag cites the rule it came from.

  3. 03

    A manager verifies. The record seals.

    Nothing enters the vault without an explicit verify. Sealed records are SHA-256-hashed and kept seven years. The database itself refuses to update or delete them. Corrections need a second approver.

Every number shows its working

Audit-grade means you can always answer one question: where did this number come from? On a KAI screen, a metric names the report it was read from, a delta names its baseline, and a flag cites the statute it enforces.

Report prose is AI-generated and machine-verified: every figure in the narrative is checked against the computed numbers before it renders. A summary that invents a figure never reaches you.

Tonight’s auditIllustrative example
Net revenue
RM 4,182.40From: Night Audit, line 47
Tourism Tax
RM 40.004 foreign-tourist room nights × RM 10
Amendment without a reason code · LHDN e-Invoice Guideline
Sealed after manager verify · SHA-256 · kept 7 years

Built like the audit it performs

Seven-year tamper-evident vault
Sealed records are SHA-256-hashed; the database refuses updates and deletes.
Maker-checker corrections
The person who requests a correction can never be the one who approves it.
Guest privacy by construction
Names, passports and ICs never reach the statutory record; raw report files purge after 30 days.
Machine-verified AI figures
Every figure in an AI-written summary is checked against the computed values before it renders.
Tenant isolation at the database
Row-level security on every tenant table. PostgreSQL enforces it, not convention.

Built for the hotels the mandate reaches

KAI is for independent Malaysian hotels and small groups above the RM1 million e-invoice line: typically 30 to 70 rooms, run by a GM who owns the numbers without a data team behind them. If your PMS prints a night audit, KAI can learn to read it. Supporting a new report format is a bounded addition, not an integration project.

See your own reports audited

Bring a night audit. In thirty minutes you'll watch it checked, verified and sealed.