-
-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHORUS PRO #612
Comments
please specify the version you are using. CC : @alexis-via |
Version 16
Philippe HERRGOTT
*Intégrateur Odoo*
*www.effiscience.eu <http://www.effiscience.eu/>*
[image: mobilePhone] +33 6 79 70 88 90 <+33+6+79+70+88+90>
Le mar. 21 janv. 2025 à 10:01, Sylvain LE GAL ***@***.***> a
écrit :
… please specify the version you are using.
CC : @alexis-via <https://github.com/alexis-via>
—
Reply to this email directly, view it on GitHub
<#612 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAGWYQXLZUSKK54XZPP4P432LYEF7AVCNFSM6AAAAABVRXC6X2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBUGA2TSMJUGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
We are working on odoo version 16 We are using CHORUS Version 16.0.1.0.0 |
If the module account_edi_ubl_cii is installed, you must uninstall it first. And then it will work, because you will be using the OCA implementation of factur-x and NOT the native implementation of factur-X, which has a faulty XML. |
Thanks a lot but it didn't solve the problem. I decided to use CII format instead of factur-x pdf and it works better. I had some issues that I solved but still one remaining. |
We use Chorus pro module to send our invoices into the platform.
Since few days all our invoices are rejected and we don't understand why.
We have this error message : "L'element FichierXml.SupplyChainTradeTransaction.ApplicableHeaderTradeSettlement.SpecifiedTradeSettlementPaymentMeans.TypeCode.value est obligatoire."
We checked in our xmlfile and we found this
How can we fix this issue?
The text was updated successfully, but these errors were encountered: