> 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/finance-and-reporting/report-catalog.md). # Report catalog The application provides 57 reports. First identify the question you want to answer, then choose the relevant report and set date, property and currency filters. ## Which report should I start with? | Question | Report | | ----------------------------------------- | ----------------------------------------------------- | | What is happening in the business? | Management overview | | Why do revenue and money received differ? | Daily revenue and payments | | Which payment methods are used? | Payment methods | | How are rooms or beds being used? | Daily occupancy, Bed occupancy or Apartment occupancy | | How busy will the coming days be? | Future occupancy | | Where were costs incurred? | Expense breakdown and Profitability by unit | | Which balances remain outstanding? | Receivables and payables | | Which tasks remain open? | Faults and maintenance, Cleaning or Task completion | ## Understand the data source Reservation, stay and unit-movement reports use those application records. Complaints, maintenance, tasks, shifts, stock, contracts, competitor prices and security deposits require the relevant transaction records. Competitor prices and reviews are not fetched automatically from external platforms. The reports show manually entered data with its recorded source. See [transaction records](/en/finance-and-reporting/transactions.md) to enter source data and [Using reports](/en/finance-and-reporting/reports.md) for calculations and export rules. ## Aparthotel | Report | What it shows | | -------------------------- | ---------------------------------------------- | | Contract expiry | Contracts expiring in the selected period. | | Apartment expenses | Expenses assigned directly to an apartment. | | Security deposits | Security deposits received and refunded. | | Apartment revenue | Accommodation revenue by apartment. | | Long stays | Reservations for 28 nights or more. | | Apartment maintenance | Maintenance records by apartment. | | Apartment occupancy | Capacity and occupancy in apartment-nights. | | Apartment operating result | Result after directly assigned expenses. | | Rent and receipts | Contract value, due dates and payment records. | ## Finance | Report | What it shows | | -------------------------- | --------------------------------------------------------------------------------------- | | Daily revenue and receipts | Accommodation accruals, additional revenue, receipts and refunds are shown separately. | | Expense breakdown | Breakdown of payroll, rent, utilities and other operating expenses. | | Income and expenses | Period revenue, operating expenses and operating result. | | Payment methods | Receipt and refund channels. | | Staff salaries | Recorded salary expenses by staff member and period. | | Operating result by unit | Unit revenue and directly assigned expenses; unallocated expenses are shown separately. | | Receivables and payables | Aging analysis of reservation balances and other open accounts. | | Cancellations and refunds | Cancelled sales, completed and pending refunds. | | Rent expenses | Track rent paid by the business by period and landlord. | | Utility expenses | Electricity, water, internet and gas expenses by type, period and supplier. | ## Guest | Report | What it shows | | ------------------ | ---------------------------------------------------------------------------------- | | Complaints | Issue categories, open cases and resolution times. | | Guest profile | New and returning guests and country distribution where identities can be matched. | | Returning guests | Repeat stays, accommodation revenue and intervals between visits. | | Guest satisfaction | Recorded review scores out of five. | ## Hostel | Report | What it shows | | -------------------------- | -------------------------------------------------------- | | Bunk capacity | Capacity by upper/lower bunk and bed group. | | Shared-area usage | Recorded use of shared areas. | | Additional service revenue | Locker, laundry, breakfast and other additional revenue. | | Group stays | Reservations linked by a group code. | | Bed and room changes | Reservation allocation history. | | Bed occupancy | Occupancy measured in bed-nights. | | Bed readiness | Bed cleaning status and preparation tasks. | | Revenue per bed | Nights and revenue by bed. | | Short stays | Reservations for 1–7 nights. | | Dormitory performance | Sales and usage by unit type. | ## Management | Report | What it shows | | ------------------- | ------------------------------------------------------------------------- | | Management overview | Revenue, receipts, capacity and operational indicators. | | Property comparison | Compare the properties you are authorized to manage over the same period. | | Transaction records | Financial and operational records used as report sources. | ## Occupancy | Report | What it shows | | -------------------- | --------------------------------------------------------- | | Capacity utilization | Current physical, sellable and closed units. | | Daily occupancy | Physical and sellable capacity use separate denominators. | | Future occupancy | Capacity view based on current reservations. | | Past occupancy | Daily, weekly and monthly comparisons. | | Unit performance | Nights, revenue and occupancy per room, bed or apartment. | ## Operations | Report | What it shows | | ---------------------- | -------------------------------------------------------------------------- | | Loss and damage | Source, cost and recorded damage payments. | | Housekeeping | Current cleaning status and recorded housekeeping tasks for each unit. | | Stock and consumption | Stock entries, consumption, balance and reorder threshold by product code. | | Faults and maintenance | Open faults, resolution times and maintenance costs. | ## Revenue management | Report | What it shows | | ----------------- | ------------------------------------------------------------------------- | | Competitor prices | Recorded price observations with their sources. | | Revenue forecast | Future accommodation value of confirmed reservations. | | ADR and RevPAR | Revenue per sold night and per available night for the same product type. | | Price performance | Average nightly sales by product and day type. | ## Reservations | Report | What it shows | | ----------------------- | -------------------------------------------------------------- | | Reservation sources | Channel revenue, cancellation rate and sales after commission. | | Sales conversion | Enquiries, quotes, won and lost sales. | | Arrivals and departures | Planned arrivals and departures for the selected period. | | Length of stay | Number of nights and distribution of short and long stays. | | Reservation summary | Reservation status by creation date. | ## Staff | Report | What it shows | | ----------------- | ------------------------------------------------------------------------------- | | Staff performance | Reservation operations, tasks and overtime. | | Shifts and cash | Compare counted cash with opening balance + cash receipts − refunds − payments. | | Task completion | Completed, open and overdue tasks. | --- # 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/finance-and-reporting/report-catalog.md?ask=&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.