ZenotiHelp

Configure Malaysia e-invoicing

ZTZenoti Docs Team Updated September 5, 2026 10 min readHow-to

The Malaysia e-invoicing integration submits Zenoti invoices to LHDN (Lembaga Hasil Dalam Negeri, the Malaysian Inland Revenue Board) through LHDN's MyInvois platform. Once configured, Zenoti issues either a simplified receipt or a full validated e-invoice for each transaction, based on the transaction mode configured at the center.

Region served: Malaysia only. LHDN is the Malaysian federal tax authority; this integration is not interchangeable with any other country's e-invoicing.

Deployment model: LHDN operates MyInvois as a cloud service. Zenoti submits invoices via the MyInvois API over the public internet. There is no on-premise component on the Zenoti side. MyInvois validation is near-real-time; QR codes and document UUIDs are returned synchronously.


On this page


Before you begin

Permission: You need organization administrator access to configure regional compliance integrations.

  • Each Malaysian center must have accurate address, TIN (Tax Identification Number), and MSIC industry code before enabling e-invoicing.

External-system prerequisites

1. Register with LHDN and enrol in MyInvois

  • Your business must be registered with LHDN and hold a valid TIN.

  • Enrol your business in MyInvois β€” LHDN's e-invoicing portal β€” and obtain your MyInvois API credentials (API key). Visit the MyInvois portal for the current enrolment steps; LHDN updates the procedure periodically.

  • Confirm your seller Registration Type with LHDN. Zenoti supports the following registration types:

    Registration type Use when
    Business Registration Number Your entity is a registered company (most common for businesses).
    National Registration Identity Card Your entity is a sole proprietor or individual.
    Passport Number The seller is a foreign national without a Malaysian NRIC.
    Army Identification Number The seller holds a Malaysian armed forces identification.

    The correct choice depends on your entity structure β€” consult LHDN or your tax advisor.

  • Identify your MSIC industry code (Malaysia Standard Industrial Classification). MyInvois requires this on every submission.

2. Understand the B2B vs B2C rollout phases

LHDN has rolled out e-invoicing in phases by taxpayer size. Confirm which phase applies to your business and whether you are required to issue full e-invoices for all transactions, B2B only, or specific thresholds. Zenoti supports both modes β€” your configuration should match LHDN's expectation for your business.

3. Capture buyer information for B2B

For B2B e-invoices, LHDN requires the buyer's TIN, registration number, address, and (where applicable) SST registration. Train front-desk staff to collect these before closing a B2B invoice, or set defaults for recurring business buyers.


Network requirements

Direction Port Protocol Endpoint to allowlist
Outbound: Zenoti β†’ MyInvois 443 HTTPS The MyInvois API host URL provided by LHDN (sandbox or production).

No inbound connectivity is required. If MyInvois is unreachable, e-invoice submissions fail and must be retried manually β€” there is no automatic background retry.


Transaction modes

Zenoti submits invoices to MyInvois in one of two modes per transaction:

Mode What it does When to use
Receipt Submits a simplified receipt record to MyInvois. B2C transactions where the buyer does not need a validated e-invoice.
E-Invoice Submits a full LHDN-validated e-invoice with buyer details, line items, taxes, and returns a document UUID and QR code. B2B transactions, and B2C transactions where the buyer has requested a validated e-invoice, or where LHDN rules require it (for example, when a B2C buyer requests an invoice under their personal TIN).

The mode is chosen per invoice at closure time, influenced by the center's default mode and whether buyer TIN/registration details have been captured on the invoice.


Configure LHDN credentials

  1. Select the center in the scope selector, navigate to Configuration > Integrations > Integration Settings, and expand Malaysia E - Invoicing.

  2. Enter the following values. All values come from LHDN or from your own MyInvois enrolment records. Zenoti does not supply defaults.

    Field Source What to enter
    Seller Tin Number LHDN registration. Your organisation's Tax Identification Number.
    Seller Registration Type Your business structure. Business Registration Number, National Registration Identity Card, Passport Number, or Army Identification Number, matching the type under which you enrolled with LHDN.
    Seller Registration Id Your own business registration. Your registration identifier of the chosen type, as LHDN recognises it.
    Industry Code MSIC classification system. Your MSIC industry code (as registered).
    Industry Description MSIC classification system. Human-readable industry description matching the code.
    API Key MyInvois portal (after enrolment). The API key issued by LHDN. Zenoti stores this encrypted at rest.
    Host URL MyInvois portal. The MyInvois API endpoint. Sandbox and production differ.
  3. Select Save. Zenoti saves the credentials and enables Malaysia e-invoicing.

