SAP BCM – XML Banking in UK – Barclays Example

Scope – All outgoing payments will be sent in XML format Version 3 through Bank Communication
Management (BCM) using Swift interface.

Banks in Scope – Barclays bank

Bank Countries in Scope – GB, CH

Payments – F110S outgoing payment runs have been scheduled on autosys. Payment runs will be batched
automatically in BCM and payment files will be sent automatically to bank through Swift interface. Swift will
send status messages for these payments when they receive the payment files and when these files are
sent to bank. After the files are processed at bank, they will send us Payment Status Report (PSR) with
status of payments which will be automatically updated in BCM. Payments can be monitored in BNK_MONI.

Payment methods:

Payment methods mapping – Old v/s New CGI

 Old payment methods are mapped with new CGI payment methods in below table.
 Request execution date in the payment file will come depending on the type of payment and
payment method used. Details on value dates are given in below table:

1
Duplicate payment validation :

Duplication validation is done by the bank at file level and payment level. If the file which has already been
processed earlier is resent again within 3 months then bank will reject the entire file. There is a second level
validation at the transaction level. EndtoEndId is checked at client level (For all Our accounts together) for
a period of last 3 months and if there is duplication than the payment will be rejected. EndtoEndId will have
payment document number followed by paying company code.

1. Payment Method 3 – Urgent payments (Domestic and Foreign)

Business Description
Urgent payments with same day value date.

Background
In country GB, Urgent same day payments are required for both domestic and foreign payments. In
country CH, Urgent same day payments from Barclays bank account can only be made for GBP
payments. Domestic payments if sent as urgent payments will not be considered as BSAP payments and
will not follow 3 days payment cycle.

Vendor Master Data

2
  IBAN is not mandatory to be populated in vendor master however it is recommended to use
IBAN’s where applicable.
 If IBAN is not available then bank account number will be sent.
 Request execution date will be same as posting date on the F110 payment run
 URGP will be sent as the Service level code in payment file

2. Payment Method 4 – BSAP payments in CH

Business Description

BSAP payment where bank country is CH. BSAP payment will follow 3 days payment cycle.
Example – If payment run is done on D then request execution date on payment file will be D+1. Our
bank account will be debited on D+1 and beneficiary will receive the payment on D+2. We have also
used factory calendar for calculating the value date which means if the execution date falls on a weekend
or holiday it will be rolled over to next working day.

Background

New XML version 3 will populate the payment files with information required for BSAP payments

Vendor Master Data

 IBAN is not mandatory to be populated in vendor master however it is recommended to use

IBAN’s.
 If IBAN is not maintained then bank account number will be sent in the payment file.
 Service level code will be sent as NURG.
 Service User Number (SUN) is required to be sent in payment files for all BSAP outgoing
payments. These numbers are specific to each entity and assigned in house bank configuration
from where it is picked and sent in the payment files.

3
There is no itemized reporting for BSAP payments in MT940 statements as it is received as a single
consolidated amount. To identify if the amount is related to BSAP payment, BSAP has been added in
PmtInfId tag of payment file. PmtInfId is received in tag 61 of MT940 statements. This value will be used
for automatic clearing in autobank rules.

3. Payment method 5 – BSAP payments in GB

Business Description
BSAP payments where bank country is GB. BSAP payment will follow 3 days payment cycle.
Example – If payment run is done on D then request execution date on payment file will be D+1. Our
bank account will be debited on D+1 and beneficiary will receive the payment on D+2. We have also
used factory calendar for calculating the value date which means if the execution date falls on a weekend
or holiday it will be rolled over to next working day.

Background

New XML version 3 will populate the payment files with information required for BSAP payments

Vendor Master Data

 IBAN is not mandatory to be populated in vendor master however it is recommended to use

IBAN’s.
 If IBAN is not maintained then bank account number will be sent in the payment file.
 Service level code will be sent as NURG.
 Service User Number (SUN) is required to be sent in payment files for all BSAP outgoing
payments. These numbers are specific to each entity and assigned in house bank configuration
from where it is picked and sent in the payment files.

4. Payment Method 6 – Wire payments without IBAN – This payment method should be used for Wire
payments to vendors / countries where IBAN is not available.

Value date – If payment run is done on D then request execution date on payment file will be D+2.

4
5. Payment method 7 – Wire payments with IBAN – This payment method should be used for Wire
payments to vendors / countries where IBAN is available.

Value date – If payment run is done on D then request execution date on payment file will be D+2.

6. Payment method 8 – EUR SEPA CT Payment – This payment method should be used for EUR
payments within EU (SEPA zone) from Our EUR bank account and where beneficiary has a valid swift
code and IBAN

7. Payment method 9 – UK Direct Debit collection from customers – This payment method should be
used for GBP cash collections from customers. It is not SEPA direct debit collection and therefore no SEPA
mandates are required to be created.

 Value date – If payment run is done on D then request execution date on payment file will be
D+1.
 Service User Number (SUN) is required to be sent in payment files. These numbers are specific
to each entity and assigned in house bank configuration from where it is picked and sent in the
payment files.

5
House Bank configuration for Service User Number (SUN)

Note – First 6 characters is SUN for outgoing payments and next 6 characters after hyphen is SUN for
incoming cash collections. There are some company codes where same SUN number is used for
outgoing payments and incoming cash collections, in these cases same number should be maintained
as first 6 digits and last 6 digits.

Few other codes are also required to be sent in payment files for customer cash collections for which
instruction keys have been created and assigned to payment method 9. Depending upon the type of
direct debit, instruction key will have to be assigned in customer master or at invoice level. If instruction
key is not assigned then it will default to 51 (Recurrent Customer Direct Debit)

6
Note – If the direct debit collection is other than Recurrent(RCUR) which has been defaulted, it will
be the responsibility of TECHNICAL ACCOUNTING to get correct instruction key assigned in
customer master or invoice otherwise payment will fail.

Naming convention of payment files:

 Outgoing payments - 3_PN13_XXXX_YYYY_ZZZZ

 Incoming payments – 3_PN82_XXXX_YYYY_ZZZZ

XXXX – Paying company code

YYYY – Bank name – BARC

ZZZZ – Internal sequential number generated by SAP

Naming convention of Payment Status Report (PSR) from bank

PSR will start with BARC*, followed by date and SNL number from Swift.

MT940 bank statements

MT940 statements will be received through the Swift channel. Barclays bank will be sending individual bank
statements for each entity which will be re-grouped at Corporate ECC system for each country and sent to
SAP. Mapping table has been maintained in Corporate ECC system with tag 25 details and bank statement
group in which SAP will get the statement. Autosys jobs have been set up which will upload these bank
statements automatically.

In MT940 statements received through Swift for all foreign bank accounts, tag 25 will have sort code 207102
instead of 201174 due to a limitation in bank’s system. These values are therefore maintained in alternate
bank account in House bank configuration.