E-invoice reception 2026: calendar, obligations and what happens if you are the receiver

This guide is written from the side almost no one covers: the invoice receiver, i.e. the accounts payable team. All media and advisory coverage talks about the issuer (what software to use, how to sign, how to send to the AEAT). Here we work the other way around: what you have to do if your SME receives invoices from hundreds of suppliers and needs to process them on time, reconcile them with POs and delivery notes, and retain them with integrity.

Why the receiver side matters (and why nobody tells the story this way)

The dominant narrative around mandatory e-invoicing in Spain treats the issuer as the protagonist. There is logic to it: the issuer is the one who installs the invoicing software, signs the XML, transmits it through an accredited or interoperable channel. But for every issuer there are dozens of receivers, and the receivers are the ones doing the invisible work: validating, parsing, reconciling line by line, retaining and booking.

A distribution SME that processes 800 invoices a month does not issue 800; it receives them. When its 250 active suppliers start sending invoices in structured format - Factur-X, UBL, CII or FacturaE 3.2.x - the SME becomes an XML operator overnight. The operational reality of the payer side is what this guide tackles.

If you are also interested in how Verifactu specifically impacts the receiver (because you will see the QR and the hash on every invoice you receive), we have a dedicated page on the cross-cutting angle.

Regulatory framework: the three pieces that coexist

Three different regulations cover three different aspects. Confusing them is common and leads to wrong operational decisions.

Rule	What it regulates	Who it binds	Calendar
Law 18/2022 ("Crea y Crece") + implementing regulation	Format (structured XML) and channel (accredited or interoperable platform) of B2B invoices	Businesses and professionals invoicing other businesses or professionals	Entry into force staggered from the publication of the technical regulation, still pending as of May 2026. First >8M EUR, then everyone else. Check the BOE monthly under the Ministry of Finance's current calendar.
Royal Decree 1007/2023 + Royal Decree-Law published in 2025 (Verifactu)	The invoicing software: invoicing records, QR, chained hash and submission (or custody)	Anyone who issues invoices and uses software	1 January 2027 (companies under Corporate Income Tax) - 1 July 2027 (freelancers under personal income tax). Dates amended by the Royal Decree-Law published in the BOE during 2025.
Immediate Information Supply (SII)	Reporting of VAT ledgers to the AEAT within 4 days	Companies with operations >6M EUR, VAT groups, REDEME, voluntaries	In force since 1 July 2017

All three coexist. The receiver notices them like this: SII forces you to report quickly what is already booked; Verifactu lets you validate the QR and hash of every received invoice; mandatory e-invoicing means the input format stops being PDF and becomes structured XML.

Primary regulatory sources:

• Law 18/2022, of 28 September, on business creation and growth: BOE-A-2022-15818
• Royal Decree 1007/2023, of 5 December, on the Regulation of invoicing IT systems: BOE-A-2023-24840
• Royal Decree-Law published in the BOE during 2025 (urgent measures delaying Verifactu): see the current Ministry of Finance calendar
• Official AEAT information on invoicing IT systems (Verifactu): AEAT Electronic Office

Canonical 2026 / 2027 / 2028 date table by tax regime

This is the information most pages have out of date. The dates reflect the regulatory situation as of May 2026 after the Royal Decree-Law published in the BOE during 2025.

Tax regime	Verifactu (issuance)	B2B e-invoice (issuance)	B2B e-invoice (reception)
Companies under Corporate Income Tax, revenue > 8M EUR/year	1 January 2027	12 months after publication of the technical regulation (under the current Ministry of Finance calendar)	From the same date as issuance: they must accept the structured channel
Companies under Corporate Income Tax, revenue < 8M EUR/year	1 January 2027	24 months after publication of the technical regulation	Reception obligation from the first tier (together with >8M): the receiver must be ready when structured invoices start arriving
Freelancers (personal income tax, direct estimation)	1 July 2027	24 months after publication of the technical regulation	Same as small companies: they must accept structured XML when an obligated supplier issues to them
Public Administrations	Not applicable (own regime)	In force since 2015 (Law 25/2013): FacturaE 3.2.x mandatory	FACe / FACeB2B operational since 2015 (face.gob.es)
SII companies (> 6M EUR, VAT groups, REDEME)	1 January 2027 (if they issue with software)	Same issuance rules apply by tier	Reception + SII obligation coexist: 4-day reporting on what was received

Operational read of the calendar. If your SME processes between 100 and 2,000 invoices a month, the expected pattern is:

• 2026 (second half). The largest suppliers (utilities, brands, national distributors) start issuing structured XML. Your input mix moves from "PDF at 95%" to "PDF + XML mixed".
• 2027. Verifactu live. Invoices you receive, beyond arriving in structured format, will carry a QR and a hash you can verify against the AEAT. SII still requires fast reporting.
• 2028. Steady state. Almost every B2B supplier issues in structured format. The receiver that has not automated has become a manual XML operator.

What you have to do as receiver before your suppliers change

