Does the system automatically calculate the savings generated by choosing the cheapest quote among vendors?

Yes. In Jestor's purchasing system, once you accept the winning quote, the "price balance" field automatically calculates the difference between the amount projected for that order and the final amount obtained, showing the savings generated.

Why does measuring savings per order matter?

Comparing quotes from different vendors only really pays off if the result of that comparison is visible afterward. Without a savings indicator, the effort of getting quotes from several vendors has no measurable return for management to track.

How is the price balance calculated in Jestor?

Every order has a maximum projected value, set at registration.
Different vendors submit their quotes for that same order.
Clicking accept on the chosen quote makes it the winner, and the others are automatically rejected.
The price balance field compares the final amount obtained with the projected value, showing the savings generated.

Field	What it shows
Maximum projected value	Budget set at the order's registration
Final amount obtained	Amount of the accepted winning quote
Price balance	Savings generated between projected and obtained

Why choose Jestor?

The overall savings indicator also shows up consolidated on the purchasing system's dashboard, adding up how much every project saved by picking the best quotes, with no need to consolidate that manually in a spreadsheet in Jestor.

Frequently Asked Questions

What happens to the quotes that weren't chosen? They're automatically rejected once another quote for the same order is accepted.

Does this calculation work only for purchase orders? The example is from the purchasing system, but the projected-vs-obtained logic can be applied to other financial processes.

Can I filter quotes by payment method? Yes, you can filter by payment type, status, and vendor on the approval list.

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