STUZZA and Austrian banking EDI

Austria has a highly consolidated EDI banking ecosystem driven by STUZZA — the Study Society for Cooperation in Payments, an interbank consortium founded in 1992. Today, ISO 20022 dominates for orders and statements, EDIFACT FINSTA/FINPAY is still used for legacy uses and the migration to SEPA Instant is complete.

STUZZA — what is it?

Creation: 1992, at the initiative of the major Austrian banks to mutualise R&D, technical standards and payment interoperability.
Role: define national technical rules (RKSZ — Regelwerk für Kontostandsmeldungen), ensure compatibility between banks (interbank clearing), and represent Austria in European bodies (EBA, EPC).
European comparison: equivalent of the French CFONB, the Italian CBI, the Dutch Betaalvereniging Nederland.
Publications: RKSZ specifications for CAMT, PAIN ↔ EDIFACT mappings, AT IBAN implementation guides, corporate coding conventions (purpose codes).
Official site: stuzza.at — fully public, free downloads for Austrian vendors and businesses.

SEPA in Austria — specifics

Adoption: Austria in the SEPA zone since 1 January 2008. Full migration of domestic credit transfers and direct debits to SEPA format in 2014 (EU deadline).
AT IBAN: 20-character format AT + 2-digit checksum + 5-digit BLZ (Bankleitzahl) + 11-digit account. Example AT611904300234573201.
Austrian BIC: 8 or 11-character format, e.g. BKAUATWWXXX (Bank Austria), GIBAATWWXXX (Erste Bank), RZBAATWW (Raiffeisen Zentralbank).
SEPA Instant: mandatory since November 2025 for all AT BIC banks (EU Regulation 2024/886). Large corporate flows use SCT Inst for urgent payroll or supplier payments.
SDD e-Mandate: Austria uses paper or electronic mandates (Bürgerkarte qualified signature) depending on business processes.

ISO 20022 — pain.001 / camt.052 / camt.053 / camt.054

ISO 20022 message	Use	Direction
pain.001 — CustomerCreditTransferInitiation	Credit transfer initiation by the corporate client	Corporate → Bank
pain.008 — CustomerDirectDebitInitiation	SEPA SDD direct debit initiation	Corporate → Bank
pain.002 — PaymentStatusReport	Execution / rejection status of pain.001/008	Bank → Corporate
camt.052 — BankToCustomerAccountReport	Intraday account report (positions, pending)	Bank → Corporate
camt.053 — BankToCustomerStatement	End-of-day bank statement (FINSTA + CFONB 120 equivalent)	Bank → Corporate
camt.054 — BankToCustomerDebitCreditNotification	Individual credit or debit notification (ideal for INVOIC reconciliation)	Bank → Corporate

xml camt054-2026-05-19.xml

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.054.001.08">
  <BkToCstmrDbtCdtNtfctn>
    <GrpHdr>
      <MsgId>BKAU-NTF-20260519-000045</MsgId>
      <CreDtTm>2026-05-19T09:15:00Z</CreDtTm>
      <MsgRcpt>
        <Nm>Beispiel Lieferant GmbH</Nm>
        <Id><OrgId><Othr><Id>ATU12345678</Id></Othr></OrgId></Id>
      </MsgRcpt>
    </GrpHdr>
    <Ntfctn>
      <Id>NTF-2026-05-19</Id>
      <Acct>
        <Id><IBAN>AT611904300234573201</IBAN></Id>
        <Ccy>EUR</Ccy>
      </Acct>
      <Ntry>
        <Amt Ccy="EUR">2592.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts><Cd>BOOK</Cd></Sts>
        <BookgDt><Dt>2026-05-19</Dt></BookgDt>
        <ValDt><Dt>2026-05-19</Dt></ValDt>
        <NtryDtls>
          <TxDtls>
            <Refs>
              <EndToEndId>2026-AT-000412</EndToEndId>
            </Refs>
            <RmtInf>
              <Strd>
                <CdtrRefInf>
                  <Ref>RF18539007547034</Ref>
                </CdtrRefInf>
              </Strd>
            </RmtInf>
          </TxDtls>
        </NtryDtls>
      </Ntry>
    </Ntfctn>
  </BkToCstmrDbtCdtNtfctn>
