← All supported banks

Germany  ·  Landesbank Saar  ·  EBICS

Connect SaarLB without learning EBICS.

EBICS 2.5 and 3.0 on Host ID I82-ELKO, a 16:00 cut-off, and DTAZV ending at the end of October 2026. We handle the payments, the statements and every protocol step underneath.

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
I82-ELKO
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.14 s

Published by the bank

The bank's imprint, articles of incorporation and profile.

Bank details

BICSALADE55
Bank code590 500 00
Legal nameLandesbank Saar, Anstalt des öffentlichen Rechts
Also trading asSaarLB · SaarLB-La Banque Franco-Allemande
Registered officeUrsulinenstraße 2, 66111 Saarbrücken
RegisterHRA 8589, Saarbrücken
LEI52990050SU0S4QQ4Z793
VAT IDDE 138 11 69 52
OwnersSaarland · Sparkassenverband Saar
OfficesSaarbrücken · Mannheim · Paris · Lyon · Strasbourg
SupervisorsEuropean Central Bank · BaFin · Ministerium für Wirtschaft, Arbeit, Energie und Verkehr des Saarlandes

Checked live

Address and versions from the live host; the rest from the bank's conditions for remote data transmission.

Access data

EBICS addresshttps://li2ebics.sparkasse-banking.de/ebicsweb/ebicsweb
Host IDI82-ELKO
Protocol versionsH004 (02.50) and H005 (03.00)
Your IDsKunden-ID and Teilnehmer-ID
Bank key hashesNot published — provided over a second, separately agreed channel
Signature classesE single · A first · B second · T transport
Distributed signatureVEU — HVD, HVE, HVS, HVT, HVU, HVZ
Self-blockingSPR blocks the User ID it is sent under
Record keepingSubmitted files kept for 30 calendar days from execution date
French banking softwareSAREA, over EBICS-TS
Technical specificationPublished at www.ebics.de

Published by the bank

The bank's EBICS order-type schedule, valid from 5 October 2025, and its payee-verification notes.

Order types published by SaarLB

2.5What it does3.0 BTFDirection
CCTSEPA credit transfer, payee check opt-outSCT / — / VOO / pain.001Send
CTVSEPA credit transfer, payee check opt-inSCT / — / VOI / pain.001Send
CCCSEPA credit transfer, XML container, opt-outSCT / DE / VOO / pain.001Send
XCTSEPA credit transfer, wages and salary — on requestSCT / BIL / — / pain.001Send
CIPInstant credit transfer, payee check opt-outSCI / — / VOO / pain.001Send
CIVInstant credit transfer, payee check opt-inSCI / — / VOI / pain.001Send
CCUEuro urgent transferXCT / DE / URG / pain.001Send
AXZForeign credit transfer, ISO 20022XCT / DE / — / pain.001Send
AZVForeign credit transfer, DTAZVXCT / DE / — / dtazvSend
CCXService data centre release, credit transfer, opt-outSCT / DE / 0CCX / pain.001
VCXService data centre release, credit transfer, opt-inSCT / DE / 0VCX / pain.001
VPZPayee verification status report, ZIPREP / DE / VOP / pain.002Download
CRZPayment status report, SEPA credit transfers, ZIPREP / DE / SCT / pain.002Download
CIZPayment status report, instant transfers, ZIPREP / DE / SCI / pain.002Download
C53End-of-day statement, ZIPEOP / DE / — / camt.053Download
STAEnd-of-day statement, MT940EOP / DE / — / mt940Download
C52Intraday items, ZIP — on requestSTM / DE / — / camt.052Download
VMKIntraday items, MT942 — on requestSTM / DE / — / mt942Download
C54Debit and credit notification, ZIP — on requestSTM / DE / — / camt.054Download
BKAEnd-of-day statement as signed PDF, ZIPEOP / DE / — / pdfDownload

Payee verification applies from 5 October 2025 to SEPA credit transfers and SEPA instant. Euro urgent transfers and foreign payments sit outside it. A single instant transfer sent under CIP is rejected. Batch transfers holding one transaction may still go under CCT until further notice, under a BaFin publication.

An opt-in file reaches the distributed signature only once its VPZ report is final, and is then authorised or cancelled as a whole. Partial authorisation inside a collective order is not possible.

Direct debits, each requiring a collection agreement.

CDDCDCCDBC2CCDXC2XCDZ

