# Procedure to correct an erroneous supplier shipment (quantity declared is more than received)

**URL:** <https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732>\
**Category:** User\
**Tags:** purchasing\
**Created:** [November 27, 2023, 9:35am UTC](https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732 "2023-11-27T09:35:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxx](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/maxx/32/2320_2.png) [@maxx](https://discuss.tryton.org/u/maxx)\
**Post date:** [November 27, 2023, 9:35am UTC](https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732/1 "2023-11-27T09:35:06Z")

</div>

Hi,

We recently have a problem with a supplier shipment. We had to receive 10000 units of products and the user inputs 15000 units (incoming moves). Stock people didn’t check the stock arrival and confirm 15000 units instead of 10000 units. The problem was noticed by accounting people with the invoice.

Doing an inventory seems not a good solution to solve this quantity problem.

- How to fix such error to keep cost price correct, having a correct stock quantity and a correct invoice?
- If doing a purchase return, how account people could identify the new invoice line to add to the original invoice with negative amount ?

We noticed also when doing a supplier shipment return, “From Location” of the return shipment could be different of “From Location” of the move (“Storage Zone”(View) on the shipment VS “real location” as From Location of the product in the move)

 ![2023-11-27_10-33](https://discuss-cdn.tryton.org/uploads/default/original/2X/d/db291dbdb7340d0b619e7331da7fb252be50bcca.png)

Thanks for help! 🙂

---

<div class="post-metadata">

**Author:** ![dotbit](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/dotbit/32/2093_2.png) [@dotbit](https://discuss.tryton.org/u/dotbit)\
**Post date:** [November 27, 2023, 11:14am UTC](https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732/2 "2023-11-27T11:14:01Z")

</div>

Hi Maxime,

You have been in the forum for some time more than me, so it is possible that I am not understanding your question correctly.

For me it is not clear if your problem is starting from Purchase or Supplier Shipment.

Is there a reason why you can not return all the goods and then recreate the right quantity?

Also if using Purchase, I select the stock move that is pending rather than introducing the quantity manually.

If the wrong quantity is in Purchase line, then you can use purchase amendment to rectify it, and then the right Supplier shipment will be recreated.

If the problem starts with Purchase line, after correcting it using Stock amendment the right invoice should be recreated. I guess if you have posted the wrong invoice you should cancel, and post the right one.

---

<div class="post-metadata">

**Author:** ![maxx](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/maxx/32/2320_2.png) [@maxx](https://discuss.tryton.org/u/maxx)\
**Post date:** [November 27, 2023, 1:42pm UTC](https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732/3 "2023-11-27T13:42:24Z")

</div>

> [@dotbit](#):
>
> For me it is not clear if your problem is starting from Purchase or Supplier Shipment.

It’s supplier shipment. The purchase is correct with the right quantity.

> [@dotbit](#):
>
> Also if using Purchase, I select the stock move that is pending rather than introducing the quantity manually.

Indeed, but in our business, we never receive the exact quantity that we ordered because it’s linked to a batch of production. So most of the time, it’s not the quantity we purchased. We define correct quantities and lot for the supplier shipment when we receive the supplier packing list. (and a human error could happen ☹ )

> [@dotbit](#):
>
> Is there a reason why you can not return all the goods and then recreate the right quantity?

In our case, goods are already received and stored in the warehouse. The main problem is an inexact quantity.

> [@dotbit](#):
>
> If the wrong quantity is in Purchase line, then you can use purchase amendment to rectify it, and then the right Supplier shipment will be recreated.

In our case, supplier shipment is done so amending the purchase doesn’t change anything and also quantity on purchase is correct, we need to fix a received quantity greater than real quantity.

We could imagine a return shipment on the original purchase but “actual quantity” field doesn’t care about negative quantities…

---

<div class="post-metadata">

**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\
**Post date:** [November 27, 2023, 6:34pm UTC](https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732/4 "2023-11-27T18:34:57Z")

</div>

For me you must create a supplier return shipment (at the same date as the reception) with the extra quantity and add those return stock moves to the invoice line which has the correct quantity but too much stock move.  
This way the average cost price computation will be corrected.

This is a little bit similar to what does `account_invoice_correction` but for the shipment 🙂

---

<div class="post-metadata">

**Author:** ![system](https://discuss-cdn.tryton.org/uploads/default/original/1X/c6f8ec0a40525cdcd50058c734283450a4b3d38b.png) [@system](https://discuss.tryton.org/u/system)\
**Post date:** [December 27, 2023, 6:35pm UTC](https://discuss.tryton.org/t/procedure-to-correct-an-erroneous-supplier-shipment-quantity-declared-is-more-than-received/6732/5 "2023-12-27T18:35:31Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
