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.
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.
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.
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.
A document can need the branch manager under AED 50,000 and the owner above it. Each level can need one approver or several.
The person who raised a document does not clear their own credit hold. It is a setting, and it starts switched on.
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.
The document is saved and checked against the matrix. If nothing matches, it posts exactly as before.
If a rule trips, the screen names the approvers and the level, and says the document is safely raised.
It appears in their approval inbox and in their notification bell — they are not relying on someone remembering to chase them.
Approved, and it posts. Rejected, and it goes back with the reason; amending it raises a fresh request.
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.
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.
Picked, Packed, Loaded, Delivered — whatever your operation calls them, on whichever documents you choose.
Say which state can follow which, who may make the move, and whether a note is required.
The current state sits beside the posting status on every screen, so nobody has to ask where an order is.
Every move records who, when, from what and why. The history cannot be edited after the fact.
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.
Open the public demo, install the Windows trial, or talk to the Zeyto team about your exact workflow, branches, users and reporting needs.
Explore the hosted ERP without installing anything. Use the public demo login below.
Demo data refreshes nightly to keep the sample company clean.
Run Zeyto in your preferred deployment: cloud, private cloud, on-premise, local server, desktop shell, browser access and mobile app.
Send your industry, branch count, users, devices and reporting needs. We route you to sales, support or partner onboarding.
Open the live demo, set an approval rule against a value you actually use, and watch an invoice stop at it.