> 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/banquet/banquet-module/transaction/faq-on-reservation/what-is-the-complete-workflow-from-venue-blocking-to-billing.md). # What is the complete workflow from venue blocking to billing? The complete workflow from venue blocking to the final billing process, as detailed in the sources, involves several stages across the Transactions and Cashier menus: **1. Venue Blocking** The process begins with securing a venue for a specific time. • Navigate to Block under the Transactions Menu. • Choose a Block Type (e.g., Wait List or Maintenance Block). • Enter essential data, including the Guest Name, Date, Session,Venue, Plan, and Expected/Guaranteed Pax. • Provide business details such as Function Type, Business Source, and Market Segment before clicking Save. **2. Creating a Reservation** Once a block is ready to become a formal booking, a reservation is created. • Under the Transactions menu, select Reservation and click New. • Guest Info: Select the Guest Type and Name. Enter details like Settlement mode, Billing Instructions, and the Guest's address. • Event Details: Enter the Date, Session, and Venue. You must also specify the Seating Arrangement, Event Start/End times, and any Department Aids required. • F\&B and Menu: Under the F\&B tab, select the Plan and Pax. In the Menu tab, select the specific menu (which loads based on the chosen Plan) and add any extra items. • Additional Charges: Select the Amenities and Event menus to enter specific items and their Charge Rates. • Save the reservation to complete the entry. **3. Approval and Communication** • Banquet Approval: Reservations must be approved via the Banquet Approval menu. Select the appropriate Template Type/Name and the Guest name, then click Approve and Save. • Banquet Emails: You can send confirmations via Email or WhatsApp through the Banquet Emails transaction. **4. Documentation (Function Prospectus)** Before the event, a Function Prospectus is generated. Select the reservation under the Function Prospectus menu and click Save/OK to print the document. **5. Advances and Charges** • Advance Payment: To record a deposit, go to the Cashier Menu, select Advance, choose the reservation, enter the amount and payment mode, and Save. • KOT/Charges: During the event, additional items or services are recorded via Kot/charges in the Transactions menu. Select the Reservation No., pick the items or charges, and Save to raise the KOT. **6. Billing and Settlement** The final stage occurs in the Cashier menu. • Bill Creation: Click Bill, search for the Reservation no., and click Save to generate the final bill. • Bill Settlement: Navigate to Bill Settlement/Cancellation, search for the Bill No., and click OK to settle the payment and officially close the reservation. If any errors occur after billing, the system allows for Bill Resettlement (to change payment modes) or Bill Reprinting for auditing purposes --- # 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/banquet/banquet-module/transaction/faq-on-reservation/what-is-the-complete-workflow-from-venue-blocking-to-billing.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.