Skip to main content
Question

French E-Invoice Transformer IFS Connect

  • January 29, 2026
  • 6 replies
  • 47 views

Forum|alt.badge.img+9

We are planning to implement the French e-Invoicing solution using IFS version 24R1, with an upgrade to version 25R2 planned around May.

Our partner will provide supplier invoices in XML format.

We have started reviewing the following documentation:

https://docs.ifs.com/techdocs/24r1/030_administration/030_integration/330_ifs_applications_business_components/022_configure_receiving_ifs_e-invoices/

However, we would like to understand how to convert the partner-provided XML into a structure that IFS can process. How should the XML fields be mapped to the corresponding fields in IFS?

Do we need to use a transformer for this purpose? If so, could you please explain how to create one and point us to any relevant documentation.

 

Thank you in advance

6 replies

Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • May 26, 2026

Hello

Have you found a solution?


Forum|alt.badge.img+9
  • Author
  • Hero (Customer)
  • May 26, 2026

@jgiroud  We have implemented a hybrid solution.

We retrieve the XML file from the e-invoicing partner (which is not in UBL format) and then convert it into an STDSIN file that is consumed by IFSCONNECT.


Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • May 26, 2026

Thank you for your prompt reply

Have you completed the migration to 25R2?
If so, which service pack did you install?


Forum|alt.badge.img+9
  • Author
  • Hero (Customer)
  • May 26, 2026

@jgiroud 

No, we haven’t. It got postponed to October.


Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • May 26, 2026

And for French e-invoicing, have you created any custom fields?
If so, how did you go about incorporating them into the transformer?
Sorry for all these questions, but it’s difficult to find answers to them 


Forum|alt.badge.img+9
  • Author
  • Hero (Customer)
  • May 26, 2026

@jgiroud 

Since we are still using version 24R1, we are not using the IFS Connect e-invoice functionality.

From my understanding, compliance is expected starting from version 25R2.5; however, some clients have indicated that it may still not be fully compliant.

 

Custom fields have already been mentioned here, but there hasn’t been a clear explanation of how to implement them

 

We have applied the same hybrid principles as before.

For supplier invoices, our external tool generates the STDSIN file, which is then integrated into IFS through IFS Connect. Afterwards, the external tool enriches the invoices that have been created if custom fields are present ont he supplier invoice sides.

 

The same principles apply to customer invoices.

The UBL file is generated outside of IFS using an external tool.

The tool reads all invoices that were created and sent the previous day, generates the corresponding invoice files accordingly, and then sends them to the e-invoicing platform.

 

 

If you like to modify an existing transformer : 

https://docs.ifs.com/techdocs/25r2/060_development/024_integration/015_connect/050_transformer/020_about_transformer_dev/?h=transformer+deve#how_to_develop_a_transformer

https://docs.ifs.com/techdocs/25r2/060_development/024_integration/015_connect/050_transformer/200_workflow_java_transformer/