Javascript is required Bulk Channels - ABN AMRO

Bulk channels

The solution for bulk payment transactions

  • Your transactions processed immediately
  • Reduce your operational costs
  • Simplify your reconciliation process

Connect your system through our bulk channels for a secure and direct link to ABN AMRO. File uploads and transaction processing are handled automatically.

Four solutions for you

Access Direct OpenLink

Connect your system to one or more banks with Access Direct OpenLink. You'll gain access to ABN AMRO's network and payment solutions. Also you can manage other banks through this system.

  • For large-scale payment transactions and reporting
  • Optimising investments, such as in ERP systems

SWIFT FIN

FIN is used to send individual structured messages. It is particularly suitable for individual transactions.

  • Monitoring, prioritization, and storage of your messages
  • Structured messages ensure fast and secure processing

SWIFT FileAct

FileAct sends various types of files containing all kinds of data, such as financial reports or images.

  • Processes bulk data, ideal for large files containing multiple transactions

EBICS

The Electronic Banking Internet Communication Standard (EBICS) is a transmission protocol for Electronic Banking communication. In Germany, EBICS has become the market standard for such communications.

  • Our EBICS offering is suitable only for German and Dutch clients

Which solution do you choose?

In this table, you can see the differences between the various solutions.

ProductAccess Direct OpenLinkSWIFT FINSWIFT FileActEBICS
Suitable forLarge or international companies regularly sending large files or receiving extensive end-of-day reports.Large or international companies submitting high-value transactions using MT101.Large or international companies regularly sending large files or receiving extensive end-of-day reports.Large or international companies with an existing EBICS setup through another bank, requiring a direct German relationship.
File formatsSEPA CT, Non-SEPA CT, SEPA DDMT101 (until November 2026)SEPA CT, Non-SEPA CT, SEPA DDSEPA CT, Non-SEPA CT, SEPA DD, DTAZV
ReportingMT940, SAP MT940, MT940 (structured) / MT942, CAMT052 / CAMT053MT940, MT942MT940 / MT942, CAMT052 / CAMT053MT940 (structured) / MT942 (structured), CAMT052 / CAMT053
ProtocolsSFTP, FTPSSWIFT networkSWIFT networkEBICS
AuthorisationTwo methods:
  • Automatic signing via XML signature (in your own environment/software)
  • Manual signing via online signing.
No ABN AMRO software installation required. Business clients use the SWIFT application (SWIFT Alliance Lite).No ABN AMRO software installation required. Business clients use the SWIFT application (SWIFT Alliance Lite).No ABN AMRO software installation required. Clients can use standard or custom third-party software for communication and security.
SecuritySecure connection via FTPS or SFTP. Security is optimised during implementation to ensure integrity and authentication.Utilises SWIFT infrastructure ensuring payment integrity, authentication, and origin non-repudiation. Double file/payment checks and internal checks on sending SWIFT address and client settings.Utilises SWIFT infrastructure ensuring payment integrity, authentication, and origin non-repudiation. Double file/payment checks and internal checks on sending SWIFT address and client settings.EBICS requires multiple signature levels. Authentication signatures ensure package integrity, while electronic signatures authenticate payments.

Please note! Coming soon: instant processing of SEPA credit transfer batches

What does this mean for you?

We will then automatically check whether we can process the individual credit transfers in the batch as an instant payment. If possible, the money will reach the recipient's account within a few seconds. Otherwise, this usually happens within a few hours, but no later than within 1 working day.

How it works

  • You submit your SEPA credit transfer batch via FileAct or Access Direct. Your account will be debited once for the total amount of the batch. The batch is unpacked into individual transactions.
  • Each individual transaction in the batch is processed within 5 to 10 seconds if instant processing is possible. Sometimes this is not possible, for example because the recipient’s bank cannot process instant payments. In that case, the money will be credited to the recipient's account within 1 working day at the latest. The total processing of the entire batch may take longer.
  • SEPA credit transfer batches can be submitted every day, 24 hours a day. You do not need to take delivery times into account.
  • Would you like the credit transfer batch to be processed on a specific day? Then enter your desired execution date. This can be up to 364 days in the future.

Validation of SEPA and non-SEPA files

If you submit the files to us, we will automatically check whether they are technically correct and whether we can process them.

