90 Days to E-Invoicing Compliance: An AP Readiness Checklist

Thirteen EU member states now enforce e-invoicing mandates, and by July 2026 that number climbs to at least sixteen. Yet a 2025 survey of global business services organizations found only 11% feel fully equipped to meet these requirements. That gap — between the deadlines that have already arrived and the finance teams still operating with manual or PDF-based workflows — is what a 90-day readiness plan exists to close. This is not a vendor evaluation guide. It is a calendar: four phases, each with a concrete deliverable, so that when your next mandate deadline hits, your AP team is not scrambling to figure out what a Peppol Access Point is while non-compliant supplier invoices pile up in the inbox.

Why 90 Days — and Why Starting Now Matters

The calendar is not arbitrary. E-invoicing implementation timelines reported by organizations that completed the transition cluster around three to six months for configuration and supplier onboarding alone — and that is for a single country. For AP teams handling invoices from suppliers across three or more mandate jurisdictions, overlapping deadlines mean the preparation window for the next country is already overlapping with the go-live of the previous one.

Consider the 2026–2027 calendar on the table right now. Belgium went live January 1, 2026. Poland's KSeF became mandatory for large businesses in February, with all VAT-registered entities required by mid-2026. France's universal reception obligation activates September 1, 2026 — under 80 days away — covering all ~4 million VAT-registered entities regardless of size. Germany's B2B mandate phases in from January 2027. Spain's Verifactu and Crea y Crece obligations roll out across 2027. Any AP team receiving supplier invoices from three or more of these markets is effectively in a continuous compliance cycle, not a one-time project.

If you are reading this and your organization has not mapped which of your entities are registered in which jurisdictions, which suppliers send invoices from which countries, and whether your ERP can receive structured XML in any of the required formats — you are not late. But you are at the point where every week of delay compresses the testing and supplier communication phases that determine whether go-live is smooth or chaotic.

What 90 days can and cannot do: Ninety days is sufficient to achieve compliance readiness for one to three mandate jurisdictions if your ERP has some XML ingestion capability and your supplier list is under 200. It is not sufficient if your ERP requires a full upgrade cycle, your entity registration status is unresolved in multiple countries, or your supplier count exceeds 500 and you have no existing digital communication channel with them. In those scenarios, use this framework to triage — focus on the jurisdiction whose deadline hits first, and build the repeatable process you will apply to subsequent countries.

Before the 90-day clock starts, establish one governance decision: who owns e-invoicing compliance in your organization. If the answer is unclear — tax says it belongs to finance, finance says IT, IT says procurement — the 90-day window closes before the first meeting ends. A dedicated cross-functional project owner with authority to make tooling and process decisions is the prerequisite, not a nice-to-have.

Days 1–15: Map Your Mandate Exposure

The first two weeks are not about technology. They are about data: knowing exactly which of your entities are registered where, which suppliers invoice from which jurisdictions, and which mandates apply to each intersection. Most AP teams discover during this phase that their exposure is wider than assumed — a French subsidiary receives invoices from a Belgian logistics provider, a German entity buys from a Polish manufacturer, an Italian office processes invoices from Spanish freelancers. Each pair is a compliance intersection.

Deliverable: Entity-Supplier-Mandate Matrix

Create a spreadsheet with these columns. Fill it out for every entity in your organization that receives supplier invoices:

Your Entity	Country	Tax ID / Registration	Registration Status	Top 10 Supplier Countries	Applicable Mandate	Deadline	Format Required
Example SARL (Paris)	France	SIRET 123 456 789 00012	Registered (TVA FR XX...)	FR, BE, DE, IT	Art. 91 LF 2024 — Reception obligation	Sep 1, 2026	Factur-X, UBL, CII (EN 16931)
Example GmbH (Berlin)	Germany	USt-IdNr DE123456789	Registered	DE, PL, AT, NL	Wachstumschancengesetz — B2B receipt	Jan 1, 2027	XRechnung, ZUGFeRD 2.x

Key questions for this phase:

