ZenotiHelp

Submit invoices to regional tax authorities

ZTZenoti Docs Team Updated April 20, 2026 8 min readGuide

When a regional compliance integration is configured, Zenoti submits each invoice to the relevant tax authority as part of the invoice-closure step. This article covers the day-to-day flow that applies across all four supported regions β€” Spain (Fiskaly), Saudi Arabia (ZATCA), Montenegro, and Malaysia (LHDN) β€” along with failure handling, edit/void rules, refunds, and reconciliation.

The setup for each region lives in its dedicated article. This workflow assumes configuration is complete.


On this page


Before you begin

Permission: You need billing permissions to close invoices at your center. Fiscal submission is performed automatically by Zenoti at closure β€” there is no separate permission for the submission itself.


How fiscal submission works

The closure flow follows the same pattern in every region:

  1. Services are completed and an invoice is created in Zenoti.
  2. The front desk reviews and finalises the invoice (amounts, discounts, buyer details).
  3. If the region requires additional buyer information (Spain Complete NIF, Saudi B2B VAT, Malaysia E-Invoice TIN), Zenoti prompts for the missing fields before allowing closure.
  4. At closure, Zenoti:
  • Formats the invoice according to the regional specification (bilingual fields for ZATCA, two-step Confirm/Fiscalize for Montenegro, Receipt vs E-Invoice mode for Malaysia, Complete vs Simplified for Spain).
  • Signs the invoice where the scheme requires signing (Fiskaly provides signing; ZATCA applies a cryptographic stamp; Malaysia e-invoices are LHDN-validated; Montenegro returns a fiscal number).
  • Submits the invoice to the tax authority's API over HTTPS.
  1. The authority returns a compliance response (signature, QR code, fiscal number, or document UUID).
  2. Zenoti stores the fiscal confirmation with the invoice and logs the submission.
  3. The guest receipt includes the region's verification details β€” typically a QR code that can be scanned by the authority's consumer app, plus a fiscal or document number.

Region-specific requirements at a glance

Region Authority Document types Buyer info required Special behaviour
Spain Fiskaly (cloud) Simplified, Complete Buyer NIF required for Complete (over 3,000 EUR). Fiskaly signs with a managed certificate; Zenoti rotates the signer automatically.
Saudi Arabia ZATCA Fatoora B2B invoice, B2C invoice, credit note (B2B/B2C), debit note (B2B/B2C) Buyer VAT for B2B; bilingual (EN+AR) seller address always required. ZATCA applies a cryptographic stamp and QR code.
Montenegro Tax Administration (DDDI) Invoice, Corrective (refund) Buyer VAT where applicable. Two-step Confirm + Fiscalize per invoice; cash register initialisation auto-triggers on first CASH payment.
Malaysia LHDN MyInvois Receipt, E-Invoice, credit note, debit note Buyer TIN + registration for E-Invoice (B2B). Receipt and E-Invoice modes selected per invoice based on center default and buyer details.

See each setup article for the full field-by-field prerequisites.


Close an invoice and trigger submission

  1. Open the invoice in the POS (Point of Sale).
  2. Review the line items and totals.
  3. Capture any required buyer information the region calls for (see the table above). Zenoti prompts if a required field is missing.
  4. Collect payment.
  5. Select Close Invoice. Zenoti submits to the authority in the background as part of the closure.
  6. Confirm the fiscal confirmation details appear on the receipt:
  • Spain: Fiskaly QR code and signature block.
  • Saudi Arabia: ZATCA QR code and stamp reference.
  • Montenegro: Fiscal invoice number, IIC (verification ID), and QR code.
  • Malaysia: MyInvois document UUID and QR code (E-Invoice mode only).

If the receipt prints without fiscal details, the submission likely failed β€” see the next section.


Handle a failed submission

Regional compliance failures surface on the invoice with a status and error reason. Zenoti does not silently retry in the background β€” staff must act on a failure.

Failure mode User-visible symptom Resolution
Authority unreachable (network / authority maintenance). Submission error with a network timeout or connection failure. Verify outbound HTTPS. If the authority reports an outage, wait for recovery and retry. The invoice stays in a retriable state in Zenoti.
Authentication / token expired. 401 / unauthorized. Re-enter credentials on the integration setup page. For Fiskaly, also confirm the signer has not expired.
Signature / cryptographic validation failure. Authority rejects the stamp or signature. Typically indicates a clock-skew or credential problem. Verify server time (NTP) and credentials. For Fiskaly, a signer regeneration may be required.
Missing required buyer field. Closure blocked with a prompt for NIF / VAT / TIN. Collect from the guest and re-enter. If the guest declines, determine whether a Simplified/Receipt/B2C variant is permitted under the scheme.
Invalid field format (NIF, VAT, TIN, address). Authority returns a validation error naming the field. Verify the value with the guest. Re-enter and retry.
Duplicate submission. Authority returns a duplicate-reference error. Check the compliance log β€” if the original succeeded, the duplicate is safe to ignore. Do not reissue the invoice.
Invoice in invalid state (closed parent invoice, zero amount without prefix). Authority rejection citing invalid document configuration. Correct the source condition. Most often this is a configuration gap discovered at go-live.
Schema version mismatch (authority updated its API). Validation errors on fields that previously worked. Contact Zenoti Support β€” schema changes require a Zenoti-side update.
Montenegro Confirm succeeded, Fiscalize failed. Closure blocked, invoice in a partial state. Retry closure; the Confirm record is reusable. Escalate if repeated.
Malaysia QR code fetch failed (DocumentDetails). E-Invoice submitted but receipt shows no QR. Retry closure or fetch from MyInvois portal; document is valid on LHDN side.

