A busy office with two people working through numbers
E-Invoicing · Spain

Spain's Verifactu and the Software You Already Bought

Most mandates regulate what you send. Spain has also regulated the system that produces it, which puts your software vendor inside your compliance perimeter.

Key Takeaways
  • Spain has approached the problem from two directions: requirements on billing software itself, and a business to business e-invoicing mandate under separate legislation.
  • Software level rules focus on record integrity: entries that cannot be altered silently, sequential records and a verifiable trail.
  • That makes your billing system a compliance object, so vendor readiness becomes a question your finance team has to ask directly.
  • Timing has moved more than once and depends on implementing regulations, so plans need reconfirming rather than assuming.
  • ChatFin never writes silently and never bypasses system validations, which is the property these rules are built around.

Most e-invoicing regimes regulate the document. Spain has also regulated the machine that produces it, which is a meaningfully different idea.

The billing software requirements focus on integrity of the record: invoices recorded in a way that cannot be quietly altered or deleted, sequential and traceable, with a verifiable trail behind them. A separate business to business e-invoicing mandate has been progressing under its own legislation and its own timetable.

For a finance team the consequence is direct. Your compliance position now depends partly on software you bought years ago from a vendor you may not have spoken to recently.

Spain
Verifactu
Billing Systems
Compliance
Audit Trail
ChatFin
01

Regulating the system, not the output

Document level rules ask whether what you sent was correct. System level rules ask whether what you kept can be trusted.

The underlying concern is deletion and alteration: records changed after the fact, sequences with gaps, and invoices that quietly disappear. The response is to require billing systems to produce records that resist that, with integrity that can be demonstrated.

It is closer in spirit to audit trail requirements than to invoice formatting, which is why finance rather than tax usually ends up owning it.

This approach is spreading. Several jurisdictions have concluded that regulating the document alone leaves too much room for records to be adjusted afterwards, and that the more effective control point is the system that creates them. Anyone selecting billing software now should assume the question will be asked in more places over time.

02

What this means in practice

Four consequences, and the first one is the one that surprises teams.

None of these are resolved by choosing an e-invoicing provider, and none of them appear in a project plan written around document exchange:

Your vendor is in scope. Whether your billing system meets the requirements is a question for whoever supplies it, and the answer needs to be in writing.
Workarounds become exposures. Spreadsheets and side systems that produce invoices outside the main platform are exactly what these rules target.
Corrections need discipline. Amending by deleting and re entering is the behaviour the rules exist to prevent, so processes built on it have to change.
Integrations count. Anything writing invoice records into the system through an interface is part of the same question.
03

Two compliance questions, often conflated

Spain is running two related but separate tracks, and teams frequently answer one while believing they have answered both.

Keep them apart in your planning.

Track one

Billing system integrity

Requirements on how invoice records are created, retained and made verifiable. Answered by your billing software vendor and by how your team uses the system.

Track two

Business to business e-invoicing

A separate mandate on structured invoice exchange, progressing under its own legislation with its own phasing tied to implementing regulations.

Financial reports, a calculator and a laptop on a desk
The rules attach to the machine, which puts your vendor inside the compliance perimeter.
04

Questions for your billing vendor

This is a short conversation with a written answer at the end of it. Three questions cover the ground.

If your vendor cannot answer in writing, that is the finding.

QuestionWhat you are testingWhat a weak answer looks like
Does the current version meet the requirementsWhether compliance requires an upgrade, and on what timelineA general statement about being compliant with no version reference or date
What happens to our historical recordsWhether existing data is in scope and what conversion is involvedSilence, or an assumption that only new records matter
How are integrations treatedWhether records written through interfaces satisfy the same requirementsAn answer that only covers records created through the user interface

Ask for the answers in writing and keep them. They are part of your compliance file.

05

The side systems problem

Every finance function has them. A spreadsheet that produces a particular type of invoice, a small application built years ago for one business unit, a manual process for an unusual customer.

