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
<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>
Host ID
MULTIVIA
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.13 s
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 they are 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 and pain.002, in one format |
| Not supported | Direct debits |
BankConnector
Questions
- What is Berliner Volksbank's EBICS Host ID and URL?
- Host ID MULTIVIA, address https://ebics.multivia-suite.de/ebicsweb/ebicsweb. The Host ID is case-sensitive and must be upper case: sending it in lower case returns HTTP 404. MULTIVIA is a shared gateway operated by Atruvia for the cooperative sector, so it names the platform, not the bank. What identifies you is your Kunden-ID and Teilnehmer-ID, which the bank issues.
- Which message versions does Berliner Volksbank require?
- From 14 November 2026, pain.001.001.09 for SEPA credit transfers, same-day urgent transfers and instant transfers; pain.008.001.08 for direct debits; and pain.002.001.10 for status reports, delivered by the HAC order type. The bank states all four. BankConnector already produces pain.001.001.09 for this bank.
- Does Berliner Volksbank still support MT940?
- Broadly no. The bank completed the move from MT formats to camt.052, camt.053 and camt.054 for all corporate customers in November 2025. One narrow exception remains: MT940 in the SWIFT standard, rather than the German DK standard, runs to November 2028.
- Does Berliner Volksbank support Verification of Payee?
- Yes, since 9 October 2025, on standard and instant euro transfers within the EEA, checked before authorisation. New EBICS order types and business transaction format parameters were made available on 5 October 2025, and a corporate can choose per submission whether to opt in or opt out for bulk credit transfers. The bank does not reject a payment on the check result: the payer decides.
- What does EBICS cost at Berliner Volksbank?
- The bank publishes a one-off 50 euro setup charge and 9.90 euro per month per EBICS access, outside its cash package, billed together and subject to VAT.
- Can I connect my ERP to Berliner Volksbank?
- Yes. You send canonical JSON and BankConnector produces the pain.001.001.09 credit transfer file the bank requires, then reads camt.053, camt.052, camt.054 and pain.002 back into one normalised format. SEPA credit transfers, SEPA instant, same-day urgent and international payments are supported. Direct debits are not.
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
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.
If all of this looks like a lot, it does not have to be
Five steps to a live Berliner Volksbank connection.
You do not need to know what any of the codes above mean. Our setup guide walks you through it one screen at a time.
- 1
Request the agreement from Berliner Volksbank
EBICS starts with paperwork. We draft the email, you send it, and you tell us when it has gone. There is nothing to configure until the bank replies.
- 2
Set up and send your keys
Enter the values from the agreement Berliner Volksbank returns. We already hold the ones that are public, so most of the form is filled in. Then one press generates your three key pairs and sends the public halves.
- 3
Prove your identity on paper
EBICS confirms the key exchange on paper, by design. We print the initialisation letter carrying the fingerprints Berliner Volksbank will check. You sign it by hand and simply email the bank a scan; the original goes by post only if the bank asks for it.
- 4
Verify Berliner Volksbank and go live
While you wait, we fetch the bank's public keys and check them against the fingerprints it gives you over a separate channel. When that lands, you choose which approval policy governs payments here, and the connection switches on.
- 5
Go live with one small payment
Start with one small payment and follow it all the way to your statement. Then you are in production with Berliner Volksbank: payments go out as pain.001, statements come back as camt, and the connection runs unattended from here.
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. BankConnector is not affiliated with Berliner Volksbank eG.
How BankConnector handles the November 2026 pain.001.001.09 migration for Berliner Volksbank →