> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-nightaudit/faq-on-night-audit/what-are-the-analytical-reports-for-business-sources.md). # What are the analytical reports for Business Sources? The **Business Source** is a compulsory field during reservation because it tracks the origin of a referral (e.g., OTAs), which is critical for identifying repeat business and financial implications. Several analytical reports utilize this data to provide insights into hotel performance: * **Contribution Analysis:** This report analyzes **Revenue Contribution and Room Nights Contribution** based on various aspects, including **Business Contribution**, for any selected period. * **Market Analysis:** Similar to contribution analysis, this report tracks **Market Revenue and Room Revenue** categorized by the origin of the business. * **Guest Analysis:** This provides a detailed breakdown where users can filter guest data by **Business Source**, allowing for deeper segmentation of the guest profile. * **Occupancy Statistics:** By using the **Sources filter**, you can add a dedicated column to this report that indicates exactly where each booking originated for in-house or checked-out guests. * **Occupancy Forecast:** This forward-looking report includes an **Options Filter** to add Business Source columns and a **Funnel Filter** to sort future reservations by a specific booking origin. * **Manager Report:** While not a dedicated source report, it provides a consolidated overview of rooms and related revenues, including those collected from companies and travel agents, which are often linked to business sources.
--- # 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://help.rbsgo.com/front-office-module/fo-nightaudit/faq-on-night-audit/what-are-the-analytical-reports-for-business-sources.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.