Skip to main content
Question

Generation of UBL invoices in France

  • July 31, 2026
  • 4 replies
  • 107 views
Do Gooder (Customer)
Forum|alt.badge.img+4
  • Tonio
  • Do Gooder (Customer)

Hello everyone,
I’m completely lost.

I’m using IFS Cloud 25R2 and I’m desperately trying to generate a UBL invoice in the French format.

First of all, I’ve correctly configured a customer for an E-INVOICE output.
Next, I created an OUT routing rule (first with a message_type = E-INVOICE_FR, then SEND_UBL_EINVOICE_LIFE_CYCLE_EVENT), an IFS_FINVOICE_TO_IFS_EINVOICE transformer, a routing address (functional, FinvoiceUBL_%TAG=INVOICE_ID%_%TAG=C06%.xml) and, finally, a sender).

When I send an invoice to this customer, an XML file containing the customer’s invoice data is indeed written to disk, but it does not conform to the template required by the French government.

Does anyone have a document setting out all the configuration steps required to successfully generate an invoice in the French UBL format? I’ve been searching through the documentation, but nothing I’ve tried has worked.

Thank you for your help.

4 replies

Sidekick (Employee)
Forum|alt.badge.img+8

Hi ​@Tonio ,

Have you referred to the France Country Solution which contains useful information on the setup?

https://docs.ifs.com/ifsclouddocs/25r2/lang/en/CountrySolutions/CountrySolution_pdf/FranceCountrySolution.pdf - 6 E-invoice & E-reporting

 

Also there are some on going issue corrections relevant to the template requirements as well.
 

 

Hope above are useful.

Best regards,

Shamalaka Perera

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

​@Tonio 

I have tested up to version 25R2.6. At this stage, the UBL output generated by IFS is not compliant with the new France regulations.

It seems that the required fixes are included in version 25R2.7.

 

You need to develop a transformer or generate the UBL File outside of IFS.

Do Gooder (Customer)
Forum|alt.badge.img+4
  • Tonio
  • Author
  • Do Gooder (Customer)
  • September 9, 2026

Hello everyone,

Good news for everyone in France.

The UBL invoice works with IFS 25R2 9 ; released after 15 August 2026…

It requires a few configuration steps, but we finally have an XML document – admittedly incomplete, but correct.

I’m finalising my documentation and then I’ll be able to share my experience.

To be continued...

    Sidekick (Customer)
    Forum|alt.badge.img+8
    • MCIPSTEV
    • Sidekick (Customer)
    • September 14, 2026

    Hello everyone,

    Good news for everyone in France.

    The UBL invoice works with IFS 25R2 9 ; released after 15 August 2026…

    It requires a few configuration steps, but we finally have an XML document – admittedly incomplete, but correct.

    I’m finalising my documentation and then I’ll be able to share my experience.

    To be continued...

    In my opinion it is still not working:

    1. some schemID are missing and on the wrong nodes
    ERRORS
    **** For SELLERS schemeID="0002"
    [BR-62]-The Seller electronic address (BT-34) shall have a Scheme identifier.
    /Invoice[1]/AccountingSupplierParty[1]/Party[1]/EndpointID[1]

    Example
    Value generated
    <cbc:EndpointID>XXX_YYY_zzz</cbc:EndpointID>

    Should be replaced by
    <cbc:EndpointID schemeID="0002">xxx_zzz</cbc:EndpointID>

    **** For BUYERS
    Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-63/
    BR-63
    Message
    The Buyer electronic address (BT-49) shall have a Scheme identifier.
    Example:
    Value generated
    <cbc:EndpointID>xxx_yyy_zzz</cbc:EndpointID>

    Should be replaced by
    <cbc:EndpointID schemeID="0225">xxx_yyy</cbc:EndpointID>


    Legal specification can be found here: https://docs.peppol.eu/poacc/billing/3.0/codelist/eas/e

     

    1. the document type French e-invoicing UBL export – Incorrect generation of attachment information in AdditionalDocumentReference section

      The EN 16931 specification strictly limits the permitted values for the <cbc:DocumentTypeCode> element within <cac:AdditionalDocumentReference>:

      Code 130 is mandatory when referring to an invoiced object, such as a vehicle registration or utility meter.
      Code 50 is reserved exclusively for project references.
      For standard supporting documents or attachments, such as a commercial invoice attachment, the EN 16931 syntax requires the <cbc:DocumentTypeCode> element to be omitted entirely.
      Using ATS in this context will therefore trigger an immediate Schematron validation rejection on compliant platforms.

      This is a legal and compliance requirement. As the current software implementation does not comply with the EN 16931 specification, we are currently unable to send invoices to our customers. We urgently request that the R&D team investigate and resolve this issue as soon as possible.

     

    1. Compulsory tags are  still missing like #AAB# it should have been integrated in 25R2SU09


     

     

    Terms & ConditionsAccessibility statement