Monday, February 2, 2026
1 change · saas-18.2
Enhancements to existing features
Saudi e-invoicing onboarding now checks company certificate request fields before sending them to ZATCA and handles incomplete error responses more gracefully. Users receive a clear, informative message instead of a technical crash when ZATCA rejects invalid onboarding data.
Original PR description
Previously, it was assumed that if no 'error' or 'errors' key was present that means we've received a valid response for obtaining CCSID or PCSID. But sometimes the error is not sent with those keys, and the binarySecurityToken is missing, therefore a traceback is shown to the user because the invalid requests passes through the validation unnoticed. This kind of response is the result of a new change introduced by zatca requiring csr fields to be at most 64 characters long. This commit improves the error handling mechanism of CSID responses, to show the user an informative message, and handles the length check for csr fields on the client side before sending to zatca. task-5347269 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246343 Forward-Port-Of: odoo/odoo#244507