ERP and accounting software for Spain - VeriFactu billing records and the Crea y Crece e-invoicing timetable

Two Spanish reforms with two different clocks

If you take one thing from this page, take this: Spain is running two reforms at once, and they are not the same reform. VeriFactu sets rules on billing software, requiring certified and tamper-evident invoicing records. The Crea y Crece mandate, under Law 18/2022, will require electronic invoicing between businesses. Vendors and articles routinely collapse the two into a single sentence about Spain requiring e-invoicing, and that sentence is wrong in both directions at once.

It is wrong in the first direction because it overstates the B2B mandate. That mandate has been approved, not commenced. It is wrong in the second direction because it understates VeriFactu, which is already binding on part of the taxpayer population and is the obligation most likely to affect what software a Spanish company can legitimately keep using this year.

The practical consequence is a sequencing decision. The billing-record rules bite on the system you already issue invoices from. The exchange rules will bite later on the way those invoices reach your customers. A project that starts with the second and postpones the first is starting at the wrong end.

Nothing on this page is a substitute for confirming your own position with the Agencia Estatal de Administracion Tributaria. Which date applies to you, and whether you sit inside the SII reporting regime, are determinations about your business rather than facts about Spain.

• VeriFactu: rules on billing software and the records it produces, phasing in now.
• Crea y Crece: B2B electronic invoicing under Law 18/2022, approved but not yet in force.
• Separate legal bases, separate scopes, separate commencement dates.
• A connector that sends invoices does not satisfy a rule about how records are created.
• Confirm your own scope and dates with AEAT.

VeriFactu: what a rule about software actually demands

A billing-software rule is a different kind of obligation from a filing deadline. It does not ask you to submit something by a date. It asks that the system you use, every time it issues an invoice, produces a record that is certified and tamper-evident. That is a statement about the internals of the application, and it is not something a business can retrofit with a spreadsheet or a manual control.

The awkward cases are the ones that were never treated as billing systems. Point of sale terminals issue invoices. Field service apps issue invoices. Spreadsheets with a mail merge issue invoices. A company that has genuinely centralised issuance in one system has a small problem. A company with five places an invoice can come from has five problems, and usually does not know it until someone counts.

This is where an integrated system earns its place for reasons that have nothing to do with marketing. If sales, point of sale, projects and service all post through the same billing layer, there is one record-creation path to reason about. Skyline Nexus is built that way: the document that leaves the sales screen and the document that leaves the counter are the same object in the same ledger, with the same numbering and the same audit trail behind them.

What no vendor should tell you is that their software makes you compliant. Compliance depends on how the software is configured, how it is used, which regime you fall under and what the current rules say on the day. Ask what the system does. Decide compliance with your adviser and AEAT.

• Count every place in your business that can issue an invoice, including point of sale and field apps.
• Ask what happens to a billing record after it is created, and whether it can be altered.
• Prefer one issuance path over several, because there is then one behaviour to verify.
• Keep invoice numbering unbroken and attributable across every channel.
• Treat cancellations and corrections as recorded events, not as edits to the original.
• Confirm with AEAT which requirements apply to your regime before changing systems.

Reading the VeriFactu dates without guessing

The dates are specific and the specificity matters. VeriFactu became mandatory on 1 January 2026 for companies not under the SII reporting regime. Revised deadlines then set 1 January 2027 for corporate income tax payers and 1 July 2027 for individual business owners and professionals taxed under IRPF.

Notice what that structure implies. Your date is a function of how you are taxed and whether you already report under SII, not of your industry or your size in headcount. Two businesses on the same street doing the same work can sit on different dates because one is a company and one is a professional under IRPF.

That is also why generic advice fails here. A page that tells every Spanish reader the same date is telling most of them something inaccurate. The only reliable move is to establish your own regime first and read the calendar against it, with AEAT or your adviser confirming the answer.

• 1 January 2026: companies not under the SII reporting regime.
• 1 January 2027: corporate income tax payers, under the revised deadlines.
• 1 July 2027: individual business owners and professionals under IRPF.
• Your date depends on your tax regime, not on your sector.
• Establish whether you are inside SII before reading any of the above as yours.

Crea y Crece: approved in March 2026, clock not yet started

The Royal Decree activating the Crea y Crece B2B e-invoicing mandate was approved by the Council of Ministers in March 2026. It is tempting to read that as the mandate arriving, and a good deal of commentary did. The commencement rule is different: the clock runs from publication of the final regulations, and the phase-in is defined as an interval from that publication rather than as a fixed date.

The intervals are 12 months after publication for businesses over EUR 8 million turnover, and 24 months after publication for everyone else. Until the final regulations are published, nobody can honestly tell you the day the obligation starts, because the day is defined by an event that has not happened.

