> 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/cashier/faq-on-cashier/what-is-the-difference-between-bill-reprint-and-provisional-reprint.md). # What is the difference between Bill Reprint and Provisional Reprint? The difference between Bill Reprint and Provisional Bill Reprint primarily lies in the type of document being generated and the stage of the billing process it represents, although both share similar procedural requirements. • Target Document: Bill Reprint is used to generate a copy of a finalized or settled bill. In contrast, Provisional Bill Reprint is used specifically for provisional bills, which are typically interim documents issued before final settlement. • Menu Location: Both functions are located under the Cashier menu. • Requirement for a Reason: Both processes require the user to enter a reason before the system allows the reprint to proceed, ensuring accountability for generating duplicate financial documents. • Procedural Steps: ◦ For a Bill Reprint, you navigate to the menu, click Display to see the list, select the specific bill, enter the reason, and click the Bill button. ◦ For a Provisional Bill Reprint, you navigate to the menu, choose the provisional bill from the list, click Select, enter the reason, and click the Print Button. • Auditing and Tracking: Finalized bills that are reprinted are specifically tracked in the Bill Reprint Audit report. This report displays reprint details for a selected day range and can be filtered by User to monitor who performed the reprint and why. The sources do not mention a similar specific audit report for provisional reprints --- # 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/cashier/faq-on-cashier/what-is-the-difference-between-bill-reprint-and-provisional-reprint.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.