Is every entity that receives invoices properly registered for VAT in its home jurisdiction? A lapsed registration or an unregistered branch office receiving supplier invoices is a compliance gap before e-invoicing even enters the picture.
For multi-entity organizations: does each entity have a separate tax registration number (SIREN in France, USt-IdNr in Germany, NIP in Poland, P.IVA in Italy), or are some entities operating under a parent company registration? E-invoicing platforms validate at the entity level — a shared registration creates routing problems.
Among your top 20 suppliers (by spend), which are already issuing structured e-invoices? Send a 3-question survey: (1) What invoicing format do you use today? (2) Are you capable of issuing structured e-invoices (Peppol BIS, Factur-X, XRechnung, etc.)? (3) What is your migration timeline if not yet issuing structured invoices?

If you need a detailed country-by-country timeline with exact legal references and format requirements, see our Europe e-invoicing mandate timeline. For country-specific deep dives, the France and Germany guides cover entity registration specifics and the 13 mandatory fields required by each jurisdiction.

Days 16–45: Technical Assessment

With the exposure matrix built, month two shifts to infrastructure. The core question: can your current systems receive, validate, and route structured invoice data? For most mid-market organizations, the answer is partial — the ERP can handle some formats from some countries but not others, or it can receive XML but has no mechanism to map it to the AP workflow.

Deliverable: System Readiness Report

Work through these assessment areas. Do not accept "yes, our ERP can do that" from your ERP vendor without a demonstration specific to your mandate jurisdictions:

XML format ingestion. Can your ERP natively parse and validate Factur-X (France), XRechnung (Germany), KSeF XML (Poland), FatturaPA (Italy), and Peppol BIS Billing 3.0? If the answer is "we handle EDI," that is not the same thing. EDI uses a different transport layer and different message standards. Ask your ERP vendor to demonstrate successful ingestion of an actual Factur-X file — not a demo, not a PDF mock-up, but a valid EN 16931-compliant XML with all mandatory fields populated.

Access Point or direct government connection. For Peppol-network countries (Belgium, increasingly the default for cross-border EU), you need a Peppol Access Point — either through your ERP, through a third-party provider, or built in-house. For Poland, you need KSeF API connectivity. For Italy, you interface with Sistema di Interscambio (SdI). For France, you register with an Approved Platform (Plateforme Agréée). Map each jurisdiction in your exposure matrix to its required connection method. If your ERP covers two out of five jurisdictions but leaves three uncovered, the gap is the scope of your external solution search.

Your accountant's platform. In France, many small and mid-sized businesses rely on an external accountant (expert-comptable) who uses Cegid, EBP, Pennylane, or Sage. In Germany, the Steuerberater likely uses DATEV or Lexware. Confirm with your accountant: (a) are they already set up to receive structured e-invoices in your jurisdiction's required format? (b) if not, what is their migration timeline? (c) what do they need from you — a specific platform choice, a file format, or just the raw XML — to keep your tax filings uninterrupted? This conversation alone has derailed more e-invoicing projects than any technical failure.

Data field mapping. A typical structured e-invoice contains 30–50 fields. Your AP workflow needs 6–12 of them (supplier name, invoice number, date, amount, tax amount, PO reference, payment terms). The remaining 20–40 fields are compliance metadata that need to be archived but not processed. Can your current system selectively extract the fields you need, or will it ingest the entire XML payload into your ERP — potentially overwriting existing data mappings or creating duplicate vendor records? For more on why structured XML doesn't eliminate the extraction step, see our analysis of why getting an XML file doesn't mean your AP team can skip data extraction.

Days 46–75: Process Design for the Hybrid Reality

Here is the problem every e-invoicing readiness guide avoids discussing: during the transition period — which for most organizations will last years, not months — your AP inbox will contain a mix of structured XML e-invoices, PDF invoices from suppliers not yet on the mandate, and scanned paper invoices from small vendors who will never adopt structured formats. Designing a process that handles all three through a single pipeline is the difference between compliance on paper and compliance in practice.

Deliverable: Hybrid Invoicing Workflow Design

The workflow needs to answer three routing questions for every invoice that arrives:

Format detection and routing. Is this a structured XML (Factur-X, XRechnung, Peppol BIS, etc.) or an unstructured document (PDF, scanned image, email body)? Structured invoices route to the XML ingestion path for automated field mapping. Unstructured documents route to an extraction layer. The critical design decision is whether these two paths merge before or after the data reaches your ERP. Merging before means a unified data format hits your AP workflow regardless of source. Merging after means two parallel AP processes — which is how duplicate entries and reconciliation gaps appear.

