Upload CSV File Format

Introduction

This section serves as a comprehensive guide to the required template format for performing bulk Verification of Payee (VOP) checks within the VOP Portal. The template detailed here is designed for use with CSV file, providing a consistent and efficient way for submitting large batches of IBANs for verification.

Template Formatting Guidelines

Adhering to the following formatting rules is essential to ensure your file is processed correctly and efficiently.

    • Use clear and unique file names to help identify each batch - consider including a date, batch number or other unique identifiers.
    • Double check for extra spaces before, in between or after values, especially in the field names (headers), Beneficiary Name or Beneficiary IBAN.
    • Avoid blank rows or merged cells/rows, these can cause errors during processing.
    • Ensure there are no formulas or macros in the file, only plain data should be included.
    • Use consistent data formats, aligned with the formats specified in the tables below.
    • Ensure a semicolon (;) delimiter is used.
    • Enclose names containing special characters (such as commas, semicolons or pipes) in quotation marks (“ ”).
    • Save CSVs in UTF-8 encoding to ensure special characters are preserved.

The fields that can be included when uploading a CSV are explained in the table below. The fields can be included in any order within the file.

FieldMan*FormatDescription
E2E IDOStringUnique end to end ID to uniquely track and trace individual transactions throughout the process. This identifier is
shared with the Payee Bank.
Usage Rule: If provided it is used otherwise it’s generated by SurePay on behalf of the customer.
We recommend you add this ID yourself for traceability and audit logging.
Beneficiary NameCString
Max Length: 140		The name of the Beneficiary.
    Mandatory for Natural Person.
    Optional for organisations.
Usage Rule: If name is included, the identification fields cannot be used in the same request.
Beneficiary LEICString
Max Length: 20		LEI is a code allocated to an organisation as described in ISO 17442.
Usage Rule: Can only be used if other and anyBIC fields are not used.
Format: ^[A-Z0-9]\{18}[0-9]\{2}$
Beneficiary ORG BICCString
Max Length: 11		Business Identification Code of the organisation.
Usage Rule: Can only be used if lei or other are not used.
Format: [A-Z0-9]\{4,4}[A-Z]\{2,2}[A-Z0-9]\{2,2}([A-Z0-9]\{3,3})\{0,1}
Beneficiary Other ORG IDCString
Max Length: 256		The identification code of the organisation when not a LEI or BIC.
Usage Rule: Can only be used if lei and anyBIC are not used.
Scheme Name CodeCEnumThe type of organisation identification.
Usage Rule: Either Scheme Name Code or Scheme Name Proprietary is used.
Find the code list here.
Scheme Name ProprietaryCString
Max Length: 35		The name of the identification scheme in free text.
Usage Rule: Either Scheme Name Code or Scheme Name Proprietary is used.
IssuerOString
Max Length: 35		The entity that assigned the identification.
  • You can find more information here.
  • You can find the latest list of issuers here.
IBANMString
Max Length: 34		The International Bank Account Number of the Beneficiary.
Format: ^[A-Z]\{2}[0-9]\{2}[A-Z0-9]\{1,30}$
Additional Reference NoOString
Max Length: 140		Additional information about the account number, i.e. in the case of a collection account, credit card etc.
Beneficiary Bank BICCString
Max Length: 11		The Beneficiary Bank’s BIC code.
Usage Rule: Mandatory when Requesting PSP does not utilise the SurePay BIC Enrichment service.
Format: ^[A-Z]\{6}[A-Z0-9]\{2}([A-Z0-9]\{3})?$

* Man = Mandatory. Values: M = Mandatory, C = Conditional, O = Optional

Previous
Next