Help Centre Sending & receiving payments

How do I send batch payments?

In this step-by-step guide, we'll show you how to set up, process, send, and manage batch payments from your Client Portal. Let's get started.

Enabling Batch Payments

Before you can use batch payments, you'll need to activate the feature on your account. To do this, get in touch with your Client Manager, and they will take care of everything for you.

Accessing Batch Payments

After enabling batch payments, you can access the option in your Client Portal.

  • Click on the "Transfer Money" button.

  • Select an account to send batch payments from in the dropdown menu.

At the bottom of the 'Transfer Money' form, you'll see a link named "Use our Batch Payment Import". Click it.

Preparing Your CSV File

On the batch payment page, you'll see options to:

  • Choose the account you want to send batch payments from.

  • Upload a CSV file.

  • Download a sample file.

  • View information about required fields.

What's in the CSV?

The recommended action is to download the sample file as a helpful reference. Ensure your CSV file contains the specified fields: 

payment type, company, title, name, lname, house, address1, address2, address3, town, county, postcode, country, telephone, mobile, email, gender, dob, idtype1, idnumber1, idtype2, idnumber2, bank-name, bank-address, bank-country, swift, bank-code, bank-key, sort-code, holding-branch, branch-code, account-name, account-number, account-type, iban, amount, account-fees, reference, purpose, transaction-id

Please follow the Fixed Column Structure. You cannot add, rearrange, or remove the number of CSV columns - they must remain the same and in the same order as specified.

Required Fields in a CSV File

Determining which fields are required in your CSV file is crucial for a successful batch payment process. The actual requirements for the fields can vary based on multiple factors:

  • Account Origin: The account you are transferring from can affect which fields are mandatory.

  • Payment Type: The payment type, such as "SEPA Payment," can also dictate the required fields.

Payment Type Dropdown

When selecting a payment type from the dropdown menu, you will see a table listing the required or optional fields for that specific payment type.

Populating the 'payment-type' Field

The 'payment-type' field in your CSV file must match the payment type you select in the dropdown menu.

For example, if you choose "SEPA Payment" from the dropdown, your CSV file's 'payment-type' column should also read "SEPA Payment."

Filling in the CSV File

  • Mandatory fields: The table you see after selecting a payment type will show you all the mandatory fields. Ensure these are filled in your CSV file.
     

  • Optional fields: Fields marked as optional can be left blank if they do not apply to your transaction.
     

  • 'amount': The 'amount' field is always required regardless of the payment type.

Guide to CSV fields

In addition to the real-time requirements shown in the Client Portal, we have provided a list of all the possible fields below, along with their meanings and general instances of when they might be required or optional.

