> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/help-and-reference/glossary.md).

# Glossary

| Term                       | Meaning                                                                                   |
| -------------------------- | ----------------------------------------------------------------------------------------- |
| Hotel / business           | The main business to which properties and permissions belong.                             |
| Property / branch          | The location where operations are performed; records are scoped to the selected property. |
| Unit                       | An apartment, room, dormitory or bed in the rental structure.                             |
| Physical bed               | Bed or bunk furniture; not necessarily a separately rentable unit.                        |
| Bed space                  | A place or level in the physical structure; guest capacity is defined separately.         |
| Confirmed reservation      | A saved reservation that has not checked in.                                              |
| Planned arrival/departure  | The dates expected for the reservation.                                                   |
| Actual arrival/departure   | The times when check-in and check-out actually occur.                                     |
| Allocation                 | The unit occupied by a reservation during a particular time interval.                     |
| Folio                      | A reservation's account summary of charges, services and payment movements.               |
| Accrued revenue            | The value of service provided in a period; payment may arrive on another date.            |
| Payment received           | Money received by the business.                                                           |
| Expense / outgoing payment | An expense is an incurred cost; a payment is money leaving the business.                  |
| Security deposit           | A deposit subject to return conditions; not accommodation revenue.                        |
| Unit-night                 | One unit's use or sale for one night.                                                     |
| Physical occupancy         | Used unit-nights compared with physical capacity.                                         |
| Sellable occupancy         | Usage relative to capacity available for sale.                                            |
| ADR                        | Revenue divided by nights sold, for the same product type.                                |
| RevPAR                     | Revenue divided by nights available for sale, for the same product type.                  |
| Operating result           | Revenue less operating expenses in the report; not accounting net profit.                 |
| Archive                    | Removal from daily view, not permanent deletion.                                          |

Interpret each status label together with the record's date and type. See [Using reports](/en/finance-and-reporting/reports.md) for calculation details.


---

# 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.interaktifotel.com/en/help-and-reference/glossary.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.
