Skip to Content
Menu
This question has been flagged
2 Replies
73 Views

Vendor Bill can nomore be created by the purhcase app,

this for me is an important regression and move from a lean approach to a silos approach.

the purchase office is the responsible with relation with supplier.

It interacts with the supplier in handling all the aspect. Including price, quantity and payment

if the draft vendor bill is created by the buyer, it can reflect all those interactions.

when the real bill arrives, typically to accounting, the accounting can match it with the draft.

if the vendor bill is created by accounting then we retuns to have accounting people asking to the buyer explanation on differences.

Another point is that with exception of very small organization the vendor bill are sent to the accounting office or are left to logistic and not sent to buyer. So, the upload vendor bill button is not where it is needed.

there si any way to restore the create vendor bill button in purhcase order?

Avatar
Discard
Best Answer

Hi,


You’ve highlighted what feels like a regression in Odoo’s workflow: in recent versions, vendor bills can no longer be created directly from the Purchase app. Traditionally, buyers—who manage the supplier relationship, prices, and quantities—could draft the vendor bill themselves. This allowed accounting to later validate the bill against what was agreed with the supplier, reducing back-and-forth.


Now, with vendor bills created only by the accounting team, it shifts responsibility away from the buyers and creates inefficiency. Accounting staff may have to chase buyers to resolve discrepancies, which undermines the lean, end-to-end approach where purchase officers managed the whole supplier process.


You also point out a practical issue: in most organizations, vendor bills are received directly by the accounting office (or sometimes logistics), not by buyers. Yet the “Upload Vendor Bill” function is located where the buyer doesn’t typically work. This creates friction, as the functionality isn’t aligned with the real-life flow of documents between departments.


In short: the change moves Odoo from a lean, integrated workflow to a more siloed approach, where purchase and accounting are less connected, creating unnecessary inefficiencies.


Hope it helps


Avatar
Discard
Author

Thanks to highlight properly.

I strongly suggestvto make pressure on ODOO to review this responsability shift.

I will suggest my partner not to move to 18.3 or later

Related Posts Replies Views Activity
1
Sep 25
211
1
Jul 25
1754
2
May 25
2606
2
Mar 25
1848
0
Dec 22
2153