> 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/reference/troubleshooting/fix_unpaid_reserves_not_updating_properly_on_posting.md).

# BUG fix: Unpaid Reserves not updating properly on posting

Fix Unpaid Reserves quantities after posting. Find lines where Reserved Quantity differs from Quantity Remaining, then correct the Unpaid Reserve Information quantity (fixed from v23.31.24.0).

Posting sales order lines with Unpaid Reserves (UPR) were not properly updating the **Posted Qty. (Base)** or **Qty. Remaining (Base)**. This has been fixed in release V23.31.24.0 (29/03/24).

## Prerequisites

* Unpaid Reserves exist.

## Issue

For a period after a Microsoft Hotfix, **Posted Qty (Base)** and **Qty. Remaining (Base)** fields were not being updated correctly when a sales order was posted that contained lines originating from a UPR. The underlying reservations and item ledger entry stock balances are correct. Where stock is low or most stock is held in unpaid reserve, item availability may show a negative figure.

## Fix

The fix involves identifying which records are wrong using the Unpaid Reserve Item Lines page and then manually amending the UPR Information quantity to reflect what's remaining now.

**To correct the unpaid reserve record:**

* Navigate to the Unpaid Reserve List and click on any **Quantity (Base)** figure. This opens the Unpaid Reserve Item Lines page.
* Once on the Unpaid Reserve Item Lines page remove all filters.
* Personalise the page and add the field **Reserved Quantity** to the list somewhere near **Quantity Remaining**.

  ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-370423b665367a2d94e1a36db1e8c85f57eb0952%2F46JFpgRUX60cyle4j9tM496DcRmp9dyjhQ.png?alt=media)
* Export the list to Excel and highlight the rows where **Reserved Quantity <> Quantity Remaining**. These are the records that need to be amended.
* For each incorrect UPR, open the Unpaid Reserve Information page and amend the Quantity value.

  ![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-c43372b7a51ac05d15453b8f7fedd60144acaab9%2FuC6Zj8-cKkc1bWlivs9ydaVHkeIkoglRig.png?alt=media)

  If in doubt you can navigate to the Item Ledger Entry list page filter using the entry number in the **Source Info** field and view **Remaining Quantity** and **Reserve quantity** to see if there is any free stock and who else might have that stock reserved.

Contact the Bevica team if you have any questions.


---

# 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/reference/troubleshooting/fix_unpaid_reserves_not_updating_properly_on_posting.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.