- Shared by
- Juha Ikävalko Netum Integrations Oy
- Shared with
- John Smith @companyx.com
|Profile||UBL 2.0 Invoice - DEMO|
Instance failed 4 test phases
|Instance||UBL-Invoice-2.0 sample with errors.xml|
Preconditions for this test case. These condition must be fullfilled to continue to actual validation.
Validation for basic UBL message requirements. There is no point to continue validation if these requirements are not fulfilled.
Validation against UBL-Invoice-2.0 W3C XML Schema provided by OASIS.
Validation for elements/data which must exist on each Invoice message.
Validation for data format constraints.
Validation for integrity constraints.
- Phase must be passed to continue validation
- Phase must be passed to pass the test successfully
- Phase provides informative feedback on best practices etc.
Format constraints2 errors
|5.1||Payment means code|
Payment means code is based on UN/ECE 4461 codelist version D03A.
Line 113: /Invoice/cac:PaymentMeans/cbc:PaymentMeansCode="Z20"
Allowance reason code is either trade discount "17" or deduction for late delivery "20".
Line 167: /Invoice/cac:AllowanceCharge/cbc:AllowanceChargeReasonCode="18"
Integrity constraints2 errors
|6.1||Invoice issue date vs due date|
Invoice due date is later than invoice issue date.
Line 114: /Invoice/cac:PaymentMeans/cbc:PaymentDueDate = "2004-07-21" (Line 9, /Invoice/cbc:IssueDate = "2005-06-27")
|6.2||Tax subtotal sum|
Tax subtotal matches sum of tax amounts in each tax category.
Line 172: /Invoice/cac:TaxTotal/cbc:TaxAmount = 17.50 <> 17.40