Please Note: The list only serves as a general guide. For the most accurate and up-to-date requirements tailored to your specific account, payment type, and bank, always refer to the information displayed in your Client Portal.

  • payment-type
    Payment Type

    Specifies the type of payment.
    Options include "Internal transfer," "SEPA Payment," or "SWIFT  Payment," defining the nature and route of the transaction.  Required.

    company
    Company Name or First Name, Last Name

    Indicates the business entity or individual receiving the funds. Required in: Internal transfer, SEPA Payment, SWIFT            Payment.

    fname
    First Name

    The first name of the individual who is the payment recipient.
    Optional in: Internal transfer, SEPA Payment, SWIFT Payment.

    lname
    Last Name

    The surname or last name of the individual receiving the payment.
    Optional in: Internal transfer, SEPA Payment, SWIFT Payment.


    house
    [Often blank]
    House Number

    Refers specifically to the house number in the recipient's address.

    address1
    Main Street Address

    The main part of the street address.
    Required in: SWIFT Payment. Optional in: SEPA Payment.

    address2
    Secondary Address Details

    Secondary details of the address, like apartment or suite numbers.
    Optional in: SEPA Payment, SWIFT Payment.

    address3
    [Often blank]
    Tertiary Address Details

    Tertiary address details, often an optional field.

    town
    Town/City

    Name of the town or city. 
    Optional in: SEPA Payment, SWIFT Payment.

    county
    [Often blank]
    Specific County

    The specific county for the recipient's address.

    postcode
    Postal/ZIP Code

    The postal or ZIP code for the recipient's location.
    Optional in: SEPA Payment, SWIFT Payment.

    country
    Country of Recipient

    Country in ISO 3166-1 alpha-2 code format.
    Required in: Internal transfer, SWIFT Payment.
    Optional in: SEPA Payment.

    telephone
    [Often blank]
    Home-Phone

    The recipient's home telephone number.

    mobile
    [Often blank]
    Mobile-Phone

    The mobile number for the recipient.


    email
    [Often blank]
    Email

    The email address of the recipient.

    gender
    [Often blank]
    Gender

    The gender of the recipient, 'm' for male or 'f' for female.

    dob
    [Often blank]
    Date of Birth

    Formatted as YYYYMMDD.

    idtype1
    [Often blank]
    IDType1

     

    idnumber1
    [Often blank]
    IDNumber1

     

    idtype2
    Entity Type

    Specifies entity type. Possible options are: "Legal Entity," "Individual."
    Required in: SEPA Payment, SWIFT Payment.
    Optional in: Internal transfer.

    idnumber2
    Company Website

    Optional in: SEPA Payment, SWIFT Payment.

    bank-name
    Recipient's Bank Name

    Required in: SEPA Payment, SWIFT Payment.

    bank-address [Often blank]
    Bank-Address

    The physical or postal address of the recipient's bank.

    bank-country
    Bank's Country

    In ISO 3166-1 alpha-2 code. Required in: Internal transfer, SEPA Payment, SWIFT Payment.

    swift
    SWIFT/BIC

    Length must be 8-11 characters.
    Required in: Internal transfer, SEPA Payment, SWIFT Payment.

    sort-code
    Sort-Code

    A six-digit number, often used in the UK, or in DK as bank code.

    bank-key
    [Often blank]
    Bank-Key

    A specialized banking identifier.

    sort-code
    [Often blank]
    Sort-Code

    A six-digit number, often used in the UK.

    holding-branch [Often blank]
    Holding-Branch

    The specific branch where the account is held.

    branch-code [Often blank]
    Branch-Code

    A unique identifier for the specific branch holding the account.

    account-name
    Account Name

    The registered name on the account.
    Required in: Internal transfer, SEPA Payment, SWIFT Payment.

    account-number
    MCV or IBAN or Account Number

    Required in: SWIFT Payment.
    Optional in: Internal transfer.

    account-type [Often blank]
    Account-Type

    Specifies the nature of the account.

    iban
    International Bank Account Number

    Must be 14-31 alphanumeric characters.
    Required in: SEPA Payment, SWIFT Payment.

    amount
    Transaction Amount

    Specifies the amount to be transferred.
    Required in all payment types.

    account-fees [Often blank]
    Account-Fees

    Any extra fees or charges. Leave this field empty.

    reference
    Reference or Description

    Any extra information.

    purpose
    Purpose or Payment Code

    The reason or purpose for the transaction.

    transaction-id
    Transaction ID

    A unique identifier that can be generated for each transaction. While optional, it is recommended to populate this field. Transaction IDs enable tracking of payments and auditing. They also prevent duplicate processing if the same file is uploaded multiple times, since transaction IDs should be unique. Including a transaction ID provides visibility into payment status and protects against accidental duplicates.

     

Is there a limit on how may transfers I can make?

We don't recommend sending more than 100 transfers within one CSV file. If you have difficulty processing large batch payments, you can split them into smaller files and process up to 20-30 payments simultaneously.

Batch payment troubleshooting

You get an error that the file name has already been used

We check if the file has been used before to avoid executing the same payments twice. In some cases, if batch processing is interrupted, it might still register as being used the next time you try to use it again.

To solve this, please, change the file name and try again.

You are returned to the first step after confirming the batch import

On average, processing 30 payments takes less than 1 minute, which may be longer if you have a larger batch file. If, after waiting, you get redirected back to the first step, the processing might be stuck. If this happens, please change the file name and try again.

You receive an error about having 41, 42 or more columns

This happens when your batch file has values outside the accepted range in columns. Please review the file to see if any fields in the “purpose” column are filled with a value, an extra space or additional characters. 

You receive an error about having 38, 37 or less columns

This means that your batch file does not contain all the necessary information. Even if they are not used, batch files require all empty columns to be present. Please compare your batch file to our template example (found in your Client Portal) to see which columns have been removed and restore them to your CSV file.

You receive an error about a value being too long

This error is usually caused by value length exceeding the limit. The most common fields where this error happens are the address and company name. To correct this, please shorten the value within the correct limits as required.

Invalid account number - in case IBAN or account number is 12 numbers or longer

Excel tends to shorten very long numbers. An example of this would be shortening an account number from “90000000000000000” to “9E+16”. Please apply suitable Excel formatting options by switching from “General” to “Number” while ensuring no decimal numbers are included.

Invalid account number 

This error may occur if the account number or bank code starts with zero (0). In Excel, a leading zero is usually removed from a cell, making the account number invalid. When sending money to account numbers starting with zero, please apply Text formatting to the required cells.

Need help setting up batch payments?

If you encounter any issues or have questions, please get in touch with your Client Manager.