Germany · Berliner Volksbank eG · EBICS
Connect Berliner Volksbank without learning EBICS.
EBICS 2.5 and 3.0 on the cooperative sector’s shared gateway, statements in camt, and every message format changing on 14 November 2026. We already produce the version that takes effect that day.
The host, checked live
10 Sep 2026<ebicsHEVResponse xmlns="http://www.ebics.org/H000"> <ReturnCode>000000</ReturnCode> <ReportText>[EBICS_OK] OK</ReportText> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.00</VersionNumber> </ebicsHEVResponse>
Published by the bank
The bank's imprint.
Bank details
| BIC | BEVODEBB |
| Bank code | 100 900 00 |
| Legal name | Berliner Volksbank eG |
| Registered office | Bundesallee 206, 10717 Berlin |
| Register | GnR 23 B, Amtsgericht Charlottenburg |
| Group | Genossenschaftliche FinanzGruppe Volksbanken Raiffeisenbanken |
Published by the bank
The bank's EBICS page and forms, plus our own live check.
Access data
| EBICS address | https://ebics.multivia-suite.de/ebicsweb/ebicsweb |
| Host ID | MULTIVIA — upper case, case-sensitive |
| Protocol versions | H004 (02.50) and H005 (03.00) |
| Gateway operator | Atruvia — shared across the cooperative sector |
| Bank key hashes | Published — and the gateway's, not this bank's alone |
| Your IDs | Kunden-ID (prefix BV30 or MV) and Teilnehmer-IDs |
| Distributed signature | Supported |
| Statement formats | camt — MT retired for corporates in Nov 2025 |
| Security medium | USB stick, or chip-card reader / Secoder |
| Cost | 50 EUR once, then 9,90 EUR per month per access |
The published key hashes belong to the gateway rather than to this bank: another cooperative bank publishes the identical pair for the same host. So verifying them proves you are talking to the right gateway. Your Kunden-ID and Teilnehmer-IDs are what identify you to Berliner Volksbank, and the bank issues those.
Published by the bank
The bank's ISO 20022 page, updated 12 August 2026.
Message formats from 14 November 2026
| SEPA credit transfer | pain.001.001.09 |
| Same-day urgent transfer | pain.001.001.09 |
| Instant credit transfer | pain.001.001.09 |
| Direct debit | pain.008.001.08 |
| Status report | pain.002.001.10 — order type HAC |
| Statements | camt.052, camt.053, camt.054 |
| Foreign payments | ISO 20022 XML — DTAZV ends 14 Nov 2026 |
| MT940, SWIFT standard | Runs to Nov 2028 — the one MT exception |
Berliner Volksbank publishes no order-type schedule. The one code it names in its own material is HAC, the status report. We are not going to reproduce another cooperative bank’s schedule and label it this one’s: your set is fixed by your EBICS agreement.
BankConnector
What is built and shipped for this bank today.
What our engine produces
| Payment format | pain.001.001.09 — already what the bank requires |
| Rulebook | German DK Anlage 3 v3.9, cooperative flavour |
| Charge bearer | SLEV |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Debtor BIC rule | Permissive — members carry their own GENODExxxx BIC |
| Read back | camt.053, camt.052, camt.054, pain.002 — one format |
| Not supported | Direct debits |
Published by the bank
Published by the bank; the response is ours.
What is still ahead
The last cut-off before the switch. Anything still in flight after it can be rejected, including scheduled payments and releases waiting on a second signature.
Hard cutover. Only pain.001.001.09, pain.008.001.08 and pain.002.001.10 are accepted, DTAZV ends, and unstructured addresses are rejected. We already produce .09 for this bank.
Verification of Payee reaches the non-euro EEA countries.
The extended deadline for MT940 in the SWIFT standard, the last MT format still running.
Five steps to a live connection.
You do not need to know what any of this means.
- 1
Send the bank the EBICS application
Berliner Volksbank publishes a named application form. It is returned through the electronic mailbox in online banking or by post, and it needs the accounts, the named users and a legally binding signature.
- 2
The bank sets up your access
The bank creates the EBICS access and issues your Kunden-ID and Teilnehmer-IDs. Users can only be released in line with the authorisations held against the account.
- 3
Send the initialisation letter
We generate your keys and print the letter. You sign it and return it. Private keys never leave the system.
- 4
Verify the bank and go live
We fetch the gateway's public keys and check them against the hashes the bank publishes. Then you choose the approval policy and the connection switches on.
- 5
In production
Payments go out as pain.001.001.09 and statements come back as camt, unattended.
Sources — the bank’s EBICS page, its ISO 20022 page, its Verification of Payee page, its EBICS application forms and the EBICS specifications published by Die Deutsche Kreditwirtschaft. Host response measured 10 September 2026. BankConnector is not affiliated with Berliner Volksbank eG.