Country Regulation Entry
CFO · Finance Lead · Tax Manager
User found a country-specific page that directly addresses their search query about French e-invoicing obligations. They need to know: am I affected, what format, and by when?
User searched "France e-invoicing mandate 2026" — they need compliance clarity for a specific country.
After seeing the mandate, they want to understand the format. Related standards are surfaced on the country page — e.g., Factur-X for France.
Required Format
Factur-X — France's Mandated Standard
EN 16931-compliant hybrid format: PDF + embedded XML.
After understanding the format, they need a provider. The provider shortlist CTA appears at the bottom of every country and standard page.
Provider Shortlist Request
Get matched with vetted e-invoicing providers for France, Factur-X, and your ERP.
Request Provider ShortlistCountry Readiness Checklist
10-point assessment for France: legal, ERP, format, timeline.
Get France Readiness ChecklistUser confirms obligation → understands format → requests vendor shortlist. Conversion: Provider Shortlist Form submission.
Standard Understanding Entry
Tax Manager · Compliance Manager · ERP Owner
User is trying to understand what Peppol BIS 3 is, how it relates to EN 16931, and which countries use it. They need conceptual clarity before operational planning.
User searched "Peppol BIS 3 explained" — they understand e-invoicing requires structure, but need to understand the standard landscape.
After understanding the standard, they need to know: which countries mandate this standard? The standard page surfaces countries using it.
Countries Using Peppol BIS 3
Where Peppol Is Mandated or Accepted
7 countries across Europe and Asia-Pacific use Peppol BIS 3.
With standard and country knowledge, they need to choose a route. The route page shows all four approaches with complexity indicators.
Peppol Network Route
medium complexitySend invoices via the global Peppol e-delivery network.
The Peppol network is a global e-invoicing infrastructure connecting businesses, governments, and ERP systems across 40+ countries. To use Peppol, you need a Peppol ID (obtained through a Peppol Registration Authority) and an access point subscription. Peppol handles routing, delivery confirmation, and interoperability.
How It Works
1. Generate your invoice in Peppol BIS 3.0 format. 2. Send it to your Peppol access point. 3. The access point routes the invoice to the recipient's access point using the Peppol network. 4. The recipient's system receives and processes the invoice. 5. Delivery receipt is returned to you.
Pros
- Global coverage across 40+ countries
- Standardized format ensures interoperability
- Built-in delivery and read receipts
- No need to manage bilateral integrations with each partner
- Growing network effect — more recipients joining daily
Considerations
- Access point subscription cost
- Requires Peppol BIS 3.0 format compliance
- Some countries have additional national format requirements
User understands Peppol → identifies countries → selects Peppol route → requests provider shortlist.
ERP Implementation Entry
ERP Owner · Implementation Lead · Technical Architect
User manages SAP S/4HANA and needs to understand how to configure it for German e-invoicing. They are technically focused and need implementation specifics.
User searched "SAP e-invoicing Germany" — they manage the ERP and need technical configuration guidance for a specific mandate.
The ERP page links to country-specific requirements. For SAP Germany, the ERP page surfaces German mandate details.
Germany
B2G MandatoryXRechnung required for all B2G invoices
With ERP capability confirmed and country requirements clear, they need a structured technical implementation plan. The ERP checklist provides this.
SAP S/4HANA Implementation Checklist
- 01
Enable output management configuration
Critical TechnicalConfigure the output management framework in SAP S/4HANA to generate XML-based invoices.
- 02
Map ERP fields to EN 16931 BT codes
Critical TechnicalUse BRF+ or output type configuration to map SAP invoice fields to mandatory EN 16931 data elements.
- 03
Install SAP Document Compliance (if needed)
TechnicalFor France, Italy, Spain — install and configure the country-specific compliance module.
User confirms SAP capability → understands Germany requirements → follows technical checklist → requests shortlist for access point.
Route Decision Entry
CFO · Finance Lead · ERP Owner
User is looking for vendor options but has been educated that route selection comes before provider selection. They need to understand: Peppol vs API vs Portal.
User searched "e-invoicing provider Belgium" — but vendor lists without route understanding lead to poor decisions. This page educates first.
Global Electronic Invoice Regulatory Intelligence
Navigate mandatory e-invoicing requirements by country, standard, and ERP system. Independent reference for finance, tax, and compliance teams.
A side-by-side comparison table shows complexity, country coverage, and ideal use cases for each route — helping users self-select.
| Route | Complexity | Countries | Best For |
|---|---|---|---|
| Peppol Network Route | medium | france, germany, belgium, netherlands, uk, australia, singapore | Businesses with international operations |
| Direct API / Government Portal Route | medium | france, italy, spain, germany | Single-country operations |
| Clearing House / PDP Route | high | france, italy | French or Italian businesses with B2B transactions |
| Hybrid / Multi-Route Approach | high | france, germany, italy, spain, belgium, netherlands, uk | Multi-national organizations |
After selecting a route, the user submits the provider shortlist form. Route preference is captured as a form field.
Provider Shortlist Request
Tell us your country, ERP, and route preference. We'll match you with vetted providers.
Request Provider ShortlistUser understands route → selects route → submits shortlist form with country + ERP + route preference.
Time-Pressured Entry
CFO · Finance Lead · Tax Manager
User is under time pressure — Belgium's January 2026 mandate is approaching and they need rapid clarity on obligations and immediate next steps.
Urgency-driven search. They know Belgium has a deadline and need to confirm: am I in scope, what do I need to do, how fast?
With deadline confirmed, they need a structured plan. Implementation checklist + milestone timeline provide the urgency + clarity they need.
Upcoming Milestones
Belgium E-Invoicing Timeline
Implementation Checklist
- 01
Register on Mercurius platform
Critical LegalMercurius is Belgium's central e-invoicing platform. Register to send and receive compliant invoices before the mandate date. Source: Belgian Federal Public Service Finance.
- 02
Determine if your turnover triggers Phase 1
Critical LegalIf annual turnover exceeds €85,000, you are in the first phase of the B2B mandate starting January 2026. Source: Belgian e-invoicing legislation (KB/KB of 2024).
- 03
Select e-invoice format
Critical TechnicalBelgium mandates UBL 2.1 as the primary format, with XRechnung also accepted as it aligns with EN 16931. Source: Belgian Ministry of Finance e-invoicing framework.
Under deadline pressure, they want rapid vendor evaluation. The shortlist form with timeline field captures their urgency.
Provider Shortlist — Belgium
Get matched with providers supporting Belgium UBL 2.1 + Peppol, fast.
Request Shortlist — UrgentBelgium Readiness Checklist
10-point plan to meet the Jan 2026 deadline. Download now.
Download ChecklistUser confirms urgency → gets structured plan → requests shortlist with immediate timeline. High-intent conversion with "within 1 month" urgency.
Global Journey Flow Diagram
All five user journeys converge on the same conversion point: the provider shortlist form. The diagram below shows how each path leads there.
Entry Points
Content Layer
Conversion Point
Component & Block Reference
All UI modules used above, with their data source references and usage rules.
StatusBadge
Data: status field from Country.status
AISummaryBox
France is rolling out mandatory electronic invoicing and e-reporting in phased stages. B2G mandatory e-invoicing through Chorus Pro has been in effect since 2020. The B2B e-invoicing mandate is being introduced progressively: the receiving obligation begins for all companies on 1 September 2026, and the issuing obligation begins on 1 September 2026 for large and mid-sized companies, extending to SMEs and micro-companies on 1 September 2027. Businesses must use either Factur-X (a PDF with embedded XML, widely preferred for its readability) or UBL 2.1 (pure XML). Invoices are transmitted via the Chorus Pro portal, the PEPPOL network, or through registered approved service providers (PDP). The platform requirements and scope of the clearing model continue to be clarified by DGFiP.
Grounded in official sources listed below. Not a substitute for legal or tax advice.
Data: aiSummary from Country | Standard | ERPSystem
QuickAnswerBox
Quick Answers
Data: quickAnswer[] from content data files
SourcesBox
Official Sources
All information on this page is based on the sources listed below. Always verify current requirements with the issuing authorities.
- Factur-X — Official Specification Standard Body
Cross-sector e-invoice standard in France; mandate basis for B2B/B2G
- Chorus Pro Portal Government
French government e-invoicing portal; mandatory registration for B2G and B2B
- Loi de Finances 2020 — Article 153 Government
Legal mandate basis for mandatory e-invoicing in France
Data: officialSources[] — structured Source[] with publisher, sourceType, lastChecked
DisclaimerBox
Global disclaimer from siteConfig.disclaimer — required on all content pages
InfoBlock
Data: Derived from Country, Standard, ERPSystem fields
HookCard
Data: ContentHook[] — has targetIntent and nextStepCta fields
ImplementationChecklist
Implementation Checklist
- 01
Register on Chorus Pro
Critical LegalCreate an account on the French government e-invoicing portal (Chorus Pro). Required for all B2G invoices and mandatory for B2B under the phased rollout beginning September 2026. Source: Chorus Pro is operated by the Direction Générale des Finances Publiques (DGFiP).
- 02
Select an e-invoicing format
Critical TechnicalChoose between Factur-X (PDF + XML, cross-sector) or UBL 2.1 (pure XML). Most businesses use Factur-X for its PDF readability. Source: AFNOR specification for Factur-X.
Data: implementationChecklist[] from Country | ERPSystem
Breadcrumb
Dynamic: constructed per page from URL hierarchy
DeadlineBanner
Data: effectiveDate, mandatePhase, status from Country
ProviderRouteBox
Peppol Network Route
medium complexitySend invoices via the global Peppol e-delivery network.
The Peppol network is a global e-invoicing infrastructure connecting businesses, governments, and ERP systems across 40+ countries. To use Peppol, you need a Peppol ID (obtained through a Peppol Registration Authority) and an access point subscription. Peppol handles routing, delivery confirmation, and interoperability.
How It Works
1. Generate your invoice in Peppol BIS 3.0 format. 2. Send it to your Peppol access point. 3. The access point routes the invoice to the recipient's access point using the Peppol network. 4. The recipient's system receives and processes the invoice. 5. Delivery receipt is returned to you.
Pros
- Global coverage across 40+ countries
- Standardized format ensures interoperability
- Built-in delivery and read receipts
- No need to manage bilateral integrations with each partner
- Growing network effect — more recipients joining daily
Considerations
- Access point subscription cost
- Requires Peppol BIS 3.0 format compliance
- Some countries have additional national format requirements
Data: ProviderRoute[] from providers.ts — has officialSources[]
ShortlistForm
Request Provider Shortlist
Tell us about your requirements and get matched with vetted e-invoicing providers. We'll recommend options based on your country, ERP, and route preferences.
Form fields from ContentHook.h3-provider-shortlist.formFields
Data Source → Component Mapping
| Content Type | File | Key Fields for UI | Journey Role |
|---|---|---|---|
| Country | countries.ts | status, formats[], mandatePhase, officialSources[], relatedStandards[], primaryHook | Entry point A, E |
| Standard | standards.ts | shortName, category, countriesUsing[], officialSources[], relatedCountries[] | Entry point B |
| ERP System | erpSystems.ts | name, nativeEInvoiceSupport, applicableCountries[], officialSources[], relatedCountries[], relatedStandards[] | Entry point C |
| Provider Route | providers.ts | name, complexity, countriesApplicable[], officialSources[], relatedCountrySlugs[], relatedStandardSlugs[] | Conversion layer (all paths) |
| Content Hook | contentHooks.ts | name, ctaLabel, targetIntent, nextStepCta, formFields[] | Conversion trigger (all paths) |
| User Journey | userJourneys.ts | searchIntent, entryPage, entryReason, nextClick, conversionPoint | UI annotation & documentation |