Notice! This page describes the nature of the error using a hypothetical example and not the erroneous data of the input test file. You should however be able to apply this information to your error case.

General description of the error:

The format of the error message:cvc-type.3.1.3: The value ''{1}'' of element ''{0}'' is not valid.

Error description in schema standard:

Possible causes for this error:

  • The content of the element does not match the element type definition or pattern.


Example 1


Error messageThe value 'filse' of element 'BtchBookg' is not valid.

How to fix: Open the relevant schema definition to see the list of restrictions set on the element, and apply changes to your xml instance accordingly.

Other potential schema errors that might have appearead should also be of relevance and should be looked at if the explanation of this error code page is not sufficient.

In this particular case, the schema is ISO 20022 pain.001.001.03.xsd, where BtchBookg is defined as...

<xs:simpleType name="BatchBookingIndicator">

<xs:restriction base="xs:boolean"/>
...where xs:boolean is an xsd schema atomic type and its accepted values are "true" and "false" (strictly in lower case and without the quotation marks).
In this case also another schema error, cvc-datatype-valid.1.2.1, should have been triggered.

Example 2


Error messageError cvc-type.3.1.3: The value 'AAA' of element 'PmtMtd' is not valid.

How to fix: You have to check the schema definition to see which restrictions are set for the element to be able to fix the issue. If there are other schema error messages related to same element, check those also - they might give more hints on how to fix the error. In this case the value of PmtMtd should be one of pre-defined enumeration values of TRF, TRA or CHK.



Example 3


Error messageReqdExctnDt' value '2019-11-40' is not valid.

How to fix: Verifying date format is correct. Schema validation is checking that date is realistic, so error may be given if the given date is not possible in addtition to date  format being incorrect (e.g. not containing dashes to separate years, days and months)