VeriFactu for Non-Residents and Foreign Businesses in Spain (2026)

If you own a Spanish company from abroad, run a branch in Madrid, or invoice clients in Spain as a non-resident, you have probably seen the word VeriFactu and assumed it was someone else’s problem. It might not be. The rule does not care about your passport. It cares about whether you are obliged to keep invoicing records under Spanish rules — an obligation that can reach a Delaware-owned SL, a German GmbH’s Spanish branch, or a freelancer in Lisbon billing a client in Valencia.

This guide answers the precise question behind the search “verifactu non resident foreign business spain”: does it apply to you, when, and how to comply without learning Spanish bureaucracy from scratch.

Does VeriFactu apply to non-residents and foreign-owned businesses?

The short version: VeriFactu attaches to the obligation to issue invoices and keep invoicing records under Spanish regulations (Reglamento de Facturación, RD 1619/2012), regulated technically by Royal Decree 1007/2023. It is not a residence test. It is a “do you invoice under Spanish rules” test.

That distinction matters because foreigners often assume “I’m not Spanish, so Spanish anti-fraud software rules can’t touch me.” Wrong frame. The right question is: am I required to issue Spanish invoices and maintain those records under Spanish law? If yes, your invoicing software must be VeriFactu-compliant.

Three quick examples to anchor it:

• A British founder owns a Spanish SL that sells software. The SL is a Spanish taxpayer with a Spanish NIF, invoicing under Spanish rules. In scope. Nationality is irrelevant.
• A German company opens a branch (sucursal) in Barcelona with a permanent establishment, issuing Spanish invoices. In scope.
• A US consultant with no Spanish presence flies in, does one workshop, and invoices from their US entity under US rules. Not in scope for VeriFactu — though Spanish VAT on the service is a separate question worth checking.

So the headline for the worried foreigner is calmer than the panic suggests: VeriFactu is not a trap that catches every overseas business touching Spain. It catches the ones already operating as Spanish issuers — which, if you have an SL or a branch, is you.

Who’s in scope: non-resident landlords, foreign SLs, branches, and freelancers

Let’s go case by case, because the anxiety is always specific.

Foreign-owned Spanish SL or SLU. This is the most common case and the clearest. Ownership abroad changes nothing. Your SL is a Spanish corporate taxpayer, files Modelo 303 for VAT, and issues invoices under Spanish rules. VeriFactu applies in full, on the company timeline (1 January 2027).

Spanish branch (sucursal) or permanent establishment of a foreign company. A branch that issues invoices in Spain operates under the Spanish invoicing regime. In scope, company timeline. The parent being abroad does not exempt the branch.

Non-resident freelancer billing Spanish clients. Here it gets nuanced. If you are established elsewhere (an autónomo registered in Portugal, a sole trader in the UK) and invoice under your home country’s rules, VeriFactu does not reach you — your home invoicing rules apply, and reverse-charge VAT sits with your client. But if you register in Spain as a non-resident with a Spanish tax obligation and issue Spanish invoices, you fall under the autónomo/other-taxpayer timeline (1 July 2027). The test, again, is whose invoicing rules govern the invoice.

Non-resident landlord. The case that generates the most needless worry. Most residential rentals to private individuals do not require a formal invoice under Spanish rules, and VeriFactu only attaches where the invoicing obligation exists. Renting a holiday flat to tourists, or a long-term lease to a private tenant, typically produces no invoice — so no VeriFactu software obligation. Your real Spanish duty there is the Modelo 210 non-resident income tax return, which is entirely separate and unaffected by VeriFactu. The picture changes only if you rent commercial premises to a business (which does require an invoice) or otherwise issue Spanish invoices. If you also collect Spanish indirect tax — and if your property sits in the Canary Islands, that means IGIC rather than VAT — it is worth understanding how IGIC differs from mainland VAT before assuming the peninsular rules apply unchanged.

VeriFactu vs. SII: which regime your business falls under

This is the single most useful clarification for larger or internationally structured businesses, because confusing the two leads to either over-engineering or a missed obligation.

VeriFactu governs how your software records and protects invoices: hash chains, gapless numbering, QR codes, and optional real-time submission. It applies broadly to taxpayers who are not already in the SII.

SII (Suministro Inmediato de Información) is the real-time VAT ledger system that already requires near-instant submission of invoice data to AEAT. It is mandatory for large companies (turnover above 6 million EUR), VAT groups, and monthly-refund (REDEME) filers, and is available voluntarily to others.

Here is the part foreign operators miss: if you are in the SII, you are exempt from VeriFactu. You already report to the tax authority in real time, so the anti-fraud objective is met. A foreign group running a high-turnover Spanish subsidiary already on the SII does not need to retrofit VeriFactu — it needs to keep its SII reporting clean.

For everyone else — the typical foreign-owned SL, the branch under the 6M threshold, the registered non-resident freelancer — VeriFactu is the regime that applies. If you want the full picture of how VeriFactu’s technical guarantees work in practice, our VeriFactu guide for freelancers and SMEs breaks down the hash chain, QR, and the two compliance modes in detail.

The 2026-2027 compliance calendar for foreign operators

VeriFactu’s deadlines were pushed back a year by Royal Decree-Law 15/2025, which helps if you are still organizing your Spanish setup. The dates that matter:

