Connect Berliner Sparkasse without learning EBICS.
The bank publishes its access data and a full order-type schedule mapped to EBICS 3.0. Statements are camt only, the cut-off is 19:30, and the bank keys rotate on a date the bank has not published. We handle all of it.
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
G83-ELKO
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.13 s
Published by the bank
The bank's imprint and the GLEIF LEI record.
Bank details
| BIC | BELADEBE |
| Bank code | 100 500 00 |
| Legal entity | BSK 1818 AG (renamed from Landesbank Berlin AG, 15 Jul 2025) |
| Berliner Sparkasse is | A branch and brand of that entity |
| Registered office | Alexanderplatz 2, 10178 Berlin |
| Register and LEI | HRB 99726 B, GTQYZJON3I7SXRNJTT73 |
Published by the bank
The bank's EBICS page and its terms, plus our own live check.
Access data
| EBICS address | https://be3ebics.sparkasse-banking.de/ebicsweb/ebicsweb |
| Host ID | G83-ELKO |
| Protocol versions | H004 (02.50) and H005 (03.00) |
| Gateway operator | Finanz Informatik, one instance per institute |
| Bank key hashes | Six, published: E001, E002, cert; X001, X002, cert |
| Distributed signature | Supported, but must be agreed separately |
| Signature classes | E single, A first, B second, T transport |
| Statement formats | camt version 08 only (MT940 off since 23 Nov 2025) |
| Same-day cut-off | 19:30 for remote data transmission |
| Instant transfers | No cut-off: every day, around the clock |
The gateway is a Sparkassen-Finanzgruppe platform, one instance per institute, so the address and Host ID name the instance rather than the bank’s own server. They are the same for every Berliner Sparkasse customer. Your Partner ID and User ID arrive on the Bankparameterblatt.
Published by the bank
The bank's own schedule, dated 27 April 2026.
Order types published by Berliner Sparkasse
Standard: available under the basic agreement
| 2.5 | What it does | Dir | Message | Service | Scope | Option | Container |
|---|---|---|---|---|---|---|---|
| CCT | SEPA credit transfer, payee check opt-out | Send | pain.001 | SCT | VOO | ||
| CTV | SEPA credit transfer, payee check opt-in | Send | pain.001 | SCT | VOI | ||
| CCC | SEPA credit transfer, XML container | Send | pain.001 | SCT | DE | XML | |
| CCU | Same-day urgent transfer in euro | Send | pain.001 | XCT | DE | URG | |
| AXZ | Foreign credit transfer, ISO 20022 | Send | pain.001 | XCT | DE | ||
| AZV | Foreign credit transfer, DTAZV (retires Nov 2026) | Send | dtazv | XCT | DE | ||
| CDD | SEPA core direct debit | Send | pain.008 | SDD | COR | ||
| CDC | SEPA core direct debit, XML container | Send | pain.008 | SDD | DE | COR | XML |
| C53 | End-of-day account statement | Download | camt.053 | EOP | DE | ZIP |
Additional: may need a separate agreement
| 2.5 | What it does | Dir | Message | Service | Scope | Option | Container |
|---|---|---|---|---|---|---|---|
| CIV | Instant credit transfer, payee check opt-in | Send | pain.001 | SCI | VOI | ||
| CIP | Instant credit transfer, payee check opt-out | Send | pain.001 | SCI | VOO | ||
| XCT | SEPA credit transfer | Send | pain.001 | SCT | BIL | ||
| CDB | SEPA B2B direct debit | Send | pain.008 | SDD | B2B | ||
| C2C | SEPA B2B direct debit, XML container | Send | pain.008 | SDD | DE | B2B | XML |
| C52 | Intraday transactions, not yet booked | Download | camt.052 | STM | DE | ZIP | |
| C54 | Debit and credit notification, batch detail | Download | camt.054 | STM | DE | ZIP | |
| CRZ | Payment status report, credit transfers | Download | pain.002 | REP | DE | SCT | ZIP |
| CIZ | Payment status report, instant transfers | Download | pain.002 | REP | DE | SCI | ZIP |
| CDZ | Payment status report, direct debits | Download | pain.002 | REP | DE | SDD | ZIP |
| BKA | Account statement as a signed PDF | Download | EOP | DE | ZIP | ||
| DKI | Foreign exchange rates in euro | Download | misc | OTH | BIL | 0DKI |
Four more cover service-centre submission, released internally through the distributed signature.
The rest are key management and protocol housekeeping. They carry no business transaction format and you never see one. We run them during setup and afterwards.
BankConnector
What is built and shipped for this bank today.
What our engine produces
| Payment format | pain.001.001.03 |
| Rulebook | German DK Anlage 3 v3.9 / 2025-03 |
| Charge bearer | SLEV |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Character set | Latin, transliterated before the bank sees it |
| Read back | camt.053, camt.052, camt.054 and pain.002, in one format |
| Not supported | Direct debits |
BankConnector
Questions
- What is Berliner Sparkasse's EBICS Host ID and URL?
- Host ID G83-ELKO, address https://be3ebics.sparkasse-banking.de/ebicsweb/ebicsweb. The bank publishes both. The gateway is operated by Finanz Informatik for the Sparkassen-Finanzgruppe, and the URL and Host ID together name the instance serving Berliner Sparkasse. They identify the bank, not you: your Partner ID and User ID come on the Bankparameterblatt with your EBICS agreement.
- Which EBICS version does Berliner Sparkasse use?
- Both. Its host answers on EBICS 2.5 (protocol H004, revision 02.50) and EBICS 3.0 (protocol H005, revision 03.00). BankConnector connects over EBICS 3.0 (H005).
- Does Berliner Sparkasse support MT940?
- No, not since 23 November 2025. The bank switched off MT940, MT942 and the version 02 camt formats on that date and now provides statements only as camt version 08: camt.053 as C53, camt.052 as C52 and camt.054 as C54. A system that can only read MT940 cannot be pointed at this bank.
- Does Berliner Sparkasse support Verification of Payee?
- Yes, since 5 October 2025. The check is expressed as paired order types: SEPA credit transfers use CCT to opt out and CTV to opt in, and SEPA instant uses CIP to opt out and CIV to opt in. In EBICS 3.0 the pairing is the business transaction format option, VOO against VOI.
- What is Berliner Sparkasse's EBICS cut-off time?
- 19:30 for remote data transmission, which is what EBICS is under the bank's terms. Orders arriving after that count as received on the next business day. Instant credit transfers have no cut-off at all: every day of the year is a business day, around the clock. Business days exclude Saturdays, 24 December and 31 December.
- Is Berliner Sparkasse still Landesbank Berlin AG?
- It is the same legal person under a new name. Landesbank Berlin AG was renamed BSK 1818 AG on 15 July 2025, with the LEI, commercial register entry and registered address unchanged. Berliner Sparkasse is its branch and brand. Contracts, IBANs and the BIC BELADEBE are unaffected, so a record still naming Landesbank Berlin AG points at the same bank.
- Can I connect my ERP to Berliner Sparkasse?
- Yes. You send canonical JSON and BankConnector produces the pain.001 credit transfer file the German DK Anlage 3 rulebook 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
- Not published
The bank’s own EBICS keys are replaced, and yearly from then on. Every client must fetch the new keys and confirm the new hashes by hand or communication stops. Berliner Sparkasse has not published its date; siblings on the same platform cite different days.
pain.001.001.09 replaces pain.001.001.03, pain.008.001.08 replaces pain.008.001.02. Our engine emits both.
DTAZV is withdrawn and AZV gives way to AXZ. We have never produced DTAZV, so we drive AXZ already.
Payments with unstructured addresses are rejected. Canonical input 1.1 has taken street, building number, post code, town and country as separate fields since it shipped.
If all of this looks like a lot, it does not have to be
Five steps to a live Berliner Sparkasse 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 Sparkasse
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 Sparkasse 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 Sparkasse 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 Sparkasse 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 Sparkasse: 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 order-type schedule dated 27 April 2026, its format-withdrawal notice, its price list and its terms for remote data transmission, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with BSK 1818 AG or Berliner Sparkasse.
How BankConnector handles the November 2026 pain.001.001.09 migration for Berliner Sparkasse →