Every document
Ticket (F2), full invoice (F1), invoice replacing tickets (F3), corrective invoices (R1–R5) and albaranes.
Invoicing
Tickets, invoices, corrective invoices and albaranes with numbered series and a chained record that can't be altered. VAT comes from each product.
Ticket (F2), full invoice (F1), invoice replacing tickets (F3), corrective invoices (R1–R5) and albaranes.
Each shop has its own series, consecutive per year, with no gaps.
Each record stores a hash that includes the previous one: any change is detected.
An issued invoice is never edited: it's corrected with a corrective invoice and the history is kept.
Who did each operation and when, in a chained log.
Invoicing and event records ready for an inspection or for your accountant.
Foral territories: TicketBAI (Basque Country) and Navarre's system are not covered yet.
Veri*factu is the mode in which each record is sent to the Spanish Tax Agency (AEAT) as it is issued.
Invoicing regulation: what a full invoice, a ticket and a corrective invoice are, and what each must contain.
Invoicing software must guarantee that records are not altered, are kept and can be read.
How each invoicing record is generated, its chained hash and the event log.
No. It's corrected with a corrective invoice, linked to the original.
No, unless your company switches on Veri*factu. By default records are kept in BizQ with their chained hash.
Yes. Invoicing and event records can be exported whenever you need them.
Until the 15th of the following month. BizQ reminds you of those about to expire.
Sign up yourself, no card, and sell on the free plan for as long as you like.
Free plan forever · no card