Antylogic
DemoApp login

399 operational guides

Docs sections
DocsPOS billing
Device

Configure VERI*FACTU

Prepare VERI*FACTU for a Spanish POS location from POS settings > Billing. The save stores the configuration on the location TPV settings; it does not submit invoices, create fiscal records, or test AEAT connectivity.

In this article

VERI*FACTU is managed from the POS Billing settings for Spanish locations. In the GB demo context, Harbor Soho and Harbor Borough can show the unavailable state, but they should not be used to imply that VERI*FACTU can be configured in GB.

Use this guide to review availability, platform authorisation status and save behaviour before later invoice flows consume the configuration.

Before you start

  • You are signed in and working in a valid organisation and location context.
  • You can read POS settings; saving changes requires `tpv:manage` for the location.
  • The location must be in Spain (`country_code=ES`) to show the configurable VERI*FACTU block.
  • For captures, use sandbox or mock data only. Do not use production AEAT credentials or trigger real fiscal traffic.

Instructions

  1. 1.

    Open POS Billing settings

    Open the location POS settings screen and select the Billing tab. The form loads saved TPV settings, or defaults if the location has no saved settings row yet.

  2. 2.

    Check VERI*FACTU availability

    Confirm whether the VERI*FACTU area is visible. Spanish locations can show the configurable card; non-Spanish locations show that VERI*FACTU is not available.

  3. 3.

    Review the fiscal card

    Review the status, VERI*FACTU modality and AEAT platform-authorisation mode. The current app card focuses on platform authorisation rather than exposing separate endpoint, certificate, timeout, headers, QR and system fields.

  4. 4.

    Request authorisation only in a prepared ES runtime

    Use the platform authorisation action only when the documentation runtime is supervised and safe. For GB captures, keep the flow review-only and do not attempt configuration.

  5. 5.

    Save changes

    Select Save changes after any permitted change. The app sends the complete TPV settings snapshot to `PUT /api/app/{orgId}/{locationId}/tpv-settings`, including `billing_config.verifactu` when the location supports it.

  6. 6.

    Know what this save does not do

    This action only stores configuration. It does not create `verifactu_record`, submit invoices, validate certificates against AEAT, or test the endpoint.

Validations and limits

  • The configurable VERI*FACTU block is Spain-only in the analysed flow; forced enabled configuration for a non-Spanish location is rejected.
  • Read-only users can view POS settings but cannot save VERI*FACTU changes.
  • The settings endpoint accepts `GET` and `PUT`; the save requires valid TPV settings JSON and a JSON-object `billing_config`.
  • The backend also validates unrelated TPV settings references because the endpoint persists the full settings row.
  • Do not publish field-level endpoint or certificate screenshots unless the real captured build displays those controls.

Expected result

The Spanish location stores its VERI*FACTU configuration inside TPV settings for later invoice and submission flows, while the documentation remains clear that saving settings does not submit fiscal records.