• Now (2026): software producers must already offer VeriFactu-compliant products. As a business user, your job in 2026 is to make sure the tool you invoice with will be ready — not to scramble in mid-2027.
• 1 January 2027: mandatory for companies subject to corporate income tax. This includes your foreign-owned SL and any Spanish branch.
• 1 July 2027: mandatory for everyone else — autónomos and other taxpayers, including a non-resident registered in Spain who issues Spanish invoices.

One practical note: do not conflate this with the separate B2B e-invoicing mandate under the Crea y Crece Law, which has its own timeline and concerns the exchange of structured invoices, not the anti-fraud software guarantees. They are complementary, not the same. We map the e-invoicing side in our guide to mandatory e-invoicing in Spain and the PEPPOL e-invoicing guide for Europe.

What your invoicing software must do to be VeriFactu-compliant

Whether you are running an SL from London or a branch from Munich, the software requirements are identical to a domestic Spanish business. Your tool must:

• Generate a SHA-256 hash chain. Each invoice cryptographically references the previous one. Delete or alter an invoice and the chain breaks, leaving evidence.
• Enforce gapless sequential numbering. You cannot quietly remove invoice number 47. The sequence is server-side and atomic.
• Lock critical fields after issuance. Date, amount, and tax cannot be silently edited post-issue.
• Print the AEAT QR code on every invoice, scannable to verify the record exists.
• Support both modes: VeriFactu mode (records auto-submitted to AEAT in real time, with the “verifiable at AEAT” label on the invoice) and non-VeriFactu mode (records signed and stored locally, handed over only on request). Both are legal.

Frihet’s VeriFactu implementation does all of this — hash chain on every invoice, atomic gap-free numbering, immutability locks, the AEAT QR on the PDF, and XML generation with SOAP submission to AEAT (sandbox-verified). Certificate upload is encrypted (AES-256-GCM), and the interface works the same in English as in Spanish — which matters when the person responsible for compliance does not read Spanish bureaucratic prose for fun.

Doing it without a Spanish gestoria: an English-first workflow

The fear most foreign operators express is not really about VeriFactu the rule. It is about being forced into a Spanish-language relationship with a gestoria just to stay legal. You are not. VeriFactu is a software obligation, and software does the work. Here is a clean English-first path:

1. Confirm the obligated entity and its number. Your SL or branch already has an NIF; a registered non-resident individual uses an NIE. This is the identity VeriFactu records sign with.
2. Choose invoicing software that is VeriFactu-ready and works in your language. This removes the single biggest reason foreigners hire a gestoria — translating the compliance burden.
3. Decide your mode. Most businesses pick VeriFactu mode (auto-submit) for the cleaner audit trail. For that you upload a digital certificate so the software can sign and send. In non-VeriFactu mode you skip the live submission and keep signed records ready.
4. Issue invoices normally. The hash chain, numbering and QR happen automatically. You do not touch the cryptography.
5. Keep your VAT returns on track. VeriFactu is about invoice records; your quarterly VAT obligation is the Modelo 303, which your software can prepare from the same data. If you bill internationally in multiple currencies, the underlying invoices still need to land cleanly in your Spanish records — see how to invoice in 170+ currencies from Spain.

You can still keep a gestoria for tax filings if you want a human in the loop — many foreign owners do. But you are not forced to, and the VeriFactu part specifically is handled in software.

Common mistakes foreign businesses make (and the penalties)

The penalties are blunt, which is why the mistakes are expensive. Article 201 bis LGT sets a flat 50,000 EUR per fiscal year for using non-certified invoicing software — and crucially, no intent to defraud needs to be proven. Running the wrong tool is enough. There is a separate, smaller penalty for software producers who sell non-compliant systems, but as a business user the 50,000 EUR figure is the one to fear.

The recurring foreign-operator mistakes:

• “My parent company is abroad, so we’re exempt.” No. The Spanish SL or branch is a Spanish issuer. Scope follows the entity, not the owner.
• “I’ll use my home-country invoicing software for my Spanish SL.” If that software is not VeriFactu-compliant and the SL issues Spanish invoices, you are exposed.
• “VeriFactu and the B2B e-invoice mandate are the same deadline.” They are different regulations with different timelines. Treating them as one leads to missed obligations.
• “I’m a non-resident landlord, so I must need VeriFactu.” Usually the opposite — no invoice, no software obligation. Over-engineering wastes money and attention.
• “I’m in the SII, so I also need VeriFactu.” No. SII enrollment exempts you. Doing both is redundant.

The unifying lesson: figure out which regime actually governs you before buying anything or panicking. Most of the cost in cross-border compliance is paid by people solving a problem they do not have, or ignoring one they do.

The bottom line

VeriFactu for non-residents and foreign businesses in Spain comes down to one filter: are you obliged to issue invoices under Spanish rules? Foreign-owned SLs and Spanish branches — yes, from January 2027. Registered non-resident freelancers issuing Spanish invoices — yes, from July 2027. SII filers — exempt. Most non-resident landlords — untouched, because they issue no invoice. And in every case where it does apply, compliance is a property of your software, not a Spanish-language ordeal you have to negotiate by hand.

Pick a tool that does the hash chain, the numbering, the QR and the AEAT submission for you, in a language you actually read, and the 50,000 EUR problem stops being yours.