The real deadline for preparing the receiver side is not the mandate date, but six months earlier. When a supplier decides to switch to electronic issuance, they do not warn you in advance: the next invoice simply arrives in a different format. The practical steps are as follows.

First, map the inventory of active suppliers. Identify which ones bill more than 8 million EUR a year (utilities, wholesale distributors, large manufacturers, brands with national presence). Assume that set will be the first tier to change. Cross-reference the inventory with the volume of invoices each one generates for you: if your top 20 suppliers produce 60% of your invoice volume, that is where to focus.

Second, define the reception channel. Just keeping invoices arriving by email is not enough. The B2B e-invoicing regulation foresees a structured entry point: your SME has to be addressable on an accredited platform or on an equivalent interoperable channel. This is not improvised in September; it requires prior planning.

Third, lock down the matching layer. This is where most companies trip up. Receiving a perfectly structured XML does not mean the invoice is processed. You still have to reconcile it line by line against the purchase order and the receipt note. E-invoicing solves data extraction; it does not solve reconciliation. Line-by-line three-way matching is still the control that detects real overpayments, and it only operates at unit and pre-tax unit-price level.

Fourth, integrate with the target ERP. Holded, Sage, A3, Contasol, Quipu or whichever ERP you use is still the system where the approved invoice gets booked. The difference is that now you need an intermediate layer between reception and the ERP: a layer that parses XML, matches against PO and delivery note, manages exceptions and only sends to the ERP the validated invoices. That is the role of touchless accounts payable.

Fifth, set the exception flow. Invoices that match perfectly are the minority. Most will have some variance: a price that does not match the PO, an invoiced quantity different from the received quantity, VAT misapplied, withholding not included, subtle duplicates. Each variance type needs an owner, a deadline and a traceable resolution. If exceptions end up in an email to finance, they get lost.

The most expensive technical mistake: matching by totals

It is the silent pattern affecting almost every SME, and mandatory e-invoicing does not fix it. We describe it with a reproducible real case.

A distribution SME receives from supplier A an e-invoice in Factur-X format. The XML is perfectly formed, signed and validated. The main line states: 100 boxes of product X at 50.00 EUR/unit, total 5,000.00 EUR pre-VAT.

The purchase order issued by the SME stated: 100 boxes at 49.50 EUR/unit. The receipt confirms: 98 boxes physically received (2 boxes arrived broken and were returned).

If the validation system matches by totals, it does this calculation:

• Invoice total: 5,000.00 EUR.
• PO total (with received quantity): 98 x 49.50 = 4,851.00 EUR.
• Difference: 149.00 EUR (3%).

The system applies a 3% tolerance for example and approves the invoice. Result: 149.00 EUR overpayment not detected.

If the system matches line by line pre-tax, it does two separate calculations:

• Price variance: (50.00 - 49.50) x 98 = +49.00 EUR (the supplier is overcharging per unit).
• Quantity variance: (100 - 98) x 49.50 = +99.00 EUR (invoicing units not received).

Total real discrepancy: 148.00 EUR, broken down into two different causes that require different actions (the first goes to purchasing for renegotiation; the second goes to the warehouse to regularize the receipt note or issue a credit note). E-invoicing does not detect this; line-by-line matching does. The annual operational difference, in an SME with 800 invoices a month and a 5% incident rate, comfortably exceeds the cost of automating.

Structured formats: what you will receive

The technical regulation supports several formats. You cannot assume all your suppliers will send the same one. Summary for the receiver.

FacturaE 3.2.x

Spanish standard, XML with XAdES e-signature. Dominant in invoicing to Public Administrations since Law 25/2013. If you work with public authorities, your system already knows it. The structure is dense but documented; the technical challenge is validating the XAdES signature before processing.

Factur-X / ZUGFeRD

Franco-German format. PDF/A-3 with embedded CII XML. To a human it looks like a PDF; to a machine, the XML is extracted. It is the most likely format among cross-border European suppliers and multinationals with DACH presence. Receiver advantage: if your system still depends on humans looking at PDFs, Factur-X does not break that flow.

UBL (Universal Business Language)

OASIS standard, basis of Peppol. Dominant in Nordic countries, the Netherlands, the UK. Likely format from suppliers with international logistics chains. Clear XML syntax, easy to map.

CII (Cross Industry Invoice)

UN/CEFACT standard. Technical base of Factur-X. More used in pure industrial and logistics sectors. Standalone reading is less frequent in Spanish SMEs but the parser has to support it.

Your receiving system must support all four. Any supplier that specializes in only one format will leave you outside 40-60% of the input mix.

Why your ERP will not solve this on its own

ERPs and accounting software (Holded, Sage 50/Despacho, A3, Contasol, Quipu, Anfix) are adding e-invoice reception modules. Their native function is to book and archive, not reconcile line by line with POs and delivery notes. Totals-based matching with tolerance is what gets programmed by default, and for the reasons in the previous section, it is insufficient.

For line-by-line pre-tax cross-checking, for detecting subtle duplicates, for automatically mapping the invoice to its PO even when the PO number is missing or misspelled, and for routing exceptions to the right owner, you need a dedicated layer between the entry channel and the ERP. That is the layer ininvoice operates, and it is worth reviewing the plan pricing before the mandate phase: the marginal cost of adding the layer now is much lower than handling the transition under fire.

