Record in the same operation
The record is generated when the document is issued. If it cannot be generated, the document is not issued.
- Home
- Product
- VERI*FACTU invoicing
VERI*FACTU invoicing built into the POS
Taking payment and invoicing are one and the same operation. Each document generates its invoicing record with a chained hash and a QR code, and StockRest submits it to the AEAT (Spanish Tax Agency) with the restaurant's certificate.
Your restaurantTable 4 · 13:58
- Taxable base
- €29.82
- VAT 10%
- €2.98
- Total
- €32.80
Chained record · Tax QR code
Illustrative example. This is not an issued invoice.
What changes with VERI*FACTU
Invoicing software must generate a record for each invoice, chained to the previous one, and include a QR code on the document. Under the VERI*FACTU option, those records are sent to the Spanish Tax Agency.
StockRest was designed for this option from the start: the record is not a later add-on, it is part of issuing the document.
Business-to-business e-invoicing has its own regulations and is not covered by using VERI*FACTU. Before starting, each restaurant's specific tax situation is reviewed.
Your restaurant
Tax ID (NIF) and venue address
Simplified invoice2026-0148
Table 413:58
1 Tomato salad9.90
1 Tuna tataki18.50
2 Mineral water4.40
Taxable base29.82
VAT 10%2.98
Total€32.80
VERI*FACTUInvoice tax QR code
What StockRest does with each document
The issued document and the status of its submission follow separate paths, and both remain visible.
Chained hash
Each record includes the hash of the previous one, so the chain cannot be altered without it showing.
Official format
The content of the record is checked against the schemas published by the AEAT before it is sent.
Tax QR code
The receipt and the invoice carry the QR code so that the customer can check them on the AEAT's online portal.
Restaurant's certificate
The connection to the AEAT is authenticated with the restaurant's certificate, which is stored encrypted.
Orderly submissions with no duplicates
Records are sent in batches with the waiting times set by the AEAT. If no response arrives, the status is queried before resending.
Every document, with its type
Issued documents are never overwritten. A correction is made with a corrective invoice or with a full invoice that replaces the receipt, and both remain linked to the original.
- Visible statuses: pending submission, accepted, accepted with errors or rejected.
- A rejected record is corrected following the AEAT's procedure.
- Numbering by series, protected against retries.
| Document | Code |
|---|---|
| Simplified invoice (receipt) | F2 |
| Full invoice | F1 |
| Full invoice replacing a receipt | F3 |
| Corrective invoice for a simplified invoice | R5 |
| Corrective invoice for all other invoices | R1 to R4 |
Testing first, then live
Each restaurant's submission has three modes. Going live happens once everything has been checked.
Disabled
No record is generated or sent. This is the starting point while the tax details are being set up.
AEAT testing
Records are sent to the AEAT's test environment to check the certificate and the configuration.
Live
Records are submitted to the AEAT with full tax validity. Training mode never sends anything.
Deadlines and official sources
According to the timetable published by the AEAT, adaptation becomes mandatory in January 2027 for Corporate Income Tax payers and in July 2027 for everyone else who is required to comply.
Always check the current information on the AEAT's online portal.
Request a StockRest walkthrough
Tell us how your restaurant works and we will show you how the dining room, kitchen, purchasing and till fit together.