Field standardization across formats. A supplier name on a French Factur-X invoice sits in /rsm:CrossIndustryInvoice/supplyChainTradeTransaction/ApplicableHeaderTradeAgreement/SellerTradeParty/Name. The same supplier name on their PDF invoice sits in the top-left corner in 11pt Helvetica. Your process needs to produce the same "Supplier Name" field mapped to the same ERP field regardless of the source format. Define your target field schema first — the 6–12 fields your AP workflow actually uses — then map each input format to that target schema.

For organizations that receive invoices from multiple countries, a document extraction tool that reads the visual content of any format — PDF, scan, or screenshot — and outputs the same structured fields regardless of origin country provides a unification layer that no format-specific parser can replicate. This is particularly valuable when suppliers in one country use five different invoice layouts despite all being "electronic."

Exception handling. Define what happens when: (a) an XML fails schema validation, (b) a PDF is unreadable or password-protected, (c) mandatory fields are missing from a structured invoice, (d) the supplier sends the same invoice in both XML and PDF format (duplicate detection). For each exception, specify: who is notified, what the resolution path is, and what the SLA is (e.g., "XML validation failures must be flagged to the supplier within 24 hours"). For a deeper dive on catching duplicates before they enter your AP queue, see our guide on automated duplicate invoice detection.

Process Design for the Approval Step

E-invoicing changes the approval workflow in one specific way: compliance validation and business approval become two distinct steps. The tax authority (or Peppol Access Point) validates the invoice's legal compliance before it reaches your AP team. Your team then validates the business content — is the PO reference correct, is the amount within tolerance, are the payment terms as agreed. The two-step model means your approval workflow needs a pre-filter: compliant invoices proceed to business approval, non-compliant ones never reach the approver.

For organizations that do not have a full ERP workflow with built-in approval routing, a lightweight alternative is to extract invoice data to a structured format (Excel or Google Sheets), apply conditional formatting rules for exception flagging, and route only flagged items for human review. Our guide on building an automated invoice approval workflow walks through this approach in detail.

Days 76–90: Test, Communicate, Go Live

The final two weeks are where most readiness plans collapse — not because the technology fails, but because the supplier communication didn't happen. An e-invoicing system that your team has configured perfectly is useless if your top 20 suppliers don't know how to send invoices to it.

Deliverable: Supplier Communication Package

Send the following email to your top 20 suppliers (by invoice volume) no later than Day 77. Adapt the bracketed sections to your specific mandate and platform:

Subject: Updating how we receive invoices — e-invoicing transition for [Your Company Name]

Dear [Supplier Contact],

As of [Mandate Deadline — e.g., September 1, 2026], [Country] requires all B2B invoices to be issued in a structured electronic format ([Format Name — e.g., Factur-X, XRechnung, Peppol BIS]). To ensure uninterrupted payment processing, we need to update how we receive invoices from your organization.

What changes for you: Instead of sending a PDF by email, you will need to issue invoices in [format name] and transmit them via [method — e.g., our Peppol Access Point ID: XXXX, our Approved Platform: YYYY].

What stays the same: Our payment terms, approval process, and PO reference requirements remain unchanged. This update only affects the transmission format of the invoice document itself.

What we need from you now:
(1) Confirm whether you are already capable of issuing invoices in [format name].
(2) If yes, provide your Peppol Participant ID / routing identifier so we can register your connection.
(3) If not yet, share your estimated migration timeline.
(4) Confirm the contact person on your side for testing — we will schedule a test transmission with your team in [week range].

We have attached a one-page technical specification with the exact format requirements and our receiving identifiers. If you use an external accountant or billing service, please forward this information to them.

Please respond by [date — give 10 days] so we can schedule your testing window.

Best regards,
[Your Name / AP Team]

Testing: Week 1 (Days 76–82)

