← Features · VeriFactu
You close the contract, the invoice is issued and the record goes to the AEAT on its own: with its chained hash, its printed QR code and its acknowledgement receipt coming back. With IGIC as a first-class citizen, not a last-minute patch.
Try it free for 14 daysThis is what happens when you close a contract. None of these steps is done by a person.
It is closed at the counter or from the online booking, with its vehicle, driver and deposit.
With tax rates per line: IGIC, IVA or IPSI depending on where you invoice.
SHA-256 hash chained to the previous invoice from that issuer, in the exact format required by the AEAT.
Sent to the AEAT through a certificate-authenticated channel, with retries and flow control.
The QR code is printed on the customer's invoice and the CSV from the tax authorities is stored.
Four everyday realities of car rental that break a generic VeriFactu implementation.
Fuel, damage, late returns, fines. With VeriFactu, an issued invoice is no longer edited: you issue a corrective invoice, which enters the same chain with its own hash and leaves a trail.
Several invoices from the same issuer within the same minute. If two are chained to the same previous record, the chain forks, and the AEAT accepts them without complaint. You have to serialize per issuer.
Rates per invoice line, zero rate and exemptions treated as the distinct things they are. Software that assumes 21% somewhere in the calculation produces absurd tax amounts in the Canary Islands.
Independent sequential numbering per office and per series, each with its own sequence. The hash chain is per issuer, not per counter.
VeriFactu is a national requirement and applies in the islands just the same. What changes is not the obligation but the breakdown. The hash, the chaining and the QR do not depend on the tax applied, so an invoice with IGIC and one with IVA for the same amount produce exactly the same chain.
What does change are the rates and the edge cases: the zero rate is not an exemption, and an exempt transaction is not the same as a non-subject one. They are reported in three different ways, and anyone who has only worked with mainland IVA has never had to tell them apart.
car-rent.es has invoiced in the Canary Islands from day one. IGIC is not a checkbox that was added later.
The part that talks to the tax authority is built on verifactu.co, the VeriFactu compliance infrastructure from the same team. The same hash engine, checked against the three official worked examples published by the AEAT.
The failures this page describes (the forked chain, the amount format, flow control at peak times) are not hypothetical: they were discovered here, invoicing real rentals.
Try it free for 14 days1 January 2027 if the company pays Corporate Income Tax (Impuesto sobre Sociedades), and 1 July 2027 for all other obligated parties, under Real Decreto-ley 15/2025, of 2 December. On 5 October 2026 the tax authority announced it will postpone this until October 2028, but that forecast has not yet been published in the BOE: for now it does not replace the 2027 dates. What does not change in any case are the technical requirements.
Yes. The regulation is national and applies in the same way. What changes is the breakdown and the rates; the hash and the QR do not depend on the tax. IGIC, IVA and IPSI are handled, with rates set per invoice line.
Not in VERI*FACTU mode. Records are not signed one by one: they are submitted to the AEAT through a channel authenticated with an electronic certificate. Record-by-record signing and the event log are requirements of NO VERI*FACTU systems.
Fuel, damage or late-return charges are documented with a corrective invoice, which generates its own chained record. With VeriFactu, an issued invoice can no longer be edited or deleted.
It depends on the mode: you can submit with your own certificate or on behalf of the client, with the authorization registered with the AEAT. Both are supported, and switching from one to the other does not break the hash chain.
The legal texts (legal notice, privacy policy and data processing agreement) are only available in Spanish, which is the binding version.