InsideBusiness Payments BACS STD18. Addendum to BACS_STD18_EFT_file_structures for BACS Credit Transfers

Transcription

1 InsideBusiness Payments BACS STD18 Addendum to BACS_STD18_EFT structures for BACS Credit Transfers

2 Introduction This document is an addendum to the BACS_STD18_EFT structures, version , and describes the deviations and specific details of the BACS format in InsideBusiness Payments. This is version 1.0 of the addendum and is valid from February 2016 onwards until further notice. Please verify with your bank contact whether the addendum still applies, and if it is the latest version. General remarks BACS format can be used to import batch and single payments. In InsideBusiness Payments use the menu option Payments-> Import File to upload the BACS. BACS CT can be used for domestic GBP payments processed through the Faster Payments or CHAPS clearing. Layout description A BACS may contain multiple batches. Every batch should start with an HDR1 record and ends with a UTL 1 record A BACS cannot contain credit transfers and direct debits A BACS must not contain single and multiple payments (ING specific) An UHL1 section may contain one or more CNTRA record(s) ne CNTRA per UHL or one CNTRA per Transaction is allowed An UHL1 section may contain: Singles: one payment is immediately followed by a CNTRA ultiples: two or more body payment records are followed by a CNTRA record InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

3 Format description A BACS may contain multiple batches. Every batch should start with an HDR1 record and ends with a UTL 1 record A BACS must not contain credit transfers and direct debits An UHL1 section may contain one or more CNTRA record(s) ne CNTRA per UHL or ne CNTRA per Transaction is allowed An UHL1 section for type DAILY may contain: Singles: one payment is immediately followed by a CNTRA ultiples: two or more body payment records are followed by a CNTRA record This is an ING convention since BACS does allow for multi batches within one UHL1 section BACS File 1..1 VL HDR HDR2 1..n UHL1 Payment Remitter account 1 1..n Payment Remitter account 1 Payment Remitter account 1 Contra record EF EF UTL1 HDR HDR2 UHL1 1..n Payment Remitter account 2 Contra record Payment Remitter account 3 Contra record EF EF UTL InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

4 Syntactical details and deviations = andatory = ptional A = A-Z AN = A-Z, 0-9 N = 0-9 b = blank space 1.1. File level record (VL1) Vol1 is a mandatory segment in the BACS and can occur once. Field Pos Type Name Value / A Label identifier VL N Label number AN Submission serial number AN Accessibility indicator AN Not used AN Not used AN AN wner identification Initiating party name AN AN Not used N Label standard label 1 InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

5 1.2. First level label (HDR1) HDR1 is a mandatory segment in the BACS. After closing the order with the UTL1 segment, a new order can be inserted in the. Using this logic the HDR segment can be used many times in a. Field Pos Type Name Value / A Label identifier HDR N Label number A File identifier File identifier AN Single submission ulti submission A Record identifier AN Record identifier AN Single submission N ulti submission AN Set Identification File section number 6 1 File sequence number N Single submission 3 N ulti submission AN Generation number AN Generation version number byyddd - Julian date preceded AN Creation date by a blank AN Single submission AN ulti submission AN Expiration date AN Accessibility indicator N block count AN system code A Not used InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

6 1.3. Second level label (HDR2) HDR2 is an optional segment in the BACS and can be used once per the HDR1 segment. Field Pos Type Name Value / A Label identifier HDR N Label number A Record format N Block length Record length N Single processing day payment ulti processing day payment AN Not used N Buffer offset Not used 1.4. User Header Label (UHL1) UHL1 is a mandatory segment in the BACS and can be used once per the HDR1 segment. Field Pos Type Name Value / A Label identifier UHL N Label number 1 Processing date Single processing day payment byyddd - Julian date preceded by a blank AN ulti processing day payment ust be empty N Identifying number of receiving A party AN Currency code N Country code Normal: {Empty} or "1bDAILYbb" or "4bULTIbb" Urgent: "1UDAILYbb" or AN Work code and urgency flag "4UULTIbb" Where "U" in Position 30 triggers an urgent payment N File number Not used AN Audit print identifier Not used InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

7 1.5. Body record: Transaction records TRA is a mandatory segment in the BACS and can be used multiple times per UHL1 segment. Field Pos Type Name Value / N Destination sorting code number BACS clearing sort code N Destination account number N Destination account type AN Transaction Code Z4, Z5 or N riginating sorting code If there are multiple body records followed by one contrarecord, all ordering sort codes need to be equal N riginating account number If there are multiple body records followed by one contrarecord, all originating account numbers need to be equal AN Free format - End-to-End-Id N Amount (in pence) AN Service user's name AN Service user's reference Unstructured remittance information AN Destination account name AN Processing date Single processing day payment ulti processing day payment If UHL1_3 is not used, execution date will be set to TRA_12 ust be empty byyddd - Julian date preceded by a blank InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

8 1.6. Body record: Contra records CN is a mandatory segment in the BACS and can be used multiple times per UHL1 segment. The contra record which follows one or multiple transaction records indicates the grouping of the debit posting. Field Pos Type Name Value / A 1-6 N Destination sorting code number same as TRA_5 B 7-14 N Destination account number same as TRA_6 C 15 N Destination account type 0 D N Transaction Code 17 E N riginating sorting code same as CN_A F N riginating account number same as CN_B G AN free format - order reference H N Amount Total of all TRA amounts I AN Narrative J A Contra identification CNTRA followed by spaces K L AN AN Abbreviated originating a/c name Processing date Single processing day payment ulti processing day payment byyddd - Julian date preceded by a blank ust be empty 1.7. First end of record (EF1) EF1 is an optional segment in the BACS and can be used once per the HDR1 segment. Field Pos Type Name Value / A Label identifier EF N Label number Same as HDR1 fields 3 to block count Same as HDR1 fields 13 to Second end of record (EF2) EF2 is an optional segment in the BACS and can be used once per the HDR1 segment. Field Pos Type Name Value / A Label identifier EF N Label number Same as HDR2 fields 3 to 8 InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

9 1.9. User trailer label record (UTL1) UTL1 is a mandatory segment in the BACS and can be used once per the HDR1 segment. After a UTL1 record a new order can be inserted, starting with HDR1 again. Field Pos Type Name Value / A Label identifier UTL N Label number N Total amount of credit contras Debit value total (resp. debit) N Total amount of credit (resp. Credit value total debit contras) N Number of credit contras (resp. Debit item count debit) records N Number of credit (resp. debit Credit item count contras) records Not used N DDI count For other use InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February

10 2. Sample VL1SGID1 INNAE HDR UHL ULTI E2E SERVICE USER NAE USTRD REITTANCE DEST AC NAE E2E SERVICE USER NAE USTRD REITTANCE DEST AC NAE E2E SERVICE USER NAE USTRD REITTANCE DEST AC NAE E2E SERVICE USER NAE USTRD REITTANCE DEST AC NAE REF CNTRA RDERING AC NAE E2E SERVICE USER NAE USTRD REITTANCE DEST AC NAE REF CNTRA RDERING AC NAE UTL InsideBusiness Payments - Addendum BACS STD18, Version 1.1, February