[FIX] saudi_arabia: add warning about company name length #16211
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have had lots of tickets recently about failed ZATCA onboarding. One of the most common reasons is that the company or branch name is too long compared to the strict limits imposed by zatca. As for the limits, they are technical, imposed by the QR code generated for every invoice. The limit itself is 127 bytes, which depending on the exact arabic characters used can range from 42 to 63 arabic characters. 63 is in the best-case scenario where we can encode all characters on 2 bytes. 42 characters is the worst-case scenario where special characters requiring 3 bytes are used. In an effort to keep our documentation concise and clear, we chose to stick to the best-case scenario of 63 characters, assuming that would be the most common scenario. Pull requests have been made in the main codebase to make the error messages clearer upon failed onboarding, which should cover the "42 characters edge cases". X-original-commit: 44040b9
Collaborator
|
|
Collaborator
Author
|
This PR targets saas-18.2 and is part of the forward-port chain. Further PRs will be created up to master. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
robodoo
pushed a commit
that referenced
this pull request
Feb 2, 2026
We have had lots of tickets recently about failed ZATCA onboarding. One of the most common reasons is that the company or branch name is too long compared to the strict limits imposed by zatca. As for the limits, they are technical, imposed by the QR code generated for every invoice. The limit itself is 127 bytes, which depending on the exact arabic characters used can range from 42 to 63 arabic characters. 63 is in the best-case scenario where we can encode all characters on 2 bytes. 42 characters is the worst-case scenario where special characters requiring 3 bytes are used. In an effort to keep our documentation concise and clear, we chose to stick to the best-case scenario of 63 characters, assuming that would be the most common scenario. Pull requests have been made in the main codebase to make the error messages clearer upon failed onboarding, which should cover the "42 characters edge cases". closes #16211 X-original-commit: 44040b9 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> Signed-off-by: Victorien Sonneville (viso) <viso@odoo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have had lots of tickets recently about failed ZATCA onboarding. One of the most common reasons is that the company or branch name is too long compared to the strict limits imposed by zatca.
As for the limits, they are technical, imposed by the QR code generated for every invoice.
The limit itself is 127 bytes, which depending on the exact arabic characters used can range from 42 to 63 arabic characters. 63 is in the best-case scenario where we can encode all characters on 2 bytes.
42 characters is the worst-case scenario where special characters requiring 3 bytes are used.
In an effort to keep our documentation concise and clear, we chose to stick to the best-case scenario of 63 characters, assuming that would be the most common scenario.
Pull requests have been made in the main codebase to make the error messages clearer upon failed onboarding, which should cover the "42 characters edge cases".
Forward-Port-Of: #16196