Skip to content
العربيةLet’s talk

Practical guide

Who can confirm an Odoo purchase order at the approval threshold?

Use three order totals and two accounts to check when an Odoo purchase needs manager approval, who can release it and how the team handles exceptions.

Lava Solutions · · 3 minute read

A calculator and green pencil beside an open squared notebook on a desk.
Illustrative stock photo. Photo: Cht Gsml / Unsplash.

A policy says a manager must review purchases from a certain amount. The awkward order is the one whose total lands exactly on that amount. Ask a buyer to confirm that order during the Odoo demonstration. Then ask a manager to find and approve it using their own account. Those two actions reveal both the comparison the system makes and the authority it gives each role.

Translate the policy into a decision a buyer can test

Choose one company, its working currency, an ordinary purchase user and a purchase manager. Write the approval amount, whether that amount is inclusive, and which total your written policy uses. Note any separate requirement for a second person to approve a manager’s own purchases. Use a test company or database, a test supplier and internal mailboxes throughout the exercise.

In standard Odoo 19 Purchase, two-step approval compares the order total with a company threshold. An ordinary purchase user can confirm an otherwise valid order below that threshold. At the threshold or above it, the order waits for approval. A user with purchase manager rights can approve directly. The standard check uses the order total including applicable taxes. Record the configured company and currency before comparing amounts.

Run three orders with an ordinary buyer account

Fictional example. A distributor sets a threshold of 1,000 JOD in a test company whose currency is JOD. The amounts below are final order totals. Use three separate requests for quotation so the manager can examine each result by reference. Keep the vendor and product the same. Ask the buyer to confirm each request once and read the resulting state before anyone approves it.

  • 999 JOD. The request should become a purchase order on confirmation. Save its reference as the below-threshold case.
  • 1,000 JOD. The request should wait for approval. Record its reference and leave it pending for the manager.
  • 1,001 JOD. This request should also wait. Ask the buyer to show what they can do next using their usual permissions.

If the middle order goes through immediately, verify the account’s purchasing rights, the active company, the approval setting and the final order total. A demonstration performed wholly under a manager account cannot establish what an ordinary buyer can confirm.

Give the manager the pending order reference

Have the manager sign in separately, locate the 1,000 JOD request and compare the vendor, currency, lines and total with the recorded example. Ask them to approve that one request. Confirm that its status has advanced while the 1,001 JOD request still awaits action. Record who checked both states and how another manager would find the outstanding request during an absence.

Now have the manager create and confirm another above-threshold test order. Standard manager rights allow direct approval. If your policy requires a different person to authorise every manager’s purchase, record that as a separate requirement and ask for a demonstration of the proposed control. Agree who will review any change in permissions.

Repeat the case most likely to cause a dispute

If the company buys in another currency, choose one test order with a known date and ask the finance reviewer to reconstruct the comparison using the applicable rate and rounding. Odoo 19 converts the threshold into the order currency for this check. If the policy refers to the amount before tax, add a case where tax takes the total across the threshold. Record the difference between the written policy and the demonstrated behaviour.

Keep a one-page result with each order reference, user role, total, expected state, observed state and unresolved exception. For the subsequent stock and sales steps, use the trading-company purchase-to-margin guide. To review an approval workflow with Lava, share the roles and approval rules you want to test.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