ZenotiHelp

Configure Montenegro fiscal invoicing

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

The Montenegro fiscal invoicing integration registers Zenoti invoices with the Montenegro Tax Administration's fiscal infrastructure (DDDI β€” Digital Document Distribution Infrastructure, the Tax Administration's fiscalisation platform). Once configured, every invoice closed at an enabled Montenegrin center is confirmed and fiscalized with the Tax Administration and returned with a fiscal verification number and QR code.

Region served: Montenegro only. If your organization operates in multiple countries, configure each country's compliance integration separately on its respective centers.

Deployment model: The Montenegro Tax Administration operates a cloud fiscalisation service. Zenoti calls its API over the public internet using IoT-style authorization. There is no on-premise component required on the Zenoti side.


On this page


Before you begin

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

  • Each Montenegrin center must have accurate address, VAT number, and business unit details before you enable fiscalisation.

External-system prerequisites

Complete these before attempting Zenoti configuration.

1. Register your business with the Montenegro Tax Administration

  • Your business must be registered with the Montenegro Tax Administration and hold a valid VAT number.
  • Register each point-of-sale location as a business unit with the Tax Administration and obtain its business unit code.
  • Register each fiscal device (operator/cash register) that will issue receipts and obtain its operator identifier. In Zenoti, each center typically maps to one registered device.

Refer to the Montenegro Tax Administration's official guidance for the current enrollment steps β€” the portal and form names change periodically.

2. Obtain fiscal authorization credentials

  • Request the IoT authorization token (API key) that Zenoti will send in the Authorization header when submitting to the fiscal API. These credentials are issued by the Tax Administration or by your fiscal implementation partner.
  • Record the fiscal API host URL. Sandbox and production URLs differ β€” confirm which environment your credentials are valid for.

3. Plan cash register initialization

  • The Tax Administration requires the first cash receipt of each operating period to be preceded by a cash register initialization. Zenoti performs this automatically on the first CASH-type payment after a configured initialization date, but your finance team should be aware of the reset cadence your accountant recommends.

If you do not have direct access to the Tax Administration portal, open a Zenoti Support ticket for guidance on which values are required. Zenoti cannot obtain the credentials on your behalf.


Network requirements

The following outbound connection is required from Zenoti to the Montenegro fiscal API.

Direction Port Protocol Endpoint to allowlist
Outbound: Zenoti β†’ Montenegro fiscal API 443 HTTPS The host URL provided by the Tax Administration (sandbox or production).

No inbound connectivity to Zenoti is required for Montenegro. If Zenoti cannot reach the fiscal API, invoice closure is blocked and the invoice remains in an unfiscalized state β€” it does not auto-retry without staff action.


Configure Montenegro credentials

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

  2. Enter the following values. All values come from the Montenegro Tax Administration or the fiscal implementation partner who enrolled your business β€” Zenoti does not supply defaults.

    Field Source What to enter
    Buyer Name, Buyer Tax Number Your recurring buyer, if any. Optional defaults used when a center issues most invoices to one buyer.
    VAT Number Your own tax registration. Your organization's Montenegrin VAT number.
    API Key (IoT authorization token) Montenegro Tax Administration enrollment / fiscal partner. The authorization token used in the Authorization header. Zenoti stores this encrypted at rest.
    Host URL Montenegro Tax Administration enrollment / fiscal partner. The fiscal API endpoint URL. Sandbox and production differ β€” use the one matching your credentials.
    Device Id (operator code) Montenegro Tax Administration (per fiscal device registration). The registered fiscal device / operator identifier.
  3. Select Save. Zenoti saves the credentials and enables Montenegro fiscalisation.

Worked example: A center in Podgorica has VAT number ME12345678 and a device ID of DEV-042. The fiscal partner provides a production host URL of https://efiskalizacija.tax.gov.me/api/v1 and an IoT token of the form abc123...xyz. Enter these values exactly as provided β€” do not add spaces or modify the token format.


Enable per center

Montenegro compliance is configured at the center level. Each Montenegrin center requires its own credentials and must be enabled individually.

  1. For each Montenegrin center, select the center in the scope selector and expand Montenegro - Invoicing on Configuration > Integrations > Integration Settings.
  2. Enter the center's credentials and confirm its VAT Number, Device Id, and address match the Tax Administration records.
  3. Select Save.

The first CASH-type invoice after enablement triggers an automatic cash register initialization request to the Tax Administration. Verify the initialization succeeded in the compliance log before processing real transactions.

Note: If your organization has centers in multiple countries, enabling Montenegro compliance on a center does not affect centers in other countries. Each regional compliance integration is scoped to the centers where it is enabled.


How it works

Montenegro fiscalisation is a two-step process per invoice.

  1. A service is completed and an invoice is created in Zenoti.
  2. When staff close the invoice, Zenoti assembles the fiscal payload (buyer info, line items, taxes, totals, payment type) in the Tax Administration's schema.
  3. Step 1 β€” Confirm. Zenoti sends the invoice with step code 35 (Confirm). The Tax Administration validates the data and returns intermediate identifiers.
  4. Step 2 β€” Fiscalize. Zenoti sends step code 40 (Fiscalize). The Tax Administration completes the fiscal registration and returns the fiscal serial number, fiscal invoice number, QR code content, and fiscalisation timestamp.
  5. Both steps must succeed for the invoice to be considered fiscalized. Zenoti stores the response, uploads the QR code, and prints the fiscal verification number and QR code on the guest receipt.
  6. For CASH payments, if the cash register has not been initialized for the current period, Zenoti issues an initialization request before the Confirm/Fiscalize sequence.

