> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/stock-reports/issue-receipt-register-report.md). # Issue/Receipt Register Report Logic ERP has corrected the **Receipt Prefix Filter** in the **Issue/Receipt Register Report**. A receipt prefix used in one run no longer carries over into the next run. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Stock Reports**. * Open the **Issue/Receipt Register Report**. *** ### **What's corrected** * When you ran the report with a configuration that has a **Receipt Prefix Filter**, and then, in the same window, with an older configuration saved before the **Receipt Prefix Filter** option was added (and not saved since), the second run still used the first run's receipt prefixes. Receipts with other prefixes were left out. Each run now uses only its own **Receipt Prefix Filter**. Figures may rise on the second run. This is intended. * When the report runs unattended in the **LOGIC Auto Report Mailer** and something goes wrong, it no longer opens an error message on screen that holds up the mailing. * The report no longer shows an error on receipts made from an employee; the employee's name is now shown. --- # 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/stock-reports/issue-receipt-register-report.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.