Skip to content

Prepare fiscal data carefully and verify every result

LaniTech exposes organization tax details, fiscal-device configuration, item taxes, and an invoice fiscalisation action. Treat these tools as one part of your compliance process—not proof that every statutory requirement has been met.

FiscalisationCompliance-sensitive
Skip to documentation
Browse this guide

Understand what is available today

Fiscalisation is spread across organization settings, fiscal devices, products and services, and invoice actions.

The Taxes dashboard is not available yet

The Business navigation includes a Taxes destination, but that route is currently a coming-soon screen. Configure the verified areas above instead of treating the Taxes page as an operational tax workspace.

Add the organization details used on documents

Complete the business identity before configuring devices or fiscalising customer documents.

SettingsOrganization
  1. 1

    Open Organization settings

    Go to Organization settings and confirm the legal business identity and contact details.
  2. 2

    Add tax identifiers

    Enter the VAT and TIN or registration details supplied to the business. Do not copy identifiers from another organization or an example document.
  3. 3

    Choose what customer documents show

    Review the controls that determine whether VAT, TIN, and organization addresses appear on invoices and quotations.

Configure a fiscal device

Use the values assigned to the specific device and organization. The frontend does not provide a device-connection test.

SettingsFiscal devices
  • Display name for identifying the device inside LaniTech.
  • Device ID and serial number supplied for the device.
  • Model name and model version.
  • Activation key and operation ID assigned to the organization.

Treat the activation key as a secret

Never place a real activation key in screenshots, support messages, documentation examples, or shared test data. Limit device changes to authorized organization administrators and use a secure handoff for credentials.

Review taxes on products, services, and line items

Tax configuration starts in the catalog and can be reviewed in the customer-document builder.

  1. 1

    Open the product or service

    Use the Products workspace to review the item's VAT and any additional named taxes.
    ProductsProduct or serviceTax settings
  2. 2

    Confirm the current rate

    The current product and service forms show a 15.5% standard VAT option. Confirm that rate against the business's actual requirements before saving it.
  3. 3

    Review the invoice tax breakdown

    Check the overall rate and named components on each relevant invoice or quotation line before sending the document.

A UI default is not tax advice

Tax rates and filing rules can change and can differ by item or organization. Confirm the correct treatment with your accountant or relevant tax authority before relying on a saved default.

Fiscalise an eligible invoice

The action is available from the invoice list for saved invoices that have not already been marked as fiscalised.

  1. 1

    Verify the invoice first

    Check the customer, organization identity, currency, items, quantities, prices, and tax breakdown before starting the fiscalisation request.
  2. 2

    Choose Fiscalise invoice

    Open the invoice actions menu and select Fiscalise invoice. The action requires permission to update invoices.
    PaymentsInvoicesInvoice actions
  3. 3

    Wait for the request result

    Do not repeat the action while the request is in progress. After success, refresh or reopen the record and review the fiscalisation state returned for that invoice.

Review the customer-facing output

Fiscal metadata can affect the document title and the status shown on public records and receipts.

  • A fiscalised invoice document can use the title “FISCAL TAX INVOICE.”
  • The public invoice can display fiscalisation status returned by the backend.
  • Receipts can display a fiscal day number when that metadata is supplied.
  • Download or print a test document and inspect the actual customer-facing result.

Keep compliance limitations explicit

The current frontend can submit and display data, but it cannot independently certify statutory acceptance.

A successful request is not proof of compliance

LaniTech can report that the fiscalisation request completed and show the resulting invoice state. The frontend does not expose certificate management, authority acknowledgements, device connection testing, or fiscal-day open and close controls. Preserve the evidence required by your organization outside this interface where necessary.
  • Confirm device credentials and organization identifiers before use.
  • Confirm current tax rates and filing requirements independently.
  • Do not use the coming-soon Taxes page as a compliance record.
  • Escalate rejected or ambiguous fiscalisation results before issuing the document.

Need a hand with your setup?

Talk to the LaniTech team through one of our official support channels.