Note: The API Key and Host URL fields correspond to the credential fields used by Zenoti's regional compliance integration. Keep these values confidential β€” treat them as opaque secrets and do not share them outside your finance and IT teams.

Worked example: A spa group registered as a company enters Seller Registration Type Business Registration Number, Seller Registration Id 202001012345, Seller Tin Number C12345678900, Industry Code 9602, and Industry Description Hairdressing and other beauty treatment. The Host URL is set to the MyInvois production endpoint provided in the MyInvois portal after enrolment. After selecting Save and then Verify, the integration returns a success status confirming the credentials are valid.


Configure transaction mode

Set the default mode for each center.

  1. On the integration configuration panel, set the default transaction mode to Receipt or E-Invoice.
  2. For centers handling mixed B2B and B2C traffic, leaving the default on Receipt and switching to E-Invoice at closure time (when buyer TIN is captured) is a common pattern. Confirm the approach with your tax advisor.

Toggle interactions

Zenoti's Malaysia setup has two behaviour-affecting toggles: the center-level enablement of the LHDN integration, and the default transaction mode (Receipt vs E-Invoice). Both can be changed independently, and the combination determines what happens at invoice close.

LHDN enabled at center Default mode Invoice close behaviour
Off (any) No submission to MyInvois. Invoice closes as a normal Zenoti invoice with no fiscal record.
On Receipt Each invoice submits as a Receipt unless buyer TIN / registration details are present on the invoice, in which case Zenoti submits as a full E-Invoice.
On E-Invoice Each invoice submits as a full E-Invoice. Closure is blocked if required buyer fields (TIN, registration, address) are missing.
On Receipt, but invoice has buyer TIN Zenoti submits as E-Invoice (buyer details take precedence over the center default).

Document the center default with your front-desk lead so staff know what to expect at closure.


Enable per center

Regional compliance settings are configured at the center level β€” each center has its own fiscal configuration.

  1. Select the center in the scope selector, then navigate to Configuration > Integrations > Integration Settings.
  2. Expand Malaysia E - Invoicing and enable the LHDN integration for that center.
  3. Verify the center's TIN, registration ID, industry code, and address match LHDN records.
  4. Select Save.

Important: Repeat this process for every Malaysian center. Enabling the integration at the organization level does not automatically enable it for individual centers.


How it works

  1. A service is completed and an invoice is created in Zenoti.
  2. At closure, Zenoti determines Receipt vs E-Invoice mode based on the center default and the buyer details captured on the invoice.
  3. Zenoti formats the payload according to the MyInvois schema (bilingual seller/buyer addresses, tax categories, currency).
  4. Receipt mode β€” Zenoti submits the receipt. LHDN returns a simple acknowledgement; no QR code is returned.
  5. E-Invoice mode β€” Zenoti submits the full e-invoice. LHDN validates and returns a document UUID. Zenoti then retrieves the QR code for the validated document and stores both with the invoice.
  6. On the guest receipt, a validated e-invoice displays the MyInvois document UUID and QR code. A receipt-mode submission shows only a simple acknowledgement.

Failure paths

Failure mode User-visible symptom Resolution
Buyer TIN missing for E-Invoice. Closure blocked with a prompt for TIN/registration. Collect the buyer TIN and registration ID and re-enter on the invoice. For B2C guests who have no TIN, ask whether a Receipt is acceptable β€” the center default may need to be adjusted for that transaction.
Invalid buyer TIN. MyInvois returns a validation error naming the field. Verify the TIN with the guest.
MyInvois unreachable. Closure fails with a network error. Verify outbound HTTPS. If LHDN is down, wait for recovery. Manually retry closure β€” there is no automatic retry.
Authentication failed. 401 / unauthorized. Re-enter the API key. If LHDN rotated the credential, obtain the new key from the MyInvois portal.
Duplicate submission. MyInvois returns a duplicate document error. Check the compliance log β€” if the original succeeded, do not resubmit.
Signature / schema validation failure. MyInvois rejects the document citing schema non-compliance. Review the specific error. Most schema errors trace to missing or malformed seller/buyer data. Correct at the invoice or center level.
Schema version mismatch (LHDN updated its API). Validation errors on fields that previously worked. Contact Zenoti Support.
Receipt succeeded but QR code fetch failed. E-invoice is submitted but the receipt does not show a QR code. Zenoti retries QR retrieval on the next closure. The document is valid on LHDN; re-fetch or manual verification in the MyInvois portal confirms.

