Customer guide for mapping of information in

PAIN 001.001.03 files for

SCT domestic RON payments

UniCredit Bank for Client use Only

1
 This document is used to describe to the customer how to map the needed information for RON
payments when using ISO 20022 XML files - PAIN.001.001.03 format which is supported by UniCredit
Systems, taking into account all special validations specific for Romania.

1. SEPA RON Credit Transfer – XML client information mapping rules

Pain 001.001.03 xml will be used to import SEPA RON payments. Special validations will be in place
as described below. Client should use only fields described below. Information which is mapped in
additional optional tags, other than the ones described below will NOT BE MAPPED in UniCredit’s
systems and will be discarded when payments are imported.

Standard payments (non-tax) will be distinguished from budget payments (TAX transactions) using the
beneficiary IBAN account and, where available, beneficiary BIC (BIC=TREZROBU). If the IBAN
account contains TREZ, the payment is a TAX transaction.

Fields to be available for SEPA domestic RON payments, general description and validations:

 Payment Batch reference (Payment information identification) – mandatory

o mapped to xml field: <PmtInf>/<PmtInfId>
o value must be maximum 35 alphanumerical characters

 Urgent payment flag– Optional flag

o Only two options available HIGH (High priority/urgent) or NORM (normal processing)
o if not filled in by user, default value will be entered by the system as normal
processing
o mapped to xml field: <PmtInf>/<PmtTpInf>/<InstrPrty> for the entire batch of
payments contained within a single Pmtinf parent tag or in
<PmtInf>/<CdtTrfTxInf>/<PmtTpInf>/<InstrPrty> for each individual payment

Note: If urgent flag is used, it is recommended to be filled in at "Payment information" level and
not at "Credit Transfer Transaction information".
If flag is used in both tags (not recommended), the information from Credit Transfer Transaction
information will be used for determining normal or high payment processing.

 Execution date – mandatory

o execution date of transaction (value date if sent in COT; value date next day if sent
after COT) – ISO format date YYYY-MM-DD
o mapped to xml field: <PmtInf>/<ReqdExctnDt

 Ordering Account IBAN – mandatory

o Mapped to xml field: <PmtInf>/<DbtrAcct>/<Id>/<IBAN>
o possible values – UniCredit IBAN account (Ro format mandatory)
o accounts with missing IBAN will not be allowed

 Ordering party Bank BIC – mandatory

o Mapped to xml field: <PmtInf>/<DbtrAgt>/<FinInstnId>/<BIC>
o BIC if UniCredit : BACXROBU

 Ordering party Name – mandatory

o Mapped to xml field: <PmtInf>/<Dbtr>/<Nm>
o Maximum 35 chars available

 Ordering party Postal Address – optional

o Mapped to xml field: <PmtInf>/<Dbtr>/<Pstladr>/<AdrLine>
o maximum 70 characters (only 2 lines available)

 Payment order no/reference (E2E reference) – mandatory

o mapped to xml field: <PmtInf>/<CdtTrfTxInf>/<PmtId>/<EndToEndId>
o if normal payment/tax payment value must be maximum 16 characters long

UniCredit Bank for Client use Only

2
 o if urgent payment/high value payment (amount > 50.000 RON) value must be
maximum 11 numerical characters

 Amount – mandatory field

o Mapped to xml field: <PmtInf>/<CdtTrfTxInf>/<Amt>/<InstdAmt>
o only amounts in RON currency are possible (RON currency flag to be always used)

Note: If different value than RON is used, transaction will be rejected.

 Beneficiary Account IBAN – mandatory

o Mapped to xml field: <PmtInf>/<CdtTrfTxInf>/<CdtrAcct>/<Id>/<IBAN>
o possible values – only IBAN (Ro format mandatory)
o accounts with missing IBAN will not be allowed

 Beneficiary Bank BIC subfield – optional

o Mapped to xml field: <PmtInf>/<CdtTrfTxInf>/<CdtrAgt>/<FinInstnId>/<BIC>
o If not provided value will be obtained from IBAN in banks‘ system

 Beneficiary Name – mandatory field

o Mapped to xml field: <PmtInf>/<CdtTrfTxInf>/<Cdtr>/<Nm>
o Maximum 35 chars available

 Beneficiary Postal Address – optional field

