Generic Bank Payment File Type
Learn how to structure your bank payments and manage their associated files using generic file formats.
Written by Grainne Reidy
Updated at September 23rd, 2026
Introduction
Bespoke vs Generic Formats
The following options are available to use with Bulk Payments:
- Bespoke formats: After completing a Bulk Payment, download the Bank Payment File, such as BACS & SEPA.
- Generic format: After completing a Bulk Payment, download the generic XML / JSON format and use a third-party system to transform it into the required format for your bank.
Note
The word “generic” does not mean that this file will work for all bank or transaction types. It means that the bulk payment information will be exported with a common structure in two widely accepted formats. This gives you the necessary data to use a third-party service or system that transforms the generic format into that of your bank's.
See:
Selecting a generic file format
To select a generic format:
- Go to Bank > Bank List.
- In your bank entry, click on A/C Details.
- Under Online Banking, go to Type. Select one of the following:
- Generic Export JSON Format (.JSON)
- Generic Export XML Format (.xml)
- Click Save.
Generic file structure
File Information
BatchDate: Date of the Batch Payment (Date and Time).BatchNumber: User-entered Identifier entered (String).BatchPaymentTotal: Total amount from all payments within this file rounded to two decimal points.CreationDate: Date when the batch was downloaded (Date and Time).FileNumber: Internal 3 digits online file number (String).NumberOfTransactions: Total number of payments made to beneficiaries within this file.OnlineUserID: Given by the Bank and manually entered by system-user. It can be also called SUN (Service User Number), OIN, Customer ID, or Organization Identification.PaymentID: Internal unique identifier (Integer).Debtor Information
BankAccountNumberBankCountryCodeBankCurrencyCodeBankIbanBankOnlineTypeBankSortCodeBankSwiftCodeCompanyBaseCurrencyCodeCompanyCityTownNameCompanyCountryCompanyCountyCompanyNameCompanyStreetNamePayment Line objects
BeneficiaryAddress1BeneficiaryAddress2BeneficiaryBankAccountNumberBeneficiaryBankAddress1BeneficiaryBankAddress2BeneficiaryBankCityBeneficiaryBankCountryBeneficiaryBankCountyBeneficiaryBankNameBeneficiaryCityBeneficiaryCountryBeneficiaryCountyBeneficiaryCurrencyCodeBeneficiaryEmailBeneficiaryIbanBeneficiaryIDBeneficiaryISOCountryCodeBeneficiaryNameBeneficiaryPostCodeBeneficiaryRoutingNumberBeneficiarySortCodeBeneficiarySwiftCodePaymentAmountPaymentLinePaymentReferenceInfo
The Beneficiary Routing Number and Beneficiary Swift Code are mutually exclusive. They both come from the Bank Swift Code field in the Supplier Account. If the supplier swift code only contains digits, then we output that into the Beneficiary Routing Number of the file. If it contains other letters/symbols then we output that under Beneficiary Swift Code.