> 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/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-las-aplicaciones/validar-la-emision-recepcion.md).

# Validate issuance – reception

It can be carried out, having selected in the tree (left panel) or in the list (right panel) an application to sign, in one of the following three ways:

4. From the menu “*Operations –> Application -> Validate Issue - Reception”*
5. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/I4QaSPCFdzdWoLGHbEFJ/image1.png) on the taskbar.
6. The context menu (right mouse button).

If the **application** is **for signing** and the acceptance or rejection file has been received from the receiving end, from here a new file can be generated, in Editran/FF’s own format, which marks the completion of the sending and receiving of the signatures. The file remains in the signatures directory with the same name as the application followed by the extension .ValEmiRec.p7b. While this file remains in the directory, the application signing process will be stopped. The application will reach the state “*Issue-Receipt accepted”.*

If the user has the corresponding permission in profiles, they will be able to validate the issue-receipt even from the “Rejected Receipt” state. In this case, the following message will be displayed:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/YH20aYilBiWCm4Ofr6Rj/image2.png)

This operation can only be performed by users who, in the application-user relationship profile, have the corresponding permission and on the applications that have configured “*Yes*” in the “Enablement” section of the profile.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-las-aplicaciones/validar-la-emision-recepcion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.