This is where we report on current milestones in the development of the EBICS standard and further technical topics in the context of EBICS.

There have been changes in the EBA CLEARING's mapping for RT1 and STEP2 - a link to the updated list can be found under BTF-Mapping ...

There have been changes in the EBA CLEARING's mapping for RT1 and STEP2 - a link to the updated list can be found under BTF-Mapping ...

There have been changes in the EBA CLEARING's mapping for RT1 and STEP2 - a link to the updated list can be found under BTF-Mapping ...

This year, the EBICS migration will begin in Austria. Information of general interest can be found here ...

A new scope (for services which take CBPR+ rules into account) has been added to the external BTF code list. You can find it under EBICS specification.

EBICS version 3.0.2 has now been published. The changes compared to EBICS V 3.0 (V3.0.1) are primarily clarifications as well as minor changes. In the course of this, the Common Implementation Guide was also revised.

Change requests and previous versions of the documents can be found in the archive.

With the revision version 3.0.2 of the EBICS specification, the EBICS Implementation Guide will also be revised. Two CRs have been agreed for this. The publication of the Implementation Guide will probably take place together with EBICS V 3.0.2 at the end of June.

There have been changes in the EBA CLEARING's mapping for RTZ1 an STEP2 - a link to the updated list can be found under BTF-Mapping ...

The EBICS Board adopted further CRs for the upcoming sub-version V 3.0.2 on February 16th 2022.
Further CRs are not expected - The specification documents will be published around mid-2022. Additional information: EBA Clearing has updated its BTF mapping table. The reference for the latest document can be found in the usual place here ...

A service code ("CIM" = Customer Information Message) has been added to the BTF code list. The code is used in the case of customer information provided via EBICS.
You will find the code list as usual in the section EBICS-Specification.

A first adopted change request is now available for the next revision document EBICS V 3.0.2. It can be found under passed CRs. The CR serves to clarify that banks may act as CA for their own customers. Customers can use the keys at other banks for EBICS communication. However, they are not regarded as CA certificates there, but as bilaterally agreed keys. In particular, the INI letter procedure must be carried out as usual for initialisation.

A new service code TRA (Tracker Services) was added to the BTF code list. You can find the updated code list under Specification.

The maping table of order types used in Austria on BTF is avalable now.
more details ...

The latest EBICS version 3.0.1 is avalable now. The changes compared to EBICS V 3.0 are primarily clarifications which are helpful for the migration from V 2.x to V 3.0 as well as smaller improvements and modernisations. Details ...

In the course of this, the security concept was also slightly adjusted.

Today, the three CRs EB-20-02, -03 and -04 were published - all of them are included in the revision version 3.0.1, which is scheduled for publication in February 2021. The change requests can be found under passed CRs.
 

From now on you will find references to the national BTF mapping tables of France, Germany and Switzerland on this website.
They serve in particular for the migration from EBICS V 2.5 to V 3.0. The external links always refer to the most current available documentation.
You will find them in the section BTF-Mapping.

Today the following documents were published:
- a clarifying CR (No. EB-20-01) for EBICS V 3.0 concerning HAC under passed CRs.
- the slightly revised order type list for EBICS versions 2.x. Since the order type list only refers to EBICS V 2.x ( and not the latest version 3.0), it can be found in the archive.

Some new codes for services were defined, e.g. in anticipation of current projects a code for Request to Pay. You can find the updated code list under Specification.

Initially created as a real-time notification service for the receipt of SCT inst the new concept "Real-Time Notifications" which is based on the WebSocket protocol offers further added value for EBICS users.

The new specification is no part of the EBICS standard and EBICS does not necessarily require this function. EBICS-Client and WebSocket-Client are systemically separated from each other.
However, this the concept is an ideal supplement to the EBICS procedure. 

For detailed information please refer to the Specification Document.

EBICS has been used for many years in bank-bank communication (especially with CSMs). In order to enable the clearing of instant payments according to the SCTinst regulations of the European Payments Council EBICS a delta document was created which fulfils the necessary performance and security requirements. The delta document is applicable within the framework of EBICS V 3.0, but is only permitted for the scenario described. The delta document can be found under Specification.

During the implementation of EBICS V 3.0 an obvious mistake in the EBICS specification was noticed. Details can be found under Maintain&Advance...

An extended version of the Common Implementation Guide was published - already taking into consideration first implementation experience for EBICS V 3.0 - you can download it on Implementation Guide.

Change Requests for the next EBICS version (specification and the corresponding Implementation Guide as well) came up. The approved CRs can be found on Passed CRs. Please note that most of the CRs are clarifications and can already be considered now.

In the external BTF code list new service names and some rules for service options were added. The current version can be downloaded on EBICS specification...