</Document>

EDIFACT FINSTA / FINPAY / PAYEXT

Before ISO 20022, corporate banking flows were in EDIFACT. They remain used in certain contexts:

FINSTA — Financial Statement. End-of-day bank statement. Mostly replaced by camt.053, but still present in legacy ERPs.
FINPAY — Multiple Payment Order. Bulk credit transfer order. Replaced by pain.001, except in historical SAP IS-X usage.
PAYEXT — Extended Payment Order. Detailed payment order with annexes (used in automotive for multi-INVOIC flows). Replaced by pain.001 with RmtInf/Strd.
BANSTA — Banking Status. Good / bad execution acknowledgment. Replaced by pain.002.
DEBADV / CREADV. Debit / credit advice, ancestors of camt.054.
Coexistence today. 80-90 % of new volume in ISO 20022, 10-20 % EDIFACT for automotive and industrial flows that haven't migrated yet.

EBICS and corporate banking access

For corporate-bank communication, Austria uses two main channels:

EBICS (Electronic Banking Internet Communication Standard). French-German standard, adopted in Austria since ~2010. EBICS 3.0 currently deployed at Erste, RBI, BAWAG, Bank Austria. 3-level authentication (transport signature, authorisation signature, communication certificate).
MBS (Multibanken-Standard). Historical Austrian standard, still used by some local ERP vendors (BMD, RZL). Gradual migration to EBICS.
SWIFT FIN. For large industrial accounts (voestalpine, OMV) and banking (cross-border cash management). MT940, MT942, MT103 messages — migrating to ISO 20022 under the SWIFT MX 2025 deadline.
API banking. Under PSD2, AISP/PISP access via REST API. All Austrian top 10 banks offer APIs conformant to the Berlin Group NEXTGENPSD2 standard.

Reconciliation INVOIC ↔ camt.054 ↔ REMADV

The invoice / payment / remittance advice triple is central to accounting automation. Typical convention in Austria:

EndToEndId in pain.001 = INVOIC number. The payer replicates the supplier invoice number (e.g. 2026-AT-000412) into the EndToEndId field of pain.001.
EndToEndId carried through to camt.054. The beneficiary's bank pushes a camt.054 with the same EndToEndId — enabling automatic reconciliation on the supplier side.
Structured RmtInf. The RmtInf/Strd/CdtrRefInf/Ref field can carry an ISO 11649 RF reference, enabling even more robust reconciliation.
EDIFACT REMADV as complement. For grouped flows (one payment = 50 invoices), a detailed EDIFACT REMADV is sent in parallel, with RFF PB link = bank payment number.
ERP impact. SAP S/4HANA Austria, BMD NTCS, RZL offer a Bank Statement Processing module that imports the camt.054, matches against open invoices, and clears automatically.

Common pitfalls

Mixing camt.053 and camt.054. camt.053 is an end-of-day statement (snapshot). camt.054 is a per-transaction notification. Many ERPs confuse them — both are needed.
Truncated EndToEndId. The ISO 20022 EndToEndId field is 35 chars max. An invoice number 2026-INVOICE-DEPARTMENT-IT-000412-BIS exceeds — truncated on bank side, reference loss for reconciliation.
Mishandled UTF-8 charset. Umlauts (ä, ö, ü) in descriptions can corrupt reconciliation if the ERP stores in Latin-1 but the bank export is UTF-8.
SCT Inst in off-hours. Many ERPs schedule payments at midnight. SCT Instant is 24/7 but the ERP batch can block if pain.001 is sent during bank maintenance windows (typically Saturday evening).
MT940 vs camt.053. Cross-border industrials still use MT940 SWIFT heavily. MX 2025-2026 migration will force the switch to camt.053 — anticipate ERP configuration.

Foundations

Standards

Flagship messages

Tools