New Light partners with Greenstep to bring agentic finance to the NordicsLight partners with Greenstep Read the announcement

VeriFactu e-invoicing in Spain

Guide
Admin guides
Reading
6 min read
On this page
  1. 01On this page
  2. 02At a glance
  3. 03What is VeriFactu?
  4. 04The two modes
  5. 05Getting registered
  6. 06What you need to fill in
  7. 07Document rules
  8. 08Credit notes
  9. 09Limits
  10. 10FAQ and troubleshooting
  11. 11Related articles

What is this page about: What VeriFactu is, how to authorize Light to issue invoices on your behalf, and what changes on your Spanish invoices once you are registered. This article covers what is specific to VeriFactu. The wizard, registration statuses and EDIFACT codes are the same everywhere and are explained in E-invoicing in Light.

On this page

  • At a glance
  • What is VeriFactu?
  • The two modes
  • Getting registered
  • What you need to fill in
  • Document rules
  • Credit notes
  • Limits
  • FAQ and troubleshooting
  • Related articles

At a glance

Item Detail
Country Spain
Kind of network Reporting. The record goes to the tax authority, not to your customer
Set up yourself Yes, by signing an authorization
Sending / receiving Submitting to AEAT only
Address issued None. VeriFactu has no e-invoice address or EAS code

What is VeriFactu?

VeriFactu is the Spanish anti-fraud invoicing regime run by the AEAT. Its purpose is to make invoices tamper-evident: every invoice a company issues has to become a record that is cryptographically chained to the one before it and carries a QR code, so that altering an invoice after the fact is detectable.

VeriFactu is a reporting regime. Your customer receives their invoice as before, as the PDF Light emails them. The record, with its hash chain and QR code, goes to the tax authority.

Because nothing is delivered over a network, your entity never gets an e-invoice address or EAS code. To send invoices to customers in other EU countries, use Peppol. A Spanish entity can hold both.

The two modes

Spanish law lets a company operate under one of two modes. Both require the hash chain, the QR code and a compliant PDF. The difference is what happens with the records.

Requirement VeriFactu No VeriFactu
Records sent to AEAT Yes, in near real time No, only if AEAT asks
Additional requirement None Each record must be digitally signed and stored locally
QR code and hash chain Required Required
Registration Required Required

The invoice itself is identical either way. Which mode applies to your company is a decision for your Spanish tax advisor, not something you configure per invoice.

Getting registered

Registering for VeriFactu means formally authorizing Light to issue invoices on your behalf. Spanish law requires this before any invoice can be submitted, and it takes the form of a signed representation agreement (apoderamiento).

This is a different thing from Peppol's document upload. You are not proving you own an address, you are granting a legal power.

  1. Make sure the entity's country is Spain and its VAT number (NIF) is filled in
  2. Open the entity, and in the E-invoicing section click + Add
  3. Choose VeriFactu. The wizard also shows a Registration type. Either option registers the entity for sending, since VeriFactu submits invoices to AEAT
  4. Click Open registration page. It opens the secure signing page of Invopop, our e-invoicing provider
  5. On that page, your legal representative signs the agreement and completes identity verification as the provider's page requires
  6. You can issue invoices as soon as the provider confirms the signature. The registration status moves through Created, Pending verification, Processing, then Active

Light sends Invopop the company name, NIF, business registration number and address. On Invopop's page, the legal representative enters their full name, government ID type and number, and address. A sole trader (autónomo) enters their own details.

If the documents you upload are unusable, an illegible ID for example, the registration shows an Error status instead of Active. Make sure the ID you upload is clear. An invoice sent before registration is complete is rejected with the message "Company entity has not finished VERI*FACTU onboarding."

Light never sees or stores the signing documents, because they go directly to Invopop's page.

What you need to fill in

On your entity

Field Notes
Country, set to Spain
VAT number (NIF)
Address Required for the authorization
Business registration number Checked when you send an invoice
Registration type Shown in the wizard. Either option registers for sending

Plus, on the signing page: your legal representative's name, ID type and number, and address.

On each customer

Field Notes
VAT number Required
Business registration number Required
Billing address Required

There is no e-invoice network, EAS code or e-invoice address to set on a customer for VeriFactu, because nothing is being routed to them.

Document rules

Document numbers. No format requirement. Note, though, that the hash chain means invoices are linked in issue order, so a compliant sequence matters for the same reason it always has.

Tax codes. Every tax code used needs an EDIFACT code, as on every network. What is different here is that you do not need to configure Spanish tax classification codes yourself. AEAT requires several coded fields per line, covering the operation class, the exemption reason and the applicable regime, and all of them are derived automatically from the EDIFACT code you have already set.

EDIFACT code Becomes
S, standard rate Subject to VAT, ordinary regime
Z, zero rated Subject to VAT
AE, reverse charge Subject, reverse charge
G, export Exempt, export regime
K, intra-community supply Exempt, intra-community
E, exempt Exempt
O, outside scope Not subject to VAT

The QR code and hash chain are added for you to the record Invopop sends to AEAT, with nothing for you to configure.

Lines without a tax code. A line with no tax code is sent to AEAT as exempt, so set a tax code on every line.

Credit notes

Credit notes are submitted as rectified invoices under the general correction reason. If you link the credit note to the original invoice in Light, that reference is carried through to AEAT.

Unlike Greek myDATA, there is no need to wait for the original invoice to be accepted first.

Limits

  • Reporting only. VeriFactu does not deliver to your customer and does not receive supplier invoices.
  • Spanish entities only. It will not appear in the wizard for an entity in another country.
  • Signing happens off-platform. The agreement is signed on Invopop's page, so we cannot complete it for you or resend the documents on your behalf.

FAQ and troubleshooting

Does my customer receive anything over VeriFactu?

Your customer gets their invoice as before, as a PDF from Light. VeriFactu is between you and AEAT.


Why does my entity not have an e-invoice address after registering?

Because there is nothing to address. VeriFactu is a reporting regime, not a delivery network.


Can I start invoicing straight after signing?

Yes, once the registration reaches Active. The status moves through Created, Pending verification, Processing, then Active automatically after signing. If a document can't be read, the registration shows Error instead.


My invoices are suddenly being rejected by AEAT.

Check the registration status. If it shows Error, contact support. If registration hasn't finished, AEAT rejects the invoice and Light shows "Company entity has not finished VERI*FACTU onboarding."


Which mode am I in, VeriFactu or No VeriFactu?

That is determined by how your company is set up with AEAT. Ask your Spanish tax advisor, because the invoice Light produces is the same either way.


Do I need to set Spanish tax codes on my tax codes?

No. Set the EDIFACT code and the Spanish classifications are derived from it.


Can a Spanish entity also use Peppol?

Yes, and it often should. VeriFactu handles the Spanish reporting obligation, and Peppol handles delivering invoices to customers who need them electronically.

Was this article helpful?