# Rejected Requests ## Rejected requests A rejected request cannot move forward in its current form. The rejection reason should help you decide the next step. ### Common reasons * policy violation * missing business justification * incorrect coding * duplicate or invalid spend ### What to do next 1. Read the rejection note. 2. Confirm whether the item can be corrected. 3. Create a new request if the original cannot be edited. 4. Ask your manager or finance team if the reason is unclear. ### How to avoid future rejections * follow receipt and policy requirements * use accurate coding * add clear business context --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.techzala.com/employee-guides/rejected-requests.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.