> 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/paid-reserves-and-fine-wine/selling_into_paid_reserve.md). # Selling into Paid Reserve Sell stock into Paid Reserve and allocate ownership to customers. {% hint style="info" %} Bevica Fine Wine is a separate extension. Please contact your system administrator or your TVision contact if you would like further information or would like to install Bevica Fine Wine. {% endhint %} Bevica lets you sell stock into Paid Reserve. Once posted, this creates Paid Reserve entries that then lets you manage your customer's inventory. {% hint style="warning" %} **Prerequisites** Set up inventory, purchase and sales processing. {% endhint %} ### Selling into Reserve - from stock Stock is sold into paid reserve using a Sales Order. 1. In the ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-d08791d5454211f4ad6c103dcb698478e14f0cc7%2Feosb1gH6fGFP_CUQ65dfAunzc1A3gNFQWw.png?alt=media) button, search for **Sales Orders.** 2. Once the page is open, create a new order. Select the **Customer No.** as normal. Then, make sure the **Location Code** reflects where the goods are currently stored and whilst the **Ship-to** is not used for delivery purposes, it needs to be a Ship-to with the correct **Duty Status** for the sale. Other than the normal sales order fields, you may want to populate fields like: **External Document No**, **Campaign No.** or **Order Source** Code to help identify the document & paid reserve later. Sales Lines are created as normal, selecting the item then entering quantity and Unit of Measure. Prices and discounts are applied automatically or can be manually changed. To ensure the line is posted as a Paid Reserve, you need to make sure Transaction Type is set to **Sales into Reserve**. The **Paid Reserve Split** field (hidden by default) determines how many Paid Reserve records will be created on posting. This is set by default from Bevica Setup, so you won't usually need to change it. If you do change it: | Field option | Outcome | | -------------------- | ------------------------------------------------------- | | None | One Paid Reserve record will be created per sales line. | | Unit of Measure | One Paid Reserve record will be created per unit. | | Base Unit of Measure | One Paid Reserve record will be created per base unit. | | Convert to Base | One Paid Reserve record will be created in base unit. | See [Paid Reserve Split](/documentation/guides/paid-reserves-and-fine-wine/splitting_paid_reserves.md) for examples of each option. {% hint style="info" %} **Note** To make sure the sales line is allocated against stock, link it to an **Item Ledger Entry** using Bevica Reservation functionality. You may also want to apply a Bevica Reservation if you want to apply the sales line to a particular parcel of stock. {% endhint %} To complete the sale, **Release** the order. This will perform any checks required, i.e., Credit Control, the order may be put on hold. When ready, **Ship and Invoice** the order. This will create standard sales posting records plus additional Paid Reserve postings. Record(s) will be created in the following tables: * Posted Sales Shipment & Posted Sales Invoice * Customer Ledger Entry & Detailed Cust. Ledger Entries * GL Entries * VAT Entries * Stock Item Ledger Entries & Value Entries * Paid Reserve and Paid Reserve Ledger Entries * Paid Reserve Item Ledger Entries & Value Entries (these are flagged with the Paid Reserve No.) {% hint style="warning" %} **Warning:** Once you have paid reserves against a customer, you are unable to change the customer no. {% endhint %} ### Selling into Reserve - prior to receipting stock To do this, you create the sales order in the same way, apply a **Bevica Reservation** linking the sales line to a purchase order to ensure the stock is properly allocated, then post a **Prepayment Invoice**. This will create a Customer Ledger Entry & Detailed Cust. Ledger Entries alongside other financial entries. Paid Reserve and Paid Reserve Ledger Entries are created after the stock is receipted and the order shipped. For more information, see **Prepayments.** ### Automatic Transfer of Paid Reserve Bevica has the option to automatically transfer the location of a Paid Reserve when a Sales into Reserve order is posted. This feature is to align with third-party warehouses who transfer the paid reserve onto a new account once the order has been processed. For more information, please see [Automatic Transfer of Paid Reserves](/documentation/guides/paid-reserves-and-fine-wine/automatic_transfer_of_paid_reserves.md). --- # 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/paid-reserves-and-fine-wine/selling_into_paid_reserve.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.