Key management and protocol housekeeping. We run these during setup and afterwards.

INIHIAHPBHCAHCSPUBSPRHAAHPDHTDHKDHEVHACPTKHVDHVEHVSHVTHVUHVZ

Published by the bank

The bank's price and services list, valid from February 2026.

Cut-off times and execution

SEPA credit transfer by EBICS16:00
SEPA credit transfer via service data centre16:00
Euro urgent transfer, order type CCU16:00
Foreign urgent transfer, euro within SEPA, by EBICS16:00
Foreign transfer by EBICS11:30
Foreign urgent transfer, other currency or outside SEPA11:30
Instant credit transferNo cut-off — every calendar day, around the clock
Instant executionMax. 10 seconds
Instant amount ceilingNone from the bank — agreed EBICS limits remain
Paperless euro transferCredited to the payee's bank within max. 1 business day
Non-business daysSaturdays · 24 and 31 December · Corpus Christi · 15 August · 1 November
Maintenance windowsNo processing; announced over the agreed channel

Published by the bank

The bank's price and services list, valid from February 2026.

What the bank charges for EBICS

Set up a Kunden-IDNo charge
Set up an additional Kunden-ID50,00 EUR per EBICS ID
Set up Teilnehmer-IDs and accountsNo charge
Additional participants and accounts15,00 EUR
Unblock a participant or account15,00 EUR each
File sent without electronic signature10,00 EUR per file
SEPA or instant credit transfer, per item0,20 / 0,12 / 0,05 EUR by price model
Euro urgent transfer5,00 EUR
Statements, MT940 or camt.053Included
Intraday advice, MT942 or camt.052Included
Collective booking detail, camt.05425,00 EUR per account or per file

Published by the bank

The bank's SEPA message-version sheet of January 2026 and its format notices.

Formats

pain.001.001.03 · pain.008.001.02DK specification 3.0 to 3.6 — withdrawn November 2026
pain.001.001.09 · pain.008.001.08DK specification 3.7 to 3.9 — no end date
DTAZVDiscontinued end of October 2026, replaced by pain.001.001.09
AXZGiven automatically to every participant holding AZV
Unstructured addresses, ISO 2009Allowed until November 2025
camt.052 · camt.053 · camt.054Version .001.08 — no end date
camt version 02Supported until end of October 2025
MT940 · MT942Supported until end of October 2025, replaced by camt V08
STA · VMKHolders given C53 and C52 automatically

BankConnector

What is built and shipped for this bank today.

What our engine produces

Payment formatpain.001.001.03
Also producedpain.001.001.09 — live for other banks today
RulebookGerman DK Anlage 3 v3.9 / 2025-03
Charge bearerSLEV
Batch bookingFalse
Remittance limit140 characters
Name limit70 characters
Character setLatin — transliterated before the bank sees it
Payment types builtSEPA credit transfer · SEPA instant · domestic account transfer · international
Read backcamt, pain.002 — one normalised format
Not supportedDirect debits

Published by the bank

Dates the bank has announced. What we do about each one is ours.

Upcoming events in our register

  1. DTAZV is discontinued at the end of the month. Foreign payments move from AZV to pain.001.001.09 under AXZ. We have never produced DTAZV.

  2. pain.001.001.03 and pain.008.001.02, DK specification 3.0 to 3.6, are withdrawn. Our engine emits pain.001.001.09 today for other banks.

If all of this looks like a lot  ·  it does not have to be

Five steps to a live SaarLB 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. 1

    Request the agreement from SaarLB

    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. 2

    Set up and send your keys

    Enter the values from the agreement SaarLB 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. 3

    Prove your identity on paper

    EBICS confirms the key exchange on paper, by design. We print the initialisation letter carrying the fingerprints SaarLB will check. You sign it by hand and send it.

  4. 4

    Verify SaarLB 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. 5

    You are now in production with SaarLB

    Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.

Sources — SaarLB’s EBICS page, its EBICS order-type schedule valid from 5 October 2025, its SEPA message-version sheet of January 2026, its notices on message formats for payments and on account information formats, its real-time transfer and payee-verification page, its SAREA page, its conditions for remote data transmission, its price and services list valid from February 2026, its articles of incorporation, its imprint, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Landesbank Saar.

How BankConnector handles the pain.001.001.09 migration, bank by bank →

← Back to all supported banks