Select 5 pilot suppliers — ideally a mix: one large supplier already issuing structured invoices, one mid-size supplier transitioning, and one small supplier who will continue sending PDFs (to test your hybrid workflow).
Run end-to-end test for each: invoice arrives → format detected → data extracted/mapped → ERP field populated → approval workflow triggered. Time each step and document where manual intervention was required.
Test the exception paths: submit an intentionally invalid XML, a password-protected PDF, and a duplicate invoice. Confirm the exception handling defined in Phase 3 actually works.
Archive validation: confirm that compliant invoices are being archived in the original format with the metadata retention period required by each jurisdiction (generally 6–10 years depending on the country).

Adjust: Week 2 (Days 83–90)

Fix field mapping errors. The most common test failure is a field mapped to the wrong ERP column — a tax amount going into the net amount field, a supplier ID populating the invoice number column. These are configuration issues, not system failures, but they cause the same downstream reconciliation pain.
Update the supplier communication template with answers to the questions suppliers actually asked during the pilot — their real questions will reveal gaps in your original message.
Set your ongoing monitoring cadence: weekly review of (a) XML validation failure rate, (b) PDF-to-structured conversion accuracy, (c) duplicate flag rate, (d) supplier onboarding completion percentage. For organizations with a month-end close focus, our month-end close automation guide shows how to fold these metrics into your existing close cycle.

How to Evaluate Tools Without Getting Stuck in a Vendor Pitch

At some point during this 90-day process, you will need to decide whether your current ERP can handle e-invoicing or whether you need an external platform. Every vendor you talk to will tell you their solution handles "all formats in all countries." The evaluation framework below is designed to cut through that.

Ask every vendor — including your current ERP provider — these eight questions. Require specific answers, not marketing claims:

Question	What a Good Answer Looks Like	Red Flag
1. Which exact mandate jurisdictions does your platform cover natively — not through a partner integration?	"We natively handle Factur-X, XRechnung, KSeF XML, FatturaPA, and Peppol BIS Billing 3.0. Here is the list of jurisdictions and the API endpoints we connect to."	"We cover all of Europe through our partner network" — means you will be managing multiple vendor relationships.
2. Can I see a live demo of your platform ingesting an actual [Country X] e-invoice XML — not a marketing demo file?	A live screen-share showing a real, complex XML file being parsed, validated, and mapped to AP fields — with field-level mapping visible.	"We can send you a recorded demo" or "Our sales engineer will prepare one for the next call."
3. How does your platform handle the PDF invoices that arrive alongside structured e-invoices during the transition period?	"We process both in a single workflow: XML goes through schema-based extraction, PDFs go through visual AI extraction, and both produce the same output schema."	"We recommend you use a separate tool for PDF processing during the transition" — two systems, two processes, two places for errors.
4. What happens when a mandate format changes — who updates the schema, and how fast?	"We monitor regulatory changes across all covered jurisdictions. Schema updates are deployed within [X] days of government publication, with no action required from your side."	"You can update the mapping rules yourself in our configuration panel" — means you are the compliance department.
5. How do you handle tax registration number validation at the entity level for multi-entity organizations?	"We support entity-level tax ID configuration with per-entity format validation rules. Here is how our routing logic separates invoices by entity tax ID."	"Tax ID validation is handled by your ERP" — means you will be manually sorting invoices by entity before they enter the platform.
6. What is your actual supplier onboarding process — not the feature description, but the steps my suppliers will go through?	"We provide a supplier portal with self-service registration, bulk CSV upload for mass onboarding, and a dedicated supplier support team with [language] coverage. Average supplier onboarding time is [X] days."	"Suppliers just send invoices to our network" — no mention of registration, testing, or support.
7. What does your archiving solution cover — which countries' retention rules, in which formats, for how long?	"We archive the original XML/PDF in its native format plus a human-readable version, with retention periods configurable per jurisdiction. We comply with [specific archiving standards per country]."	"We store invoices for 7 years" — one retention period for all countries ignores that Germany requires 10 years and France requires 6 years for commercial documents.
8. Can you provide a reference customer who operates in the same mandate jurisdictions and has a similar supplier count?	"Here are two references with [X] suppliers across [countries], happy to connect you."	"We have customers in [unrelated industry] who love us" or "Our references are confidential."

