Comments (5)
I do not see this as an error.
Buyer electronic address is 0..1 in EN16931
This is the address to which the invoice has to be sent.
You may have confused with Contact email address (which is also 0..1 in fact)
No modification has to be done.
from einvoicing-en16931.
I do not see this as an error. Buyer electronic address is 0..1 in EN16931 This is the address to which the invoice has to be sent.
You may have confused with Contact email address (which is also 0..1 in fact) No modification has to be done.
@csautereau Thanks for your opinion. However please try out the example invoice or read my post carefully.
Hint: Failed validation != Working validation with rejection
from einvoicing-en16931.
I have tried your example.
The schematron gives an error with an invoice with more than one
ram:URIUniversalCommunication
<ram:URIID schemeID="EM">[email protected]</ram:URIID>
</ram:URIUniversalCommunication>
On BUYER (and any Party).
If I delete the secund email on your invoice example, validation passes fine.
Then the error is to provide 2 ram:URIUniversalCommunication, which is not allowed for EN16931.
Now the rule is "
The Buyer electronic address (BT-49) shall have a Scheme identifier.
If I delete the shemeID="EM" in your example corrected (only 1 ram:URIUniversalCommunication), then schematron rejects with the comment :
[BR-62]-The Seller electronic address (BT-34) shall have a Scheme identifier.
Which is normal as your example in fact plays with ram:URIUniversalCommunication of the Seller (and not the buyer)
To finish, If if delete the shemeID="EM" for the Buyer (BT-49, the result is also a mistake with comment
[BR-63]-The Buyer electronic address (BT-49) shall have a Scheme identifier.
Conclusion for me : Schematron is correct on the control of SchemeID presence for Party's Electronic Address (BT-49, BT-34) and also on cardinalities which must be 0..1 (and not multiple)
KR
from einvoicing-en16931.
@csautereau There is a difference between a crashing schematron and a schematron that found errors in the invoice.
I don't care whether the invoice should be rejected or accepted, but the bug is that, because of the buggy rule, the schematron crashes and is unable to generate a correct report.
Try for yourself and add other schematron errors into the invoice, e.g. BR-CO-10. Those should now be reported as well.
Also look at the output for my example invoice. Is the rule stated, which was wrong, i.e. ?
from einvoicing-en16931.
The rule is improved with a [1] to check for the first occurrence of the URIUniversalCommunication avoiding crashes. This will not raise any error in case there are more than one URIUniversalCommunication in the document instance. In order to check for this two new rules have been added in the EN16931-CII-Syntax. CII-SR-459 and CII-SR-460 to warn in case more than one URIUniversalCommunication exist.
from einvoicing-en16931.
Related Issues (20)
- Undocumented and missing changes in v.1.3.11 release HOT 3
- BR-33 / BR-CO-21 rules validation doesn't work on CII files (OK on UBL files) HOT 1
- Tolerance of 1 € on BR-S-09 HOT 2
- BT-32 path check missing in BR-AE-02, BR-AE-03, and BR-AE-04 in CII HOT 1
- Code list changes
- ISO 4217 VEF/VES
- Commit did overwrite PR changes
- CII special ID elements without attributes - not handled correctly
- VAT Category "B" supported even though it is not in the EN
- Contradicting message
- ISO 4217 HRK / Kuna
- Artefacts v1.3.12 (CII) do not check BR-62 / BR-63 correct any more HOT 2
- Allow code 106 (Withheld taxes and social security contributions) on Allowance code list 5189
- BR-CO-15 for correct amounts HOT 1
- Invoice Content: Romania Commercial Registaration No. of the Customer (Legal requirment)
- Error with a validation with xsl HOT 1
- br-co-25 check does not match description HOT 5
- CII Schematron - BT-8 - [CII-SR-462] - Only one DueDateTypeCode shall be present - Not well implemented - URGENT HOT 7
- codes_validation_BR-CL-23_weakness HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from einvoicing-en16931.