CSV File Format (Request)
The CSV request file contains the payment details required to perform multiple Verification of Payee checks, with each row representing an individual payee verification request.
Request File Guidance / Best Practice
Please follow the "best practice" formatting guidance set out below. Keeping to this guidance will ensure your file is processed correctly and is not rejected.
- Use the following file naming convention to ensure each file uploaded is unique and identifiable from other file uploads.
- file name must start with the prefix "vop_req" to identify this as a VoP Request file
- file name must include your "company short name", agreed with your assigned Apicunia account manager during technical onboarding
- file name must include a date formatted as "yyyyMMdd"
- file name must include a "batch number" to uniquely identify the file incase of multiple files uploaded on the same date. Format: 3 digits starting 001 through to 999
^(?!000)[0-9]{3}$ - Required format file name: "vop_req_companyshortname_yyyyMMdd_batchnumber.csv"
- Example file name: "vop_req_bobsbank_20260827_001.csv"
- Include column headers in the file, as specified in the table below.
- Use only the specified data type/format for each column in the file, as specified in the table below.
- Trim any leading and trailing spaces around values.
- Do not include empty/blank rows.
- Ensure a comma (,) delimiter is used.
- Enclose all column headers and values in quotation marks (" ").
- Use UTF-8 encoding for the file to ensure preservation of any special characters.
Request File Structure
The structure of the request CSV file to be used for upload is detailed in the table below.
| Column (Header) | Data Type | Format | Required | Description |
|---|---|---|---|---|
CorrelationId | string | max length: 100 | Yes | A unique value to track/trace each individual request within the file. This could be a unique value from an external system (e.g. uuid, integer or another unique identifier) |
Iban | string | max length: 34 | Yes | The International Bank Account Number (IBAN) of the Payee. Format: ^[A-Z]{2}[0-9]{2}[A-Z0-9]{1,30}$ |
PartyIdentifier | string | max length: 140 | Yes | Either the Payee Name (PartyName) or the Payee ID (PartyId), depending on the specified PartyType. ID formats must adhere to standard VoP rules. See here |
PartyType | string | max length: 9 | Yes | One of PartyName or PartyId (case-insensitive) |
IDType | string | max length: 10 | Conditional | When PartyType is PartyId this must contain either LEI, ANYBIC or a valid SchemeNameCode (SREN,TXID etc). See here |
Sample Request File Structure
Below is sample CSV request file using a mixture of both Name (Personal and Legal) and ID based VoP requests:
This is dummmy account data that can be used against the Bulk File Service Sandbox;
vop_req_bobsbank_20260827_001.csv
"correlationid","iban","partyidentifier","partytype","idtype"
"1","DE33500105175746121394","Lukas Klein","partyname",""
"2","BE19131422633712","Marc Bart","partyname",""
"3","HR1523400098798559268","Marija Horvat","partyname",""
"4","CZ6508000000192000145399","TOTRO TRUCKS a.s.","partyname",""
"5","DE03500105176539151254","INGDDEFFXXX","partyid","ANYBIC"
"6","LU480105958751389217","ZDRR00LIUAK4DOUWA805","partyid","LEI"
"7","EE941278378388623643","Alysa Saar","partyname",""
"8","BE58233874292679","BE0445661649","partyid","TXID"
"9","AT412040426856977333","D8LO002OE85NREDPXC66","partyid","LEI"
"10","HR4625000091742766125","EU87105440722","partyid","EUID"