The distinction between a tool you need and a tool being sold to you becomes visible in how a vendor answers question 3 — PDF handling during the transition. If their answer is "our platform handles e-invoicing; PDFs are a different problem," they are selling compliance infrastructure, not an AP workflow solution. A platform that only processes perfectly structured XML from Day 1 leaves your team dealing with the 40–70% of supplier invoices that will still arrive as PDFs through a second, disconnected process. For organizations evaluating whether their current extraction approach can bridge this gap, our Peppol explainer clarifies the distinction between the transmission network and the data formats that travel across it — understanding this is key to evaluating any platform's actual capabilities.

If early payment discounts are part of your AP strategy, the evaluation framework should include a ninth question: can the platform automatically detect and flag payment term discounts (2/10 Net 30) during the extraction step? Most e-invoicing platforms focus on compliance fields and ignore commercial terms. Losing visibility into early payment discounts during the format transition costs more than most compliance penalties. Our early payment discount automation guide covers the ROI of capturing these terms systematically.

If you take one thing from this section: The most expensive e-invoicing decision is not choosing the wrong platform. It is choosing a platform that covers compliance perfectly but leaves your team operating two separate AP processes — one for structured XML and one for PDFs — for the next three to five years while the transition plays out. The cost of that dual-process overhead, in labor hours and error rates, exceeds the cost of almost any platform licensing fee.

Appendix: Official E-Invoicing Resource Links by Country

Bookmark the official portals for each jurisdiction in your exposure matrix. Third-party summaries are useful for orientation, but the government portals are the authoritative source for format specifications, registration procedures, and deadline updates:

Country	System	Official Resource	What You'll Find There
Mexico	CFDI via SAT	sat.gob.mx	CFDI 4.0 technical specifications, PAC (Authorized Certification Provider) directory, digital certificate (e.firma) application
Brazil	NF-e via SEFAZ	nfe.fazenda.gov.br	NF-e technical manual, state-level SEFAZ web service endpoints, digital certification requirements, national NF-e repository
France	PPF + Plateformes Agréées	impots.gouv.fr	DGFiP official reform page, registered Approved Platform (PA) directory, annuaire (national recipient directory), Factur-X specification, BOFiP commentary
Germany	XRechnung / ZUGFeRD	ferd-net.de (ZUGFeRD) + xeinkauf.de (XRechnung)	ZUGFeRD specification and validation tools; XRechnung standard, technical documentation, and Peppol integration guidelines
Poland	KSeF (Krajowy System e-Faktur)	podatki.gov.pl/ksef	KSeF API documentation, testing environment (sandbox), token generation, mandatory field specifications, timeline updates
Italy	Sistema di Interscambio (SdI) / FatturaPA	fatturapa.gov.it	FatturaPA XML schema, SdI technical specifications, registration procedures, FatturaPA validation tools
Belgium	Peppol BIS	finances.belgium.be	B2B e-invoicing obligation scope, Peppol registration guide, grace period conditions, format requirements
Spain	Verifactu / Crea y Crece	agenciatributaria.es	Verifactu technical specifications, Crea y Crece implementation calendar, certified software registry
EU-wide	OpenPeppol / EN 16931	peppol.org	Peppol BIS Billing 3.0 specification, Access Point directory, transport infrastructure documentation, country-specific implementation guides

Frequently Asked Questions

Do I need a Peppol Access Point, or can I connect directly to each country's government platform?

It depends on the country. Belgium and Norway require Peppol for B2B e-invoicing. France's Approved Platforms use Peppol as the interoperability layer between platforms, so you don't need your own Access Point — your PA handles it. Poland's KSeF is a direct government API, no Peppol required. Germany accepts both XRechnung (via Peppol or direct) and ZUGFeRD (email). The country that hits your deadline first determines the architecture. If you operate in 3+ EU countries, a single Peppol Access Point that covers all of them reduces integration work. For organizations with one or two mandate countries, a direct connection or country-specific platform may be simpler.

Can I just keep processing PDFs and extract the data manually during the transition?

You can continue processing PDFs — many suppliers will keep sending them, and some small vendors never move to structured formats. The risk is not the PDF processing itself. The risk is operating two separate workflows: one for XML e-invoices that enter automatically and one for PDF invoices that require manual entry. When the same AP team is running two parallel processes with different cycle times, error rates, and visibility, reconciliation becomes the bottleneck. The practical approach is a single extraction layer that handles both formats and outputs the same structured data to the same downstream workflow. That way, whether a supplier sends XML or PDF is a format detail, not a process fork.

