> ## 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 to Build an Approval Layer Over a Legacy ERP
- URL: https://blog.jestor.com/approval-layer-over-legacy-erp/
- Published: 2026-09-03T20:55:42.000Z
- Updated: 2026-09-03T20:55:42.000Z
- Author: Bruno Bannach

Building an approval layer over a legacy ERP means creating a flexible decision and threshold workflow outside the tax and accounting system, one that still sends the already-approved entry into the ERP, without requiring a switch of the main tool.

Many companies keep a legacy ERP because it already handles the tax, accounting, and fiscal side well. The problem shows up when the team tries to use that same system for operational approvals: the ERP tends to be too rigid to keep up with changes in thresholds, cost centers, or hierarchy.

Switching ERPs just to fix that problem is expensive and risky. The more common alternative among COOs and operations directors is adding an operational layer on top, one that talks to the existing ERP without replacing it.

## Signs that a legacy ERP doesn't cover approvals

- Fixed thresholds in the system, hard to adjust without opening an IT ticket
- Approvals that end up happening by email, outside the ERP itself
- No visibility into requests stuck waiting for a decision
- Difficulty orchestrating approvals across multiple branches or tax IDs
- Operational processes treated as an exception inside a system built for tax purposes

## How an approval layer on top of the ERP works

- The approval flow is built outside the ERP, with configurable threshold rules
- Each approval can factor in amount, role, cost center, or a combination of the three
- Once approved, the entry automatically flows to the legacy ERP
- The ERP remains responsible for the tax, accounting, and fiscal side
- The approval layer can be adjusted without depending on updates to the core system

## Why Jestor works well as that layer

- **Jestor** is described as an extension of the ERP, complementing what's already in place rather than replacing it
- **Jestor** connects natively to Omie and Conta Azul, among other systems, via an open API
- No-code automations let you adjust thresholds quickly, without depending on IT
- Companies like Rumo and Locaweb use **Jestor** to organize processes the ERP doesn't cover

## Frequently asked questions

**What is an approval layer over a legacy ERP?** It's a configurable decision flow outside the ERP, like the one [Jestor](https://www.jestor.com/?ref=blog.jestor.com) offers.

**Does this layer replace the ERP?** No, it organizes the approval process and sends the already-decided entry to the ERP.

**Do you need to migrate ERP data to use this layer?** Not necessarily, native integration usually avoids a full data migration.

Building an approval layer over a legacy ERP is a way to gain operational flexibility without risking a switch of the tax system that already works.

## 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.

**Reference video:** [O seu ERP não é o Problema](https://www.youtube.com/watch?v=lXqExscXvyc&ref=blog.jestor.com). Explains why the real problem is usually the lack of a flexible operational layer, not the ERP itself.