Tutorial: how to create an invoice approval workflow

To create an invoice approval workflow in Jestor, configure a process with the stages: received, validation, approval, and posting. Jestor automatically extracts data from the invoice via OCR (AI-powered Image Reader), fills in the card fields, and triggers the corresponding approver based on the amount or cost center — without manual data entry.

Why companies are looking to automate this workflow

The invoice approval process is one of the most repetitive in finance. Receiving the invoice, checking the data, forwarding for approval, posting in the ERP — each step is manual and dependent on a sequence of people.

Any invoice stalled for more than a day already impacts cash flow and accounting close.

What makes the invoice process slow today

Invoices received via email with no organization or tracking
Manual verification of data such as tax ID, amount, and period
Informal approval via WhatsApp with no recorded history
ERP posting done hours or days after approval
No visibility into how many invoices are awaiting approval

How the workflow works in Jestor

Invoice arrives via form, integrated email, or direct upload to the card
AI-powered OCR automatically extracts: vendor, amount, date, tax ID
Card created with pre-filled data and stage set to "Awaiting Approval"
Approver automatically notified via WhatsApp or email
After approval, automation posts the accounts payable in Omie or Conta Azul
Invoice and receipt remain linked to the card for future auditing

Why Jestor solves this

AI Image Reader for automatic data extraction from documents
Complete approval workflow with thresholds by amount and cost center
Native integration with Omie and Conta Azul for posting without intermediaries
Auditable history of each invoice with receipt and approval dates

FAQ

Can Jestor automatically read the data from an invoice? Yes. The AI Image Reader extracts data from images and documents automatically.

Can I link the invoice to the ERP posting? Yes. The file stays in the card and the posting is generated automatically after approval. Learn more at jestor.com.

What if the vendor isn't registered in the ERP? For Conta Azul, Jestor creates it automatically. For Omie, this logic can be configured in the automation.

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support. Discover Jestor at jestor.com and find out how to take your company's management to a new level of efficiency and integration.

How to modernize financial processes without replacing your current ERP

Modernizing financial processes without replacing the ERP is possible when you add an automation and process layer on top of the existing system. Jestor integrates with the current ERP — whether Omie, Conta Azul, TOTVS, SAP, or Sankhya — and automates what happens before the posting: approvals, requests, notifications, and threshold controls.

How to build approval reports for the board with real-time data

Board-level approval reports are built in Jestor from data automatically generated in each workflow: approved requests, amounts by cost center, average approval time, and open pending items. This data is accessible in real time in the dashboard, without needing to export to a spreadsheet or wait for month-end close. Why

How to control spending limits by department with thresholds

Controlling spending limits by department means configuring automatic rules that prevent approvals above each area's budget — or that escalate the approval to a higher level when the limit is close. In Jestor, this is done through thresholds linked to cost centers, with real-time visibility into what has been

How to support finance in multi-branch companies

In multi-branch companies, the finance challenge is consolidating requests from multiple units, applying the correct thresholds for each branch, and ensuring that all entries reach the ERP in an organized manner. Jestor allows you to create a single approval workflow that works for all branches, with different rules per unit