Crea y Crece Law: how mandatory B2B e-invoicing changes accounts payable management

There is a confusion pattern that comes up in conversations with CFOs and admin managers. Crea y Crece, Verifactu, FacturaE and the implementing Royal Decree get mixed up as if they were the same. They are not. Each has a different goal, a different timeline and a different impact on your AP flow.

This article focuses on Crea y Crece from the receiver's angle. What it requires, what it means for whoever receives supplier invoices, and what you must prepare before the first XML lands in your inbox.

What Law 18/2022 requires exactly

Law 18/2022, of 28 September, amends article 12 of Law 56/2007 and introduces a clear obligation: all commercial relations between companies and professionals in Spain must be documented through electronic invoices in structured, interoperable format.

The points that matter for AP:

• Full B2B scope. Applies to any relation between companies or between a company and a freelance professional. It does not apply to B2C or to relations with public administrations (these already had FACe).
• Mandatory structured format. A digitally signed PDF does not comply. The invoice must arrive in XML with tagged fields: number, date, issuer, per-line amounts, VAT rate, total.
• Interoperability required. Systems must be able to read and exchange invoices regardless of the software used by each party.
• Acknowledgement of receipt. The receiver must acknowledge and communicate the invoice status (accepted, rejected, paid).
• Free access. Nobody can charge the receiver for accessing their electronic invoices. This point protects SMEs against platforms that charge for downloads.

The law is the framework. Technical details (formats, platforms and deadlines) are set by Royal Decree 238/2026, published in the BOE on 31 March 2026, and by Order HAC/1028/2026. This information is general guidance. Consult your tax adviser.

Staggered deadlines: who is in first

The obligation does not come into force on the same day for all companies. The timetable is staggered by turnover and type of obliged party, according to the AEAT implementation calendar.

Segment	Issuing and receiving	Status and payment reporting
Companies with turnover above EUR 8M	6 October 2027	6 October 2027
Other legal persons	6 October 2028	6 October 2028
Natural persons (self-employed and professionals)	6 October 2028	6 October 2029

Companies with turnover above EUR 8 million start issuing, receiving and reporting statuses on the same day. Other companies get one more year, and natural persons report payment status from 2029. Confirm with your tax adviser which tier each company in your group falls into before setting internal dates. This information is general guidance. Consult your tax adviser.

Difference between Crea y Crece and Verifactu

The confusion between these two frameworks is the most frequent. They are different rules with different objectives.

Aspect	Crea y Crece (Law 18/2022)	Verifactu (RD 1007/2023)
Objective	Mandatory B2B e-invoicing	Signed and chained billing records
Who is obliged	Issuer and receiver in a B2B relation	The software used to issue the invoice
Format	Structured, interoperable XML	Record signed with chained hash + QR
Scope	All B2B relations in Spain	Non-SII companies and self-employed
AEAT transmission	Not directly (intermediary platforms)	In verifiable mode, in real time

They are complementary. An invoice can comply with Crea y Crece (structured XML format) and Verifactu (signed record with QR) at the same time. For your AP stack, the practical impact of Crea y Crece is that the invoices you receive change format. The impact of Verifactu is that the data on those invoices is already with AEAT from the moment the issuer generates them. This information is general guidance. Consult your tax adviser.

Direct impact on accounts payable

The most concrete change for whoever manages AP is this: the PDF disappears as a reference format. The invoices you receive by email or portal will be XML. Or they will carry an attached XML. Or they will arrive through a platform that converts them.

What changes in your daily flow:

• Ingestion no longer depends on OCR. With structured XML, fields come tagged. Line number, description, unit price, quantity, VAT rate. No need to interpret pixels or infer which field is which.
• Three-way matching gains accuracy. Comparing line 3 of the XML invoice with line 3 of the PO is comparing homogeneous fields. Tolerance applies on clean data, not on text extracted from a PDF.
• Fewer reading errors. Moving from PDF+OCR to structured XML means fewer invoices to correct before approval, without changing the matching engine.
• Capture errors drop to zero. No re-keying. No mis-copied digit. The InvoiceLineUnitPrice field arrives as a number, not as text on a PDF with 80 digits per page.
• Mandatory acknowledgement. The law requires the receiver to communicate status. This requires a system that records whether the invoice was accepted, rejected or paid, and on what date. A manual AP process does not generate this record automatically.

