How does BVG Exchange Transfer work?

A centralised exchange platform requires a standardised exchange format: BVG Exchange Transfer uses XML Schema Definition (XSD). A generic, robust data format that supports numerous data types can be expanded as required, and is therefore versionable. 

The exchange format is designed in such a way that even lower-quality data can still be processed. This means that affiliated institutions can send and/or receive departure data to all other institutions via BVG Exchange. 

As a result of the shared use of the platform, each affiliated occupational benefits institution will only need one technical connection instead of several. 

Since the launch of BVG Exchange, the XML Schema has been adapted with every change in the legal requirements.

Web service and sequence diagram
The exchange takes place via a web service that receives data and can be used to retrieve data. Every step is transactionally secured, transparent and verifiable . The process is shown in the sequence diagram (figure).

All actions of the sequence diagram are logged. All log entries pertaining to an institution can either be obtained from the institution via the web service or viewed on BVG Exchange. This means that every action can be traced at any time.

Sequence diagram

The web service user 

• Authenticates themself with a user name and password for each method call. 
• May have the following authorisations: delivery of datasets (SUBMIT), receipt of datasets (RECEIVE; evaluated as a binding delivery), reading datasets (GET; reading does not correspond to receipt).
• May be enabled for a number of institutions. The permissions relate to one or more institutions on whose behalf the web service user(s) may act. 

Institutions can define whether and in which XML Schema version they want to receive documents. If two institutions do not use the same schema version, there is an automatic migration for an exchange of data.

Command Line Client (CLI Client)
There is also a CLI client in the distribution. This is a reference implementation. This allows XML data to be sent to BVG Exchange and received by the platform. The CLI client includes a demo mode with which the complete process can be tested.

The use of the client requires basic knowledge of the operating system used and is primarily intended for a low-threshold connection with simple process sequences. 

The source code for the application is also supplied and can be used freely as a basis for institutions’ own implementation.

Links and downloads

For general information, see BVG Exchange Transfer; for further details, see Technical questions about BVG Exchange Transfer.

For legal issues, see Legal questions and the general Terms and Conditions of Use of BVG Exchange.

How does BVG Exchange Match work?

The service uses REST architecture, which is widely used on the Internet. REST is based on the HTTP protocol or the basic principles of the Internet, which means that the necessary infrastructure is already in place. This makes it very easy to connect a web service which communicates via REST.

JSON was selected as the data exchange format for BVG Exchange Match. JSON is a compact file format that can be read even without technical knowledge. Many common programming languages are able to read and write data in JSON format automatically.

Web service and sequence diagram
The web service is structured in such a way that any occupational benefits institution affiliated with BVG Exchange Transfer can also enter data in BVG Exchange Match. The same login credentials are used for this purpose. Afterwards, departures and admissions can be reported and deleted via various REST endpoints. The data is transferred as a DTO (data transfer object) in JSON format and saved by the web service. Matches are generated and saved from this stored data by the web service, which in turn can be retrieved via the REST endpoints. 

BVG Exchange Match does not check whether the transmitted data is meaningful. Each occupational benefits institution which sends data is itself responsible for ensuring that its data is up to date. BVG Exchange Match only deletes the associated match when departures and admissions are deleted, as such a match is no longer valid without a valid departure and admission.

Sequence diagram

Link

For general information, see BVG Exchange Match; for further details, see Technical questions about BVG Exchange Transfer.

For legal issues, see Legal questions and the general Terms and Conditions of Use of BVG Exchange.

How does BVG Exchange Payment Validation work?

The service uses REST architecture, which is widely used on the Internet. REST is based on the HTTP protocol or on the foundations of the Internet. This means that the necessary infrastructure is already in place. Therefore, this makes it very easy to connect a web service which communicates via REST.

JSON was selected as the data exchange format for BVG Exchange Match. JSON is a compact file format that can be read even without technical knowledge. Many common programming languages are able to read and write data in JSON format automatically.

Web service
The web service is structured in such a way that any occupational benefits institution affiliated with BVG Exchange Transfer can also request payment details from BVG Exchange Payment Validation. The same login credentials are used for this purpose. You can then search for payment details via the REST endpoint. The data is transferred as a DTO (data transfer object) in JSON format.

Link

For general information, see BVG Exchange Payment Validation; for further details, see Technical questions about BVG Exchange Payment Validation.

For legal issues, see Legal questions and the general Terms and Conditions of Use of BVG Exchange.

We offer all pillar 2 occupational benefits institutions the opportunity to test BVG Exchange on a non-binding basis. Please contact us to request access.

Back to overview