TL;DR: Verifactu does not make Spanish invoicing irreversible. The factura rectificativa mechanism, set out in Article 15 of Real Decreto 1619/2012, has governed how you fix invoice mistakes in Spain for well over a decade, and it still works the same way; Verifactu is the verification and reporting layer on top, not a replacement for that underlying commercial law. The original record is preserved, the correction is appended, and the audit trail stays tamper-evident, which is the point. Verifactu becomes mandatory on 1 January 2027 for Impuesto sobre Sociedades taxpayers, and on 1 July 2027 for autónomos and other small businesses.

You send an invoice on a Tuesday afternoon, close the laptop, and four minutes later you realise the VAT rate was wrong. Or the client’s name is missing an accent. Or the scope of work changed two days after issuing, and you now owe the customer a partial refund.

Welcome to the reality of freelancing – this kind of juggling has always been part of the ride. However, with Verifactu (Spain’s new verifiable-invoicing regime) rolling out across 2027, that small, normal, everyday moment of “oh, no” has started to feel much bigger than it should. The fear I’ve heard most often, from autónomos and small-business owners alike, is some version of: if I file an invoice through Verifactu and I’ve made a mistake, am I stuck with it forever?

The short answer is no. Spain has had a perfectly good legal mechanism for fixing invoice mistakes for well over a decade, called the factura rectificativa (rectifying invoice), and Verifactu doesn’t remove it. It just digitises the audit trail around it. The underlying invoicing law hasn’t changed, what’s new is the verification layer that sits underneath it.

That distinction is the whole point of this piece. Once you understand it, the anxiety tends to evaporate.

What Verifactu actually is (and what it isn’t)

Verifactu is the consumer-facing name for the rules in Real Decreto 1007/2023, of 5 December, which sets out the requirements that invoicing software has to meet in Spain (BOE-A-2023-24840). It was further developed by Orden HAC/1177/2024 for technical specifications, and amended by Real Decreto 254/2025 (BOE-A-2025-6600).

In plain English, the regulation says that the software you use to issue invoices has to produce records with specific safety features baked in: chained cryptographic hashes, an electronic signature on each record, a QR code on the printed or PDF invoice, and a standardised format that allows the AEAT (the Spanish tax agency) to read those records cleanly. Businesses can then choose between two operating modes: the Verifactu mode, where records are transmitted to AEAT in real time as you issue them, and the non-Verifactu mode, where the records stay in the system and are produced on request.

Verifactu is therefore a verification and reporting layer for the invoicing process. It is not a new commercial-law regime, and it doesn’t override the existing rules on what an invoice has to contain, when you have to issue one, or what to do when you need to fix one. Those rules still live in the Reglamento de Facturación (Invoicing Regulation), Real Decreto 1619/2012 (BOE-A-2012-14696), which has governed Spanish invoicing for years and which the new regime explicitly builds on top of.

The current rollout timeline (as of mid-2026)

The Verifactu dates have shifted more than once, so it pays to use the latest published version rather than anything you read in early 2025, and to keep an eye on our Spain news feed because Spain has form for this and things may change again.

The current AEAT position, after the extension introduced by Real Decreto-ley 15/2025 (AEAT informative note, December 2025), is:

  • Corporate income-tax payers (Impuesto sobre Sociedades): adapted systems required by 1 January 2027.
  • All other obligated taxpayers, which is where most autónomos and small businesses sit: adapted systems required by 1 July 2027.

Until those dates, you’re inside an extended adaptation window. You can still use your current software, you can pilot Verifactu submissions if your provider supports them, and nothing terrible happens if you’re still on the old workflow at the time of writing. The world has not, yet, ended. Software providers had a separate (earlier) compliance deadline tied to the Orden HAC/1177/2024 technical specs, which is why most of the major Spanish invoicing tools are already advertising Verifactu compatibility well in advance of the user-facing deadline.

The mechanism that defuses the anxiety: factura rectificativa

The Spanish answer to “I’ve made a mistake on an invoice” is, and has been since long before Verifactu, the factura rectificativa. The rules sit in Article 15 of RD 1619/2012, and they’re worth knowing in outline.

You must issue a rectifying invoice when:

  • The original invoice didn’t meet the legal content requirements set out in Articles 6 or 7 of the same regulation (so: missing data, wrong client identifiers, wrong dates, wrong tax breakdown).
  • The amounts of VAT charged were calculated incorrectly.
  • The taxable base of the operation is modified by one of the circumstances listed in Article 80 of the Spanish VAT Law (Ley del IVA), such as a return of goods, a discount or rebate applied after the fact, an annulled operation, an uncollectible debt, or an insolvency situation involving the customer.

The rectifying invoice has to be issued as soon as you become aware of the circumstance, and in any case within four years of the moment the tax accrued or the modifying circumstance occurred. That four-year window is generous by any standard; it’s the same limitation period that applies to most VAT matters in Spain.

