OdooWiki OCA HUB

OCA/tier-validation

OCA community repository with 14 Odoo modules confirmed in the OdooWiki catalogue (versions 19.0). Reviewed on 2026-11-03.

Open on GitHub

Confirmed modules per version

12.0
0 modules
13.0
0 modules
14.0
0 modules
15.0
0 modules
16.0
0 modules
17.0
0 modules
18.0
0 modules
19.0
14 modules
20.0
0 modules

Modules in the repository

  • account_move_tier_validation

    Adds an approval workflow to invoices, bills, credit notes and refunds: before an entry can be posted it may need to be reviewed and approved by one or more tiers of reviewers. Users also get new filters to find entries waiting for their review.

  • account_move_tier_validation_approver

    Lets you set a default approver on a vendor and automatically fills that person as the Responsible for Approval on vendor bills, with an option to make it mandatory before posting.

  • base_tier_validation

    Adds a configurable multi-step approval workflow to any Odoo document, so records must be reviewed and approved by chosen users or groups before they can move forward.

  • base_tier_validation_confirm_auth

    Adds an option on tier definitions so that approvers must re-enter their password (identity check) before approving, rejecting or commenting on a tier review.

  • base_tier_validation_correction

    Lets authorised users replace the reviewer of pending tier validation reviews on documents, either immediately or on a scheduled date, and revert the change later.

  • base_tier_validation_formula

    Lets you write Python formulas to decide when a tier approval is required and who must approve it, instead of only using fixed domains or user lists.

  • base_tier_validation_forward

    Adds a Forward option to tier approvals, letting an assigned reviewer pass the decision to another user instead of approving or rejecting.

  • base_tier_validation_server_action

    Extends tier validation so each approval step can automatically run a server action when it is approved or rejected, and can auto-approve itself when a condition is met.

  • hr_expense_tier_validation

    Adds a multi-level approval (tier validation) process to expense reports, so submitted expenses must be reviewed and validated by designated reviewers before they can be approved.

  • partner_tier_validation

    Adds an approval workflow to Contacts so that new or changed company contacts must be reviewed and approved before they can be used. Reviewers can find contacts waiting for their approval from a dedicated filter.

  • purchase_request_tier_validation

    Adds a multi-level approval workflow to Purchase Requests: requests must be reviewed and validated by assigned reviewers before they can be confirmed.

  • purchase_tier_validation

    Adds an approval workflow to purchase orders: orders can require one or more reviews before they can be confirmed, and reviewers see a dedicated filter for the orders waiting for them.

  • sale_tier_validation

    Adds an approval workflow to sales orders and quotations: orders can require one or more validation tiers before they can be confirmed, and printing can be blocked until approval.

  • stock_picking_tier_validation

    Adds an approval workflow to stock transfers: before a transfer can be validated (done), it may need to be reviewed and approved by one or more designated people.

Data imported from GitHub: every listed version is confirmed (branch, module directory and installable manifest checked on the review date). Active support and OCA certification are not assessed.