In fact, its a technical problem. You must integrate with their API. https://communaute.chorus-pro.gouv.fr/documentation/api-implementation-guide/?lang=en https://communaute.chorus-pro.gouv.fr/documentation/external-specifications/?lang=en https://communaute.chorus-pro.gouv.fr/wp-content/uploads/2018/06/Specifications_Externes_Annexe_Processus_de_facturation_V4.00.pdf https://communaute.chorus-pro.gouv.fr/wp-content/uploads/2017/08/AIFE-Chorus-Pro-Le-mode-EDI_Annexe-1.pdf https://communaute-chorus-pro.finances.gouv.fr/?action=publicPage&uri=intranetOnePage/4003

Thanks for the answer I was able to download an xsd file which seems to describe the structure is it someting I can import into uniface to generate this structure ? if yes how do i do it Dominique

If your import requires the specification of a lot of uniface entities, you can use a mailmerge program or awk to convert the xsd-information into a *.CIF file and use the "case load" functionality to generate these entities. Beauty of this way is that the CIF file needs only minimal information, but adds a lot of standard uniface trigger code in this loading process. Unfortunately, the last time the CIF format was documented in 1999 (cbc.pdf under 7.2.06) but you can contact me, Uli  

A small example: * CIF:2.0 ; Uniface CASE Interface Format file ; Generated by the UNIFACE CASE unload facility, 26-12-2012 16:49:45 EX CIF_MINI2 #D Y #I C* #R N #U Y #Z DEF FX MSGID #B MsgId #D Y #I C35 #T S #ED FX AFIELD #X 7 #B Labeltext #D Y #I C1 #T S #ED Just a more or less FX BFIELD #X 6 #B Label #D Y #I N1 #T N #ED a description FX DFIELD FX GFIELD FX EFIELD KX 1.CIF_MINI2 #F MSGID #Y P