Two other practical points. First, rectifying invoices must use a separate numbering series from your ordinary invoices, so most software defaults to something like R-2026-0001 or RECT-2026-0001. The point is sequentiality and traceability, not a magic prefix. Second, you can express the correction either by showing the rectified amounts directly (the base and VAT as they should have been, with the original amounts shown alongside as what was rectified) or by showing the difference between the original and the corrected figures, positive or negative. Both are acceptable; your software will almost certainly choose one method and apply it consistently.

There’s also a small but useful exception in Article 15: if a base modification is the result of returned goods or packaging and you’re going to invoice the same customer for a subsequent operation at the same tax rate, you can simply roll the rectification into that next invoice rather than issuing a standalone rectifying document. Convenient, and absolutely legal.

What goes wrong, and what you actually do about it

Concrete scenarios help. Here’s how the most common cases play out under the existing rules (which, again, Verifactu does not change).

A typo in the client’s name, or a missing accent, where the amounts and tax are right. Strictly, this is a content defect under Article 6 and triggers the rectifying-invoice rule; in practice, your software will let you issue a factura rectificativa that identifies the original and replaces the bad data. Tax effect: zero. Audit-trail effect: clean.

A wrong VAT rate, for example you charged 21% on something that should have been 10%, or you forgot to apply the reverse-charge mechanism on a B2B intra-EU service. This is a substantive error, and a rectifying invoice is the correct tool. Your tax position will move (you’ll owe less or more VAT in the corresponding modelo 303 period), and the rectification will flow through to that filing.

A scope change after issue, where work was added or removed after you sent the invoice. The cleanest pattern is to issue a rectifying invoice for the original (often coded as a nota de crédito, a credit note that reduces or reverses the original) and then issue a fresh invoice for the actual final scope. You can also handle the difference directly in a single rectifying invoice, depending on what your software supports.

A refund or returned goods. Same mechanism: a rectifying invoice that reflects the reduction. Your software will usually call this a nota de crédito or abono; the legal vehicle underneath is still the factura rectificativa.

Wrong client entirely, where you invoiced Client A for work that belongs to Client B. This is rarer but it happens. The clean path is to issue a rectifying invoice that cancels the original to Client A, and then issue a fresh original invoice to Client B. Your accountant should sign off on the timing if it crosses a VAT-filing period.

In every case, the original invoice number is preserved in your sequential series. You don’t delete it; you correct it. That’s the whole point of the audit trail, and it’s exactly what Verifactu codifies.

What Verifactu adds (and why it’s not as scary as it sounds)

Here’s where the irreversibility myth comes from, and here’s why it doesn’t actually bite.

Under Verifactu, when you issue an invoice your software generates a registro de alta (a high registration record) and, in Verifactu mode, transmits it to AEAT. That record is cryptographically chained to the previous one; you can’t edit it later without the chain breaking. So far, so scary.

The crucial bit is what happens next when you need to correct something. Per AEAT’s own published guidance, the original record is not removed. Instead, a linked registro de anulación (annulment record) or a factura rectificativa with a code (R1 for legal errors and most Article 80 cases, R2 for concurso / insolvency situations, R3 for uncollectible debts, R4 for other modifications, R5 for simplified invoices) is added to the chain. Both the original and the correction stay visible. The AEAT FAQ on procedimientos de facturación and on registros de facturación: anulación states this directly: erroneous records “must be maintained” so that the chain integrity is preserved, with the cancellation or rectification recorded alongside (AEAT FAQ – procedimientos de facturación; AEAT FAQ – anulación).

Read that again, because it’s the line that undoes the anxiety: the original is preserved, the correction is appended, the auditor sees the full history. That is, structurally, exactly how a well-run paper accounting system has always worked; Verifactu just makes the audit trail tamper-evident.

Tamper-evident is the right word here, and it’s worth pausing on. The point isn’t that the past is set in stone; it’s that any change to the past leaves a visible mark, a digital fingerprint on the process. If you’ve heard “blockchain” before, this is the bit of the concept that survives the hype: each record is mathematically linked to the one before it, so silently changing a past record breaks the chain that the AEAT can read. No tokens, no mining, no speculation, just the audit-trail half of the idea.

The “irrevocable” word that has been frightening people in Facebook groups and forums refers to the submission record, not the underlying transaction. You can’t delete a record you’ve already sent to AEAT. You can absolutely issue a correction, and the system is designed to make exactly that correction obvious to anyone reading the record.

My own autónoma reality check

I’ve been issuing invoices in Spain under the autónomo / autónoma (self-employed) regime for a while, and Xolo, my accountant, audits every single invoice description before it goes out. The first time they sent one back to me for editing (the month and reference period weren’t right; my fault, not theirs) I had to issue a corrected version. The world did not end, the tax position resolved cleanly, the audit trail showed the original and the correction, my customer received both.