Failure paths

The following table describes the failure modes you may encounter and how to resolve each one.

Failure mode User-visible symptom Resolution
Confirm step fails (data validation on Tax Administration side). Closure is blocked and an error references the rejected field. Fix the flagged field (buyer tax number format, VAT mismatch, invalid date). Retry closure.
Fiscalize step fails after Confirm succeeded. Closure is blocked; the invoice is left in a partially-validated state. Retry closure. If the Fiscalize error persists, contact your fiscal partner β€” the Confirm record remains valid and the retry will complete fiscalisation.
Fiscal API unreachable. Closure fails with a network error. Verify outbound HTTPS to the host URL. If the Tax Administration portal reports an outage, wait for recovery. The invoice remains open in Zenoti.
Authentication failed (invalid or rotated IoT token). 401 / unauthorized error. Re-enter the API key. If rotation is required, request a new token from the Tax Administration or your fiscal partner.
Cash register initialization failed. First CASH invoice cannot be fiscalized; all subsequent CASH invoices are blocked until initialization completes. Retry the initialization by closing the blocked invoice again; if repeated failures occur, review the Device ID and Business Unit Code for accuracy and contact your fiscal partner.
Duplicate submission (same invoice submitted twice). The Tax Administration returns a duplicate-reference error. Check the compliance log β€” if the original succeeded, the duplicate error is safe to ignore. Do NOT create a new invoice.
Schema version mismatch (Tax Administration updated its API). Validation errors on fields that were previously accepted. Contact Zenoti Support. Schema updates require a Zenoti-side change.

Edit or void a fiscalized invoice

Fiscalized invoices are immutable on the Montenegro Tax Administration side. The Confirm + Fiscalize sequence generates a fiscal record that cannot be altered after the fact.

Invoice state What you can do
Open in Zenoti, not yet fiscalized Edit freely. No fiscal record has been created.
Closed in Zenoti, successfully fiscalized Cannot be edited. To correct, issue a corrective invoice (see Refunds and corrective invoices) that reverses the original, then issue a new invoice with the correct details.
Closed in Zenoti, Confirm succeeded but Fiscalize failed Retry closure in Zenoti. Do NOT recreate the invoice β€” the Confirm record is reusable.
Closed in Zenoti, submission never attempted (network down) Retry closure once connectivity is restored.

Refunds and corrective invoices

A refund in Zenoti generates a corrective (credit-note equivalent) fiscal document on the Tax Administration side.

Zenoti action Montenegro Tax Administration side Reconciliation note
Full refund of a fiscalized invoice. A corrective invoice is fiscalized with a corrective document type code. Amounts are negative (reverse of the original). Both the original and corrective records appear in fiscal reports.
Partial refund. A partial corrective invoice referencing the original. The original retains its full amount; the corrective records the reversed portion.
Refund of a non-fiscalized invoice. No corrective is issued β€” there is no fiscal record to reverse. Handle as a Zenoti-side cancellation.

Train cashiers that refund documents are fiscalized separately from the original invoice and will appear in the daily fiscal report as distinct entries.


Reconciliation

Reconcile Zenoti records against the Tax Administration portal daily.

Source What to match on Cadence
Zenoti: Collections by Invoices report, filtered to Montenegrin centers. Zenoti invoice number. Daily at close.
Montenegro Tax Administration portal: daily fiscal report. Fiscal invoice number (returned by the Fiscalize step) and the Zenoti invoice number as the external reference. Daily.

Recommended cadence: reconcile at end of day. The Tax Administration's reporting window typically aligns to calendar days in Montenegro time. If the Zenoti log shows a successful Fiscalize but the portal does not list the entry, escalate to your fiscal partner β€” the Zenoti-side log is the record of what was sent, not what the authority accepted.


Tips

  • Run the full Confirm + Fiscalize flow in the Tax Administration sandbox before enabling production. Use non-production invoices with a clearly-marked test VAT buyer.
  • Cash register initialization is triggered automatically β€” but it only runs on CASH payments. If your center uses only card payments, plan with your accountant whether a periodic manual initialization is needed.
  • Monitor the compliance log at least daily until staff are familiar with the Confirm vs Fiscalize distinction β€” failures at either step require retry.
  • When rotating the IoT authorization token, update API Key on the Montenegro configuration page and select Save before the old token expires to avoid a gap in fiscalisation.

Troubleshooting

Symptom Likely cause Resolution
Invoice closure is blocked with "authentication failed" after working previously. The IoT authorization token was rotated or expired. Obtain the new token from the Tax Administration or your fiscal partner, then update it on the Montenegro - Invoicing accordion (Configuration > Integrations > Integration Settings, center scope).
Cash invoices are blocked at the first transaction of the day with an initialization error. The cash register initialization request failed β€” typically a mismatch between the Device Id in Zenoti and the Tax Administration's records. Verify the Device Id and business unit code values in the Montenegro configuration match the Tax Administration's registered values exactly. Correct any discrepancy and retry closing the invoice.

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