> 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/editran-ff/graphical-interface/user-management/presentation-sessions/reception-signing-rules.md).
# Reception signing rules
1\) For the case of a generic rule, it will use rule ‘00’.
The rules for generic rule 00 must not include NIF, suffix, or amounts. The reason is that, if the rule is not determined, the location in the document from which this information should be gathered is unknown, and without this information it is not possible to make the comparison.
2\) If a rule is entered, the rule will apply to files belonging to that rule. Rules 19 and 34 are allowed.
The company is composed of NIF (9 positions) and suffix (3 positions). These NIF and suffix values are obtained from the File Presenter Identification and, if unavailable, from the Identification of the first ordering party (rule 34) or the Identification of the first creditor (rule 19). To define a company that can be applied to a NIF and all suffixes, we can enter the NIF and suffix “???”. If we enter company, it is mandatory to include the rule.
For a receipt application, multiple rules can be defined: without rule, with rule and without company, and with rule and company.
Rule validations are carried out in order from most to least restrictive.
* If the file has a rule, only the rules for that rule are validated.
- [x] The rule with the same NIF and suffix as the file will be applied first
- [x] If there is none, the one matching the NIF and with no suffix defined (“???”) will be applied
- [x] If none match, the rule without NIF or suffix will be applied
* If the file has no rule, the generic rule is applied
If on the initial screen of the “Reception Signing Rules” we enter the values: Option, Local code, Remote-remote code, application, and rule, the following menu appears:
* The following fields appear.
* Session: Local code, remote code, and application.
* Rule: Banking rule.
* Company: Composed of NIF plus suffix.
* Type: Reception
* Total number of signatures: Number of signatures the rule can have. This parameter only applies in reception and can only be entered in the case of modification.
* Number of mandatory groups: Number of user groups the rule can have. This parameter only applies in reception.
* Option: U (User) or G (Groups)
* Name: Name of the group or user.
---
# 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/editran-ff/graphical-interface/user-management/presentation-sessions/reception-signing-rules.md?ask=&goal=
```
`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.
.png?alt=media)
.png?alt=media)