What is EDITRAN? The BdE and SEPBLAC file channel

EDITRAN is not a single connection you switch on once. It is a channel you are registered for one reporting process at a time, by signed letter, and for some filings it is the only channel accepted at all. Spanish firms meet EDITRAN early: SEPBLAC accepts the Fichero de Titularidades Financieras exclusively over it, and several Banco de España returns travel the same way. This walks through what EDITRAN is inside the Banco de España’s own framework, how registration actually works, the operating conditions that produce most first-year failures, and what the acknowledgement chain tells you after a file lands.

1. What EDITRAN is — and what it is not

EDITRAN is a commercial file-transmission product, used over TCP/IP, that the Banco de España accepts as one of its telematic file-exchange channels. The governing document is the Banco de España’s Instrucción Externa 2005.24, Manual de uso para el intercambio telemático de archivos con el Banco de España, maintained by its Departamento de Sistemas de Información.

Two definitions in that instruction do more work than anything else in the framework. A channel is a specific protocol implemented on a specific network. A process is a file-exchange procedure defined by the department that owns the information, identified by a six-character code. Each department issues its own instructions — generically a Manual de Uso — stating, for that process, the permitted channels and any timetable differing from the general one.

So the assumption that a Spanish firm “gets an EDITRAN connection” and can then file anything is wrong twice over: authorisation is per process, and EDITRAN is not always the permitted channel.

The network column is the detail most often missed at design time. EDITRAN runs over the Banco de España’s own VPN (RedBdE) or the public-administration VPN (Intranet Administrativa) — not over the open internet. A firm that has budgeted for a software licence but not for network connectivity has budgeted for half the channel.

2. Registration is per process, and it starts with a letter

Adhesion to a process is requested by a signed letter to the Banco de España, at Sistemas de Información, Servicio de Gestión de Clientes BdE, Apartado de Correos 15, 28080 Madrid — or presented at the Registro General del Banco de España, Alcalá 48. It may be replaced by an electronically signed email to gestionclientesbde@bde.es using a legal-person certificate issued to the entity by a certification service provider the Banco de España recognises. The paper signature must be autograph, from a person recognised by the department that owns the information.

The content is prescribed: the six-character process code from that process’s Manual de Uso, the entity name, the four-digit entity code, the CIF, a technical contact for transmission incidents and a separate functional contact for content incidents, and the chosen channel with its security mechanism.

Once the owning department approves the adhesion, Sistemas de Información configures the Banco de España side and the sender or named technical contact receives an email confirming the channel is available for that process.

Facts: a newly authorised Spanish e-money institution has to file the FTF monthly and expects to file two Banco de España returns later in the year. It plans one onboarding project, one letter, one connectivity test.

What the rule says: adhesion is to a process, identified by its own six-character code, and each process’s Manual de Uso sets its own permitted channels and may set its own timetable.

What the practitioner does: builds the reporting catalogue first — one row per process, with its code, owning department, permitted channels and deadline — and treats each row as its own adhesion, while reusing the technical connectivity underneath.

Outcome: one network build and several registrations, which is the shape the framework actually has.

3. The operating conditions that catch people out

Four conditions in the instruction produce most avoidable failures.

• The window. Unless a process says otherwise, the channel is available 08:00 to 22:00, Monday to Friday, excluding national and European holidays. Sending outside the period can produce errors or simply leave the file unprocessed.
• One file per transmission. Each transmission carries a single data file, in both directions.
• The character set. Files may be converted between ASCII and EBCDIC in processing, so only the character set in the instruction’s annex may be used — a stray character is a processing error, not a cosmetic issue.
• The receive buffer. On inbound files the Banco de España retries for a defined period, after which files still pending stop being available. The receiving infrastructure has to be ready inside the window, or a supervisory response can expire unread.

4. What the FTF looks like over the wire

SEPBLAC’s Instrucciones para la declaración de información al FTF — issued under Article 43 of Ley 10/2010 — are more restrictive than the Banco de España framework. FTF data is presented exclusively by telematic means, as text files, exclusively over EDITRAN, over TCP/IP with the product’s public-key encryption. There is no web-portal alternative.