How ininvoice processes the receiver side

Functional summary, no marketing. The operational flow:

1. Multi-channel ingestion. Read-only OAuth connection to the mailbox (Gmail, Outlook). Additional acceptance of structured XML incoming through accredited channels when the technical regulation enters into force.
2. Format detection and parsing. The system recognizes whether the incoming file is PDF, Factur-X, UBL, CII or FacturaE 3.2.x. It extracts the lines into a common format.
3. PO matching by similarity. If the invoice does not carry a PO number or carries it incorrectly, the system finds the corresponding PO by supplier, date, descriptions and amounts.
4. Line-by-line three-way matching. Each invoice line is compared to the corresponding PO and delivery note line. Variances are calculated pre-tax, with configurable tolerances (absolute and percentage) and OR/AND combiner per accounting policy.
5. 0-100 risk score. Each invoice gets a score reflecting the likelihood of error or fraud, based on signals (potential duplicate, variances, new supplier, unusual amounts).
6. Exception routing. Reconciled invoices are exported to the ERP. Those that do not reconcile are routed to the right owner: price to purchasing, quantity to warehouse, duplicate to payment block.

ininvoice does not replace the ERP. It sits between the entry channel and accounting. The operational source on the payer-side model is described in touchless accounts payable, and the quantitative impact of the Verifactu framework on this flow in Verifactu and its impact on touchless AP.

Frequently asked questions

When does the obligation to receive e-invoices in Spain take effect?

The reception obligation enters into force in parallel with the issuance obligation, staggered by tiers based on issuer revenue. As of May 2026, the technical regulation developing Law 18/2022 has not yet been published in its definitive version; once published, the 12-month countdown for issuers above 8M EUR begins, with 24 months for the rest. Check the BOE periodically or consult a tax adviser.

Has Verifactu been delayed to 2027?

Yes. The Royal Decree-Law published in the BOE during 2025 pushed the Verifactu entry into force (Royal Decree 1007/2023) to 1 January 2027 for companies subject to Corporate Income Tax and to 1 July 2027 for freelancers under personal income tax. The original date was 1 July 2025 for companies.

Can my company keep receiving PDF invoices once the obligation kicks in?

Only if the supplier issuing them is not yet under obligation (because they fall in a later calendar tier). Once a supplier is in scope, they must issue in structured format and over an enabled channel. The receiver must be technically ready to accept it; the operational corollary is that your system needs to support PDF + XML in parallel during the entire transition (at least 2026-2028).

Which structured format will my suppliers adopt?

It depends on the supplier. FacturaE 3.2.x is likely in sectors with a public-administration invoicing tradition. Factur-X often shows up among multinationals and European suppliers. UBL is common in international logistics chains. CII concentrates in pure industrial sectors. Your receiving system must process all four.

Does mandatory e-invoicing eliminate the need for OCR?

For the flow of invoices arriving in structured format, yes. For the rest (suppliers not yet obligated, small freelancers, expense invoices, tolls, per diems, international ticketing) there will still be PDF and scanned paper. The operational receiving system needs both paths: structured parsing and robust OCR in parallel, at least during the whole transition.

Are there penalties for not being ready as a receiver?

Law 18/2022 sets a specific penalty regime for non-compliance. The detail will be developed in the technical regulation. What is clear: if the obligated supplier issues electronically and the receiver cannot accept the format, operational responsibility for the transaction is unclear. Verify with a tax adviser the penalty scope applicable to each specific case.

How is a received e-invoice retained?

The receiver is obligated to retain the e-invoice with integrity, origin authenticity and legibility for the tax limitation period (generally 4 years; extended in some cases). Retention must allow reproducing the invoice in its original format (structured XML) and, if it carries an e-signature, maintaining the verifiability of that signature. Certified archive systems or copies on an accredited platform are accepted.

What role does Verifactu play on the receiver side?

Verifactu operates on the issuer's invoicing software, not the receiver's. But the receiver notices: from 2027, every invoice issued under the Verifactu regime will carry a QR code and a chained hash that the receiver can verify against the AEAT. This reduces fraud (made-up or duplicated invoices) and improves traceability. For details on the operational impact on the payer flow, see Verifactu from the receiver side.

What if I receive a mix of PDF and structured XML invoices?

That is the transitional reality from 2026 to 2028. Your accounts payable system must accept both paths simultaneously and process them with the same matching logic. Parsing differs (OCR for PDF, structured reader for XML); line-by-line reconciliation against PO and delivery note is the same.

How much does automating the receiver side with ininvoice cost?

The plan is 249 EUR/month up to 300 invoices per month, no implementation fee, no commitment. Plug and play. Operational detail and comparison on pricing.

This guide is reviewed monthly to reflect regulatory changes. Last review: 13 May 2026 by ininvoice team. Regulatory references have been verified against BOE and AEAT on that date. Always consult a tax adviser before making operational decisions.