Skip to main content
Question

We are in 24R1 and for eInvoice our IFS does not support the new format for France Mandate . how other companies are handling this?

  • September 4, 2026
  • 2 replies
  • 37 views
Do Gooder (Customer)
Forum|alt.badge.img+2

We are implementing Pagero for e-invoicing in France, we are in version 24R1 and our version does not support the UBL format, we know the new format is available in version 25R2 (which we cannot update at this moment), can we request this structured file in a patch? or how do other IFS customers are handling this issue. 

 

thanks, 

 

    2 replies

    Hero (Customer)
    Forum|alt.badge.img+10
    • N.GEORGI
    • Hero (Customer)
    • September 6, 2026

    We handled the situation outside of IFS.

    For the supplier invoice, we recovered the invoice through the ETL and imported it into IFS as an STDSIN.

    For the customer side, we created the UBL ourselves outside of IFS by querying the invoice database.

      Hero (Employee)
      Forum|alt.badge.img+10
      • Jane Perry
      • Hero (Employee)
      • September 8, 2026

      Hi.  I found the following information -

       

      Navigating the French e-invoicing mandate (B2B / PPF / PDP requirements) while on IFS Cloud 24R1 is a common challenge for companies preparing for the compliance deadline.

      The native localized UBL 2.1 / Factur-X outbound e-invoicing capability for France (developed under R&D initiatives such as IP-3769: Support e-invoice compliance in France) was targeted natively for 25R2.

      Below is a detailed breakdown of how other IFS customers handle this, whether a patch can be requested, and the practical workarounds available today.

      1. Can You Request the Structured UBL File as a Patch in 24R1?

      • Standard Backport Policy: Generally, IFS delivers major new regulatory localizations (such as full French UBL 2.1 compliance) in the latest core release tracks (25R2). Standard Service Updates (SUs) on older tracks like 24R1 typically cover bug fixes rather than full backports of new localization feature sets.

      • Raising a Support Case / CCR (Critical Core Request): You can and should submit a support ticket / Service Request to IFS Support. If the missing UBL format blocks legal compliance, IFS R&D evaluates whether specific core patch corrections or localized transformation files can be released as an extension or patch for your 24R1 Service Update track.

      2. How Other IFS Customers Are Handling France e-Invoicing on 24R1

      Because many organizations on 24R1 or 24R2 cannot immediately upgrade to 25R2, they utilize one of three primary approaches:

      Approach A: Pagero Online Data Transformation & Enrichment (Most Common)

      Since you are implementing Pagero (IFS’s official global e-invoicing partner and certified PDP - Plateforme de Dématérialisation Partenaire):

      1. Send Standard Outbound XML from IFS 24R1: Configure IFS Cloud 24R1 to export the standard available invoice XML (e.g., IFSFinvoice XML or standard Peppol BIS 3.0 XML).

      2. Transform in Pagero: Pagero’s integration engine ingests the 24R1 XML and transforms/maps it into the compliant French UBL 2.1 / Factur-X / EN 16931 format required by the French PPF (Portail Public de Facturation).

      3. Enrich Missing Tags in Pagero: Mandatory French tags that may be absent in 24R1 (such as specific French legal notices, SIREN/SIRET numbers, or line-level tax categories) can be enriched directly within Pagero using mapping rules, master data lookups, or static translation tables.

      Approach B: IFS Connect XSLT Transformer (In-House XML Mapping)

      If you prefer the XML file leaving IFS Cloud to already reflect the UBL structure before reaching Pagero:

      • Use IFS Connect to create a custom XSLT Transformer.

      • The transformer intercepts the standard outbound invoice message payload (CustomerOrderInvoice or InstantInvoice) and reshapes the XML structure into UBL 2.1 format before transmitting it via the outbound HTTP/REST routing address.

      Approach C: Aligning the Upgrade Roadmap Ahead of Mandatory Deadlines

      • The French General Directorate of Finance (DGFiP) shifted the mandatory B2B e-invoicing timeline (phased rollout starting in September 2026).

      • Many IFS customers use the intervening time to schedule their IFS Cloud Release Update from 24R1 to 25R2, ensuring they go live on a version that natively generates compliant UBL files without needing custom mapping layers.

      1. Engage Your Pagero Integration Team: Work with Pagero to confirm whether they can map your existing 24R1 IFSFinvoice or standard e-invoice XML into the French UBL 2.1 format on the Pagero portal layer.

      2. Open an IFS Support Case: Submit a case with IFS Support referencing French e-invoicing compliance on 24R1 to request official guidance or potential patch availability.

      3. Review Release Update Timeline: Evaluate upgrading to 25R2 before your French go-live date to take advantage of native compliance.

       

      I hope this information helps.  Thanks!  Jane

      Terms & ConditionsAccessibility statement