Edit or cancel a validated e-invoice

LHDN allows a short cancellation window after submission (typically up to 72 hours β€” confirm with your tax advisor and the current MyInvois rules, which change). After the window closes, the e-invoice is immutable and must be corrected via a credit or debit note.

Invoice state What you can do
Open in Zenoti, not yet submitted Edit freely. No fiscal record has been created.
Submitted as Receipt, within cancellation window Cancel in MyInvois, then edit and resubmit in Zenoti. Confirm current cancellation rules with LHDN.
Submitted as E-Invoice, within cancellation window Cancel in MyInvois and issue a corrected e-invoice.
Submitted as E-Invoice, cancellation window closed Cannot be edited or cancelled. Issue a credit note to reverse (or a debit note to adjust upward), then issue a new invoice if needed.

Refunds, credit notes, and debit notes

Zenoti action LHDN / MyInvois side Reconciliation note
Full refund of an E-Invoice. A credit note is submitted to MyInvois referencing the original document UUID. Negative amounts. Both the original and credit note appear in the MyInvois ledger.
Partial refund. A partial credit note referencing the original. The original retains its full amount.
Invoice correction that increases the amount. A debit note is submitted referencing the original document UUID. Both the original and debit note appear in the ledger.
Refund of a Receipt (non-validated). No credit note is issued to MyInvois β€” there is no validated fiscal record to reverse. Handle as a Zenoti-side refund.

Reconciliation

Source What to match on Cadence
Zenoti: Collections by Invoices report, filtered to Malaysian centers. Zenoti invoice number. Daily.
MyInvois portal: submitted documents list. Document UUID (stored with the Zenoti invoice) and seller TIN. Daily for high-volume centers; at least weekly otherwise.

Investigate any Zenoti E-Invoice submission that shows success in the compliance log but is not present in MyInvois within a working day. LHDN's processing is usually within minutes, so multi-hour lag warrants escalation to LHDN support.


Tips

  • Always test in the MyInvois sandbox before enabling production. Use a non-production buyer with a test TIN.
  • Train staff to recognise the Receipt vs E-Invoice prompt. The difference matters for the buyer's own tax reporting.
  • Collect buyer TIN at booking (not at checkout) for known B2B guests β€” it reduces closure-time interruptions.
  • Revisit the MSIC industry code and registration type during any business restructure; mismatches cause LHDN to reject submissions silently on their side at audit time.
  • Enable the integration for one center first and process a small number of test transactions before rolling out to all Malaysian centers.

Troubleshooting

Symptom Likely cause Resolution
The first submission fails immediately after entering credentials. Incorrect API Key or Host URL, or the sandbox/production endpoint mismatch. Verify both values against your MyInvois portal. Confirm you are using the sandbox URL for test environments and the production URL for live centers.
Invoices close successfully in Zenoti but do not appear in the MyInvois portal. The center-level LHDN integration is not enabled, or the center's TIN does not match LHDN records. Confirm the integration is enabled for the specific center (see Enable per center) and that the center TIN matches exactly what is registered with LHDN.
Front-desk staff report that invoice closure is blocked even for B2C walk-in guests. The center default transaction mode is set to E-Invoice, which requires buyer TIN for every submission. If B2C transactions without buyer TIN are expected, change the center default to Receipt. Consult your tax advisor before changing this setting.
QR code does not appear on the printed receipt after a successful E-Invoice submission. The QR code retrieval step (DocumentDetails fetch from MyInvois) failed after the initial submission succeeded. Zenoti retries QR retrieval on the next closure. You can also verify the document directly in the MyInvois portal using the document UUID stored with the invoice.
MyInvois returns a schema validation error after a previously working configuration. LHDN has updated the MyInvois API schema version. Contact Zenoti Support β€” a platform update is required to align with the new schema.

Was this article helpful?
Your feedback helps us improve our documentation.