-
Notifications
You must be signed in to change notification settings - Fork 55
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
Validation error BR-CO-16 #255
Comments
See #242 on a work around |
I could add the workaround, but to bad I have to throw away my time because your group have messed up your release. I have got lots of error reports from other accesspoint now using this latest release. |
There is no process to have hotfixes for EN16931? @phax |
Passing this on to @oriol - I am no longer actively involved. Just commenting on a voluntary/personal basis |
Ah good to know, thanks Philip! :) |
The problem is not only on fixing the EN16931 validation artefacts but also on how they are adopted and used in different user communities. We decided to publish a note instead of issuing a hotfix release of the 1.3.3 because it could have caused a negative impact on organizations alreeady using them. Based on your new input, we will work again on the process for hotfixes and will take action on this particular issue. Thanks @phax for your support on this. |
Duplicated from #242 |
A customer has sent an invoice as shown below. I can’t see anything wrong with it but for those who have upgraded to the latest version of the validator artifacts it says its wrong:
0.00 (PayableAmount – BT-115) = 4500.00 (TaxInclusiveAmount – BT-112) - 4500.00 (PrepaidAmount – BT-113) + 0.00 (PayableRoundingAmount – BT-114)
In my head this is 0.00 = 0.00
The text was updated successfully, but these errors were encountered: