How to process e-Payments

Banking software	Adam Online
Required component	Adam Online
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments as normal.

You mustn't amend the reference for the transaction. If this is changed from a reference of BACS, the transaction doesn't appear in the E-payments option. Also payments posted using Batch Supplier Payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.
Click OK and complete the Sage Adam Online Payment Processing window as follows:

Standard Domestic/IATs - You should select this option if there's no template or bulk list created in Adam Online.
Use a Template for Domestic/IAT - If there's a template in Adam Online, you should select this option then enter the template reference in the Online Payment/Bulk List Template box.
Bulk List Payments - If a bulk list exists within Adam Online, select this option, enter the bulk list reference in the Online Payment/Bulk List Template box then enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Adam Online must have the same bulk list reference, beneficiary account details and references.
If you choose the Bulk List Payments option, the relevant supplier's record must contain a beneficiary id in the BACS Ref box in the Bank tab.
If the payment file includes inter account transfers (IATs), select the Do you wish to define Payments as being 'Inter Account Transfers' (IATs)? check box then select the transactions that are IATs and click Set.
Ad Hoc Bulk Payments - If a bulk list exists within Adam Online, select this option to make Ad-Hoc bulk list payments, enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Adam Online must have the same beneficiary account details and references.
If you don't know which option to choose or what details to enter, please refer to your Adam bank support contact.

Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.

Potential issue with the bulk list payment files including the letter C

When you generate the payments file and select the Bulk List Payments option, the output file includes a letter C in the header row.

The file is correct to include the C, for the following reasons:

This is the specification that was provided to us originally by the bank.
The C indicates that a remittance will be printed from Bankline.
For any newly created bulk list payment in Bankline, this is the default setting and can't be switched off.

For older bulk lists, this wasn't the case and it was possible to create a bulk list where a remittance wouldn't be printed and this is where a problem arises.

If you generate a payment file from Sage Accounts and combine this with an old bulk list that doesn't require a remittance, the payment file is rejected. In this case, you must remove the letter C from the payment file then try importing the payment file again.

Choose your banking software:

Banking software	iBusiness Banking (iBB)
Required component	Allied Irish iBB
E-payments file type	Text file (*.TXT)

When you import the file into iBB, you must choose APACS from the File Format drop-down list and not Sage.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Allied Irish iBB Payment Processing window then click OK.

If you don't know what to enter in these boxes, please refer to your Allied Irish support contact.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be eight digits.
Bank	Bank Details	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	If left blank, it uses the transaction details, for example Payment on Account. You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Allied Irish Bank SEPA
Required component	Allied Irish Bank SEPA
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Allied Irish iBB Payment Processing window then click OK.

If you don't know what to enter in these boxes, please refer to your Allied Irish support contact.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Choose your banking software:

Banking software	Bank of America
Required component	Bank of America
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Bank Of America Processing window as required then click OK.

If you don't know what to enter in these boxes, please refer to your Bank of America support contact.
To save the file . Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	If left blank, it uses the transaction details, for example Payment on Account. You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Bank of America SEPA
Required component	SEPA Credit Transfer 1
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Bank Of America Processing window as required then click OK.

If you don't know what to enter in these boxes, please refer to your Bank of America support contact.
To save the file . Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Choose your banking software:

Banking software	Business On Line
Required component	Bank of Ireland Business On Line
E-payments file type	Text file (*.TXT)

View example file

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank of Ireland BOL Payment Processing window then click OK.

If you don't know what to enter in these boxes, please refer to your Bank of Ireland support contact.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	If left blank, it uses the transaction details, for example Payment on Account. You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Bank of Ireland SEPA
Required component	Bank of Ireland SEPA
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank of Ireland SEPA Payment Processing window then click OK.

If you don't know what to enter in these boxes, please refer to your Bank of Ireland support contact.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Choose your banking software:

Banking software	Business Internet Banking Business Master Business Master Lite Barclays.Net
Required component	Barclays Business Master II
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and create the file again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Barclays Bank SEPA
Required component	SEPA Credit Transfer 1
E-payments file type	Comma separated file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank SEPA Processing Details window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and create the file again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Banking software	BNP Paribas Bank
Required component	SEPA Credit Transfer 1
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank SEPA Processing Details window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Banking software	Bottomline Technologies limited
Required component	Bottomline Technologies limited
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bottomline Technologies Payment Processing window then click OK.

If you don't know what to enter in these boxes, please refer to your Bottomline Technologies support contact.
Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	If left blank, it uses the transaction details, for example Payment on Account. You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Choose your banking software:

Banking software

Corporate Online (CO)

Formerly known as Corporate Internet Banking (CIB) or CHOBS

Required component

Bank of Scotland CHOBS

E-payments file type

The e-payments file format depends on whether BACS or CHOBS is selected during the e-payments process.

BACS - text file (*.TXT) - Referred to as COL Bacs on the HBOS website.

CHOBS - comma separated file (*.CSV) - Referred to as COL CSV on the HBOS website.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank of Scotland Payment Processing window then click OK.

If you don't know which option to choose, please refer to your Bank of Scotland support contact. If you select CHOBS, you must enter a CHOBS Batch Name.
Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	If left blank, it uses the transaction details, for example Payment on Account. You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	HBOS Commercial Banking Online
Required component	HBOS Commercial Banking Online
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then, if required, enter your Batch name and Batch Description, for guidance contact your bank.
Click OK.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Choose your banking software:

Banking software	Clydesdale / Yorkshire Bank - Business Online
Required component	Clydesdale / Yorkshire BACS Cr
E-payments file type	Comma separated file (*.CSV)

Telebank is no longer supported by Clydesdale or Yorkshire bank.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Clydesdale / Yorkshire Bank - Faster Payment - EFT Service
Required component	Clydesdale / Yorkshire EFT
E-payments file type	Comma separated file (*.CSV)

View example file

Telebank is no longer supported by Clydesdale or Yorkshire bank.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.

Banking software	Financial Director
Required component	Cooperative Bank Financial Director
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Coutts Online
Required component	Coutts Online
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments as normal.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Coutts Online Payment Processing window as follows:

Standard Domestic/IATs - You should select this option if there's no template or bulk list created in Coutts Online.
Use a Template for Domestic/IAT - If there's a template in Coutts Online, you should select this option then enter the template reference in the Online Payment/Bulk List Template box.
Bulk List Payments - If a bulk list exists within Coutts Online, select this option, enter the bulk list reference in the Online Payment/Bulk List Template box then enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Coutts Online must have the same bulk list reference, beneficiary account details and references.

If you choose the Bulk List Payments option, the relevant supplier's record must contain a beneficiary id in the BACS Ref box in the Bank tab.

If the payment file includes inter account transfers (IATs), select the Do you wish to define Payments as being 'Inter Account Transfers' (IATs)? check box then select the transactions that are IATs and click Set.
Ad Hoc Bulk Payments - If a bulk list exists within Coutts Online, select this option to make Ad-Hoc bulk list payments, enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Coutts Online must have the same beneficiary account details and references.

If you don't know which option to choose or what details to enter, please refer to your Coutts support contact.

Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.

Potential issue with the bulk list payment files including the letter C

When you generate the payments file and select the Bulk List Payments option, the output file includes a letter C in the header row.

View screenshot

The file is correct to include the C, for the following reasons:

This is the specification that was provided to us originally by the bank.
The C indicates that a remittance will be printed from Bankline.
For any newly created bulk list payment in Bankline, this is the default setting and can't be switched off.

For older bulk lists, this wasn't the case and it was possible to create a bulk list where a remittance wouldn't be printed and this is where a problem arises.

If you generate a payment file from Sage Accounts and combine this with an old bulk list that doesn't require a remittance, the payment file is rejected. In this case, you must remove the letter C from the payment file then try importing the payment file again.

Banking software	Danske Bank
Required component	Danske Bank SEPA
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Danske Bank SEPA Processing Details window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Banking software	Deutsche Bank SEPA
Required component	SEPA Credit Transfer 1
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank SEPA Processing Details window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Banking software	iBusiness banking (iBB)
Required component	Allied Irish iBB
E-payments file type	Text file (*.TXT)

When you import the file into iBB, you must choose APACS from the File Format drop-down list and not Sage.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Allied Irish iBB Payment Processing window then click OK.

If you don't know what to enter in these boxes, please refer to your First Trust support contact.
Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be eight digits.
Bank	Bank Details	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	If left blank, it uses the transaction details, for example Payment on Account. You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	J P Morgan Access
Required component	J P Morgan Access
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage JPMorganAccess Payment Processing window as required then click OK.

If you use a serial number in the Enter a Serial Number for this Batch box which has been used previously on the same processing day, even if it's in a different company, a Duplicate Batch error is reported. To avoid the Duplicate Batch error, ensure that an alternative serial number is used. The serial number is also known as the VOL number.
If multiple companies are used, as a workaround, use a different starting number for each company. For example, Company 1: 000001, Company 2: 100001. This way 100000 files may be used before duplication occurs. If you've already exported the payment file, you can change the serial number in the text file before you import it into the bank. You must change the first number next to VOL and the last number.
Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Choose your banking software:

Banking software	HSBCNet
Required component	HSBC Net
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage HSBCNet Payment Processing window as required then click OK.

If you use a serial number in the Enter a Serial Number for this Batch box which has been used previously on the same processing day, even if it's in a different company, a Duplicate Batch error is reported. To avoid the Duplicate Batch error, ensure that an alternative serial number is used. The serial number is also known as the VOL number. The serial number normally defaults to the next consecutive number, however if you use a different computer this may not happen.
If multiple companies are used, as a workaround, use a different starting number for each company. For example, Company 1: 000001, Company 2: 100001. This way 100000 files may be used before duplication occurs. If you've already exported the payment file, you can change the serial number in the text file before you import it into the bank. You must change the first number next to VOL and the last number.
Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	wiz_HSBC SEPA
Required component	SEPA Credit Transfer 1
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank SEPA Processing Details window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Choose your banking software:

Lloyds are migrating to a new platform which means the file formats from this component no longer work. However, Lloyds are issuing an import map for customers to manipulate the files into a format compatible with their system.

Banking software	LloydsLink
Required component	LloydsLink
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Lloyds are migrating to a new platform which means the file formats from this component no longer work. However, Lloyds are issuing an import map for customers to manipulate the files into a format compatible with their system.

Banking software	Lloyds Bank Commercial Banking Online
Required component	Lloyds Bank Commercial Banking Online
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click Click OK then if required, enter your Batch name and Batch Description, for guidance contact your bank.
Click OK.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be eight digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

If the customer experiences problems with the file format, as a workaround, the LloydsLink file format has been found to resolve the issue.

Banking software	Business EBanking
Required component	National Irish Bank
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then complete the Sage National Irish Payment Processing window as required.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be six digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Name	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters. This is only included in the Payment 1 To 1 format.
Bank	Bank Details	Sort Code	No	This must be six digits. This is only included in the Payment 1 To 1 format. You may enter dashes but they aren't included in the payment file.
Bank	Bank Details	Account Number	No	This must be eights digits. This is only included in the Payment 1 To 1 format.

Choose your banking software:

Banking software	RBS / NatWest Internet Bankline
Required component	RBS / NatWest Internet Bankline
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments as normal.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage RBS/NatWest Internet Bankline Payment Processing window as follows:

Standard Domestic/IATs - You should select this option if there's no template or bulk list created in Bankline.
Use a Template for Domestic/IAT - If there's a template in Bankline, you should select this option then enter the template reference in the Bankline Payment/Bulk List Template box.
Bulk List Payments - If a bulk list exists within Bankline, select this option, enter the bulk list reference in the Bankline Payment/Bulk List Template box then enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same bulk list reference, beneficiary account details and references.

If you choose the Bulk List Payments option, the relevant supplier's record must contain a beneficiary id in the BACS Ref box in the Bank tab.

If the payment file includes inter account transfers (IATs), select the Do you wish to define Payments as being 'Inter Account Transfers' (IATs)? check box then select the transactions that are IATs and click Set.
Ad Hoc Bulk Payments - If a bulk list exists within Bankline, select this option to make Ad-Hoc bulk list payments, enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same beneficiary account details and references.

If you don't know which option to choose or what details to enter, please refer to your NatWest Bankline support contact.

Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.

Potential issue with the bulk list payment files including the letter C

When you generate the payments file and select the Bulk List Payments option, the output file includes a letter C in the header row.

View screenshots

The file is correct to include the C, for the following reasons:

This is the specification that was provided to us originally by the bank.
The C indicates that a remittance will be printed from Bankline.
For any newly created bulk list payment in Bankline, this is the default setting and can't be switched off.

For older bulk lists, this wasn't the case and it was possible to create a bulk list where a remittance wouldn't be printed and this is where a problem arises.

If you generate a payment file from Sage Accounts and combine this with an old bulk list that doesn't require a remittance, the payment file is rejected. In this case, you must remove the letter C from the payment file then try importing the payment file again. Alternatively, in the bank software you can select the option to form a remittance advice however we strongly advise that you contact your bank to ensure this doesn't have any other implications before doing so.

Banking software	Autopay Online Plus
Required component	NatWest Autopay Online Plus
E-payments file type	Comma separated file (*.CSV)

View example file

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK
To save the file, Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Supplier	Bank	Account Name	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	Business EBanking
Required component	Northern Bank
E-payments file type	Comma separated file (.CSV) or text file (.TXT)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then complete the Sage Northern Bank Payment Processing window as required then click OK.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Name	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters. This is only included in the Payment 1 To 1 format.
Bank	Bank Details	Sort Code	No	This must be 6 digits. This is only included in the Payment 1 To 1 format. You may enter dashes but they aren't included in the payment file.
Bank	Bank Details	Account Number	No	This must be eights digits. This is only included in the Payment 1 To 1 format.

Banking software	Permanent TSB Bank
Required component	SEPA Credit Transfer 1
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Bank SEPA Processing Details window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Choose your banking software:

Banking software	RBS / NatWest Internet Bankline
Required component	RBS / NatWest Internet Bankline
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments as normal.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage RBS/NatWest Internet Bankline Payment Processing window as follows:
- Next Available BACS Crediting Date - This automatically shows the next available date you can make a BACS payment and takes into account weekends and bank holidays. You can change this date if required.
- Standard Domestic/IATs - You should select this option if there's no template or bulk list created in Bankline.
- Use a Template for Domestic/IAT - If there's a template in Bankline, you should select this option then enter the template reference in the Bankline Payment/Bulk List Template box.
- Bulk List Payments - If a bulk list exists within Bankline, select this option, enter the bulk list reference in the Bankline Payment/Bulk List Template box then enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same bulk list reference, beneficiary account details and references.
  
  If you choose the Bulk List Payments option, the relevant supplier's record must contain a beneficiary id in the BACS Ref box in the Bank tab.
  
  If the payment file includes inter account transfers (IATs), select the Do you wish to define Payments as being 'Inter Account Transfers' (IATs)? check box then select the transactions that are IATs and click Set.
- Ad Hoc Bulk Payments - If a bulk list exists within Bankline, select this option to make Ad-Hoc bulk list payments, enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same beneficiary account details and references.
  
  If you don't know which option to choose or what details to enter, please refer to your Royal Bank of Scotland support contact.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.

Potential issue with the bulk list payment files including the letter C

When you generate the payments file and select the Bulk List Payments option, the output file includes a letter C in the header row.

View screenshot

The file is correct to include the C, for the following reasons:

This is the specification that was provided to us originally by the bank.
The C indicates that a remittance will be printed from Bankline.
For any newly created bulk list payment in Bankline, this is the default setting and can't be switched off.

For older bulk lists, this wasn't the case and it was possible to create a bulk list where a remittance wouldn't be printed and this is where a problem arises.

If you generate a payment file from Sage Accounts and combine this with an old bulk list that doesn't require a remittance, the payment file is rejected. In this case, you must remove the letter C from the payment file then try importing the payment file again.

Banking software	Santander Connect
Required component	Santander
E-payments file type	Text file (*.TXT)

View example file

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Santander Payment Processing window as required then click OK.
Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Number	No	This must be 8 digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Banking software	O4B
Required component	Lloyds/TSB O4B
E-payments file type	N/A

You can't process e-payments with Lloyds O4B.

Choose your banking software:

Banking software	Ulster Bankline Money Transfer
Required component	Ulster Bank Anytime
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Ulster Bank Anytime Payment Processing window as required then click OK.
To save the file, Click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be eight digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters. This is only included in the Bulk Domestic format.

Banking software	Bankline
Required component	Ulster Bank Bankline
E-payments file type	Text file (*.TXT)

To create the payment file

Post the supplier payments as normal.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Ulster Bank Bankline Payment Processing window as follows:
- Standard Domestic/IATs - You should select this option if there's no template or bulk list created in Bankline.
- Use a Template for Domestic/IAT - If there's a template in Bankline, you should select this option then enter the template reference in the Bankline Payment/Bulk List Template box.
- Bulk List Payments - If a bulk list exists within Bankline, select this option, enter the bulk list reference in the Bankline Payment/Bulk List Template box then enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same bulk list reference, beneficiary account details and references.
  
  If you choose the Bulk List Payments option, the relevant supplier's record must contain a beneficiary id in the BACS Ref box in the Bank tab.
  
  If the payment file includes inter account transfers (IATs), select the Do you wish to define Payments as being 'Inter Account Transfers' (IATs)? check box then select the transactions that are IATs and click Set.
- Ad Hoc Bulk Payments - If a bulk list exists within Bankline, select this option to make Ad-Hoc bulk list payments, enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same beneficiary account details and references.
  
  If you don't know which option to choose or what details to enter, please refer to your Ulster Bank support contact.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Box	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.

Potential issue with the bulk list payment files including the letter C

When you generate the payments file and select the Bulk List Payments option, the output file includes a letter C in the header row.

The file is correct to include the C, for the following reasons:

This is the specification that was provided to us originally by the bank.
The C indicates that a remittance will be printed from Bankline.
For any newly created bulk list payment in Bankline, this is the default setting and can't be switched off.

For older bulk lists, this wasn't the case and it was possible to create a bulk list where a remittance wouldn't be printed and this is where a problem arises.

If you generate a payment file from Sage Accounts and combine this with an old bulk list that doesn't require a remittance, the payment file is rejected. In this case, you must remove the letter C from the payment file then try importing the payment file again.

Banking software	Bankline
Required component	Ulster Bank Bankline SEPA (XML)
E-payments file type	XML file (*.XML)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Ulster Bank SEPA Payment Processing window then click OK.
To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Banking software	Bankline
Required component	Ulster Bank Bankline SEPA (CSV)
E-payments file type	Comma separated file (*.CSV)

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK and complete the Sage Ulster Bank Bankline SEPA Payment Processing window then click OK.

Standard Domestic/IATs - You should select this option if there's no template or bulk list created in Bankline.
Use a Template for Domestic/IAT - If there's a template in Bankline, you should select this option then enter the template reference in the Bankline Payment/Bulk List Template box.
Bulk List Payments - If a bulk list exists within Bankline, select this option, enter the bulk list reference in the Bankline Payment/Bulk List Template box then enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same bulk list reference, beneficiary account details and references.

If you choose the Bulk List Payments option, the relevant supplier's record must contain a beneficiary id in the BACS Ref box in the Bank tab.

If the payment file includes inter account transfers (IATs), select the Do you wish to define Payments as being 'Inter Account Transfers' (IATs)? check box then select the transactions that are IATs and click Set.
Ad Hoc Bulk Payments - If a bulk list exists within Bankline, select this option to make Ad-Hoc bulk list payments, enter the beneficiary reference in the Beneficiary Reference box. The bulk list in Bankline must have the same beneficiary account details and references.

If you don't know which option to choose or what details to enter, please refer to your Ulster Bank support contact.

To save the file click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Account Name	No	You can enter up to 60 characters.
Bank	Bank Details	IBAN	No	For more details on IBAN, please refer to article .
Bank	Bank Details	BIC/Swift	No	For more details on BIC/Swift, please refer to article .
Supplier	Bank	Account Name	No	You can enter up to 60 characters.
Supplier	Bank	IBAN	No	For more details on IBAN, please refer to article .
Supplier	Bank	BIC/Swift	No	For more details on BIC/Swift, please refer to article .

Choose your banking software:

Banking software	Clydesdale / Yorkshire Bank - Business Online
Required component	Clydesdale / Yorkshire BACS Cr
E-payments file type	Comma separated file (*.CSV)

Telebank is no longer supported by Clydesdale or Yorkshire bank.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.
Supplier	Bank	BACS Ref	Yes	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.

Payment file format

Banking software	Clydesdale / Yorkshire Bank - Faster Payment - EFT Service
Required component	Clydesdale / Yorkshire EFT
E-payments file type	Comma separated file (*.CSV)

View example file

Telebank is no longer supported by Clydesdale or Yorkshire bank.

To create the payment file

Post the supplier payments in the usual way.

Payments posted using batch supplier payments, and payments posted via the batch invoice window, can't be sent as an e-payment.
Click Bank accounts then select the required bank account and click E-payments.

You may need to click the double chevron to access the E-payments option.
Select the required payments and click Send.

The Payment Confirmation window summarises the payments.
Click OK then click Save.

The Save As window defaults to the file name and location specified when the banking component was configured. If required, you can change the file name or location.

Payment error log

If you receive an error when you create the payments file, click Yes to view the payment error log. This provides more information to determine what's wrong with the file.

This file is added to each time you receive errors, the previous errors don't clear. To make it easier to find the errors specific to the payments you're posting, delete the payment error log file and post the payments again. The error log is within the accdata folder in the data directory and the file name consists of the sort code and account number for the bank account you're sending the e-Payments from. To find your data directory click Help then click About.

An error occurs if there's incorrect information in Sage Accounts. The following information is included in the output file. You must check these details are correctly entered in Sage Accounts:

Record	Tab	Field	Can be left blank?	Validation
Bank	Bank Details	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Bank	Bank Details	Account Number	No	This must be 8 digits.
Supplier	Bank	Account Name	No	You can enter up to 60 characters in Sage Accounts but the output file only includes up to 18 characters.
Supplier	Bank	Sort Code	No	This must be 6 digits. You may enter dashes but they aren't included in the payment file.
Supplier	Bank	Account Number	No	This must be 8 digits.

Before you start

To create the payment file

Payment error log

Potential issue with the bulk list payment files including the letter C

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

Potential issue with the bulk list payment files including the letter C

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

Potential issue with the bulk list payment files including the letter C

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

Potential issue with the bulk list payment files including the letter C

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log

Potential issue with the bulk list payment files including the letter C

To create the payment file

Payment error log

To create the payment file

Payment error log

To create the payment file

Payment error log