> 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/changing_item_or_unit_of_measure_on_a_paid_reserve.md).

# Changing Item or Unit of Measure on a Paid Reserve

Change the item or unit of measure on a Paid Reserve without losing allocation detail.

In some cases, you may need to change the customer, item, or unit of measure on an existing paid reserve. This could be part of the En Primeur process or to correct an error. This is achieved by cancelling all or part of an existing paid reserve and creating a new paid reserve with new details.

{% hint style="warning" %}
**Prerequisites**

Set up inventory, purchase, and sales processing.

Set up paid reserves.
{% endhint %}

### Paid Reserve Journal

The Paid Reserve Journal is used to change the details on a Paid Reserve. This involves creating a line to cancel the existing Paid Reserve and a new line to create the new Paid Reserve.

**To cancel the existing Paid Reserve:**

1. In the ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-d08791d5454211f4ad6c103dcb698478e14f0cc7%2FDL0xdIeok9M9VHtlr_ZkSS8d3vpeWsvPZA.png?alt=media) button, search for **Paid Reserve Jnl.**
2. Once the page is open, populate the **Source No.** with the customer whose reserves you want to cancel.
3. Select **Process** on the journal ribbon and **Get Paid Reserves to Cancel.**
4. The **Paid Reserve Selection** page will appear, find or search for the Paid Reserve record you want to credit and enter the **Quantity** to cancel.
5. Click OK to copy the line(s) back onto the **Paid Reserve Journal lines**.

Each journal line will set **Entry Type** to **Cancel Sales Into Reserve.**

**To create the new paid reserve:**

* Manually create a new line with the same:
  * Posting Date
  * Document No.
  * Source Type
  * Location Code
  * Variant Code
* Set the following fields:
  * Entry Type to **Stock into Paid Reserve.**
  * If applicable, set the new **Source No.** (Customer No.)
  * If applicable, set the new **Item No.** and **Unit of Measure**.
  * Set the new **Quantity** (this should match, in volume, the cancelled line).
  * Copy **Total Price** from the cancelled line to the new line.

The **Internal Information** field on the journal lines can be used to add notes.

Once both lines have been created correctly, you can post the journal, F9. This removes the original paid reserve from the customer's account and replaces it with a new paid reserve with a new number.

Positive and Negative record(s) will be created in the following areas:

* GL Entry.
* Item Ledger Entry & Value Entry.
* Paid Reserve & Paid Reserve Entry.

### Viewing the Linked Records

The old and new paid reserve ledger entries are linked by the **Posting Date** and **Document No.** on the original Paid Reserve Journal. **Find Entries** can be used to find these linked movements.

Navigate to the customer's Paid Reserves and highlight either the old or new Paid Reserve record. From here, select the **Ledger Entries** ribbon option (No.1 below) ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-f97c098a1e9a20cf314ba528f54f9ece8bfe6072%2FzSZKTgtmzTVUz_4UWzxsuC-uQozW8lInAQ.png?alt=media). From the **Paid Reserve Ledger Entries** page, highlight the particular movement and click **Find Entries** (No.2 below) ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-ce0908e4c0ca5dc60a3757bf40fcb59b9dcdaebc%2FlwCdPj7E4HfGd4ntb8XkKL4E_3AB32DEaA.png?alt=media). This finds all linked entries across multiple tables. **Paid Reserve Ledger Entries** (No.3 below) best shows all movements created as part of the original Paid Reserve journal posting ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-ab4b14ace1c113ea9e5c872c984d7279a8378fa8%2F1cHj4F3QD9ehzmyHpZJa-Wb30WfNdQAMdQ.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/paid-reserves-and-fine-wine/changing_item_or_unit_of_measure_on_a_paid_reserve.md?ask=<question>&goal=<endgoal>
```

`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.