> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/items-and-inventory/return_reasons_and_stock_write-off.md). # Return Reasons and Stock Write-off Record return reasons and write off stock with the right postings and audit trail. **Return Reasons** can be used to add clarity to stock movements. Used primarily on Sales Return Order lines, but also available on Sales Order lines and Item journals, return reasons also give you the ability to report on and control what happens to that stock on receipting, i.e. move to a quarantine location or write it off automatically. **Return Reasons** should not be confused with **Reason Codes.** To find out more about **Reason Codes,** click here: [Sales and Purchasing: Reason Codes](/documentation/guides/sales/sales_and_purchasing_reason_codes.md) [Microsoft: Setting Up Source Codes and Reason Codes for Audit Trails](https://docs.microsoft.com/en-gb/dynamics365/business-central/finance-setup-trail-codes) {% hint style="warning" %} **Prerequisites** Items have been created. Sales processing set up. {% endhint %} ### Setup Navigate to **Return Reasons,** here you can create multiple codes for all the reasons stock might be moved, i.e. input error, damaged in transit, unwanted by customer, mis-pick, sold for a particular event, goodwill. The codes can be used by themselves for reporting and specifically on Sales Return Orders to manage what happens to that stock on receipt. ### **Return Reason fields** | Field | Note | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Code | A unique reference for the return reason code. | | Description | A description to help identify the code. | | Default Location Code | Where this is set, when a return reason is added to a sales return order line, the Location Code on that line is changed. Stock will be moved to this location. This can be used, for example, where you have a quarantine location. | | Inventory Value Zero | The returned stock is posted with zero value. This option should be used with care, as it results in stock being available to sell with zero cost. Also note that any Additional Charges against the original document are still posted. This option should be used on sales return order lines created manually. If you use it against lines created when running 'Get Posted Document Lines to Reverse' the cost adjustment routine will add the original cost to the item ledger entry created on the return. See below for an example scenario on when this option could be used. | | Automatic Neg. Adjustment | Tick this option to have Bevica process Sales Return Orders normally on receipt, then post a negative adjustment for the entire line quantity, removing the stock from inventory. Note: you are unable to use a return reason code that has Automatic Neg. Adjustment ticked to return stock into a location that has Bin Mandatory set. | | Sales Quantity (Base) | See Reporting at end. | | Purchase Quantity (Base) | See Reporting at end. | ### Processing You can add the **Return Reason** field to the following document lines: * Sales Return Order * Sales Order * Purchase Return Order * Purchase Order ### Reporting You can view and report on **Return Reasons** on the following document lines: * Item Ledger Entry * Value Entry * Posted Sales Shipment * Posted Sales Invoice * Posted Purchase Receipt * Posted Purchase Invoice The Return Reasons page has two additional fields, **Sales Quantity (Base)** and **Purchase Quantity (Base)** that display quantities returned against each code. You can use **Filter Totals To** filter fields: **Date Filter** and **Location Filter** to further refine the values. ![Return Reasons list showing Sales Quantity (Base) and Purchase Quantity (Base) totals](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-90b35231ebc8922d5a1b9732ad3d5c80a451f7b2%2Fm0GlDVxE7-YAf5cbeGoy7JLffMry0WVmWg.png?alt=media) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kb.bevica.com/documentation/guides/items-and-inventory/return_reasons_and_stock_write-off.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.