ci4j.hbci4j-core.3.1.37.source-code.pain.008.001.02.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of hbci4j-core Show documentation
Show all versions of hbci4j-core Show documentation
HBCI4j - Home Banking Computer Interface for Java
Mandatory if changes occur in ‘Mandate Identification’, otherwise not to be used.
Mandatory if changes occur in 'Creditor Scheme Identification', otherwise not to be used.
Mandatory if changes occur in debtor account, otherwise not to be used.
If changes occur in debtor agent and SMNDA is NOT used in OrgnlDbtrAcct
If a Creditor Reference contains a check digit, the receiving bank is not required to validate this.
If the receiving bank validates the check digit and if this validation fails, the bank may continue its processing and send the transaction to the next party in the chain.
It is recommended that all transactions within the same ‘Payment Information’ block have the same ‘Creditor Scheme Identification’.
This data element must be present at either ‘Payment Information’ or ‘Direct Debit
Transaction’ level.
It is recommended that this element be specified at ‘Payment Information’ level.
This data element may be present either at ‘Payment Information’ or at ‘Direct Debit Transaction Information’ level.
Mandatory if provided by the debtor in the mandate.
Mandatory if 'Amendment Indicator' is 'TRUE'
The reason code from the Rulebook is indicated using one of the following message subelements.
Either ‘BIC or BEI’ or one
occurrence of ‘Other’ is allowed.
Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ is allowed
Private Identification is used to identify either an organisation or a private
person.
‘Name’ is limited to 70 characters in length.
‘Name’ is limited to 70 characters in length.
If present the new’ Name’ must be specified under ‘Creditor’. ‘Name’ is limited to 70 characters in length.
‘Name’ is limited to 70 characters in length.
If present and contains ‘true’, batch booking is requested. If present and contains ‘false’, booking per transaction is requested. If element is not present, pre-agreed customer-to-bank conditions apply.
This data element may be present either at ‘Payment Information’ or at ‘Direct Debit Transaction Information’ level.
It is recommended that this element be specified at ‘Payment Information’ level.
It is recommended that all transactions within the same ‘Payment Information’ block have the same ‘Creditor Scheme Identification’.
This data element must be present at either ‘Payment Information’ or ‘Direct Debit
Transaction’ level.
Only ‘B2B’ and 'CORE' is allowed. The mixing of different Local Instrument values is not allowed in the same message.
Depending on the agreement between the Creditor and the Creditor Bank, ‘Category Purpose’ may be forwarded to the Debtor Bank.
Only one occurrence of ‘Other’ is allowed, and no other sub-elements are allowed.
Identification must be used with an identifier described in General Message Element Specifications, Chapter 1.5.2 of the Implementation Guide.
Scheme Name’ under ‘Other’ must specify ‘SEPA’ under ‘Proprietary
Only codes from the ISO 20022 ExternalPurposeCode list are allowed.
When present, the receiving bank is not obliged to validate the reference information.