Under system level rules these become the exposure rather than an inefficiency. The remediation is usually to bring them into the main platform, which is work most teams have been deferring for other reasons and now have a deadline for.

System level rules turn every workaround into an exposure. The invoice produced outside the platform is the one to look at first.
"

Document rules ask whether what you sent was correct. System rules ask whether what you kept can be trusted.

ChatFin
06

Getting to a defensible position

Four steps, starting with the one that takes the longest to answer honestly.

Inventory every system that creates an invoice

Including spreadsheets and departmental tools. The list is almost always longer than the finance leadership expects, and the exercise itself is valuable.

Get vendor confirmation in writing

Version, timeline and treatment of historical records and integrations. Verbal assurance from an account manager is not a compliance artefact.

Eliminate delete and re enter corrections

Move to proper corrective documents. This is a process and training change more than a system one, and it takes time to stick.

Confirm the current timetable before planning

Dates here depend on implementing regulations and have moved. Plan against the current published position and reconfirm it with your advisers.

An accountant working through documents at a desk
Every finance function has side systems. Under integrity rules they stop being an inefficiency.
07

Why the ChatFin write model fits these rules

ChatFin never writes silently and never bypasses the validations a system enforces. Every action is prepared as a transaction inside the ERP using its own supported interfaces, then approved by a named person.

That matters under integrity focused rules because it means an agent cannot create a record outside the system's controls, cannot alter one without leaving the system's own audit trail, and cannot produce an invoice through a side channel that sits outside the platform.

Across NetSuite, SAP Business One, JD Edwards, Acumatica, Dynamics 365 and Sage Intacct, the ERP remains the system of record and the enforcement point. ChatFin adds a further layer on top by logging the instruction, the evidence retrieved and the payload prepared.

No side channel. Records are created through the ERP's supported interfaces, which means system validations and numbering apply.
No silent alteration. Changes follow the ERP's own change and audit mechanisms rather than bypassing them.
Extra evidence layer. Instruction, evidence and prepared payload logged alongside the system's native trail.
Before you budget for it

AI Cost Estimator for the CFO Office

Four inputs, a first year cost range, a timeline, and three delivery models compared. No login required.

Frequently Asked Questions

Is this an e-invoicing mandate or a software rule?

Spain has both. One set of requirements addresses the integrity of billing software and its records. A separate business to business e-invoicing mandate is progressing under its own legislation. They are related, they have different timetables, and answering one does not answer the other.

Does this apply to us if we invoice from outside Spain?

It depends on your Spanish establishment and registration position and on the transactions concerned. This is a question for your advisers, and it is worth asking specifically rather than assuming a group system is out of scope.

What is the most common gap teams find?

Invoices produced outside the main billing system. Spreadsheets and small departmental tools that were tolerated as inefficiencies become the primary exposure under integrity rules, and they take time to eliminate.

How does ChatFin sit against these requirements?

It works through the ERP's supported interfaces rather than around them, so system validations, numbering and audit trails apply to everything it prepares, and every action is approved by a named person before it takes effect.

General information only. It is not legal, accounting or tax advice, and rules change. Check your own position with your advisers before acting on it.

Inventory first, vendor second

Find every system that can produce an invoice.

When rules attach to the billing system rather than the document, your compliance position depends on software decisions made years ago and on workarounds nobody has counted.

ChatFin operates through the ERP's own interfaces with human approval on every action, so the system of record stays the enforcement point.

Book a Demo
See the platform
Take it to your own ledger

Keep the ERP as the enforcement point.

Bring one billing or payables process you would like to automate. We will show how ChatFin prepares work through your ERP's own interfaces and what the evidence record contains.

✓Runs on the ERP you already have, on the version you already run
✓Every posting prepared as a draft that a named person approves
✓Prompt, evidence and prepared payload logged for the audit file
Schedule a Demo
Confidential & private
Photos by Mikhail Nilov, Pavel Danilyuk and Tima Miroshnichenko, free to use under the Pexels License (commercial use, no attribution required). Diagrams and product imagery © ChatFin.