The declaring population answers the passporting question directly: banks, savings banks, credit cooperatives, electronic money institutions, payment institutions — and the Spanish branches of foreign credit institutions, e-money institutions and payment institutions. What is declarable includes every payment account a PI or EMI opens for a client, expressly including accounts used only to record each client’s individual balance and movements inside the safeguarding account where they are not used directly to settle third-party transactions. Credit cards and prepaid cards are not payment accounts, without prejudice to any declarable account they are attached to.

Then the acknowledgement chain, which is the part that makes EDITRAN a two-way channel rather than an upload. On arrival, SEPBLAC returns an acuse de recibo saying whether the file is admitted — in which case it moves to processing — or not admitted, with the reasons, in which case it is not processed at all. After processing, one of three outcomes:

Whole-file rejection is automatic wherever the origin of the submission cannot be guaranteed or identified, where there is any suspicion of manipulation, where the file identification is defective, or where an error could mix data across products or intervinientes. The named triggers include an incorrect declaring-entity code, a missing type-00 header or type-99 end-of-file record, any error in the sequence numbering, a record-type sequence departing from the specification, and a count of type-10 product records or of total records that does not match the type-99 record.

Facts: an EMI’s monthly file is admitted, and the requerimiento that follows lists errors in three product blocks out of several thousand. The team plans to fix the three and resend the whole month.

What the rule says: this is partial acceptance. The correct blocks are already loaded; the response required is a fichero complementario carrying the corrected blocks, inside 10 working days.

What the practitioner does: resends only the corrected blocks as a complementary file, and — because SEPBLAC’s instructions state that files received over the channel receive automatic treatment and cannot be deleted or discarded except in expressly provided cases — runs the validation tooling before transmitting rather than relying on being able to withdraw a bad file.

Outcome: the correction is a targeted complementary file, not a resubmission, and the audit trail matches the requerimiento block by block.

5. The seven-working-day clock, and the negative file

The monthly file must reach SEPBLAC within the first seven working days of the following calendar month. An entity with nothing to declare for a month does not simply stay silent: it must send a negative monthly file inside the same seven working days. Working days here means every day of the year except days that are non-working across the whole national territory — Saturdays, Sundays and non-substitutable national holidays — as published periodically in the Boletín Oficial del Estado.

Two consequences follow. If the deadline passes with neither file, SEPBLAC issues a requerimiento. And a negative file is not an acceptable answer to a requerimiento, except where that requerimiento was itself generated by a delay in sending the mandatory monthly file. An entity not yet marketing declarable products notifies SEPBLAC in writing — at sepblac.ftf@bde.es — at least one month before its FTF obligation begins, and sends no files until it has a declarable product.

Facts: a Spanish branch of a foreign EMI opens no new accounts in a quiet August and files nothing.

What the rule says: silence is a breach. A negative monthly file was due within the first seven working days of September, and the branch is squarely inside the declaring population.

What the practitioner does: makes the negative file an automatic monthly job with the same calendar entry as a populated one, and diaries the seven-working-day deadline off the BOE national holiday calendar rather than a generic business-day count.

6. FAQ

7. What to do, today

• Build a process inventory, not a connection. One row per reporting process: the six-character code, the owning department, the permitted channels from its Manual de Uso, the deadline, and the state of your adhesion. This is the artefact the framework is organised around.
• Split the network question from the software question. EDITRAN needs a product licence and RedBdE or Intranet Administrativa connectivity. Confirm both before committing to a go-live date, and check whether the processes you need permit ITW instead — a web channel over the internet is a materially different project.
• Instrument the return leg. The acuse de recibo, the acuse de proceso and the requerimiento all arrive as files on the same channel, and the requerimiento starts a 10-working-day clock. Route them to a monitored queue with an owner.
• Automate the negative file. A quiet month is still a filing month.

One caveat on sourcing: both the Banco de España instruction and SEPBLAC’s FTF instructions are versioned and have been reissued. Before a build, take the current Manual de Uso for the specific process from the owning department rather than relying on any summary, including this one.

Belgium: see the PCC / CAP central register of accounts.

Related: What is the FTF? · What is SEPBLAC? · The DMO monthly declaration · What is CIRBE? · How to issue Spanish IBANs · ANIFI — Spain’s new AML authority · SEPBLAC video-identification — remote onboarding in Spain · The Spanish reporting calendar · ITA — file exchange with the Banco de España