o Mapped to xml field: <PmtInf>/<CdtTrfTxInf>/<Cdtr>/<Pstladr>/<AdrLine>
o maximum 70 characters

 Beneficiary Identification – mandatory field for TAX transactions, optional for normal
transactions
o Identification type subfield –
 Either ORGANISATION ID or Private ID will be selected (for legal entities or
private individuals)
o Identification subfield

 For Tax payment if validation is not passed, payment is rejected. For normal
payment if validation does not match either Fiscal code or Private ID
algorithm the provided information will be considered as an another
Organization ID - Other ID
 For Normal payments if other Identification information is used, client can use
other available ID types according to SEPA standard, e.g. Date and Place of
Birth, BIC or BEI and the information must filled in accordingly in Tax number/
Other ID subfield.

o Tax Number/Other ID subfield

 Tax numbers (fiscal code and private id) will be considered for Private ID if
their length is exactly 13 characters, otherwise they will be considered for
Organization ID
 Mapped to:
<PmtInf>/<CdtTrfTxInf>/< Cdtr><Id>/<OrgId>/<Othr>/<Id>/[Fiscal code]
OR
<PmtInf>/<CdtTrfTxInf>/<Cdtr><Id>/<PrvtId>/<Othr/<Id>/[Private ID]
 For all transactions the Tax number will be validated using the national
validation rules. For TAX transactions if the provided information is not
validated the payment is rejected.

Mapping to XML depending of Identification information used:

Benef Identification Code (ID type)
Benef BIC or BEI (OrganizationID)
Recommended:
Benef Tax Number (OrganizationID) or
Benef Tax Number (PrivateID)
Mapping
Creditor <Cdtr><Id><OrgId><BICOrBEI>
Creditor <Cdtr><Id><OrgId><Othr><Id> or
<Cdtr><Id><PrvtId><Othr><Id>

UniCredit Bank for Client use Only

3
Benef other ID (OrganizationID) or
Benef other ID (PrivateID)
Benef other Code (OrganizationID) or
Benef other Code (PrivateID)
Benef other proprietary (OrganizationID) or
Benef other proprietary (PrivateID)
Benef other issuer (OrganizationID) or
Benef other issuer (PrivateID)
Benef birth date (PrivateID)
Benef birth province (PrivateID)
Benef birth city (PrivateID)
Benef birth country (PrivateID)
Creditor <Cdtr><Id><OrgId><Othr><Id> or
<Cdtr><Id><PrvtId><Othr><Id>
Creditor <Cdtr><Id><OrgId><Othr><SchmeNm><Cd> or
<Cdtr><Id><PrvtId><Othr><SchmeNm><Cd>
Creditor <Cdtr><Id><OrgId><Othr><SchmeNm><Cd> or
<Cdtr><Id><PrvtId><Othr><SchmeNm><Cd>
Creditor <Cdtr><Id><OrgId><Othr><Issr> or
<Cdtr><Id><PrvtId><Othr><Issr>
Creditor <Cdtr><Id><PrvtId><DtAndPlcOfBirth><BirthDt>
Creditor <Cdtr><Id><PrvtId><DtAndPlcOfBirth><PrvcOfBirth>
Creditor <Cdtr><Id><PrvtId><DtAndPlcOfBirth><CityOfBirth>
Creditor <Cdtr><Id><PrvtId><DtAndPlcOfBirth><CtryOfBirth>

 Instruction ID (client) – optional

o with the same purpose as the tag <CdtTrfTxInf> <PmtId><InstrId> in pain.001 file
o maximum 35 alphanumerical chars
o Map to: <PmtInf>/<CdtTrfTxInf>/<PmtId>/<InstrId>

 Service Level code – optional = SEPA

o Only value SEPA is allowed
o Map to: <PmtInf>/<CdtTrfTxInf>/<PmtTpInf>/<SvcLvl>/<Cd> for each individual
payment or : <PmtInf>/<SvcLvl>/<Cd> for the entire batch of payments contained
within a single Pmtinf parent tag.

 Local Instrument – optional