That is genuinely useful information for a finance director, because it converts an unbounded anxiety into a bounded one. You do not have a date, but you do know the minimum warning you will get. A business over the turnover threshold has at least a year from publication. A smaller business has at least two. Neither is long enough to redesign a billing estate from scratch, and both are long enough to do it deliberately.

Treat any vendor claim that Spanish B2B e-invoicing is already compulsory as a reason to check their other claims. The mandate is approved and pending, and saying so accurately costs nothing.

• Approved by the Council of Ministers in March 2026.
• Commencement runs from publication of the final regulations, not from approval.
• Over EUR 8 million turnover: 12 months after publication.
• All other businesses: 24 months after publication.
• No fixed calendar date exists until publication occurs.
• Confirm the position with AEAT rather than with a vendor timeline.

Where Spain sits in the European picture

Europe is not converging on one model, and it helps to see the shapes side by side. Poland operates a clearance model: the invoice goes to the tax authority through KSeF and is approved before it reaches the buyer, and the authority assigns the invoice its identifier. Belgium operates a network model: structured invoices are exchanged over Peppol between trading partners, with the tax authority not standing in the middle of each document.

Spain, today, is at a third point. There is no live domestic B2B exchange obligation, and there is an approved one waiting on publication. What Spain has moved on first is the integrity of the billing record itself, through VeriFactu. That is a records-first approach rather than a transmission-first one.

And the Netherlands is a fourth point, with no domestic B2B mandate in force at all and a design framework aimed at 2030. Four neighbouring EU member states, four different answers. Any group operating across them should assume divergence as the default and design for it, rather than waiting for a single European shape to emerge and standardising on it early.

• Poland: clearance through KSeF, authority in the middle of every invoice.
• Belgium: structured exchange over the Peppol network, live since January 2026.
• Spain: billing-record rules live, B2B exchange mandate approved and pending.
• Netherlands: no domestic B2B mandate in force, framework targeting 2030.
• A multi-country group needs per-country behaviour, not one European setting.

Spanish VAT as data on the invoice

Spain applies a standard VAT rate of 21 percent, with reduced rates for defined categories, and transacts in euro. The rate is the least interesting part. What decides whether a return can be produced without a reconciliation exercise is whether the VAT treatment was captured as structured data on each line at the moment the invoice was issued.

Cross-border trade inside the European Union makes that concrete. Supplies to VAT-registered businesses in other member states, reverse charge on many business-to-business services, and the customer VAT identification number all have to sit on the document as fields, with the number validated rather than typed hopefully into a notes box. A total that happens to be correct but cannot be explained line by line is a problem waiting for an inspection.

Rounding is the other quiet failure. VAT computed on a document total and VAT computed line by line diverge, and the difference compounds across thousands of invoices. Decide the basis once, apply it consistently, and be able to show which basis was used.

• Standard rate 21 percent; reduced rates apply to defined categories.
• Store the VAT treatment per line, not just a rate on the total.
• Capture and validate customer VAT identification numbers for intra-EU supplies.
• Handle reverse charge as a treatment, with the correct wording on the document.
• Fix the rounding basis and keep it consistent across every channel.
• Every VAT return figure should trace back to the individual invoices behind it.

Which accounting framework you report under

This is a real structural difference between Europe and the Gulf, and it deserves a plain statement. Listed companies in the European Union report their consolidated accounts under IFRS as adopted by the EU. Individual entities within a group commonly prepare their statutory accounts under the local generally accepted accounting principles of the member state they are registered in.

For a Spanish subsidiary of a foreign parent, that means one set of underlying transactions has to serve two presentations: the local statutory accounts and the group reporting package. The differences typically show up in recognition timing, in the treatment of leases and provisions, and in disclosure rather than in the invoice itself.

What a system can usefully do about it is limited but valuable. It can keep the transaction detail rich enough that either presentation can be derived from it, rather than forcing a choice at posting time. It can carry entity, branch and cost centre as dimensions on the posting. It can keep the subledgers reconciled to their control accounts so that both closes start from the same numbers. The framework decision itself belongs to your auditor.

• EU listed companies report consolidated accounts under IFRS as adopted by the EU.
• Individual entities commonly use local GAAP for statutory accounts.
• One transaction set must serve local statutory and group reporting.
• Keep entity and branch as posting dimensions, not report-time guesses.
• The framework determination is a matter for your auditor.

What to do in the interval

Spain has handed businesses something unusual: an obligation already running on records and a known warning period on exchange. The sensible use of that interval is to fix the parts that are hard and slow, because the parts that are fast can wait.

