Shopify POS, TicketBAI and VERI*FACTU: requirements and checks

Shopify POS alone does not certify that all company invoicing complies with TicketBAI or invoicing-system requirements. Identify the applicable regime and check the software issuing, recording and communicating each operation.

TicketBAI, VERI*FACTU, SII and B2B electronic invoicing are distinct concepts. Installing an app or printing a QR code does not establish coverage of all these areas.

If you are planning the full setup, our Shopify POS guide for retail and online stores covers inventory, pickup and returns.

How TicketBAI and VERI*FACTU differ

Official TicketBAI information for Álava includes documentation and the registered guarantor-software list. Confirm territorial requirements; a generic app description is not proof of regional coverage.

RRSIF deadlines are not January 2026 for everyone

According to the current AEAT FAQs, mandatory adaptation is scheduled for 1 January 2027 for corporate income taxpayers and 1 July 2027 for other included taxpayers. Review each company's scope and exclusions.

A provider's published date does not replace legislation or competent-authority information. Retain the legal reference used to define the project and review it if the timetable changes.

VERI*FACTU is not the regulation's only mode

The AEAT distinguishes two SIF compliance modes: VERI*FACTU and NO VERI*FACTU, with different requirements. It is incorrect to say every system must send every receipt to the AEAT identically.

Also check SII participation or other situations affecting scope. Validate the decision with tax advisers so technical integration implements the correct regime.

The role of Shopify POS and apps

Shopify publishes in-person selling requirements by country and Comply guidance. This helps evaluate the product but does not prove every app, version, ERP and tax-regime combination is valid.

Ask which software issues invoices, which version is delivered, which declaration or registration applies and what cases are covered. Distinguish POS receipts, ERP-issued invoices and records required by the tax system.

Documentation to request

• Identification of the issuing system and components.
• Covered territories, regimes and operation types.
• Applicable conformity or registration documentation.
• Handling of sequences, corrections and cancelled operations.
• Connection-outage and retry procedures.
• Business access to and retention of records.

A QR-generating demo is insufficient. Check a complete sale cycle and cases altering issued documents.

Retail operation tests

1. In-person sale and issued document.
2. Online order collected or returned in store.
3. A sale with multiple tax rates where applicable.
4. Partial return and corrective document.
5. Communication failure and recovery without duplicate records.
6. ERP and accounting reconciliation.

Use suitable environments and data. A real tax operation should not become a casual test without correction and recording procedures.

How to approach the project

Start with the regime and invoicing system, then choose integration and operational flow. Define responsibilities across advisers, tax-software provider, ERP and Shopify team. App pricing is not the entire configuration, testing and maintenance cost.

For inventory, see physical and online stock; for business orders, the Shopify B2B guide. We can organise technical dependencies through Shopify integration consulting coordinated with your tax advisers.

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.