[ADD] How to determine if a vendor bill should be paid (3-way matching)
This commit is contained in:
parent
c27456ef57
commit
8f1fbe3a29
@ -11,3 +11,4 @@ Request for Quotations
|
|||||||
rfq/cancel
|
rfq/cancel
|
||||||
rfq/approvals
|
rfq/approvals
|
||||||
rfq/analyze
|
rfq/analyze
|
||||||
|
rfq/3_way_matching
|
67
purchase/purchases/rfq/3_way_matching.rst
Normal file
67
purchase/purchases/rfq/3_way_matching.rst
Normal file
@ -0,0 +1,67 @@
|
|||||||
|
=================================================================
|
||||||
|
How to determine if a vendor bill should be paid (3-way matching)
|
||||||
|
=================================================================
|
||||||
|
|
||||||
|
In some industries, you may receive a bill from a vendor before
|
||||||
|
receiving the ordered products. However, the bill should maybe not be
|
||||||
|
paid until the products have actually been received.
|
||||||
|
|
||||||
|
To define whether the vendor bill should be paid or not, you can use
|
||||||
|
what is called the **3-way matching**. It refers to the comparison of
|
||||||
|
the information appearing on the Purchase Order, the Vendor Bill and the
|
||||||
|
Receipt.
|
||||||
|
|
||||||
|
The 3-way matching helps you to avoid paying incorrect or fraudulent
|
||||||
|
vendor bills.
|
||||||
|
|
||||||
|
Configuration
|
||||||
|
-------------
|
||||||
|
|
||||||
|
Go in :menuselection:`Purchase --> Configuration --> Settings`
|
||||||
|
and activate the 3-way matching.
|
||||||
|
|
||||||
|
.. image:: media/3_way_matching01.png
|
||||||
|
:align: center
|
||||||
|
:width: 6.50000in
|
||||||
|
:height: 0.70833in
|
||||||
|
|
||||||
|
|
||||||
|
Should I pay this vendor bill?
|
||||||
|
------------------------------
|
||||||
|
|
||||||
|
Once this setting has been activated, a new information appears on the
|
||||||
|
vendor bill, defining whether the bill should be paid or not. There are
|
||||||
|
three possible values:
|
||||||
|
|
||||||
|
*Use case 1*: I have received the ordered products.
|
||||||
|
|
||||||
|
.. image:: media/3_way_matching02.png
|
||||||
|
:align: center
|
||||||
|
:width: 2.26042in
|
||||||
|
:height: 0.28125in
|
||||||
|
|
||||||
|
*Use case 2*: I have not received the ordered products.
|
||||||
|
|
||||||
|
.. image:: media/3_way_matching03.png
|
||||||
|
:align: center
|
||||||
|
:width: 2.03125in
|
||||||
|
:height: 0.26042in
|
||||||
|
|
||||||
|
*Use case 3*: the quantities do not match across the Purchase Order,
|
||||||
|
Vendor Bill and Receipt.
|
||||||
|
|
||||||
|
.. image:: media/3_way_matching04.png
|
||||||
|
:align: center
|
||||||
|
:width: 1.92708in
|
||||||
|
:height: 0.34375in
|
||||||
|
|
||||||
|
.. tip::
|
||||||
|
The status is defined automatically by Odoo. However, if you want
|
||||||
|
to define this status manually, you can tick the box *Force Status* and
|
||||||
|
then you will be able to set manually whether the vendor bill should be
|
||||||
|
paid or not.
|
||||||
|
|
||||||
|
.. image:: media/3_way_matching05.png
|
||||||
|
:align: center
|
||||||
|
:width: 1.92708in
|
||||||
|
:height: 0.34375in
|
BIN
purchase/purchases/rfq/media/3_way_matching01.png
Normal file
BIN
purchase/purchases/rfq/media/3_way_matching01.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 4.9 KiB |
BIN
purchase/purchases/rfq/media/3_way_matching02.png
Normal file
BIN
purchase/purchases/rfq/media/3_way_matching02.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 1.5 KiB |
BIN
purchase/purchases/rfq/media/3_way_matching03.png
Normal file
BIN
purchase/purchases/rfq/media/3_way_matching03.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 1.4 KiB |
BIN
purchase/purchases/rfq/media/3_way_matching04.png
Normal file
BIN
purchase/purchases/rfq/media/3_way_matching04.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 1.7 KiB |
BIN
purchase/purchases/rfq/media/3_way_matching05.png
Normal file
BIN
purchase/purchases/rfq/media/3_way_matching05.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 1.3 KiB |
Loading…
Reference in New Issue
Block a user