o either Code or Proprietary will be possible
o for Code subfield only the values available in the SEPA Local instrument codes list
used by local ACH will be allowed,
o for Proprietary subfield with max 35 alphanumerical code will be available
o Map to: <PmtInf>/<CdtTrfTxInf>/<PmtTpInf>/<LclInstrm>/<Cd>

 Category Purpose – optional

o either Code or Proprietary will be possible
o for Code subfield only the values available SEPA Category Purpose Codes used by
local ACH will be allowed.
o for Proprietary subfield with max 35 alphanumerical code will be available
o Map to: <PmtInf>/<CdtTrfTxInf>/<PmtTpInf>/<CtgyPurp>/<Cd>

 Purpose Code – optional

o only the values available in list of SEPA Purpose Codes used by local ACG will be
allowed
o Map to: <PmtInf>/<CdtTrfTxInf>/<Purp>/<Cd>

 Ultimate Creditor – optional

o subfield Name – maximum 70 characters
o subfield Identification – functionality will offer ID types in accordance with SEPA rules
o Map to: <PmtInf>/<CdtTrfTxInf>/<UltmCdtr >/<Nm>
o Map to: <PmtInf>/<CdtTrfTxInf>/<UltmCdtr >/<Id><OrgId><Othr><Id> or
<PmtInf>/<CdtTrfTxInf>/<UltmCdtr >/<Id><PrvtId><Othr><Id

 Ultimate Debtor – optional

o subfield Name –maximum 70 characters
o subfield Identification –functionality will offer to use ID types in accordance with SEPA
rules
o Map to: <PmtInf>/<CdtTrfTxInf>/<UltmDbtr >/<Nm>
o Map to: <PmtInf>/<CdtTrfTxInf>/<UltmDbtr >/<Id><OrgId><Othr><Id> or
<PmtInf>/<CdtTrfTxInf>/<UltmDbtr >/<Id><PrvtId><Othr><Id

UniCredit Bank for Client use Only

4
 Remittance Information – either unstructured or structured

 Unstructured Remittance Information - Mandatory for TAX transactions, optional

for normal payments
o Details of Payment subfield
 For TAX transactions the field will be mandatory and max 89 characters will
be allowed
 for PAYM transactions maximum 140 characters will be allowed,
o Fiscal Account subfield (NEP)
 only available for TAX transactions
 optional subfield of remittance information
 if provided, the dedicated validation rules will be applied (See NEP validation
rules)

Note: Final Unstructured Remittance Information that will be provided in XML by client
should have the following structure:
 for Standard payments (non-budget)
<Ustrd>Details of Payment</Ustrd>
 for TAX transactions
<Ustrd>/ROC/Fiscal Account /RFB/ Details of Payment </Ustrd> where
ROC and RFB are static and mandatory labels (Example: <Ustrd>/ROC/
20100010000170514000022/RFB/my payment</Ustrd>)

 Structured Remittance Information - will be available only for Normal transactions

as follows:
o Creditor Reference subfield
 optional field maximum 35 alphanumerical chars
 the value will be mapped to xml tag
<PmtInf>/<CdtTrfTxInf>/<RmtInf>/<Strd>/<CdtrRefInf>/<Ref>
 for xml tag <RmtInf><Strd><CdtrRefInf><Tp><CdOrPrtry><Cd>
automatically the default value “SCOR” will be used (according to
standard SEPA rules)

o Referred Document Code subfield

 optional field
 Map to <PmtInf>/<CdtTrfTxInf>/<RmtInf>/<Strd>/<RfrdDocInf>/<Tp>/
<CdOrPrty>/<Cd>
 only the values available in SEPA Referred Document Codes will be
allowed, functionality will offer the list of available codes

o Referred Document Number subfield

 optional field maximum 35 alphanumerical chars
 map to: <PmtInf>/<CdtTrfTxInf>/<RmtInf>/<Strd>/<RfrdDocInf>/<Nb>

o Referred Document Related Date subfield

 optional field – ISO date
 map to: <PmtInf>/<CdtTrfTxInf>/<RmtInf>/<Strd>/<RfrdDocInf>/
<RltdDt>

NOTE: Structure Remittance can contain only 140 char considering also tags.
Client should consider only one single occurrence of Referred Document
Information possible.

UniCredit Bank for Client use Only