The hard and slow parts are almost always master data and process. Customer records with a validated VAT identification number and a settled legal name. One invoice numbering scheme rather than one per channel. Credit notes and corrections handled as recorded events. A defined owner for the case where an invoice is rejected downstream. None of that depends on which format Spain eventually mandates, and all of it will be needed whatever the format turns out to be.

The fast part is the connector. Formats and transmission are the last mile, and they are the part a software supplier can add without your process changing. Businesses that spend the interval on the last mile and skip the master data arrive at the deadline with a working connection sending badly formed documents.

Skyline Nexus holds the pieces this argument is about: one ledger behind every issuing channel, customer master data with tax identifiers held as fields, structured VAT treatment per line, and credit notes linked to the invoices they correct. It does not certify you against any Spanish regime, and no software can.

• Clean customer master data, including validated VAT identification numbers.
• Consolidate invoice issuance into as few systems as possible.
• Settle numbering, cancellation and correction handling now.
• Name an owner for downstream rejections before the volume exists.
• Leave format and transmission to the end; that part is genuinely fast.

Questions worth asking a supplier about Spain

Vendor conversations about Spain go badly when the buyer accepts the word compliant without unpacking it. A short list of specific questions separates suppliers who have read the rules from suppliers who have read a headline.

Ask them to distinguish VeriFactu from Crea y Crece in their own words. Ask which of the two their product addresses. Ask what their software does to a billing record after issuance. Ask whether their answer changes for point of sale. Ask what happens when the final Crea y Crece regulations are published and the interval starts running.

Then ask the question that matters most for a group: what do they do differently in Poland, in Belgium and in the Netherlands. A supplier who gives the same answer for all four countries has not built for any of them.

• Explain VeriFactu and Crea y Crece separately, in your own words.
• Which of the two does this product address, and which does it not?
• What happens to a billing record after it is issued?
• Does the answer change for point of sale and field invoicing?
• What is your plan for the interval after the final regulations are published?
• How does your behaviour differ in Poland, Belgium and the Netherlands?

Confirm the position before you act on it

Spanish rules in this area have moved more than once, including the revision of the VeriFactu deadlines and the long path of the Crea y Crece decree. Everything on this page reflects the position as confirmed on 7 September 2026, and a page is not a source of law.

The Agencia Estatal de Administracion Tributaria is the authority for both the billing-record rules and the eventual e-invoicing obligation. Before you commit budget or change systems, confirm with AEAT or a Spanish adviser which regime you fall under, which date applies to you, and whether the final Crea y Crece regulations have been published.

What software can honestly offer is capability, not certification. It can show you what it records, what it produces, what it prevents and what it can export. Judge it on that, and leave the compliance conclusion to the people who are accountable for it.

• Authority: Agencia Estatal de Administracion Tributaria (AEAT).
• Confirm your regime, your date, and the publication status of the regulations.
• Position stated as confirmed on 7 September 2026.
• No software is a substitute for advice from your auditor or tax adviser.

Common questions

Is B2B e-invoicing mandatory in Spain?

Not yet. The Royal Decree activating the Crea y Crece B2B e-invoicing mandate under Law 18/2022 was approved by the Council of Ministers in March 2026, but the clock runs from publication of the final regulations. Businesses over EUR 8 million turnover become subject 12 months after publication and everyone else 24 months after. Confirm the current status with AEAT.

What is the difference between VeriFactu and Crea y Crece?

They are two different reforms. VeriFactu sets rules on billing software, requiring certified and tamper-evident invoicing records, and it is already phasing in. Crea y Crece, under Law 18/2022, will require electronic invoices to be exchanged between businesses, and it is approved but not yet in force. Meeting one does not satisfy the other.

When does VeriFactu apply to my business?

It became mandatory on 1 January 2026 for companies not under the SII reporting regime, with revised deadlines of 1 January 2027 for corporate income tax payers and 1 July 2027 for individual business owners and professionals under IRPF. Which date applies depends on how your business is taxed and whether you are inside the SII regime, so confirm your own position with AEAT.

What is the standard VAT rate in Spain?

The standard rate is 21 percent, with reduced rates for defined categories, and Spain transacts in euro. What matters for a system is that the VAT treatment is stored as structured data per line, including reverse charge cases and the customer VAT identification number on intra-EU supplies.

Which accounting framework do Spanish entities report under?

Listed companies in the European Union report consolidated accounts under IFRS as adopted by the EU, while individual entities commonly prepare statutory accounts under local GAAP. A Spanish subsidiary of a foreign parent therefore serves two presentations from one set of transactions. Your auditor determines which framework applies.

Rates, regimes and deadlines in this summary change, and many countries are actively legislating on e-invoicing. This is general information, not tax or legal advice — confirm the current position with the authority named above or with your tax adviser before you rely on it.