How does Jestor automatically define who approves a payment request based on the cost center?

In Jestor's payment approval app, the cost center chosen on the request is what defines the approval authority: each cost center has a linked owner, who receives and approves the request before it's posted to Omie. Jestor connects natively to Omie, letting approval workflows and ERP integrations run without manual rework.

Why is the cost center the key to the approval authority?

Instead of manually defining who approves each payment, Jestor uses the cost center — like "IT" or "Marketing" — which already has a registered owner. That guarantees the right person gets notified automatically, without depending on someone remembering to forward the request manually.

How does this cost-center-based approval flow work?

A new payment request is created with a title, amount, company, and cost center.
Once the cost center is chosen, Jestor automatically identifies who's responsible for approving it.
The request enters an approval queue, visible to whoever holds that authority.
Once approved on the Kanban, the payment is automatically posted as accounts payable in Omie.

Field	Role in the approval authority
Cost center	Automatically defines who's responsible for approval
Company	Matches the specific account in Omie, if there's more than one
Approval Kanban	Where the request gets approved or rejected

Why choose Jestor?

Once approved, Jestor posts the record directly to Omie in an integrated way, cutting out the manual step of typing accounts payable after the approval happens.

Frequently Asked Questions

Can a cost center have more than one owner? The cost center's owner is whoever receives the request to approve in that flow.

What happens if the company has more than one Omie account? It's possible to bring the different Omie accounts as an option within the request form.

Does approval happen automatically or does it need a manual action? A manual action from the owner is required to approve; only then does the posting to Omie happen.

Reference video

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.

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