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

# Automatic Transfer of Paid Reserves

Automatically transfer Paid Reserves based on setup rules and trigger conditions.

{% hint style="info" %}
Bevica Fine Wine is a separate extension. Please contact your system administrator or your TVT contact if you would like further information or would like to install Bevica Fine Wine.
{% endhint %}

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 Vision Managed warehouses who transfer the paid reserve on to a new account once the order has been processed.

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

Vision Managed warehouse managing paid reserve movements between accounts.
{% endhint %}

### Setup of Automatic Transfer

The automatic transfer of Paid Reserves is set up at location level and will require initial setup on the Location card. To set this up, navigate to 'Locations' and select your default stockholding location. In the below example, this is the BLUE warehouse. Under the 'General' tab there will be a dropdown selection titled **'Paid Reserve Transfer To'.** In this dropdown, select the desired location for the automatic transfer. In the example below, this would be the BRONZE warehouse.

![Location card showing the Paid Reserve Transfer To field](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-658c076fd8d0c57d5b0185b007bea83fca0a696e%2F9ALuoDRgD_gLZtRxQyUz-787szsS9DJvUA.png?alt=media)

Only Locations where Bin Mandatory = NO will be available for selection as a Transfer To Location.&#x20;

### Posting a Sale into Reserve Order

The Sales into Reserve order should be created as normal and sent to your Vision Managed Warehouse using your default stockholding location. Once the file has been sent you can then post the order. On posting, Bevica will create the following entries:

* Stock into Paid Reserve entry in default location
* Transfer of Stock entry out of default location
* Transfer of Stock entry into your chosen 'Transfer To' location

These entries will show on the Paid Reserve card as well as in your Item Ledger Entries. The entries on your Paid Reserve Card will show the document type as 'Sales Invoice' and reference the Sales Invoice number on the 'Document No' column. Once posted, the Paid Reserve inventory will be available at the new 'Transfer To' location.

After posting, this can be managed through standard process. For more information on managing Paid Reserves, please see [Fine Wine (Paid Reserves)](https://kb.bevica.com/documentation/guides/paid-reserves-and-fine-wine.md)

### Inbound Request File from Vision Managed Warehouse

Once the Vision Managed Warehouse have transferred the Paid Reserve onto the new account, they will issue a Goods Received file. This file will contain confirmation that the Paid Reserve has been transferred along with the items new rotation number & rotation number reference. On processing and posting the file, the new rotation number and rotation reference supplied by the Vision Managed Warehouse will be copied onto the Paid Reserves original Item Ledger Entry. This new rotation number will flow through to the Paid Reserve Card. For more detail on how processing receipt confirmations, please see [Warehouse Goods Received Integration](https://kb.bevica.com/documentation/integration/bevica_warehouse_integration/warehouse_goods_received_integration.md).

{% hint style="info" %}
Bevica is only able to handle the automatic update of the rotation number if there is a 1-1 relationship between the Bevica Item Ledger Entry and the Goods Received file. If the Sales into Reserve order is drawn from one ILE but the Vision Managed Warehouse send two rotation numbers the file will error. In this scenario, the Paid Reserve would need to be split using a [Paid Reserve Journal](https://kb.bevica.com/documentation/guides/paid-reserves-and-fine-wine/splitting_paid_reserves.md) and the new rotation number would need to be applied manually using [Item Ledger Entry Edit](https://kb.bevica.com/documentation/guides/items-and-inventory/rotation_serial_and_lot_tracking.md#item-ledger-entry-edit-list).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.bevica.com/documentation/guides/paid-reserves-and-fine-wine/automatic_transfer_of_paid_reserves.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
