On this page
What are workflows and approvals in a company?
A workflow is the path a document follows before it becomes effective: who creates it, who reviews it and who approves it. Approvals are the sign-off decisions along that path. Every company has unwritten paths: the manager approves a large expense, finance approves purchase orders, the owner signs above a certain figure. The software turns them into written rules that run every time.
In Anzma it is the approvals and workflows module. It has no documents of its own; it serves the documents of other modules: sales, purchasing, expenses, stock and accounting. You write the rule in one place and it applies where documents are created.
The module belongs to Anzma’s operations management software line and is available on every plan. When you switch it on, the old per-module “needs approval” settings become rules that keep following their setting until you edit them.
Which documents go through approvals?
Nine kinds of document can pass through approval rules, and each appears in the editor only when its module is on. Other types, such as quotations, are available to automation without approval.
| Document | Module | A condition you can use |
|---|---|---|
| Sales invoice | Sales | Invoice total or balance |
| Purchase order | Purchasing | Order total |
| Purchase bill | Purchasing | Total or balance |
| Expense | Expenses | Total and expense category |
| Stock issue | Stock movements | Reason and warehouse |
| Journal entry | Accounting | Total debit |
| Depreciation run | Fixed assets | Total depreciation |
| Instalment reschedule or write-off request | Instalments | Request amount |
| Commission run | Sales targets | Total commissions |
How do you build an approval matrix by amount?
An approval matrix is a table that says, for each document type and amount band, who approves. In Anzma you turn it into rules: each has a name, a document type, conditions (amount at or above a limit, or a certain branch), a priority and steps. The matching rule is applied to the document, and if none matches the document goes through without extra approval.
The example is illustrative, with made-up numbers, for a trading company; it is a template you can copy and adjust to your structure.
To see it in motion: a purchasing clerk submits a purchase order for 120,000, so the third rule applies. It goes first to the finance director, who approves after checking the budget, then to the general manager, who approves the next day. The order becomes approved and can be sent to the supplier, and the log holds four events with dates and names. Had the general manager rejected it, the order would have gone back to draft with their comment.
| Document | Amount band | First approver | Second approver |
|---|---|---|---|
| Purchase order | Up to 20,000 | Purchasing manager | — |
| Purchase order | 20,000 to 100,000 | Purchasing manager | Finance director |
| Purchase order | Over 100,000 | Finance director | General manager |
| Expense | Over 5,000 | Line manager | Finance director |
| Stock issue | Reason “damaged” | Warehouse manager | — |
| Journal entry | Over 50,000 | Chief accountant | Finance director |
How do approval steps and approvers work?
A rule has from one to ten steps, taken in order. Each step has a list of approvers, any one of whom may decide. When one approves, the document moves to the next step, and after the last step it becomes approved and continues its path in its own module. An approver is defined in five ways: the requester’s line manager, their department manager, everyone holding a role, a specific user, or everyone with a given permission.
The requester is left out of the approver list as long as someone else exists, so nobody approves what they requested. If the requester holds the approval permission and you want their document to pass at once, turn on self-approval for that step, which mimics the old settings. If a step has no approver it is opened to those who manage approvals, and the owner can always decide.
- 1
Create the document
An employee creates a purchase order or expense and submits it for approval, and the system matches the rule conditions in priority order.
- 2
First step
The approval reaches the first step’s approvers, who are notified in the system and by email, and one of them approves or rejects with a comment.
- 3
Next steps
On approval the next step activates with its approvers, steps with nobody to approve are skipped, and every transition is logged with time and name.
- 4
The outcome
After the last step the document is approved and goes on. On rejection it returns to draft with the comment and the requester is notified.
What happens when a request is rejected, late or its approver is away?
On rejection a comment is mandatory, the document returns to draft, and the requester is notified in the system and by email. They edit and resubmit, and everything sits in the request log in time order.
Lateness has two routes. Escalation: if a step is not decided within the hours you set (48 by default, or a value specific to the step) its approvers are reminded and the people who manage approvals are notified. And SLA reminders: you can set a deadline on a given step, and one reminder goes out when it passes.
Absence is handled by delegation: an approver registers a delegate for a period and for the document types they choose, and requests go to the delegate. If the approver is on approved leave in HR, the leave delegate stands in, otherwise their line manager. Your company does not stall because somebody travelled.
What is the My approvals inbox?
My approvals is a single screen for each approver gathering what awaits their decision from every module: purchase orders, expenses, invoices and more. They open a request to see the document, its steps and earlier comments, and approve or reject from there. The requester has a tab for what they sent and its status, and the approvals manager has a tab for every request in the company.
The practical benefit is that an approver does not have to visit each module hunting for what is waiting, and a requester does not have to ask “did they approve?”, because they can see where their request is and why it is delayed.
What automation is available and how does it work?
An automation has three parts: a trigger, conditions and actions. The trigger is an event on a document: it is created, its status changes to one you choose, a given field changes, or a date on it is reached, such as an invoice’s due date (with an offset of days before or after). Conditions narrow the cases, for example amount above a limit. There are five action types.
The system makes sure each event runs only once, logs every run and the result of each action in the run log, and caps automations per hour to prevent flooding. No written code is ever executed; the actions are fixed types that you configure with forms.
- An in-app notification to a user, role, permission or the document’s creator.
- An email from a text template carrying document details, to its contact or an address you set.
- Changing a permitted text field on the document, such as notes or reference.
- Creating a task with an owner and due date linked to the document.
- Calling a web address with a payload signed by a secret you set.
How do tasks tied to documents work?
A task is a light work item with a title, an owner, a due date and a status, tied to a document so you open it in one click. You create tasks by hand or an automation creates them: an invoice not collected a week after its due date generates a task for the collector, and an accepted quotation generates a task to prepare the order. Open tasks show on the owner’s dashboard, and the tasks screen lets a manager sort by due date.
Tasks are not a substitute for project management software. They are a follow-up list tied to the document that created the need, so you do not copy information from the system into another tool.
How does approval over chat differ from approval inside the system?
Many companies today rely on a message in a chat app or a signature on paper. It works at small volume and fails when someone is away, a request is forgotten or numbers are edited after approval. Approval inside the system is tied to the document itself and to its version at the moment of approval.
| Aspect | Chat or paper | Approvals module |
|---|---|---|
| Knowing who approves | Depends on who remembers | A written rule by amount and document type |
| Following a request | Ask and wait | An inbox and a status on each request |
| An absent approver | The request stalls | Delegation or the absent person’s manager |
| Delay | No alert | Escalation and SLA reminders |
| Audit trail | Scattered across messages | A full timeline for each request |
| Rejection | A verbal reply | A mandatory comment and return to draft |
Which settings and permissions control approvals?
In the module settings you set the default escalation time in hours, a company-wide cap on automation runs per hour, and a secret for signing web calls. Inside a rule you can give each step its own escalation and SLA, disable a rule without deleting it, and order rules by priority.
Permissions are separate: viewing rules is distinct from creating, editing and deleting them, viewing automations, the run log and tasks each have a permission, and managing approvals is a permission for administrators who see every request and step in when no approver is available.
Who is approval workflow software for?
It suits any company whose owner needs assurance that what goes out was approved: supply companies with large purchasing, contractors with scattered project spending, real estate developers, and accounting and law firms where expenses tie to cases and clients. A small company usually needs only a rule or two.
Approvals do not replace permissions; they are a layer on top. See the guide to choosing an ERP to understand where approvals sit in a company’s system, or book an online meeting and we will build your approval matrix on the module’s screen.
Frequently asked questions
What is a workflow?
It is the path a document follows until it becomes effective: who creates it, who approves it and in what order. In Anzma it becomes multi-step approval rules on documents across modules, plus simple automation that runs actions when something happens to a document.
How do I set approval by document value?
Create a rule for the document type with a condition that the amount is at or above a limit, then add one or more steps with their approvers. Several rules with priorities can cover amount bands so large documents follow a longer path, as the matrix example shows.
Which documents go through approvals?
Sales invoices, purchase orders and bills, expenses, stock issues, journal entries, depreciation runs, instalment reschedule requests and commission runs. They appear when their modules are on. Employee requests follow their own cycle in HR requests.
What happens on rejection?
A comment is mandatory and the document returns to draft, and the requester is notified in the system and by email to edit and resubmit. The rejection is logged with time and the rejecter’s name, and earlier steps stay documented.
Does the approver get a notification?
Yes. When a request reaches their step they get an in-app notification and an email, reminders follow on escalation after the time you set, and an SLA reminder arrives if you set a deadline on the step. The system sends no automatic WhatsApp messages.
What automation is available?
A trigger (a document is created, or its status or a field changes, or a date is reached) with conditions, then five actions: notification, email, setting a permitted field, creating a task and calling a signed web address. Runs are logged and capped per hour, with no free-form code.
Can approval be delegated during leave?
Yes. An approver registers a delegate for a period and for chosen document types. If they are on approved leave in HR, their requests go to the leave delegate and otherwise to their line manager, so approvals do not stall.
How many steps can one rule have?
From one to ten steps taken in order, and each step can have up to ten approvers, any one of whom completes it. You can set escalation time and an SLA reminder per step, and self-approval for someone who holds the permission.
Part of the product line
operations management software
What your company sells besides finished goods, from appointments to rented units, work orders and production, becomes an invoice and an entry automatically in one system.
Rate this page
Did you find this useful? Your rating helps others.
No ratings yet.


