Skip to content
Banco de España · Spain

How to issue Spanish IBANs

Fintech Passport
June 21, 2026 · 6-min read
How to issue Spanish IBANs

Spanish IBANs are routed through Banco de España, validated against a Modulus-97 check, and tied to a BIC4 that BdE recognises. Companion to our Dutch IBANs walkthrough: the Spanish format, the BIC application, the BdE registration steps, the national clearing connection, and the reporting catalogue that switches on the moment the first IBAN goes live.

1. The Spanish IBAN format

The Spanish IBAN follows the ISO 13616 pattern ES2!n4!n4!n1!n1!n10!n — 24 characters total:

  • Positions 1–2: country code, always ES
  • Positions 3–4: two check digits, calculated by Modulus 97 under ISO/IEC 7064
  • Positions 5–8: entity code (Código de Entidad) — four digits identifying the credit institution, EMI or PI, assigned by Banco de España
  • Positions 9–12: branch / office code (Código de Sucursal) — four digits identifying the specific branch or virtual branch within the entity
  • Positions 13–14: two internal check digits (Dígitos de Control) per the Spanish CCC standard
  • Positions 15–24: ten-digit account number allocated by the PSP

Every Spanish IBAN must pass both the IBAN Modulus-97 check and the legacy CCC two-digit check. Generators that validate only the outer ISO check produce IBANs that look valid but are rejected by Spanish counterparties.

2. Getting your entity code from Banco de España

The four-digit Código de Entidad is the identifier under which BdE knows your firm. It is assigned during the licensing process for credit institutions, EMIs and PIs. For passporting institutions establishing a branch in Spain, a code is assigned at the time of the branch notification.

The assignment is administrative — BdE allocates the next available number in the relevant series. You do not choose the code, but you do live with it. Once allocated, your entity code appears in every IBAN you issue, every supervisory return you file, and every CIRBE record (see our CIRBE piece).

3. The BIC connection

Spain’s Código de Entidad maps to a SWIFT Business Identifier Code (BIC) under ISO 9362. The mapping is one-to-one: every authorised Spanish PSP has a BIC under which it participates in SEPA and SWIFT-routed payments. The first four letters of the BIC form the BIC4 that identifies the institution in cross-border counterparty checks.

4. SEPA scheme adherence

Issuing IBANs that no one can pay into is useless. Adherence to at least one European Payments Council scheme is the precondition:

  • SCT (SEPA Credit Transfer) — the baseline; required for receiving incoming credit transfers
  • SCT Inst (Instant) — mandatory for euro-area PSPs under the Instant Payments Regulation from a defined date
  • SDD Core (Direct Debit) — optional, with additional Spanish overlays for government claims

Adherence is per-scheme, with separate sign-up packs and conformance testing. Plan for it from day one.

5. The national-clearing connection

Spanish PSPs settle euro payments through the Spanish national clearing system, which interconnects with the wider EU instant-payments and large-value rails. The connection is technical and contractual:

  • Direct participation requires settlement-account access at the national central bank and operational readiness
  • Indirect participation through a sponsor bank is the common route for smaller PSPs; the sponsor settles on the firm’s behalf
  • The PSD3 / PSR package, once in force, will change the direct-access framework for non-bank PSPs materially

6. What switches on the moment the first IBAN goes live

Issuing a Spanish IBAN is not just a payments engineering exercise. The first issuance triggers a catalogue of reporting obligations:

  • FTF — monthly feed of every IBAN-NIB account holder to SEPBLAC
  • DMO — monthly systematic AML reporting
  • DTE — Banco de España balance-of-payments return for cross-border flows
  • CIRBE — credit-risk register, where the firm extends credit
  • CESOP — EU-level cross-border payments register
  • IPR statistical report — annual filing covering credit-transfer volumes, charges and denied instant payments

The connectivity layer for most of these is EDITRAN. Onboarding to EDITRAN runs in parallel with the licensing application — start it day one.

7. Internal IBAN generator rules

Two non-negotiable validations:

  • Modulus-97 check — the IBAN-level check digits
  • Spanish CCC check — the legacy two-digit check at positions 13–14, computed under a defined algorithm against the entity, branch and account-number components

Beyond validation, three operational rules apply:

  • Branch / virtual-branch code allocation — pick a structured scheme that distinguishes product types or customer segments; supervisors look at the structure during inspections
  • Avoid IBANs that match well-known public-sector accounts (tax authority, social security, public-utility collection accounts) — commercial avoid-list, not statutory
  • Sequence the account-number allocation to leave room for future expansion; running out of account numbers under a single branch code requires opening a new branch code with BdE

8. Passporting in vs. domestic licence

An EMI or PI authorised in another EU member state can issue Spanish IBANs only after establishing a branch in Spain or, in defined cases, on a Freedom of Services basis with Spanish-IBAN issuance permission. See our branch vs Freedom of Services piece. The home-state authorisation is the foundation; the BdE-side mechanics — entity code, BIC, SEPA scheme adherence, EDITRAN — are the same regardless of whether the home is Spain or another member state.

9. FAQ

How is the Spanish IBAN different from the Dutch one?

The Spanish IBAN is 24 characters (the Dutch is 18) and includes a legacy CCC two-digit check beyond the standard ISO Modulus-97. The entity-code allocation by Banco de España also differs from the SWIFT-allocated BIC4 logic used in the Netherlands.

Can I choose my entity code?

No. Banco de España allocates the next available code in the relevant series. Once allocated it is permanent.

What is the relationship between the entity code and the BIC?

Every authorised Spanish PSP has both: an entity code (used in the IBAN structure) and a BIC (used in SWIFT and SEPA messaging). The two are mapped one-to-one in Banco de España’s records.

Do I need to coordinate with the Spanish national clearing operator?

Yes, indirectly. Direct participation in clearing requires national-central-bank settlement-account access; indirect participation requires a sponsor bank. The clearing membership is separate from the IBAN issuance itself but operationally linked.

What is the typical timeline from licensing decision to first IBAN issued?

For a Spanish-licensed PSP, three-to-six months post-grant for a complete payments build covering BIC, SEPA scheme adherence, EDITRAN, FTF / DMO infrastructure and operational testing. The IBAN format itself is straightforward; the surrounding plumbing takes the time.

Are there reserved IBAN ranges in Spain?

Yes — certain entity-code series are reserved for specific institution types (credit institutions, EMIs, PIs, specialised lending establishments). Banco de España publishes the current allocation. The internal account-number allocation is also subject to a commercial avoid-list to prevent confusion with public-sector accounts.

10. What to do, today

  • Confirm whether your BdE licensing route is direct authorisation, branch passport-in or Freedom of Services with IBAN-issuance permission.
  • Apply for the BIC alongside the BdE file — do not wait for grant.
  • Open EDITRAN onboarding in parallel.
  • Decide direct vs. indirect clearing participation early — it shapes settlement architecture.
  • Map the post-go-live reporting catalogue before the first IBAN — FTF, DMO, DTE, CIRBE, CESOP, IPR — and plan the data layer once for all of them.

Related: How to issue French IBANs · How to launch Dutch IBANs · How to issue Italian IBANs · What is the FTF? · What is EDITRAN?

Related reads.