5
2. General domestic payments XML import rules in a nutshell
Import functionality will accept and import SEPA compliant pain.001.001.03 files in accordance with the
official SEPA Credit Transfer Scheme Rulebook and xsd structure. Special validations are needed for
information in certain tags, specific for Romania.

If, in addition to the fields described in this document, other OPTIONAL fields (tags) from the standard
scheme are used, information filled in on these additional tags will NOT BE mapped in the payment
narratives! The xml file will not be rejected but the additional information will be discarded when importing the
payments.

 The value of the pain.001 tag Message Id (<CdtTrfTxInf><GrpHdr><MsgId>) can be used by client
as Pre-system reference
 Payment Batch reference (Payment information identification) will be used as a batch
reference for all payments within a <PmtInf> parent tag.
 The Debtor/Creditor account must be in UniCredit IBAN format
 Urgent payments will be identified based on the tag for Instruction Priority (Instruction Priority
“HIGH” = urgent payment).
 Batch booking tag will be ignored.
 Debtor/Creditor Agent BIC codes in pain.001 file are mandatory
o If Debtor Bank BIC is provided we must always validate to BIC of UniCredit Bank.
 If Debtor/Creditor Agent BIC code is delivered in pain.001, it will be checked. Wrong BIC codes or
disagreement between BIC code and IBAN will invalidate the transaction.
 E2E reference must be validated as described above (for HIGH Priority payments and high value
payments only 11 numerical chars are accepted, otherwise 16 alphanumerical chars are possible
 Creditor ID/Debtor (tax number) will be considered for Fiscal code/Private ID only if ID tag type
“Other” is used. Otherwise the Creditor/Debtor ID will be considered for other type of SEPA ID.
Creditor ID must be validated against the algorithm and for TAX transactions if it is not correct
payment will be rejected.
 For TAX transactions, if debtor Fiscal code (tax number) does not meet the validation rules for fiscal
code (e.g. for non-resident accounts), only the Schema Name Code “ARNU” will be accepted as
assigned to Debtor ID.
 Client can use structured or unstructured information. For processing of the tag Unstructured
Remittance Information (URI) use the following rules:

o for normal transactions following structure of URI is expected:

 <Ustrd>Creditor Narrative (details of payment)</Ustrd>
o for TAX transactions the following structure of URI is expected:
 <Ustrd>/ROC/Fiscal (Treasury) Account/RFB/Creditor Narrative (details of
payment</Ustrd>
If Treasury Account is not available, value after the code word will be missing (eg:
<Ustrd>/ROC//RFB/ Creditor Narrative</Ustrd>)

Details of payment filed number if characters must be validated as described above in the document:
o For normal payments: 140 alphanumerical char allowed
o For tax payments: only 89 alphanumerical chars allowed

If the text in URI does not correspond to this structure and it’s length is exceeded, payments will be
rejected when imported by client in application.
For TAX payment if URI does not correspond to the structure described above (especially Fiscal
Account- NEP) than all information provided in URI is considered as Details of Payment within the
allowed maximum length.

 Client can use also Structured Remittance Information (SRI), only for normal payments (non-tax).
Following values of structured remittance information will be imported:
o <RmtInf><Strd><CdtrRefInf><Ref> Creditor Reference. The check of the field Structured
Beneficiary Reference (Creditor Reference) against ISO norm 11649 should not be
implemented. Check for maximum 35 alphanumerical chars

UniCredit Bank for Client use Only

6
 o for xml tag <RmtInf><Strd><CdtrRefInf><Tp><CdOrPrtry><Cd> the default value “SCOR”
should be used (according to standard SEPA rules)
o <RmtInf><Strd><RfrdDocInf> - only one occurrence will be imported
 <RmtInf><Strd><RfrdDocInf><Tp><CdOrPrtry><Cd> Referred Document Code, if
used only the values available in SEPA Referred Document Codes used by local
ACH will be allowed
 <RmtInf><Strd><RfrdDocInf><Nb> Referred Document Number, if used check
maximum 35 alphanumerical chars
 <RmtInf><Strd><RfrdDocInf><RltdDt> Referred Document Related Date (ISO date)

NOTE: Only one occurrence of Referred Document Information will be possible.

NOTE: We don’t allow import of TAX payments with structured remittance information

UniCredit Bank for Client use Only

7