BYTE · Controls · Approvals Coming soon

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

Purchase order PO-318Approval chain, PO-318Purchase order, JOD 3,200.00Waiting for the finance managerSignApproval stepsSubmitted by the buyerBranch manager signedFinance manager
Illustration of an example approval chain: a purchase order has passed its first two steps, and the last step is waiting for the finance manager. The names and steps are examples, not a screenshot.

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

  1. Set the scenarios your policy needs: which documents, the limit for each person, and the steps.
  2. A document within the limits goes ahead. A larger one routes to the next step.
  3. Each signer sees the document in their waiting list, and signs it or rejects it.
  4. 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.

StepSignerStatus
SubmittedThe buyer (maker)Done
Step 1Branch manager, up to JOD 5,000.00Signed
Step 2Finance managerWaiting
ReleasedAfter the last stepNot 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.

AreaWhat BYTE doesStatus
One engineJournals, orders, bills, payments, leave, overtime and expense claimsBuilt
ThresholdsSet per scenario, so a document needs approval above its amountBuilt
Limits per personAbove a signer's own limit, the document moves to the next stepBuilt
SignersA step with no possible signer is refused at submitBuilt
Separation of dutiesThe maker never signs; one person signs one stepBuilt
ChangesApproval again follows the scenario's ruleBuilt
Department headA step can route to the head of the document's departmentBuilt
Waiting for meOne list across all scenariosBuilt

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.

Be first to try BYTE.

Send us a short note about your business and the modules you care about. We will tell you when early access opens.

Talk to us See all of BYTE