How to Build a Purchase Approval Workflow Integrated With Your ERP

A purchase approval workflow integrated with the ERP starts with a structured request, goes through an authorization tier, and only then generates the posting in the ERP. In Jestor, this flow is built with Pedidos de Compra (Purchase Orders) natively connected to Omie, without spreadsheets or a middleman.

Why does the purchasing process tend to get stuck at approval?

Many companies treat purchasing as haggling for a discount the moment a need shows up. Without a structured process, the company loses traceability over what was spent, with whom, and when, and can't analyze its own purchasing data later.

What companies are trying to solve?

Purchase requests scattered across email or WhatsApp, with no centralized history
No automatic alert when a request has been stuck for too long
Rework from manually posting every approved purchase in the ERP
Difficulty comparing quotes before approving

How does the Jestor–ERP purchasing integration work?

The request is created in Jestor, goes through the right tier, and once approved is sent automatically to the ERP Expansion connected to Omie.

Stage	Where it happens	Result
Purchase request	Form in Jestor	Card created with vendor, amount, and cost center
Tier-based approval	Purchase Orders Kanban	Card only advances once the responsible owner approves
Posting	Native integration with Omie	Record sent automatically, with no manual data entry

Why choose Jestor?

Native integration with Omie, with no Zapier, Make, or other middleman needed
Dynamic authorization tiers by cost center and amount, with no reconfiguration for every exception
Full history of every request, including who approved it and when

Reference video

Check out more practical tutorials on the Jestor YouTube channel.

Frequently Asked Questions

Does Jestor replace the ERP in the purchasing process?

No, Jestor structures the approval and sends the posting to the ERP, which stays responsible for the tax side.

Can different cost centers have different tiers?

Yes, the tier can vary by cost center, category, or request amount.

Can it be used with more than one Omie account?

Yes, Jestor orchestrates multiple Omie accounts with no extra cost per CNPJ. Learn more at jestor.com.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize