AiStaffo

Spain e-invoicing 2027: what to set up now and what can wait

Stock photo: invoices, laptop, desk

In Spain, the B2B e-invoicing deadlines are already fixed. Businesses and professionals with turnover above 8 million euros in the previous year must comply from 6 October 2027. Everyone else must comply from 6 October 2028. The order that sets these dates, Orden HAC/1028/2026, entered into force on 6 October 2026. Verifactu is a separate rule. On 5 October 2026 the Ministry of Finance announced it plans to move the outstanding Verifactu obligations to October 2028, but that announcement was not yet in the BOE when checked, so the earlier legal dates still stand. Whatever the timing, the setup is the same: capture invoice data cleanly, check structured files before sending, and track rejection and payment status. A person still approves rejections, corrections and payment dates that do not match the bank.

In short

  • Order HAC/1028/2026 fixes B2B e-invoicing for 6 October 2027 (large firms) and 6 October 2028 (everyone else).
  • Verifactu's move to October 2028 was announced on 5 October 2026 but was not in the BOE when checked, so the 2027 dates still stand on paper.
  • Recipients must report rejections and payment status within four calendar days, excluding weekends and national holidays; silence means presumed acceptance.
  • Set up numbering, pre-send checks and one status queue first, then automate payment matching.
  • A person approves rejections, corrections, unmatched payments and any software change.

Two calendars that people mix up

Spain is running two separate obligations, and many guides blur them. The first is mandatory B2B e-invoicing. It rests on the Ley Crea y Crece (Law 18/2022), Royal Decree 238/2026 and Order HAC/1028/2026, which sets up the public e-invoicing solution run by the Agencia Tributaria, the national tax agency. The second is Verifactu, the set of requirements that invoicing software must meet under Royal Decree 1007/2023. Each has its own deadlines. Only the e-invoicing dates are fixed in a published order today.

What is already fixed

Order HAC/1028/2026 is dated 2 October 2026, was published in the BOE on 5 October 2026 and took effect the next day. The legal clock for the deadlines runs from that date. The Agencia Tributaria's implementation calendar lists the two main points:

  1. Businesses and professionals whose turnover in the previous year exceeded 8 million euros must issue and receive structured e-invoices from 6 October 2027.
  2. All other businesses and professionals must do the same from 6 October 2028.

A structured invoice is a data file generated by invoicing software or by the public platform. A PDF sent by email is not the same thing. During the first 12 months of each phase, the agency's calendar says a readable PDF must accompany the structured invoice. That transition is useful for firms that are not yet ready, but it does not replace the file.

Status reporting is the part most owners miss. The recipient of an invoice must report to the public platform whether it was accepted or rejected, the date of full payment and the payment due date. The report is due within four calendar days, excluding Saturdays, Sundays and national public holidays, counted from the day the status occurs. If no rejection or corrective invoice is sent, the invoice is presumed accepted. That presumption makes a missed rejection an expensive mistake, not just a missing record.

The start date for status reporting is less clear in the summaries. The EY tax note and the vatcalc analysis put the first group at October 2027, other legal entities at October 2028, and individuals and entities under the income attribution regime at October 2029. One guide describes status reporting from October 2027 for all businesses in the scope of the mandate. Those summaries disagree on the smaller group. Check the Order's text before you fix the reporting date in your own plan.

Verifactu: announced, not yet changed in law

On 5 October 2026 the Ministry of Finance published an information note saying it plans to postpone the outstanding Verifactu obligations to October 2028. The stated reason is to line them up with the e-invoicing calendar. This is a note, not a legal text. When the BOE was checked for this guide, the change to Royal Decree 1007/2023 had not been published, and the Agencia Tributaria's own page describes the change as a forecast.

Until a modification is published, the dates set by Real Decreto-ley 15/2025 still apply on paper: 1 January 2027 for corporate income tax payers and 1 July 2027 for everyone else, including sole traders. The practical point is simple. Do not wait for October 2028 before checking your software. Ask your software provider in writing which version will meet the Verifactu rules and on which date. Treat the 2028 date as a possibility until the BOE publishes it.

Why this costs money

The cost of a manual invoice is mostly labour, and labour is the part most owners do not measure. Ardent Partners' 2025 AP Metrics report puts the average fully loaded cost of processing an invoice manually at about 12.88 US dollars for organisations without best-in-class automation. That figure is a US-based benchmark for accounts payable teams. It shows the shape of the cost, not what a Spanish firm will pay.

A simple local calculation is more useful. Take the minutes a person spends on one invoice, multiply by their fully loaded hourly cost in euros, and divide by 60. For example, 12 minutes at 25 euros per hour is 5 euros per invoice. Then add the cost of the exceptions: the invoices that need a second look, a correction, or a chase for payment. Those exceptions usually cost more than the clean invoices.

There is also a deadline cost. Under the status rules, a rejection that is not reported in time can leave the invoice presumed accepted. A payment date that is entered from memory, rather than from the bank line, can produce a wrong report. Both problems are easy to avoid with a log, but they are expensive to fix after the fact.

The manual way and the automated way

TaskManual wayAutomated way, with a person checking
Capturing invoice dataSomeone retypes numbers, NIF, dates and totals from PDFs or screensData comes from the invoicing program or ERP export. OCR or an LLM reads PDFs from suppliers and proposes values for a person to confirm
Checking files before sendingA visual check, if there is timeRules check mandatory fields, NIF format, totals and duplicate invoice identifiers before the file leaves the system
Logging rejectionsEmails read when someone opens the inboxStatus messages land in one queue with a deadline date and a daily review
Recording payment datesBank statement compared by hand, often weeks laterBank feed matched to invoice numbers. Unmatched lines go to a person
Chasing unpaid invoicesAd hoc emails and callsScheduled reminders, sent only to customers who have agreed to that channel
Audit trailFolders and memoryA dated log of every invoice, status and approval

How to set this up, step by step

  1. Confirm your scope. Write down your tax identification number (NIF), your turnover for the previous year, and which of your customers are Spanish businesses or professionals. Consumer sales are not part of this B2B calendar. Use the turnover figure to decide whether your first date is 2027 or 2028.
  2. Map where invoice data lives. List your invoicing program, any ERP, spreadsheets, shared mailboxes and the bank account you use for receipts. For each one, note whether the invoice number can be linked to the original invoice file and to its payment line. Most gaps appear at this step.
  3. Fix the invoice identifier. The technical rules build a unique identifier from the supplier's NIF, the invoice number, the series and the issue date. Check that your numbering series do not repeat, and that no two series share a number for the same issuer.
  4. Capture incoming data. Use the structured file where your software produces one. For PDFs from suppliers, use OCR or an LLM to propose the fields, then have a person check the supplier NIF, invoice number, date and total against the original before posting. Do not accept a proposed value that does not appear in the source document.
  5. Run structured file checks before sending. Build a checklist of mandatory fields, format rules and total checks. Failed files go to a person. The public platform has its own validation, rejection and correction procedures, so your checks should catch errors before they reach the platform, not after.
  6. Set up a status queue. Route acceptance, rejection and payment messages to one shared inbox or ticket queue. Start a four-day clock, excluding weekends and national holidays, from the day each status occurs. Review the queue every working day. Keep the national holiday calendar in the tool that counts the days.
  7. Record payment dates from the bank, not from memory. Match each transfer to its invoice number. Where a transfer has no clear reference, leave the payment date empty and send the line to a person. Never enter a payment date that the bank line does not support.
  8. Run a monthly reconciliation. Compare the invoices you issued and received with the platform records and the payment log. Clear the exception list, and keep a dated record of each correction.

Customer reminders can run on WhatsApp Business API or on email. Use WhatsApp only for customers who have agreed to be contacted that way, and follow the data protection rules that apply to your business. A reminder is not the same as the status report, and it does not replace the report.

What a person still approves

Automation can gather, check and log. It cannot decide. A person should approve every rejection sent to a supplier or customer, every corrective invoice, any PDF sent in place of a structured file during the transition, every payment date that the bank does not clearly match, and every change to the software or numbering rules. The owner or finance lead also decides which Verifactu version and go-live date the business accepts from its software provider.

What breaks, and how to prevent it

The most common break is a missed status message. A rejection that is not reported in time can leave the invoice presumed accepted. Prevent it with a single queue, a visible deadline date and a named person who reviews it every working day.

The second break is duplicate or reused invoice numbers. When two series share a number, or an export overwrites an old file, the unique identifier stops being unique. Prevent it with locked numbering series and a duplicate check before each file is sent.

The third break is a bad read by OCR or an LLM. A tool can read 4,500 euros as 450 euros, or take a due date for an issue date. Prevent it with a total check against the line items and a rule that every proposed value must match text in the original document. A person confirms the exceptions.

The fourth break is platform downtime. The rules include arrangements for technical failures, but a business still needs its own record. Keep a copy of each file, its send time and any error message. Do not delete the PDF or the structured file until the reconciliation is done.

The fifth break is a date that moves. Verifactu may move again if the BOE publishes a different date. Prevent it by asking your software provider for its update plan in writing and by checking the BOE before each planning review.

When not to automate

Automation is not worth the set-up time for every business. If you issue only a handful of invoices a month, a checked spreadsheet and a calendar reminder may be enough, and a full integration will cost more time than it saves. If your invoices involve one-off contracts, unusual VAT treatment, or negotiation on each price, a person should make those calls, and a tool should only collect the data.

Do not automate a process you cannot describe. If your invoice numbers are inconsistent, fix the numbering first. If your software vendor has not confirmed what it supports for the public platform, do not build the workflow around an assumption. A workflow that runs on wrong data simply produces wrong reports faster.

If setting this up changes anyone's role or hours, the notice and consultation rules in Spanish labour law apply, and the change should be agreed with the employee or checked with a lawyer.

What it typically takes

The main cost is time from the people who know the invoices. Expect the early weeks to go on scoping, numbering and the software export. The agency has opened a test environment for the public platform, so you can run trial files before the live date. The platform is due to be available at least two months before the first mandatory phase, so firms in the first group should plan testing during 2027, not after October 2027.

Build the setup in this order: scope, data map, numbering, checks, status queue, payment matching, reconciliation. Each step gives a working output you can test on a month of real invoices. Results depend on your own invoice volumes, error rate and staff costs, which the free automation audit measures.

This explains the rule in general terms; it is not legal or tax advice for your case.

How AiStaffo would automate this

AiStaffo would connect your invoicing program or ERP export, the inbox where supplier PDFs arrive, and your bank feed, so that every invoice lands in one log with its identifier. The AI worker would check mandatory fields, totals and duplicate numbers before a file is sent, and would route status messages into one queue with a four-day deadline. Payment dates would be matched to bank lines automatically, with unmatched lines passed to a person. The owner or finance lead still approves rejections, corrections, any PDF used during the transition, and the software and go-live choices. Book a free automation audit.

Questions people ask

Is e-invoicing mandatory for my Spanish business in 2027?
It depends on your turnover in the previous year. Businesses above 8 million euros must comply from 6 October 2027, and all other businesses and professionals from 6 October 2028. Check which group you fall into before you plan the work.
Has Verifactu been postponed to October 2028?
The Ministry of Finance announced on 5 October 2026 that it plans to postpone the outstanding obligations to October 2028. That announcement was not in the BOE when this guide was checked. Until a modification is published, the earlier dates in Real Decreto-ley 15/2025 remain on paper.
What happens if I do not report a rejected invoice?
The order states that an invoice is presumed accepted if no rejection or corrective invoice is sent. The rejection has to be reported within four calendar days, excluding weekends and national holidays. A missed rejection can therefore leave a bad invoice on the books.
Can I send a PDF instead of a structured e-invoice?
The Agencia Tributaria's calendar says that during the first 12 months of each phase, a readable PDF must accompany the structured invoice. A PDF sent by email alone is not treated as the e-invoice itself. Plan to produce the structured file from your software from the start.
Which tools do I need to automate this?
Start with your existing invoicing program or ERP, a shared inbox, a spreadsheet or database for the log, and your bank feed. OCR or an LLM can read supplier PDFs, but a person should confirm each value against the original. Ask your software provider in writing which public platform features it supports.
Should a small business automate this now?
Only if the volume justifies it. A business that issues a few invoices a month can run the checks in a spreadsheet with a daily reminder. Automation pays off when invoice volume, exceptions and payment chasing take regular staff time.

Book a free automation audit

Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.

We use these details only to reply to this request and prepare your audit, and keep them for up to two years. We send no marketing unless you tick the box above. Privacy policy

e invoicinginvoice processingpayment reconciliationdocument processingspain