What if my ERP is 15 years old and my IT team says upgrading will take 12 months?

A full ERP upgrade is the maximum-compliance path but not the only path. A lightweight alternative: extract invoice data from both XML and PDF formats, standardize it, and import it into your ERP as structured data — the same way you would import a CSV file. The ERP doesn't need to know whether the original was XML or PDF; it only needs the mapped fields (supplier, date, amount, tax code, PO reference). This approach doesn't eliminate the need for a compliance transmission layer (you still need a way to receive structured e-invoices and archive the original format), but it decouples the compliance infrastructure from the ERP upgrade timeline. Your ERP upgrade can proceed on its own schedule without blocking your compliance deadline.

How do I handle suppliers who send the same invoice in both XML and PDF format?

This is the most common duplicate scenario during e-invoicing transitions — a supplier issues a compliant XML e-invoice but also emails a PDF copy "for your records." Your process needs duplicate detection logic that checks the invoice number, supplier identifier, and total amount across both channels. If the same invoice appears in both XML and PDF streams, the XML version takes precedence (it's the legally compliant document), and the PDF is discarded or archived without entering the payment workflow. The key is detecting the duplicate before both versions reach the approval step — once an approver opens the PDF, the automation has failed. For a complete approach to this problem, including detection rules and exception cases, see our duplicate invoice detection guide.

We only receive 10–20 invoices per month. Do we really need to do all of this?

The compliance obligation — your legal requirement to be capable of receiving structured e-invoices — does not scale down by invoice volume. A French auto-entrepreneur receiving two supplier invoices per month has the same September 2026 reception obligation as a CAC 40 company receiving 10,000. What does scale down is the complexity of your implementation. For a low-volume AP operation, the simplest path is often: register with an Approved Platform (or Access Point) that includes a basic web dashboard, receive invoices there, and extract the 6–8 fields you need manually or with a lightweight extraction tool. The 90-day framework still applies — the phases just execute faster because the mapping and testing scope is smaller. What you cannot do is ignore the obligation because your volume is low.

What happens if I miss the deadline?

Penalty structures vary by country. France imposes €15 per non-compliant invoice with an annual cap, and first infractions may receive a warning rather than a fine. Belgium has a grace period until March 31, 2026 for certain breaches where businesses demonstrate reasonable compliance efforts. Poland initially announced a sanction-free period during 2026 for KSeF. Italy's penalties range from 90% to 180% of the VAT amount for non-compliance. The fine amounts are rarely the real business risk. The real risk is operational: if you cannot receive structured e-invoices from a key supplier, that supplier may suspend deliveries, or your payments may be delayed, or you may lose early payment discount eligibility. Missing the deadline creates a supply-chain gap, not just a paperwork error. Check the official resource portal for each mandate country in the Appendix above for the current penalty schedule — these change as governments adjust enforcement policies.

After Day 90: What Ongoing Compliance Looks Like

Day 91 is not the end. E-invoicing mandates evolve — new countries come online, existing countries update their format specifications, and supplier populations churn. The 90-day readiness plan gets you to compliance for the mandates you face today. Staying compliant means building these three habits into your AP operations:

Monthly mandate scan: designate one person to check the official portals listed in the Appendix for each jurisdiction you operate in. A 15-minute monthly check catches format version updates, new deadlines, and registration requirement changes before they become emergency projects.
Quarterly supplier audit: review which of your active suppliers are still sending PDFs — that percentage should decrease over time as more suppliers adopt structured formats. Track it. If the percentage is flat after six months, your supplier communication or onboarding process needs attention.
Annual process review: once a year, re-run the Days 16–45 technical assessment against your current systems. ERP updates, new platform features, and changing mandate requirements mean the answer to "can our system handle this?" may have changed since last year.

The organizations that treat e-invoicing as a one-time compliance project are the ones that discover, eighteen months later, that their platform doesn't support the country that just came online and their supplier PDF percentage never dropped below 40%. The 90-day plan gets you through the door. The ongoing discipline keeps you in the room.