- Shared by
- Juha Ikävalko Netum Integrations Oy
- Shared with
- John Smith @companyx.com
Truugo is a message validation platform to setup and share own validators for manual and automated scenarios. Learn more »
Instance failed 6 test phases
Preconditions for message validation. Correct message format and usage.
Validation against base conditions related to Finvoice 2.01 invoice messages.
Validation against Finvoice XSD Schema.
Validation for mandatory elements not necessarily mandated by W3C XML Schema.
Validation for recommended elements not necessarily mandated by W3C XML Schema.
Validation for data format restrictions.
Validation for integrity constraints.
Validation for recommended integrity constraints.
Validation for recommended practices which might become mandatory in the future.
Validation for SEPA requirements.
|11||Credit note requirements|
Validation for credit note spesific requirements.
- Phase must be passed to continue validation
- Phase must be passed to pass the test successfully
- Phase provides informative feedback on best practices etc.
Mandatory elements8 errors
|4.3||Invoicer's party identifier|
Invoicer's party ID is stated on a message.
Line 3: /Finvoice/SellerPartyDetails missing non-empty SellerPartyIdentifier
|4.4||Invoicer's account number|
Invoicer's account number is stated on a message.
Line 2: /Finvoice missing non-empty SellerInformationDetails/SellerAccountDetails/SellerAccountID
|4.5||Invoicer's BIC bank Identifier|
Invoicer's BIC bank identifier is stated on a message.
Line 2: /Finvoice missing non-empty SellerInformationDetails/SellerAccountDetails/SellerBic
|4.6||Invoice total tax exclusive amount|
Invoice total tax exclusive amount is stated on a message.
Line 19: /Finvoice/InvoiceDetails missing non-empty InvoiceTotalVatExcludedAmount
|4.7||Invoice total tax amount|
Invoice total tax amount is stated on a message.
Line 19: /Finvoice/InvoiceDetails missing non-empty InvoiceTotalVatAmount
|4.9||Invoicee's party identifier|
Invoicee's party ID is stated on a message.
Line 11: /Finvoice/BuyerPartyDetails missing non-empty BuyerPartyIdentifier
|4.10||ePI: Invoicer's IBAN account number|
Invoicer's IBAN account number is stated on ePI details.
Line 36: /Finvoice/EpiDetails/EpiPartyDetails missing EpiBeneficiaryPartyDetails/EpiAccountID[@IdentificationSchemeName="IBAN"]
|4.11||ePI: Invoicer's name and address|
Invoicer's name/address is stated on ePI details.
Line 36: /Finvoice/EpiDetails/EpiPartyDetails missing non-empty EpiBeneficiaryPartyDetails/EpiNameAddressDetails
Recommended elements5 errors
|5.1||Related order ID|
Message contains buyer's order number as a reference to a related order.
Line 19: /Finvoice/InvoiceDetails missing non-empty OrderIdentifier
|5.2||Payment overdue fine percent|
Commercial invoice contains a payment overdue fine percent.
Line 19: /Finvoice/InvoiceDetails missing non-empty PaymentTermsDetails/PaymentOverDueFineDetails/PaymentOverDueFinePercent
Tax category specific VAT subtotals are stated on a message.
Line 19: /Finvoice/InvoiceDetails missing VatSpecificationDetails
|5.8||Invoicer's VAT tax identifier|
Invoicer's VAT identifier is stated on a message.
Line 3: /Finvoice/SellerPartyDetails missing non-empty SellerOrganisationTaxCode
|5.18||ePI: Invoicer's BIC bank identifier|
Invoicer's BIC bank identifier is stated on ePI details.
Line 36: /Finvoice/EpiDetails/EpiPartyDetails missing non-empty EpiBfiPartyDetails/EpiBfiIdentifier
Format constraints3 errors
Currency code is specified according to ISO 4217 code list, for example: 'EUR', 'USD' or 'SEK'.
Invoice total amounts are specified with atleast two decimals.
Line 25: /Finvoice/InvoiceDetails/InvoiceTotalVatIncludedAmount = 00
Integrity constraints2 errors
|7.1||Invoice issue date and invoice due date|
Invoice due date is later than invoice issue date.
Line 27: /Finvoice/InvoiceDetails/PaymentTermsDetails/InvoiceDueDate = "20141129" (Line 24, InvoiceDate = "20141229")
|7.2||Invoice due date|
Invoice due date stated in payment terms and ePI details are same.
Line 27: /Finvoice/InvoiceDetails/PaymentTermsDetails/InvoiceDueDate = "20141129" (Line 46, EpiDateOptionDate = "20141219")
General recommendations8 errors
|9.3||No empty elements|
Empty elements are contained in messages only if it's required by the process.
Line 30: Found 1 empty elements.
|9.4||Realistic invoice issue date|
Invoice issue date is +- 90 days from a current date.
Line 24: /Finvoice/InvoiceDetails/InvoiceDate = "20141229"
|9.6||No empty spaces|
Finvoice guideline doesn't allow whitespaces in a beginning or in a end of a element value.
Line 21: /Finvoice/InvoiceDetails/InvoiceTypeText = " "
Line 22: /Finvoice/InvoiceDetails/OriginCode = " Original "
Line 23: /Finvoice/InvoiceDetails/InvoiceNumber = " "
Line 25: /Finvoice/InvoiceDetails/InvoiceTotalVatIncludedAmount = " 00 "
Line 37: /Finvoice/EpiDetails/EpiPartyDetails/EpiBfiPartyDetails = " "
Line 44: /Finvoice/EpiDetails/EpiPaymentInstructionDetails/EpiInstructedAmount = "0,00 "
SEPA validation1 error
|10.2||Invoicer's bank account numbers|
IBAN account number is specified in the following format without spaces: abcd, where: "a" = country code (like "FI"), "b" = 2 check digits, "c" = bank ID and , "d" = account ID.
Line 40: /Finvoice/EpiDetails/EpiPartyDetails/EpiBeneficiaryPartyDetails/EpiAccountID = "x"