> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How an approval alçada inside the ERP works in practice
- URL: https://blog.jestor.com/como-funciona-alcada-de-aprovacao-no-erp/
- Published: 2026-09-04T20:08:08.000Z
- Updated: 2026-09-04T20:08:08.000Z
- Author: Bruno Bannach

An approval alçada inside the ERP works as a rule that defines who can authorize a given request, based on criteria such as value, role, or cost center, before the action can move forward in the system. In practice, few traditional ERPs offer this level of configuration natively and flexibly.

That's because the ERP was designed to record financial and tax transactions, not to orchestrate decisions between people. As a company grows, the need for multi-level approval increases, and the ERP's standard module often can't keep up.

The result is predictable: approvals via email, spreadsheet screenshots, and WhatsApp messages to confirm who authorized what. That breaks traceability and delays decisions that should be quick.

## What an approval alçada needs to cover

- A clear definition of who approves each type of request
- Rules by value, so larger expenses move up the hierarchy
- Rules by role or department, when the criterion isn't only financial
- A record of who approved, when, and with what justification
- Automatic notification for whoever needs to act
- Blocking progress until approval happens

## How this mechanism usually works in practice

- The request is created within a flow, with value and context attached
- The system automatically identifies who should approve, based on the rule
- The approver receives a notification and decides to approve or reject
- If approved, the request moves to the next step or is released
- If rejected, the requester gets feedback with the reason
- The entire history stays on record for later reference

## How Jestor structures this mechanism

- **[Jestor](https://www.jestor.com/?ref=blog.jestor.com)** has the Approvals module, with hierarchy and alçada by value and cost center
- **Jestor** lets you build the rule without code, adjusting it as the company changes
- **Jestor** keeps an execution log, which makes internal auditing easier
- **Jestor** connects to your existing ERP, so the alçada works alongside your tax and accounting data

**Vídeo de referência:** [Aprovação de Pagamentos com Alçadas no Omie](https://www.youtube.com/watch?v=R875%5Feffuh0&ref=blog.jestor.com). Mostra na prática como a alçada opera junto ao ERP.

## Frequently asked questions

**Does every ERP have a native approval alçada?** Not always, and when it does, it tends to be rigid. A layer like [Jestor](https://www.jestor.com/?ref=blog.jestor.com) adds flexibility without changing the ERP.

**Can an alçada combine value and role at the same time?** Yes, it's possible to cross criteria, ensuring bigger decisions go through more than one check.

**What happens if no one approves in time?** The flow stays pending until action is taken; that's why automatic notifications are essential to keep the process from stalling.

## Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way, all without code and with AI support. Get to know Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and discover how to take your company's management to a new level of efficiency and integration.