Do not resubmit an invoice manually by creating a new one. A duplicate Zenoti invoice can produce duplicate fiscal records on the authority side.


Edit or void a submitted invoice

Across every supported region, once the authority has accepted and stamped/signed an invoice, the fiscal record is immutable. Editing a submitted invoice is not possible β€” corrections flow through credit notes, debit notes, or corrective invoices.

Invoice state What you can do
Open in Zenoti, not yet submitted Edit freely. No fiscal record has been created.
Closed in Zenoti, submission failed Resolve the cause and retry. No fiscal record exists yet.
Closed in Zenoti, successfully submitted Cannot be edited. Use the region's reversal mechanism (see the next section). For ZATCA and LHDN, credit notes and debit notes are dedicated document types. For Fiskaly, a factura rectificativa is issued. For Montenegro, a CORRECTIVE invoice is issued.
Malaysia E-Invoice within cancellation window LHDN permits cancellation within a short window (typically up to 72 hours β€” verify with your tax advisor and current MyInvois rules). After the window, only credit/debit notes.

Never delete or recreate a submitted invoice. Use the documented reversal path.


Refunds, credit notes, and debit notes

Refunds and adjustments in Zenoti generate corresponding documents on the authority side. The exact document type varies by region.

Zenoti action Spain (Fiskaly) Saudi Arabia (ZATCA) Montenegro Malaysia (LHDN)
Full refund of a submitted invoice Factura rectificativa (credit note) referencing the original. B2B or B2C credit note referencing the original. CORRECTIVE invoice with negative amounts. Credit note referencing the original document UUID.
Partial refund Partial factura rectificativa. Partial credit note. Partial CORRECTIVE invoice. Partial credit note.
Upward correction (add charge) Revised invoice or supplementary invoice per your tax advisor's guidance. Debit note. Additional CORRECTIVE or new invoice per your accountant. Debit note.
Refund before submission No authority document issued. No authority document issued. No authority document issued. No authority document issued.

In every region:

  • Both the original and the reversal document remain in the authority's ledger. Neither is deleted.
  • The reversal document references the parent invoice by number/UUID β€” reconciliation matches parent and reversal together.
  • Manual reconciliation at month end is recommended: every Zenoti credit note should have a paired original on the authority side, and vice versa.

Reconciliation

Treat the authority portal as the ultimate source of truth. Zenoti's compliance log records what was sent and the response β€” the authority ledger confirms what was accepted.

Daily reconciliation workflow

  1. Run the Collections by Invoices report in Zenoti, filtered to the center(s) using the regional integration.
  2. Pull the authority's daily submissions report:
  • Spain: Fiskaly portal invoice list; the Spanish tax authority's TicketBAI / VeriFactu portal for audit purposes.
  • Saudi Arabia: ZATCA Fatoora portal.
  • Montenegro: Tax Administration's daily fiscal report.
  • Malaysia: MyInvois documents list.
  1. Match row-by-row on the Zenoti invoice number (which is sent as the external reference to every authority).
  2. Investigate any Zenoti invoice that does not appear on the authority side within a working day. Investigate any authority-side entry that is not paired with a Zenoti invoice.
  3. For credit/debit notes, verify the parent invoice reference matches.
Volume Cadence
High-volume centers (100+ invoices/day) Daily at close.
Medium-volume At least weekly.
Low-volume At month end, aligned with statutory VAT filing.

If the Zenoti compliance log shows a success but the authority portal does not, escalate to the authority's support (Fiskaly support, ZATCA support, Tax Administration / fiscal partner, LHDN support) with the submission timestamp and Zenoti invoice number.

[SOURCE GAP β€” PM VERIFY: whether Zenoti provides a dedicated "regional compliance reconciliation" report that pre-matches Zenoti invoices to authority responses, in addition to the Collections by Invoices report.]


Network requirements summary

All four integrations use outbound HTTPS from Zenoti to a cloud authority or a cloud intermediary. No inbound connectivity to Zenoti is required from the authority side.

Integration Direction Port Endpoint to allowlist
Spain β€” Fiskaly Outbound (Zenoti β†’ Fiskaly) 443 Fiskaly host URL (sandbox or production) from the Fiskaly account.
Saudi Arabia β€” ZATCA Outbound (Zenoti β†’ ZATCA Fatoora) 443 Fatoora host URL from the ZATCA portal.
Montenegro Outbound (Zenoti β†’ Tax Administration DDDI) 443 Host URL from the Tax Administration or fiscal partner.
Malaysia β€” LHDN Outbound (Zenoti β†’ MyInvois) 443 MyInvois host URL from LHDN.

Because submission is server-to-server between Zenoti and the authority, no firewall changes are needed on your own network for front-desk operations. Infrastructure-level allowlisting on the Zenoti side is handled by Zenoti Support.


Tips

  • Train staff on region-specific buyer prompts before enabling fiscal invoicing. Missing NIF / VAT / TIN entries are the most common cause of closure delays.
  • Test end-to-end in the authority's sandbox environment before production β€” including refund, credit note, and debit note flows.
  • Monitor the integration health dashboard for submission errors. A handful of authority-side rejections at go-live is normal; persistent errors signal a configuration gap (Arabic address, registration type, industry code).
  • Keep the authority verification app on a shared staff tablet. Scanning the QR code on a guest receipt is the fastest sanity check.
  • Do not issue an invoice under a different Zenoti center on behalf of a Saudi, Spanish, Montenegrin, or Malaysian center to "save" a failed submission. Each fiscal record must belong to the center that performed the service β€” crossing centers produces orphaned records on the authority side.
Was this article helpful?
Your feedback helps us improve our documentation.