Home/ Approvals & workflow

Approvals that match how your business actually authorises spend

Most growing businesses run approvals by WhatsApp and memory. Zeyto puts the rule in the system: who may approve what, above which value, with a named deputy for when they travel.

Approval matrix

One rule table, evaluated in priority order

Rules are checked in the order you set and the first match wins, so a general policy and a specific exception can live side by side without fighting.

Condition on what matters

Match on document total, customer, supplier, item group, branch, margin or document type. A rule that trips sends the document for approval instead of posting it.

Levels, not a single gate

A document can need the branch manager under AED 50,000 and the owner above it. Each level can need one approver or several.

Self-approval blocked by default

The person who raised a document does not clear their own credit hold. It is a setting, and it starts switched on.

A misconfigured rule stops the document

If a rule names a level that resolves to nobody, Zeyto refuses and says so. A control that silently switches itself off is worse than none.

What an operator sees

From submit to posted

1

Submit

The document is saved and checked against the matrix. If nothing matches, it posts exactly as before.

2

Held, not lost

If a rule trips, the screen names the approvers and the level, and says the document is safely raised.

3

The approver is told

It appears in their approval inbox and in their notification bell — they are not relying on someone remembering to chase them.

4

Decided

Approved, and it posts. Rejected, and it goes back with the reason; amending it raises a fresh request.

Delegation

Nothing stalls because someone is on leave

Name a deputy for a fixed period and, optionally, for one document type only. The approval matrix is unchanged — only who may act on it. Zeyto refuses a delegation to yourself, and refuses a date window that ends before it starts, because both look configured and silently never fire.

Zeyto applicationlocal
Workflow engine

Your own operational states, separate from the books

Approval is about authority. Workflow is about where the work has got to — and the two are deliberately kept apart, because 'SUBMITTED' and 'Packed' answer different questions.

States you define

Picked, Packed, Loaded, Delivered — whatever your operation calls them, on whichever documents you choose.

Transitions with rules

Say which state can follow which, who may make the move, and whether a note is required.

Visible on the document

The current state sits beside the posting status on every screen, so nobody has to ask where an order is.

An audit trail by default

Every move records who, when, from what and why. The history cannot be edited after the fact.

Why this matters when you grow past a handful of people

The moment more than one person can commit money, an ERP without approvals is a filing cabinet. This is the feature that lets an owner step back from signing every purchase order without losing control of what gets spent.

Next step

See the UAE ERP running before you decide

Open the public demo, install the Windows trial, or talk to the Zeyto team about your exact workflow, branches, users and reporting needs.

Open live demo
01

Try the live demo

Explore the hosted ERP without installing anything. Use the public demo login below.

User
admin
Password
demoAdmin123
POS PIN
1234

Demo data refreshes nightly to keep the sample company clean.

02

Install the trial

Run Zeyto in your preferred deployment: cloud, private cloud, on-premise, local server, desktop shell, browser access and mobile app.

03

Talk to Zeyto

Send your industry, branch count, users, devices and reporting needs. We route you to sales, support or partner onboarding.

FAQ

Straight answers

Can different branches have different approval limits?
Yes. A rule can be scoped to a branch, so a Dubai branch and an Abu Dhabi branch can carry different thresholds under the same policy.
What happens to a document while it waits for approval?
It is saved and marked as awaiting approval, and it is visible as such in the register. It has not posted to the ledgers, so it does not affect your accounts until it is cleared.
Can the person who raised a document approve it themselves?
Not unless you deliberately allow it. Self-approval is blocked by default, because the common case is that a spending limit exists precisely to stop that.
Does the point of sale wait for approvals?
No. POS is exempt in code, so a misconfigured rule can never put a till behind a manager's inbox and stop you serving a customer.

See it on your own numbers

Open the live demo, set an approval rule against a value you actually use, and watch an invoice stop at it.