From 1 September 2026, the automatic check of SEPA files will be more in line with the SEPA rules. For non-SEPA files, we follow the CGI-MP standard. You can easily check your files yourself by testing them through Swift MyStandards.

Status messages

From 1 September 2026, we will stop with the Human Readable status messages. We therefore advise you to switch to our ISO XML pain.002 status messages as soon as possible.

If you already receive ISO XML pain.002 status messages, you will see a few new status codes.

We are also starting a new type of pain.002 status message for SEPA credit transfer batches. This message summarizes the processing of the individual transactions in the batch. Including the time when the funds from the last instant payment in the batch reached the recipient.

Please note

  1. Only if there are a maximum of 10,000 transactions in the SEPA credit transfer batch, the individual credit transfers can be processed as an instant payment. 
  2. Individual credit transfers of more than €5 million will be processed as a regular SEPA credit transfer.
  3. SEPA credit transfer batches with only one transaction are not processed as a batch but as individual transactions.
  4. When you approve the batches and/or individual credit transfers in Access Online, you will do so in Access Online Renewed from 1 September 2026.

What does this mean for you?

We will then automatically check whether we can process the individual credit transfers in the batch as an instant payment. If possible, the money will reach the recipient's account within a few seconds. Otherwise, this usually happens within a few hours, but no later than within 1 working day.

How it works

  • You submit your SEPA credit transfer batch via FileAct or Access Direct. Your account will be debited once for the total amount of the batch. The batch is unpacked into individual transactions.
  • Each individual transaction in the batch is processed within 5 to 10 seconds if instant processing is possible. Sometimes this is not possible, for example because the recipient’s bank cannot process instant payments. In that case, the money will be credited to the recipient's account within 1 working day at the latest. The total processing of the entire batch may take longer.
  • SEPA credit transfer batches can be submitted every day, 24 hours a day. You do not need to take delivery times into account.
  • Would you like the credit transfer batch to be processed on a specific day? Then enter your desired execution date. This can be up to 364 days in the future.

Validation of SEPA and non-SEPA files

If you submit the files to us, we will automatically check whether they are technically correct and whether we can process them.

From 1 September 2026, the automatic check of SEPA files will be more in line with the SEPA rules. For non-SEPA files, we follow the CGI-MP standard. You can easily check your files yourself by testing them through Swift MyStandards.

Status messages

From 1 September 2026, we will stop with the Human Readable status messages. We therefore advise you to switch to our ISO XML pain.002 status messages as soon as possible.

If you already receive ISO XML pain.002 status messages, you will see a few new status codes.

We are also starting a new type of pain.002 status message for SEPA credit transfer batches. This message summarizes the processing of the individual transactions in the batch. Including the time when the funds from the last instant payment in the batch reached the recipient.

Please note

  1. Only if there are a maximum of 10,000 transactions in the SEPA credit transfer batch, the individual credit transfers can be processed as an instant payment. 
  2. Individual credit transfers of more than €5 million will be processed as a regular SEPA credit transfer.
  3. SEPA credit transfer batches with only one transaction are not processed as a batch but as individual transactions.
  4. When you approve the batches and/or individual credit transfers in Access Online, you will do so in Access Online Renewed from 1 September 2026.
Cup

Implementation and support

Expert implementation is crucial for our cash management solutions. We collaborate closely with your finance and IT departments to ensure maximum efficiency.
 
Prepare thoroughly for the implementation. Quickly and easily test your SEPA and non-SEPA files using Swift MyStandards. Ensure the files are technically correct so we can process them.
Swift MyStandards

SEPA Transfers and Direct Debits

You can find all the information about SEPA file formats, the ABN AMRO Addenda, and more on the SEPA download page.

Scheduled maintenance

2026 ReleasesGo-live Dates
January Release R260110th Jan 2026
February Release R26027th Feb 2026
March Release R26037th March 2026
April Release R26044th April 2026
May Release R26059th May 2026
June Release R260613th June 2026
July Release R26074th July 2026
August Release R26088th Aug 2026
September Release R260912th Sep 2026
October Release R26103rd Oct 2026
November Release R26117th Nov 2026
December Release R261212th Dec 2026

Do you have any questions? Please contact us