Technical formats: FacturaE and Peppol BIS

The law requires structured, interoperable XML. Article 7.1 of Royal Decree 238/2026 admits four syntaxes: UBL, Facturae, CII and EDIFACT. See the admitted formats.

FacturaE is the Spanish national format. It uses an XML schema owned by the Ministry of Finance. It is the standard for invoicing to public administrations (FACe) and the most widespread among Spanish ERPs as initial support for Crea y Crece. Technical documentation is available at facturae.gob.es.

Peppol BIS 3.0 is the European format, interoperable in more than 32 countries. It uses the UBL 2.1 schema in line with European standard EN 16931. It is mandatory in many Nordic countries and is gaining ground in Spain for operations with European suppliers.

For your AP team, the question is not which format to use. It is whether your system can process both. A Spanish supplier will send FacturaE. A French or German supplier will send Peppol UBL. If your AP only processes one of the two, invoices will come in through the wrong path.

Constructed example (synthetic data): distributor with 400 invoices per month

Imagine an industrial cleaning products distribution company that receives 400 invoices a month. 80% arrive as PDF by email. If the AP team spends between 8 and 12 minutes per invoice on capture, verification and approval, that is between 53 and 80 hours per month on manual AP alone.

When their suppliers move to FacturaE XML under Crea y Crece, capturing those 320 current PDF invoices becomes direct XML field extraction. If the AP system reads the XML without intervention, the 53-80 hours drop to exception handling. With an assumed 15-25% exception rate, that would be between 60 and 100 invoices per month requiring review by a person; the rest would arrive matched, ready for a person to approve.

The opposite risk: if the AP system is not ready to read XML and someone opens the file in a viewer and re-keys the data manually, nothing is gained. The format is lost without taking advantage of it.

What your AP stack needs to comply

Four minimum capabilities your AP system must have before the first XMLs arrive:

1. Native FacturaE XML reading. Parsing the FacturaE 3.2.x XSD schema, extracting fields by tag, not by position on the page. If your system only does OCR over PDF, you need an additional layer.
2. Peppol UBL support. For invoices from European suppliers. Field mapping between FacturaE and Peppol UBL is standard, but requires configuration.
3. Per-invoice status record. The law requires communicating accepted/rejected/paid. Your AP must generate that status automatically upon reconciling and approving.
4. Audit history. Who approved, with what data, on what date. This record is your protection in a cross-inspection with the issuer's data.

