What Value-Based Approval Levels Can Be Configured for Payments Integrated With Omie

In Jestor, approval workflows for payments connected to Omie can be configured by value tier, defining who needs to approve each payment based on how much it represents.

How does the value-based tier work?

Instead of a single approver for all payments, the tier rule routes each request to the right approval level based on the amount — for example, smaller payments going straight through, and higher amounts requiring an additional approval from leadership.

What can be configured in an approval tier?

Configurable element	Description
Value ranges	Different thresholds defining when an extra approval is required
Approver hierarchy	Who approves at each range, possibly involving more than one level
Cost center	The tier can vary depending on the linked cost center
Direct integration	The approved payment stays synced with Omie with no manual entry

Why choose Jestor for approvals integrated with Omie?

Jestor connects its Approvals solution — with hierarchy, value tiers, and cost centers — directly to the native Omie integration, keeping financial control in place without requiring the team to leave the platform.

Can different approvers be set based on the payment amount?

Yes, Jestor lets you configure tiers by value range, routing each payment to the right approver.

Can the tier vary by cost center?

Yes, it's possible to combine value and cost center in defining the approval rules.

Is the approved payment automatically posted in Omie?

Yes, the native Omie integration keeps the approved payment synced, with no manual entry.

Video Tutorial: Step by Step

Check out more practical tutorials on Jestor's YouTube channel.

Get to know Jestor

With Jestor, tiered approvals and the Omie integration work together, keeping financial control in place without leaving the platform.

Get to know Jestor at jestor.com and see how to take your operation's efficiency to a new level.

How Do You Set a Different Homepage for Each Role as Soon as the User Logs In?

In Jestor, when editing a role, you can paste the link to a specific page (like a dashboard) into the homepage field, so that every user with that role lands directly there as soon as they log in. Why this improves the user experience Without this setting, everyone would land

What's the Access Difference Between a Member-Type User and a Builder-Type User?

In Jestor, a member-type user is meant for anyone who just uses already-configured processes, while a builder has access to create and edit tables, apps, automations, and the account's structure. Why separate these two access levels Not everyone on the team should be able to change

Why Does Grouping Tables and Apps for the Same Process Into the Same Folder Make Maintenance Easier?

In Jestor, grouping tables and applications for the same process into a single folder makes it quick to find everything related to a specific Kanban or flow, saving you from wasting time hunting for scattered pieces across the platform. Why folder organization avoids clutter Just like an unorganized computer desktop,

Can You Duplicate an Entire Application, With All Its Elements, Right From the Action Bar?

Yes. In Jestor, the action bar (opened with Ctrl+K or Cmd+K) lets you clone an entire application, with every element it contains, just by choosing the source app and giving the copy a new name. Why cloning from the action bar is faster Manually rebuilding an app from