Approval workflows in BYTE: one engine, the right signers, the right limits
Some documents need a second pair of eyes. BYTE routes each one to the people your policy names, by amount and by department, and applies the same rules to journals, orders, bills, payments and leave, so you set them once and they hold across the modules.
Last updated: 17 November 2026
What it covers
- One approval engine for many kinds of document, with the same steps, signers and waiting list.
- Thresholds set for each scenario, such as the amount above which an order needs approval.
- A limit for each person: above their own limit, a document moves to the next step.
- A step that nobody can sign is refused when the document is submitted.
- The maker never signs their own document, and one person signs one step.
- A changed document is approved again when its scenario requires it.
- Routing by department: the head of the document's department signs when the scenario asks for it.
- A waiting list that gathers, in one place, the documents waiting for you across all scenarios.
- Leave, overtime and expense claims follow the same engine, with the department head as a step.
- Journals and recurring journals, purchase orders, bills and payments route through the same engine.
How it works
- Set the scenarios your policy needs: which documents, the limit for each person, and the steps.
- A document within the limits goes ahead. A larger one routes to the next step.
- Each signer sees the document in their waiting list, and signs it or rejects it.
- A changed document is approved again when its scenario says so.
A worked example
A purchase order for JOD 3,200.00 goes through two steps, because the order scenario requires approval above JOD 2,000.00. The names and amounts are examples.
| Step | Signer | Status |
|---|---|---|
| Submitted | The buyer (maker) | Done |
| Step 1 | Branch manager, up to JOD 5,000.00 | Signed |
| Step 2 | Finance manager | Waiting |
| Released | After the last step | Not yet |
Until the finance manager signs, the order stays waiting, and it is not released to the supplier. The finance manager finds it in their waiting list.
At a glance
Built means the feature is in BYTE's current build. BYTE is coming soon, so ask us for the status of anything you need.
| Area | What BYTE does | Status |
|---|---|---|
| One engine | Journals, orders, bills, payments, leave, overtime and expense claims | Built |
| Thresholds | Set per scenario, so a document needs approval above its amount | Built |
| Limits per person | Above a signer's own limit, the document moves to the next step | Built |
| Signers | A step with no possible signer is refused at submit | Built |
| Separation of duties | The maker never signs; one person signs one step | Built |
| Changes | Approval again follows the scenario's rule | Built |
| Department head | A step can route to the head of the document's department | Built |
| Waiting for me | One list across all scenarios | Built |
Ask us before you decide
- Ask which documents need a second signature, and above which amounts.
- Ask who should sign for each department, and who may sign above a set amount.
- Ask whether a change to a signed document should go back for approval.
Questions about approval workflows in BYTE
What is an approval workflow?
A set of steps a document must pass before it is released. Each step names who may sign, and the document waits until they do.
Which documents does it cover?
Journals and recurring journals, purchase orders, bills and payments, and leave, overtime and expense claims.
Can a signer approve above their own limit?
A signer's own limit is their ceiling. A document above it moves to the next step, so the right person signs.
Can the person who made a document sign it?
Never. The maker, and the person a payment is for, do not sign their own document, and one person signs one step.
What happens if a signer leaves the company?
For leave and overtime requests, a waiting request is re-routed when the people it needs change, such as a signer who leaves.
Does a change reopen approval?
It depends on the scenario. Each scenario decides whether a changed document is approved again, and the rule is applied in one place.