So take it from me – issuing a factura rectificativa is, in lived experience, an unremarkable Tuesday-afternoon task. It happens time to time, and without drama, to most working autónomos in Spain. Verifactu doesn’t change that beat; it just makes the trail of it more legible to AEAT.

Practical preparation: pick your software, learn its correction flow

The piece of advice I’d give anyone in Spain right now, regardless of timeline shifts, is to choose a Verifactu-compliant invoicing tool ahead of your personal deadline and learn its rectification workflow before you need it. The main tools serving Spanish autónomos and small businesses have publicly published their Verifactu compatibility:

Xolo’s invoicing built into their accountancy product, which is one reason they are our choice [Insert a referral link to Xolo Spain ] Quipu, Holded, and the open-source FacturaScripts (Verifactu-compatible via its plugin ecosystem) are all on the list. There are plenty of others too. AEAT also offers a free Verifactu app for very small operators who don’t want to pay for software at all, though most autónomos with real volume will want something more polished.

Whichever you choose, you could even do a small dry run. Issue an invoice; cancel it via the software’s rectification flow; check what the audit trail looks like; confirm the QR code resolves; check that the rectifying invoice gets its own series and links cleanly back to the original. That fifteen-minute exercise is worth more than reading another five blog posts about Verifactu. Including this one.

Defusing the irreversibility myth

You are not stuck with your mistakes. Spanish invoicing law has provided for the factura rectificativa for over a decade, that mechanism is alive and well, and Verifactu is built on top of it rather than replacing it. The original record is preserved; the correction is appended; the auditor sees both; the tax position resolves to where it should have been. The four-year window is generous. The numbering rules are mechanical. Your software will do most of the work.

The shift Verifactu asks of you is much smaller than the rumours suggest. It’s a shift from “if I’m careful enough, I never need to correct” (which was never really true) to “when I correct, I do it through the proper channel and the trail is visible”. That’s a healthier mental model anyway. Mistakes happen; the law has always assumed they would; the system has always had a way to absorb them.

Click send. Get paid. Move on!

FAQ

Can I correct a mistake on a Verifactu invoice after submitting it? Yes. The submitted record itself can’t be deleted, because Verifactu chains records cryptographically for audit purposes, but you correct the underlying transaction by issuing a factura rectificativa (or an annulment record) that is linked to the original. Both the original and the correction stay visible in the chain, which is how AEAT expects the audit trail to read.

What is a factura rectificativa and when do I issue one? A factura rectificativa is the rectifying invoice that Spanish law has used for years to fix errors on a previously issued invoice. Article 15 of Real Decreto 1619/2012 requires you to issue one when the original was missing legally required content, when VAT was calculated wrongly, or when the taxable base changes under Article 80 of the Ley del IVA (returns, post-issue discounts, annulments, uncollectible debts, customer insolvency). You have up to four years from the moment the tax accrued or the modifying circumstance arose.

When does Verifactu actually become mandatory for me? The deadlines, after the extension introduced by Real Decreto-ley 15/2025, are 1 January 2027 for Impuesto sobre Sociedades taxpayers and 1 July 2027 for everyone else, which is where most autónomos and small businesses sit. Until your applicable date, you remain inside the adaptation window and can keep using your current software.

Does Verifactu apply to me if I’m an autónoma in Spain? In most cases, yes, and your deadline is 1 July 2027. The obligation attaches to taxpayers whose invoicing falls within the Spanish regime, so the practical step is to confirm your current software is Verifactu-compatible and learn its rectification workflow well before that date.

What happens if I issue an invoice with the wrong amount and the client has already paid? You issue a factura rectificativa showing either the corrected figures directly or the difference between the original and corrected amounts, and that rectification flows through to your next modelo 303 VAT filing. If you’ve over-collected, you refund the client (often via a nota de crédito); if you’ve under-collected, the rectifying invoice triggers an additional charge. Payment having already happened does not block the correction; it just shapes whether money flows back or forward.

Will the AEAT punish me for issuing a rectifying invoice? No. The AEAT FAQ on procedimientos de facturación and on registros de facturación: anulación sets out exactly how to record corrections (R1 for most legal errors and Article 80 cases, R2 for concurso / insolvency, R3 for uncollectible debts, R4 for other modifications, R5 for simplified invoices), which means the system is built to expect corrections, not to penalise them. Issuing rectifying invoices through the proper channel is the compliant behaviour; not correcting a known error is the risk.

Do I need new accounting software to be Verifactu-compliant? You need software that meets the technical requirements set out in Real Decreto 1007/2023 and Orden HAC/1177/2024. The mainstream tools serving Spanish autónomos and small businesses (Xolo’s invoicing, Quipu, Holded, FacturaScripts) have published their Verifactu compatibility, and AEAT offers a free Verifactu app for very small operators. Pick one ahead of your deadline and run a small dry rectification through it before you need to.