> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/sepa/introduction.md).

# Introduction

The EDITRAN/SEPA application is a utility that transforms files from one format to the other of the two defined by SEPA for reporting non-cash euro payments. So far, SEPA has defined the messages related to direct debits and transfer orders.

SEPA regulations require exchanging the following standards in XML format:

* SEPA Direct Debits in electronic file – Basic Scheme (19.14)
* SEPA Direct Debits in electronic file – B2B Scheme (19.44)
* Orders in file for issuance of transfers and checks in euros (34.14)

Some converters have been developed that allow:

* They transform XML to modern flat-format files (record length 600) to XML

These converters may be called:

* In the pre-issue stage, with a new procedure (P1PRESEPA) that carries a new step, before step A1P
* In the post-receipt stage, with a new procedure (P4POSSEPA) that carries a new step, after step A4P

The converters (CLI1SEPA and CLI4SEPA programs) call a TCP client program (WORKERSEPA), which connects to the Java server, resident in the UNIX services of the AS/400. They indicate to it:

* Server connection data

a) Java server IP and port

b) Java server response timeout

* Request data

a) Function (1) flat to xml, (2) xml to flat

b) Input file name

c) Output file name

d) Translation table (only if necessary)

* Other data

a) Source code,

b) Remote code (if launched with non-Editran files, it is necessary to indicate a remote code from a test session)

c) Application (if launched with non-Editran files, it is necessary to indicate an application from a test session)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/sepa/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.