What Are Approval Thresholds and How to Set Them Up
What are approval thresholds? They are the limits that define who has the authority to approve a request (usually a payment or a purchase), based on amount, role, or cost center. In Jestor, these rules are built inside the Approvals app, with an approval hierarchy configured visually and with no code.
Small companies often operate without a formal threshold: the owner approves everything. The problem shows up when the business grows and that centralization becomes a bottleneck, or worse, a risk, once nobody knows anymore who should have approved what.
Setting a threshold isn't bureaucracy: it's what ensures the right payment goes through the right person, without slowing down operations or depending on someone's memory.
Why Companies Need Approval Thresholds
- Prevent a single person from holding every approval in the company
- Make sure high-value requests go through more than one owner
- Get traceability on who approved each request, and when
- Reduce the time between a request and a decision, without relying on email
- Adapt the approval hierarchy as the company grows, without rebuilding the process from scratch
How to Set Up an Approval Threshold in Jestor
- Define the request form fields: amount, category, cost center, and vendor
- Link each cost center (or role) to a person responsible for approving
- Set up the hierarchy: who approves first, and who steps in for higher amounts
- Build the approval queue as a Kanban, with all the data visible on the card
- Connect the approval to the ERP (Omie or Conta Azul) so the entry goes out automatically
| Threshold element | Question it answers | Where it's defined in Jestor |
|---|---|---|
| Cost center | Which department is the request from? | Field on the request form |
| Amount | Does it need more than one approver? | Threshold rule in Approvals |
| Approver's role | Who has the authority to decide? | Approval hierarchy configured in the app |
Why Jestor Solves This
- The Approvals app comes with hierarchy, amount-based thresholds, and cost centers ready to configure
- No code is required: the threshold is defined in the form and workflow, visually
- The ERP entry is automatic after approval, with no repeated manual data entry
- A Jestor dashboard shows pending, approved, and rejected requests by cost center, in real time
Frequently asked questions
What is an approval threshold? The limit that defines who can approve a request, based on amount, role, or cost center.
Does every company need approval thresholds? The more an operation grows, the more it needs this control formalized. See how at jestor.com.
Can an approval threshold change over time? Yes, in Jestor it can be reconfigured at any time, without depending on IT.
Is an approval threshold the same thing as an approval hierarchy? The threshold defines the decision limit; the hierarchy defines the order of who approves first.
Understanding what are approval thresholds is the first step to taking that control out of one person's head and putting it into a traceable workflow.
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 and discover how to take your company's management to a new level of efficiency and integration.