> For the complete documentation index, see [llms.txt](https://cee-systems.gitbook.io/tcp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cee-systems.gitbook.io/tcp/starting-with-exchange/document-issue.md).

# Document issuance

It is recommended to review how masks are stored in the PNR by clicking on >i< in each *FARE QUOTE* table.

![](/files/-M9x8b_SIynQMqnImkpn)

![](/files/-M9xAB_kX1Q2zp3PkRM1)

Here you can review masks stored in the PNR.

![](/files/-M9xAOiJWsqR9YKLbktq)

## Documents to be issued

|                                 |                                                                                                                                                                                                                                                                                                     |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Documents**                   | Tickets and EMDs that are to be issued can be displayed here.                                                                                                                                                                                                                                       |
| **Last check before ticketing** | Here you must confirm that you have reviewed all ticketing masks stored in the PNR.                                                                                                                                                                                                                 |
| **Print modifiers**             | Documents to be printed on the itinerary printer. It represents DTD / DID / DAD / DTDID / DTDAD commands. TKP is always used. In this case, the itinerary is printed and MIR are generated as well. If you do not want to print for example the itinerary, you can switch off the appropriate bulb. |
| **Additional options**          | This field can be used for ticket modifiers, eg. in case of net remit (NF/NR etc.)                                                                                                                                                                                                                  |

![](/files/-M9xFLo6EzFAiVeTKjGh)

![](/files/-M9xFc-26gYYDl1iEAuX)

![](/files/-M9xFrd5Cfpqhyhu9BgK)

After the documents are issued, TCP Exchanges & Refunds service moves to the top of the PNR. Anytime you need to add or correct some data necessary for pricing or ticketing, you can click on the arrow with record locator placed on the top of the page and TCP Exchanges & Refunds service will return one step back.

![](/files/-M9xG9NYwQrU4Wx5nmFS)


---

# 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://cee-systems.gitbook.io/tcp/starting-with-exchange/document-issue.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.