How to Add Approval Limits in Your ERP, Step by Step
Adding approval limits in your ERP is possible without writing any code: create a request form in Jestor that defines who approves each request before it's posted to the tax system. The entire process runs inside the Approvals app, natively integrated with the ERP.
The pain behind this search is a familiar one: payables posted straight to the ERP with no prior review, or approval limits that only exist in the approver's head. As the company grows, this becomes a financial risk.
Operations teams already using Omie or Conta Azul feel this gap mostly in accounts payable: the ERP posts entries well, but it doesn't decide who should approve them first.
What Companies Are Trying to Solve With This Workflow
- Payments posted to the ERP without going through a defined approver
- No standard format for the data sent for approval (each requester writes it differently)
- No record of who approved what, or when
- Difficulty knowing how many requests are pending approval
- Rework when an ERP entry comes out wrong due to a lack of review
Step by Step: Setting Up Approval Limits in the ERP
- Create a request form in Jestor with the same fields the ERP requires: amount, category, vendor, cost center, and due dates
- Set the cost center or the requester's role as the criterion that routes the request to the right approver: that's the approval limit
- Set up the approval queue: no request is posted to the ERP before it's approved
- Build the approval Kanban, where the approver sees the full card to make a decision
- Turn on the native integration with the ERP (Omie or Conta Azul) so approval automatically generates the entry
- Track everything on a dashboard showing pending, approved, and rejected requests by cost center
| Step | Where it happens in Jestor | Result |
|---|---|---|
| Request | Custom form | Standardized data, matching what the ERP requires |
| Setting the approval limit | Cost center / role in the form | The right approver is notified automatically |
| Approval queue | Approval Kanban | The request only moves forward with a recorded decision |
| Posting the entry | Native ERP integration | Accounts payable entry is created with no manual data entry |
Why Do This in Jestor
- Integration with Omie and Conta Azul is native, no Zapier, Make, or other middleman involved
- The approval workflow is set up without code, right in the request form
- Every approved request is posted to the ERP automatically, cutting down on rework and data-entry errors
- The Jestor dashboard shows, by cost center, how much has already been approved and what's still pending
Frequently asked questions
How long does it take to set up approval limits in the ERP? Connecting to Omie takes about 5 minutes; the form and approval queue are built without code.
Does an approved request need to be posted to the ERP manually? No. In Jestor, the entry is posted to the ERP automatically after approval; more at jestor.com.
Can I have different approval limits by branch or entity? Yes, Jestor works with multiple ERP accounts organized in a single dashboard, at no extra cost per entity.
Does Jestor handle bank reconciliation after posting? No. Jestor organizes the approval and sends the entry; bank reconciliation stays with the ERP.
Following these steps is the most direct way to put approval limits in your ERP in place without relying on a parallel spreadsheet.
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.