Skip to content
Apolaris AI Docs

E-invoicing (VERI*FACTU Spain)

pro

Spanish organizations can invoice every paid sale into Hacienda automatically — VERI*FACTU records with the AEAT QR on every ticket, cancellations and full invoices, a fiscal register with CSV export, and a prepared path for Mexico's CFDI.

Businesses selling in Spain are required to ring up sales through certified invoicing software (RD 1007/2023 — in force for companies since January 2026 and for autónomos since July 2026). With the E-invoicing module active, Apolaris does this for you: every paid sale automatically becomes a fiscal invoicing record and streams to the AEAT, your tickets carry the official QR and the VERI*FACTU legend, and a register keeps the whole chain auditable.

Who can do this: the module is enabled per organization by the platform (ask support to switch it on), and inside your organization it is gated by the Manage e-invoicing privilege. Once enabled, find it under Sales & Finance → E-invoicing in the sidebar. Nothing changes for your sales until you activate it yourself.

How it works once active

  • When a sale is paid, Apolaris issues a registro de facturación de alta for it — by default a simplified invoice (the ordinary shop ticket), numbered gaplessly per location.
  • Each record is hash-chained to the previous one exactly as the AEAT specification requires, making the sequence tamper-evident.
  • The record streams to the AEAT automatically in the background, respecting the AEAT's pacing rules. You never submit anything by hand; the dashboard shows what's pending, accepted, or rejected.
  • Your ticket PDF, the emailed receipt, the customer portal receipt and the sale page all gain the fiscal block: VAT breakdown, the AEAT verification QR a customer can scan, and the VERI*FACTU legend.

Fiscal records are immutable by design. Once a sale has an active record, editing or deleting that sale is refused — the lawful path is a cancellation (an anulación record that joins the same chain), after which you can ring the corrected sale. The sale pages point you to it.

Setting it up

Open Sales & Finance → E-invoicing → Settings:

  1. Legal name and NIF — your fiscal identity (DNI, NIE and CIF formats are validated as you type).
  2. AEAT environment — production, or the AEAT test environment while you trial it.
  3. VAT rate — 21 %, 10 %, 4 %, or an exemption reason. Ticket totals are treated as VAT-inclusive: the base and quota are derived from the price your customer already sees.
  4. Certificate — upload your AEAT certificate (.p12/.pfx) with its passphrase. Apolaris shows the parsed identity and expiry; the file is stored encrypted in private storage and used only to talk to the AEAT.
  5. Activate. Activation requires the settings, the certificate and a euro-currency organization; it warns if your organization's country isn't Spain.

From activation onward, new paid sales are invoiced automatically. Nothing is created retroactively for older sales.

The register

Sales & Finance → E-invoicing gives you:

  • Overview — this month's base and VAT totals, pending and rejected counts, the last submission, and any configuration warnings.
  • Records list — every record with its status, filterable, with per-row actions: view the QR, download the XML, cancel, or upgrade a ticket to a full invoice.
  • CSV export — the libro registro for your accountant.

Full invoices (F1)

A simplified ticket can be upgraded to a complete invoice with the customer's NIF — for the customer who asks for "una factura con mis datos". The upgrade issues a substitute record referencing the original, all inside the same chain.

Mexico (CFDI) — prepared

The same section carries a Mexico CFDI 4.0 configuration block: RFC (validated), régimen fiscal, place of issue, IVA rate, global-invoice periodicity, and PAC credentials. It is presented honestly as prepared — stamping CFDIs legally requires a contract with a PAC, so nothing claims to send anything until that exists. Capture your data now; stamping arrives when a PAC account is connected.

Good to know

  • Rejected records stay visible with the AEAT's error text; fix the cause, cancel and re-issue.
  • One VAT rate applies per ticket; per-line mixed rates aren't modeled. Basque foral systems (TicketBAI) and Navarra are out of scope.
  • If the platform-side producer registration is still pending, records generate and chain locally and the dashboard says so — nothing is lost; submission starts when the platform side is complete.
Loyalty program Inventory