share

Shared by
Juha Ikävalko Netum Oy / Truugo Team
Shared with
John Smith @companyx.com
Expires
2098-05-30

test case

Test profile
View profile Finvoice 2.01
File tested
View instance
Finvoice_2_01_example.xml
Message layouts
FK default (Swedish)
FK default (English)
FK default (Finnish)
Report
Print report
Status
Set status to DONE to inform the author when reported errors have been resolved.

Truugo is a message validation platform to setup and share own validators for manual and automated scenarios. Learn more »

Test report

Case overview

ProfileFinvoice 2.01

INVALID

Instance failed 6 test phases

StandardFinvoice 2.01
Message typeInvoice
InstanceFinvoice_2_01_example.xml
UserJuha Ikävalko
Time2018-06-20 09:49:45Z

Test phases

PhaseImportanceResult
1Preconditions

Preconditions for message validation. Correct message format and usage.

CRITICALPASSED
2Base conditions

Validation against base conditions related to Finvoice 2.01 invoice messages.

CRITICALPASSED
3Schema validation

Validation against Finvoice XSD Schema.

MANDATORYPASSED
4Mandatory elements

Validation for mandatory elements not necessarily mandated by W3C XML Schema.

MANDATORYFAILED
5Recommended elements

Validation for recommended elements not necessarily mandated by W3C XML Schema.

RECOMMENDEDFAILED
6Format constraints

Validation for data format restrictions.

MANDATORYFAILED
7Integrity constraints

Validation for integrity constraints.

MANDATORYFAILED
8Integrity recommendations

Validation for recommended integrity constraints.

RECOMMENDEDPASSED
9General recommendations

Validation for recommended practices which might become mandatory in the future.

RECOMMENDEDFAILED
10SEPA validation

Validation for SEPA requirements.

MANDATORYFAILED
11Credit note requirements

Validation for credit note spesific requirements.

MANDATORYPASSED
Code explanations
CRITICAL
Phase must be passed to continue validation
MANDATORY
Phase must be passed to pass the test successfully
RECOMMENDED
Phase provides informative feedback on best practices etc.

Feedback

Mandatory elements8 errors

4.3Invoicer's party identifier

Condition

Invoicer's party ID is stated on a message.

Error

Line 3: /Finvoice/SellerPartyDetails missing non-empty SellerPartyIdentifier

4.4Invoicer's account number

Condition

Invoicer's account number is stated on a message.

Error

Line 2: /Finvoice missing non-empty SellerInformationDetails/SellerAccountDetails/SellerAccountID

4.5Invoicer's BIC bank Identifier

Condition

Invoicer's BIC bank identifier is stated on a message.

Error

Line 2: /Finvoice missing non-empty SellerInformationDetails/SellerAccountDetails/SellerBic

4.6Invoice total tax exclusive amount

Condition

Invoice total tax exclusive amount is stated on a message.

Error

Line 19: /Finvoice/InvoiceDetails missing non-empty InvoiceTotalVatExcludedAmount

4.7Invoice total tax amount

Condition

Invoice total tax amount is stated on a message.

Error

Line 19: /Finvoice/InvoiceDetails missing non-empty InvoiceTotalVatAmount

4.9Invoicee's party identifier

Condition

Invoicee's party ID is stated on a message.

Error

Line 11: /Finvoice/BuyerPartyDetails missing non-empty BuyerPartyIdentifier

4.10ePI: Invoicer's IBAN account number

Condition

Invoicer's IBAN account number is stated on ePI details.

Error

Line 36: /Finvoice/EpiDetails/EpiPartyDetails missing EpiBeneficiaryPartyDetails/EpiAccountID[@IdentificationSchemeName="IBAN"]

4.11ePI: Invoicer's name and address

Condition

Invoicer's name/address is stated on ePI details.

Error

Line 36: /Finvoice/EpiDetails/EpiPartyDetails missing non-empty EpiBeneficiaryPartyDetails/EpiNameAddressDetails

Recommended elements5 errors

5.1Related order ID

Condition

Message contains buyer's order number as a reference to a related order.

Error

Line 19: /Finvoice/InvoiceDetails missing non-empty OrderIdentifier

5.2Payment overdue fine percent

Condition

Commercial invoice contains a payment overdue fine percent.

Error

Line 19: /Finvoice/InvoiceDetails missing non-empty PaymentTermsDetails/PaymentOverDueFineDetails/PaymentOverDueFinePercent

5.3VAT subtotal

Condition

Tax category specific VAT subtotals are stated on a message.

Error

Line 19: /Finvoice/InvoiceDetails missing VatSpecificationDetails

5.8Invoicer's VAT tax identifier

Condition

Invoicer's VAT identifier is stated on a message.

Error

Line 3: /Finvoice/SellerPartyDetails missing non-empty SellerOrganisationTaxCode

5.18ePI: Invoicer's BIC bank identifier

Condition

Invoicer's BIC bank identifier is stated on ePI details.

Error

Line 36: /Finvoice/EpiDetails/EpiPartyDetails missing non-empty EpiBfiPartyDetails/EpiBfiIdentifier

Format constraints3 errors

6.4Currency code

Condition

Currency code is specified according to ISO 4217 code list, for example: 'EUR', 'USD' or 'SEK'.

Error

Line 25: /Finvoice/InvoiceDetails/InvoiceTotalVatIncludedAmount/@AmountCurrencyIdentifier = " xxx "

Line 44: /Finvoice/EpiDetails/EpiPaymentInstructionDetails/EpiInstructedAmount/@AmountCurrencyIdentifier = " xxx "

6.5Total amount

Condition

Invoice total amounts are specified with atleast two decimals.

Error

Line 25: /Finvoice/InvoiceDetails/InvoiceTotalVatIncludedAmount = 00

Integrity constraints2 errors

7.1Invoice issue date and invoice due date

Condition

Invoice due date is later than invoice issue date.

Error

Line 27: /Finvoice/InvoiceDetails/PaymentTermsDetails/InvoiceDueDate = "20141129" (Line 24, InvoiceDate = "20141229")

7.2Invoice due date

Condition

Invoice due date stated in payment terms and ePI details are same.

Error

Line 27: /Finvoice/InvoiceDetails/PaymentTermsDetails/InvoiceDueDate = "20141129" (Line 46, EpiDateOptionDate = "20141219")

General recommendations8 errors

9.3No empty elements

Condition

Empty elements are contained in messages only if it's required by the process.

Error

Line 30: Found 1 empty elements.

9.4Realistic invoice issue date

Condition

Invoice issue date is +- 90 days from a current date.

Error

Line 24: /Finvoice/InvoiceDetails/InvoiceDate = "20141229"

9.6No empty spaces

Condition

Finvoice guideline doesn't allow whitespaces in a beginning or in a end of a element value.

Error

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.2Invoicer's bank account numbers

Condition

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.

Error

Line 40: /Finvoice/EpiDetails/EpiPartyDetails/EpiBeneficiaryPartyDetails/EpiAccountID = "x"