> 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/roadmap/bevica-roadmap/bevica-extensions/excellar-and-commission-releases.md).

# Excellar & Commission Releases

Release notes for Excellar & Commission, including linked order fields, agreement processing, and fixes.

The list below highlights major enhancements and improvements that impact this extension (small hotfixes may not be listed).

Before applying any extension to the production environment, you should become familiar with new features in a sandbox environment first.

Please contact your system administrator to install this extension.

### Release V23.2.18.0 (08/09/26)

#### New features

* None.

#### Issues resolved

* Resolved issues with purchase currency on commission orders.
* Commission order lines can now be deleted on sales return orders.

### Release V23.2.17.0 (01/07/26)

#### New features

* Added Purchase Currency Code to the Get Excellar Lines page.
* Additional validation to ensure item lines cannot be manually added to an Excellar or Commission Sales Order.
* Improved functionality allowing multiple runs of Get Excellar or Get Commission Lines to handle order amendments.&#x20;
* Improved functionality allowing a [Create or Update of Linked Order](/documentation/guides/excellar-commission/bevica_excellar_order_processing.md#amending-the-sales-or-purchase-order) when new lines are added.
* Added the ability to allow Non-Duty Controlled, Service and Non-Inventory items to be added to an Excellar or Commission order. &#x20;

#### Issues resolved

* Removed the ability to Receive and Invoice on a linked Purchase Order to ensure this can only be posted through the Sales Order.

### Release V23.2.16.0 (24/04/26)

#### New features

* Version prepared for 2026 Wave 1, V28.
* Help Pages linked to new Bevica Knowledge Base. <https://kb.bevica.com/>

#### Issues resolved

* None

### Release V23.2.14.0 (20/08/25)

#### New features

* None

#### Issues resolved

* Fixed some tooltips on **Linked Order Fields**.
* Renamed the heading for **Linked Order Fields** on the **Linked Purchase Order**.

### Release V23.2.13.0 (26/06/25)

#### New features

* **Linked Order Fields** (**Shipment Date**, **Requested Delivery Date**, **Shipping Agent Code**, **Your Reference**) are now available on Excellar sales and purchase orders, and on the **Purchase Order Confirmation** report.

#### Issues resolved

* None

{% hint style="danger" %}
**Deployment note**

Install **Bevica Essentials V23.41.0.0**.
{% endhint %}

### Release V23.2.12.0 (22/05/25)

#### New features

* None

#### Issues resolved

* **Qty. Per Unit of Measure** will now update correctly on Purchase Agreements.

### Release V23.2.11.0 (16/09/24)

#### New features

* None

#### Issues resolved

* Ensure the **Purchase Price** on an **Excellar Purchase Order** remains as per the Excellar agreement when updating the quantity on the linked sales order.

### Release V23.2.10.0 (30/09/24)

#### New features

* None

#### Issues resolved

* Resolved an issue when running **Get Posted Document Lines to Reverse** on a **Purchase Return Order**.

### Release V23.2.9.0 (26/09/24)

#### New features

* None

#### Issues resolved

* Ensure the **Purchase Price** on a **Commission Purchase Order** stays at 0 when updating the quantity on the linked sales order.

### Release V23.2.8.0 (19/09/24)

#### New features

* None

#### Issues resolved

* Clear **Linked Order Fields** when running **Get Posted Document Lines to Reverse** on a **Sales Return Order**.

### Release V23.2.7.0 (10/07/24)

#### New features

* Modifications to allow users to **import Excellar and Commission agreements** using a configuration package.

#### Issues resolved

* None.

### Release V23.2.6.0 (04/07/24)

#### New features

* None

#### Issues resolved

* Fixed an issue where the **Get Commission Lines** list wasn't showing the relevant records when the **Sell-to Customer** had a linked **Bill-to Customer**.

### Release V23.2.5.0 (07/05/24)

#### New features

* Improved tooltips and navigation.
* Improved functionality when changing dates on sales orders and purchase orders. See **Amending dates on sales orders** and **Amending dates on purchase orders**.

#### Issues resolved

* None

### Release V23.2.2.0 (13/10/23)

#### New features

* Updated for v23.

#### Issues resolved

* None

{% hint style="danger" %}
**Deployment note**

If the install fails, uninstall the previous version first.
{% endhint %}

### Release V20.2.0.0 (01/08/23)

Enhanced features to manage Excellar and Commission orders within Bevica:

* **Excellar functionality**
* **Commission functionality**

#### Issues resolved

* None

### Release V20.1.1.0 (25/01/23)

New features to manage Excellar and Commission orders within Bevica:

* **Excellar functionality**
* **Commission functionality**

#### Issues resolved

* None

{% hint style="danger" %}
Deployment note

Install **Bevica Essentials V21.27.5.0** before installing the Excellar & Commission extension.
{% 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 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/roadmap/bevica-roadmap/bevica-extensions/excellar-and-commission-releases.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.
