Skip to content

Commit d9626a2

Browse files
committed
[IMP] Purchase: update control policy doc
1 parent ba512f1 commit d9626a2

File tree

5 files changed

+7
-76
lines changed

5 files changed

+7
-76
lines changed
Lines changed: 7 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -1,69 +1,24 @@
1-
=====================
2-
Bill control policies
3-
=====================
1+
==============
2+
3-way matching
3+
==============
44

55
.. _purchase/manage_deals/control-bills:
66

77
.. |PO| replace:: :abbr:`PO (Purchase Order)`
88
.. |POs| replace:: :abbr:`POs (Purchase Orders)`
99

10-
In Odoo's *Purchase* app, the *bill control* policy determines the quantities billed by vendors on
11-
every purchase order (PO), for either ordered or received quantities.
12-
13-
The policy selected in the *Purchase* app settings acts as the default value, and is applied to any
14-
new product created.
15-
16-
Configuration
17-
=============
18-
19-
To configure the *bill control* policy, navigate to :menuselection:`Purchase app --> Configuration
20-
--> Settings`, and scroll down to the :guilabel:`Invoicing` section. Under :guilabel:`Bill Control`,
21-
select either :guilabel:`Ordered quantities` or :guilabel:`Received quantities`. Then, click
22-
:guilabel:`Save`.
23-
24-
.. image:: control_bills/control-bills-selected-policy.png
25-
:align: center
26-
:alt: Selected bill control policy in Purchase app settings.
27-
28-
- :guilabel:`Ordered quantities`: creates a vendor bill as soon as a |PO| is confirmed. The products
29-
and quantities in the |PO| are used to generate a draft bill.
30-
- :guilabel:`Received quantities`: a bill is created only *after* part of the total order has been
31-
received. The products and quantities received are used to generate a draft bill. An error message
32-
appears if creation of a vendor bill is attempted without receiving anything.
33-
34-
.. image:: control_bills/control-bills-error-message-popup.png
35-
:align: center
36-
:alt: Bill control policy draft bill error message.
37-
38-
.. note::
39-
If a specific product should use a different control policy than selected in the *Purchase* app
40-
settings, the :guilabel:`Bill Control` policy for that product can be changed from its product
41-
form.
42-
43-
To do that, navigate to :menuselection:`Purchase app --> Products --> Products`, and select a
44-
product. From the product form, click the :guilabel:`Purchase` tab. Under the :guilabel:`Vendor
45-
Bills` section, modify the selection in the :guilabel:`Control Policy` field.
46-
47-
3-way matching
48-
==============
49-
50-
The *3-way matching* feature ensures vendor bills are only paid once some (or all) of the products
51-
included in the |PO| have been received.
10+
In Odoo's **Purchase** app the *3-way matching* feature ensures vendor bills are only paid once
11+
some, or all, of the products included in the |PO| have been received.
5212

5313
To activate *3-way matching*, navigate to :menuselection:`Purchase app --> Configuration -->
5414
Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, tick the checkbox for
5515
:guilabel:`3-way matching` to enable the feature, and click :guilabel:`Save`.
5616

5717
.. image:: control_bills/control-bills-three-way-matching.png
58-
:align: center
5918
:alt: Enabled 3-way matching feature in Purchase app settings.
6019

61-
.. important::
62-
The :guilabel:`3-way matching` feature **only** works with the :guilabel:`Bill Control` policy
63-
set to :guilabel:`Received quantities`.
64-
6520
Pay vendor bills with 3-way matching
66-
------------------------------------
21+
====================================
6722

6823
When *3-way matching* is enabled, vendor bills display a :guilabel:`Should Be Paid` field under the
6924
:guilabel:`Other Info` tab. When a new vendor bill is created, the field is set to :guilabel:`Yes`,
@@ -78,18 +33,15 @@ Paid` field.
7833

7934
.. important::
8035
The |PO| selected from the list **must not** be billed yet, or an :guilabel:`Invalid Operation`
81-
pop-up window appears. This occurs for |POs| with a :guilabel:`Received quantities` policy, and a
82-
:guilabel:`Fully Billed` :guilabel:`Billing Status`.
36+
pop-up window appears.
8337

8438
.. image:: control_bills/control-bills-invalid-operation.png
85-
:align: center
8639
:alt: Invalid Operation pop-up window for billed Purchase Order.
8740

8841
Click the drop-down menu next to :guilabel:`Should Be Paid` to view the available options:
8942
:guilabel:`Yes`, :guilabel:`No`, and :guilabel:`Exception`.
9043

9144
.. image:: control_bills/control-bills-should-be-paid.png
92-
:align: center
9345
:alt: Should Be Paid field status on draft vendor bill.
9446

9547
.. note::
@@ -131,28 +83,7 @@ Orders --> Purchase Orders`, and select a |PO| to view.
13183
Click the :guilabel:`Other Information` tab, and locate the :guilabel:`Billing Status` field.
13284

13385
.. image:: control_bills/control-bills-billing-status.png
134-
:align: center
13586
:alt: Billing status field on a purchase order form.
13687

137-
The table below details the different values the :guilabel:`Billing Status` field could read, and
138-
when they are displayed, depending on the *Bill Control* policy used.
139-
140-
.. list-table::
141-
:header-rows: 1
142-
:stub-columns: 1
143-
144-
* - Billing Status
145-
- On received quantities
146-
- On ordered quantities
147-
* - Nothing to Bill
148-
- PO confirmed; no products received
149-
- *Not applicable*
150-
* - Waiting Bills
151-
- All/some products received; bill not created
152-
- PO confirmed
153-
* - Fully Billed
154-
- All/some products received; draft bill created
155-
- Draft bill created
156-
15788
.. seealso::
15889
:doc:`manage`
-15.1 KB
Loading
-9.21 KB
Loading

0 commit comments

Comments
 (0)