5 Min read

Ebury's Mass Payments client toolkit

We are pleased to share with you our new client toolkit. These comprehensive documents can support you throughout your use of our innovative online payments platform.

Last updated:
09/29/2026

We are pleased to share with you our new client toolkit. These comprehensive documents can support you throughout your use of our innovative online payments platform.

Speak to our team
Content

Testo del pulsante

‍

Client cut off times

This document explains the cut off times and processing days incurred for each currency allowing you to accurately plan your payments.

Beneficiary requirements

This will outline the beneficiary information that we require to pay your beneficiaries in our extensive range of currencies.

Multipayment spec sheet

This document outlines the formatting requirements for our multipayment upload file. The multipayment function allows quick and seamless execution of many payments in multiple currencies in one upload file.

Using a file to instruct bulk payments

Ebury offers clients an easy way to bulk pay beneficiaries. Their Multipayment functionality lets you book payments in many currencies and execute larger payment runs through a single file upload.

Formatting guidance
  • File can be .csv, .xls or .xlsx
    ‍
  • If using .csv, fields must be comma-delimited (,) and data enclosed in double quotes (" ") — e.g. "beneficiary name","beneficiary address","DE","EUR", etc.
    ‍
  • The first row is the header and is ignored on upload
    ‍
  • "Yes" = always mandatory; "*" = mandatory only when creating a new beneficiary (or conditionally, as noted in the description). if the beneficiary isn't already in the system, some additional fields become mandatory to create them — marked with a star (*)
    ‍
  • Cell data in columns 1, 2, 6, 7, 8, 9, 14, 15, 16, 18, 19, 24, 27, 28, 29, 30, 31 must contain no spaces
    ‍
  • For country code formats, see ISO 3166-1
  • ‍
    ‍
  • Column Name Mandatory Description
    1DirectionYesBUY or SELL — used to calculate the payment amount (Column 8). No spaces.
    2ProductProduct for execution (default: 'SPOT'). No spaces.
    3Beneficiary Name*Name as per receiving bank account. Letters, numbers, and only these symbols: / - ? ( ) . , ' + { }. No accents or other special characters.
    4Beneficiary Address 1Address of the beneficiary
    5Beneficiary CityCity of the beneficiary
    6Beneficiary CountryYes*Two-character ISO 3166-1 code (e.g. GB, US, ES, NL). No spaces.
    7Payment CurrencyYes*Three-character ISO 4217 code (e.g. GBP, USD, EUR, AUD). No spaces.
    8Payment AmountYes*Amount in the direction currency (Column 1). Decimals must use a dot (.). No spaces.
    9Settlement CurrencyCurrency of the sell side of the trade. Currently ignored — chosen on the platform when uploading the file. No spaces.
    10Bank NameName of beneficiary bank
    11Bank Address 1Address of beneficiary bank
    12Bank CityCity of beneficiary bank
    13Bank CountryYes*Two-character ISO 3166-1 code (e.g. GB, US, ES, NL)
    14Account No*Account number of the beneficiary. Mandatory only if IBAN not entered (Column 15). No spaces.
    15IBAN*IBAN of the beneficiary. Mandatory only if Account Number not entered (Column 14). No spaces.
    16Swift Code*SWIFT BIC of the beneficiary bank. No spaces.
    17Payment ReferencePayment narrative shown on beneficiary's statement. Numbers, letters, and some symbols only: . : + ( ) ? ' - (35 characters max)
    18Bank CodeNational Clearing Code of the bank account (e.g. UK sort code, US ABA or Fedwire number, Australian BSB). Mandatory for some currencies — speak to your account manager. No spaces.
    19Value DateValue date (the crediting date) of the payment, in DD/MM/YYYY format. If left blank, defaults to SPOT (T+2) where available. No spaces.
    20Remitter NameName of the remitter
    21Remitter Address Line 1Address of the remitter
    22Remitter Address Line 2Address of the remitter
    23Remitter Account NumberAccount number of the remitter
    24Remitter CountryCountry of the remitter. No spaces.
    25Reason for paymentPurpose or reason for payment. Mandatory for certain payment currencies and countries — speak to your account manager for more information.
    26Beneficiary referenceA permanent, fixed payment reference assigned to the beneficiary (if creating for the first time). Pulls through as the payment reference on every future payment to this beneficiary.
    27Purpose code*(CNY payments only) 6-letter purpose code. No spaces.
    28INN*(RUB payments only) Registration Number in Tax authorities. Should consist of 10 digits (legal entities) or 12 digits (individuals). No spaces.
    29VO*(RUB payments only) Currency Operation Code. Should consist of 5 digits and start with "VO". No spaces.
    30KIO*(RUB payments only) Tax ID for foreign legal entities in Russia. 5 digits. No spaces.
    31Russian central bank account*(RUB payments only) 20 digits. No spaces.

    ‍

    File upload troubleshooting

    A guide to resolving multipayment upload errors with examples of cause and solution. (plain text page)

    Commonly used terms

    A quick look up guide of industry language and acronyms. (glossary)

    Client FAQs

    Frequently asked questions and quick tips to streamline your experience and build your knowledge of our payments booking platform. (help centre)

    ‍

    ‍

    Commonly used terms

    No items found.

    If you have any questions or queries on any of these documents, please do not hesitate to contact your account manager. We are constantly updating these documents, and the most recent versions will always be available in this toolkit. Please check back frequently for updates. Please contact your account manager for any further queries at the below details:
    ‍

    Ebury Mass Payments Ltd
    Tel: +44 1494 484183 | Email: masspayments@ebury.com

    ‍

    ‍Ebury Payments Pte Ltd
    Tel: +65 6817 5248 | Email: singapore@ebury.com
    ‍

    Ebury Mass Payments Limited is Authorised and Regulated in the UK by the Financial Conduct Authority under the Payment Services Regulations 2017 for the provision of payment services (FRN577057) and regulated by HMRC (MLR12572236). Ebury Mass Payments Limited is a registered company in England and Wales (7061945). Ebury Payments Pte Ltd is authorised and regulated in Singapore by the MAS under the Payment Services Act (Licence No. PS20200148). Ebury Payments Pte is a registered company in Singapore (201733573G). Our corporate bankers hold all client monies in segregated accounts.

    Ebury
    Unlock global growth

    About  Ebury

    Helping businesses unlock 
their global growth potential

    Ebury is a global fintech powering international growth for ambitious businesses in a frictionless economy. With majority backing from Santander, we offer an integrated, cross-border platform for payments and currency risk management, together with local market expertise.

    Ebury is a global fintech powering international growth for ambitious businesses in a frictionless economy. With majority backing from Santander, we offer an integrated, cross-border platform for payments and currency risk management, together with local market expertise.

    50+

    Offices Worldwide

    30+

    Regulated Markets

    1.9M+

    Payments processed in 2025

    25K

    Transacting clients