Difference between revisions of "MetaData - SEPA"
From All n One's bxp software Wixi
(→SEPA Import Form Required Fields) |
(→SEPA Pain 002 Import) |
||
Line 289: | Line 289: | ||
1) Store a CCL of the refusal record creation for each record created | 1) Store a CCL of the refusal record creation for each record created | ||
− | 2) | + | 2) Update the Refusal Reason to include the English Reason i.e. convert the refusal code |
− | 3) Delete the original file from the specified location (optional action - but highly recommended) | + | 3) Store a CCL of the SEPA file that was processed for each record created (optional action - but highly recommended) |
+ | |||
+ | 4) Delete the original file from the specified location (optional action - but highly recommended) | ||
Revision as of 15:13, 30 September 2016
Contents
1 MetaData - SEPA Rule
bxp has the ability through MetaData, both manual and scheduled to generate a SEPA PAIN 008 file and import to a form a SEPA PAIN 002 Rejection file.
2 SEPA Pain 008 Export
In order to generate a SEPA Pain 008 file bxp needs two forms, one to store all of the Header information for the file and one that stores the individual transaction data. Both the header form and the transaction form must contain the fields mentioned below.
Once the MetaData Process Rule has been set up correctly, bxp will cycle through the header and transaction forms taking all of the required data. The MetaData sequence needs to be set up on the transaction form as this controls the transactions to include in the file.
After a success full process bxp will store the SEPA Pain 008 file in the specified MetaData directory and also perform the following options:
1) Store a CCL of the SEPA file generation in all of the transaction records included
2) Store a CCL of the SEPA file generation in the header form record
3) Store a copy of the SEPA file generated in the header form record, once here this copy cannot be modified/deleted (optional action)
Reference Document -- Media:SEPA_008_LayoutDocument.pdf
2.1 Header Form Required Fields
# | BOI XML Reference | Information | Manual or Automatic Data Entry |
---|---|---|---|
1 | 1.1 | Message Information | Manual |
2 | 2.2 | Creation Date Time | Automatic |
3 | 1.6 | Number of transactions | Automatic |
4 | 1.7 | Control Sum | Automatic |
5 | 1.8 | Identification | Manual |
6 | 2.1 | Payment Information Identification | Manual |
7 | 2 | Payment Method | Manual |
8 | 2.4 | Number of transactions | Automatic |
9 | 2.5 | Control Sum | Automatic |
10 | 2.9 | Code | Manual |
11 | 2.12 | Code | Manual |
12 | 2.14 | Sequence Type | Manual |
13 | 2.17 | Proprietary | Manual |
14 | 2.18 | Requested Collection Date | Manual |
15 | 2.19 | Name | Manual |
16 | 2.20 | IBAN | Manual |
17 | 2.21 | BIC | Manual |
2.2 Transaction Form Required Fields
# | BOI XML Reference | Information | Manual or Automatic Data Entry |
---|---|---|---|
1 | 2.30 | Payment Identification/Instruction Identification | Manual |
2 | 2.31 | Payment Identification/End to End Identification | Manual |
3 | 2.44 | Instructed Amount | Manual |
4 | 2.48 | Mandate Identification | Manual |
5 | 2.49 | Date of Signature | Manual |
6 | 2.66 | Identification | Manual |
7 | 2.66 | Proprietary | Manual |
8 | 2.70 | Financial Institution Identification | Manual |
9 | 2.72 | Name | Manual |
10 | 2.73 | IBAN | Manual |
2.3 Rule Parameter Explanation
# | Example | Type | Mandatory | Description |
---|---|---|---|---|
0 | SEPAFileGeneration | Text | True | This tells bxp what rule to execute and must be as specified |
1 | Header Form Id | Number | True | This tells bxp what form contains the header information |
2 | Header Record Id | Number | True | This tells bxp what record contains the header information |
3 | Header form fields | Text | True | This tells bxp the fields that the header information are stored |
4 | Transaction form Id | Number | True | This tells bxp what form contains the transaction information |
5 | Transaction form fields | Text | True | This tells bxp the fields that the transaction information are stored |
6 | Record Status update | True/False | True | This tells bxp to apply a custom status to the records updated |
7 | Custom Status to apply | Text | True | This is the custom status that will be applied to the records |
8 | Store in CCL of Record | True/False | True | This tells bxp to store a copy of the XML file in the CCL of the header record |
9 | Sub folder Location | Text | True | This tells bxp to look in sub folders if specified |
2.4 Example Rule
SEPAFileGeneration
[[-SEP-]]1
[[-SEP-]]1
[[-SEP-]]strCDA_1_field_0_1,strCDA_1_field_0_2,..............,strCDA_1_field_0_16,strCDA_1_field_0_17
[[-SEP-]]2
[[-SEP-]]strCDA_2_field_0_1,strCDA_2_field_0_2,..............,strCDA_2_field_0_9,strCDA_2_field_0_10
[[-SEP-]]True
[[-SEP-]]SEPA FILE GENERATION
[[-SEP-]]True
[[-SEP-]]SubFolder1\SubFolder2\SubFolder3
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
3 SEPA Pain 002 Import
In order to import a SEPA Pain 002 file bxp needs one forms, one to store all of the transaction information as wee as the group header information. The form must contain the fields mentioned below.
Once the MetaData Input Rule has been set up correctly, bxp will go through .xml files in the specified location and take all group header information and refused transaction information and store them in the form. Please note that there will be one record in the form for every refused transaction.
After a success full process bxp will perform the following options:
1) Store a CCL of the refusal record creation for each record created
2) Update the Refusal Reason to include the English Reason i.e. convert the refusal code
3) Store a CCL of the SEPA file that was processed for each record created (optional action - but highly recommended)
4) Delete the original file from the specified location (optional action - but highly recommended)
Reference Document -- Media:SEPA_002_LayoutDocument.pdf
3.1 SEPA Import Form Required Fields
# | BOI XML Reference | Information | XML Data Path |
---|---|---|---|
1 | 1.1 | Message Identification | GrpHdr > MsgId |
2 | 1.2 | Creation Date Time | GrpHdr > CreDtTm |
3 | 1.6 | BIC | GrpHdr > CdtrAgt > FinInstnId > BIC |
4 | 2.1 | Original Message Identification | OrgnlGrpInfAndSts > OrgnlMsgId |
5 | 2.2 | Original Message Name Identification | OrgnlGrpInfAndSts > OrgnlMsgNmId |
6 | 2.4 | Original Number of Transactions | OrgnlGrpInfAndSts > OrgnlNbOfTxs |
7 | 2.5 | Original Control Sum | OrgnlGrpInfAndSts > OrgnlCtrlSum |
8 | 3.1 | Original Payment Information Identification | OrgnlPmtInfAndSts > OrgnlPmtInfId |
9 | 3.2 | Original Number Of Transactions | OrgnlPmtInfAndSts > OrgnlNbOfTxs |
10 | 3.3 | Original Control Sum | OrgnlPmtInfAndSts > OrgnlCtrlSum |
11 | 3.16 | Status Identification | TxInfAndSts > StsId |
12 | 3.17 | Original Instruction Identification | TxInfAndSts > OrgnlInstrId |
13 | 3.18 | Original End To End Identification | TxInfAndSts > OrgnlEndToEndId |
14 | 3.19 | Transaction Status | TxInfAndSts > TxSts |
15 | 3.21 | BIC Or BEI | TxInfAndSts > StsRsnInf > Orgtr > Id > OrgId > BICOrBEI |
16 | 3.23 | Code | TxInfAndSts > StsRsnInf > Rsn > Cd |
17 | 3.35 | Instructed Amount | TxInfAndSts > OrgnlTxRef > Amt > InstdAmt |
18 | 3.40 | Requested Collection Date | TxInfAndSts > OrgnlTxRef > ReqdColltnDt |
19 | 3.42 | Identification | TxInfAndSts > OrgnlTxRef > CdtrSchmeId > Id > PrvtId > Othr > Id |
20 | 3.42 | Proprietary | TxInfAndSts > OrgnlTxRef > CdtrSchmeId > Id > PrvtId > Othr > SchmeNm > Prtry |
21 | 3.59 | Code | TxInfAndSts > OrgnlTxRef > PmtTpInf > SvcLvl > Cd |
22 | 3.62 | Code | TxInfAndSts > OrgnlTxRef > PmtTpInf > LclInstrm > Cd |
23 | 3.64 | SequenceType | TxInfAndSts > OrgnlTxRef > PmtTpInf > SeqTp |
24 | 3.67 | Proprietary | TxInfAndSts > OrgnlTxRef > PmtTpInf > CtgyPurp > Prtry |
25 | 3.70 | Mandate Identification | TxInfAndSts > OrgnlTxRef > MndtRltdInf > MndtId |
26 | 3.71 | Date of Signature | TxInfAndSts > OrgnlTxRef > MndtRltdInf > DtOfSgntr |
27 | 3.72 | Amendment Indicator | TxInfAndSts > OrgnlTxRef > MndtRltdInf > AmdmntInd |
28 | 3.121 | Name | TxInfAndSts > OrgnlTxRef > Dbtr > Nm |
29 | 3.122 | IBAN | TxInfAndSts > OrgnlTxRef > DbtrAcct > Id > IBAN |
30 | 3.123 | BIC | TxInfAndSts > OrgnlTxRef > DbtrAgt > FinInstnId > BIC |
31 | 3.125 | BIC | TxInfAndSts > OrgnlTxRef > CdtrAgt > FinInstnId > BIC |
32 | 3.127 | Name | TxInfAndSts > OrgnlTxRef > Cdtr > Nm |
33 | 3.128 | IBAN | TxInfAndSts > OrgnlTxRef > CdtrAcct > Id > IBAN |
3.2 Example Rule
SEPA002FileRead
[[-SEP-]]1
[[-SEP-]]strCDA_1_field_0_1,strCDA_1_field_0_2,..............,strCDA_1_field_0_32,strCDA_1_field_0_33
[[-SEP-]]SubFolder1\SubFolder2\SubFolder3
[[-SEP-]]True
[[-SEP-]]SEPA Rejection
[[-SEP-]]False
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]
[[-SEP-]]