Furthermore, while XML and PDF coexist (the transition period may last 12-24 months depending on your suppliers' adoption pace), your AP system must process both formats without the team having to decide each time which path each invoice takes.

Common errors in the adaptation

The CFOs I talk to make three recurring mistakes when preparing the transition:

Error 1: Waiting until the last quarter. Some large suppliers will start before the legal deadline. If you receive an XML in November and your system is not ready, you have an operational problem now.

Error 2: Confusing issuer compliance with receiver readiness. Your ERP already issuing FacturaE does not mean your AP can process received FacturaE. They are different flows. Issuance is your ERP's part; reception and matching is your AP stack's part.

Error 3: Thinking the PDF disappears overnight. Smaller suppliers will have a longer deadline. At least between 6 October 2027 and 6 October 2028 your AP will process a mix of structured XML and PDF. You need a flow that handles both without friction.

CFO checklist: 8 actions before the deadline

1. Confirm with your tax adviser the exact deadline applicable to your company based on billing volume.
2. Audit how many invoices arrive as PDF vs XML today. Identify the 20 highest-volume suppliers and ask them in which format they plan to issue and from when.
3. Verify whether your current AP system can parse FacturaE XML. If the answer is "we do not know", that is a gap.
4. Check whether your destination ERP (Holded, Sage, A3 or others) accepts the import of reconciled data referencing the source XML invoice.
5. Establish the acknowledgement flow: how you will communicate accepted/rejected/paid to each supplier as required by the regulation.
6. Define the transition flow for the mixed PDF+XML period. Which system handles each type and how they unify in the received-invoices ledger.
7. Document the audit trail: every reconciled invoice must have a record of who approved, when and with what data. Retention obligation: four years for the tax limitation period (art. 66 of the General Tax Law) and six years for commercial purposes (art. 30 of the Commercial Code).
8. Run a real test with a supplier already issuing FacturaE voluntarily. Do not wait until it is mandatory to discover that your system does not process it.

How ininvoice fits in this context

ininvoice is the AP layer between your inbox and your ERP. It does not issue invoices. It is not an ERP. Crea y Crece changes the format in which invoices arrive; what does not change is the control you need over each one before paying it. That is what ininvoice does:

• Reading of the invoice as PDF or image (photo or scan); reading XML e-invoices is in development.
• Line-by-line three-way matching with a configurable tolerance (by default 2% or EUR 1.50 per line).
• Duplicate blocking before approval and tax checks (base, VAT, withholding, tax ID).
• Approve, reject or ask for clarification from the panel, with each invoice's history exportable to Excel.
• Export of approved invoices as CSV or Excel importable into the ERP.

If you want to see the full hands-free accounts payable flow, it shows each step from receipt to approval.

Frequently asked questions

Does Crea y Crece also apply to self-employed professionals?

Yes, but with different deadlines. The self-employed issue and receive e-invoices from 6 October 2028, one year after companies with turnover above EUR 8 million, and report payment status from 6 October 2029, according to the AEAT implementation calendar.

Does a digitally signed PDF comply with Crea y Crece?

No. The law requires structured, interoperable format. A PDF, even if electronically signed, does not comply because the data is not machine-readable without OCR.

Is Crea y Crece the same as SII?

No. SII (Immediate Information Supply) requires large companies to send their VAT ledgers to AEAT in short timeframes. Crea y Crece mandates the format of the invoice between companies. They are different frameworks with different scopes.

What happens if a supplier keeps sending me PDFs after the deadline?

The non-compliance is the supplier's, not yours. But the operational cost falls on you: if your system only processes XML and you receive PDFs, someone will have to handle them manually. Communicate deadlines to your suppliers in advance.

Does Crea y Crece apply to invoices from foreign clients?

The scope is commercial relations in Spain. Invoices from European suppliers may arrive in Peppol BIS, which uses the UBL syntax, one of the four admitted by article 7.1 of Royal Decree 238/2026 (UBL, CII, EDIFACT and Facturae, on the EN 16931 model). For intra-EU operations, consult your adviser.

Do I have to change ERP to comply?

Not necessarily. Many Spanish ERPs (Holded, Sage, A3) already support FacturaE issuance. The gap is usually on reception and matching, which is where a specialised AP layer adds value.

What obligations does the receiver of the electronic invoice have?

Under the law, the receiver must be able to access their invoices, acknowledge receipt and communicate the status (accepted, rejected, paid). The implementation detail is in Royal Decree 238/2026 and Order HAC/1028/2026.

Is FacturaE different from Peppol BIS?

Yes. FacturaE is the Spanish national format; Peppol BIS 3.0 is the European format and uses the UBL syntax. Facturae and UBL are among the four syntaxes admitted by article 7.1 of Royal Decree 238/2026, together with CII and EDIFACT. Your AP system must be able to process both, especially if you have suppliers in other EU countries.

Three things to remember

1. Crea y Crece changes the format of the invoices you receive. PDF + OCR is not the future flow. Structured XML + direct parsing is the arriving standard.
2. The transition period will be mixed. For months XML and PDF will coexist. Your AP stack must handle both without friction for the team.
3. The acknowledgement and status obligation requires a system that records it automatically. It cannot be done manually with 300 invoices a month.

This information is general guidance. Consult your tax adviser.

Related content

• Three-way matching: the complete walkthrough
• Touchless AP and where people still decide
• FacturaE 3.2.x: technical format and XAdES validation