Operion Journal
Purchasing approves on paper, a branch approves on WhatsApp, finance replies "approved" by email. When the auditor asks who approved, when and with what authority, the search begins. A unified workflow turns written policy into states, transitions, roles and a log.
What a workflow is
A definition of the states a document passes through, who may move it and under which conditions, with every transition logged. ERPNext workflows are configured without code: states, transitions, allowed roles, conditions such as amount or department, and which state finalises the document.
Signs you need one
- Approvals happen outside the system.
- Nobody knows where a document is stuck.
- Rules differ between branches without reason.
- Auditors struggle to prove approvals.
- People without authority approve.
From scattered approvals to a clear workflow
- Capture how approvals really happen today.
- Agree one policy per document type.
- Simplify: remove steps that prevent no real risk.
- Translate policy into states and transitions.
- Link permissions, notifications and reminders.
- Test, go live and monitor bottlenecks.
| From | Action | To | Allowed | Condition |
|---|---|---|---|---|
| Draft | Submit | Pending manager | Requester | - |
| Pending manager | Approve | Approved | Department manager | Below threshold |
| Pending manager | Approve | Pending finance | Department manager | Above threshold |
| Pending finance | Approve | Approved | CFO | - |
| Any pending | Reject | Rejected | Current role | Reason required |
Common workflows
- Purchase requests and orders by value.
- Leave via manager then HR; see HR system.
- Expenses and advances.
- Exceptional sales discounts; see urgent orders.
- New customers and credit limits.
- Manual journal entries.
Workflow, authorization rule or notification?
Use a workflow for multi-stage paths, authorization rules to require a role above a value or discount, notifications to inform without blocking, and permissions to prevent actions entirely. The right tool keeps the system simple.
Common mistakes
- Copying every old signature.
- Too many levels.
- No backup approver.
- Never reviewing thresholds.
See from problem to requirement, or request a demo.
Frequently asked questions
Does an ERPNext workflow need coding?
No, it is configured with states, transitions, roles and conditions.
Can the path vary by amount?
Yes, via transition conditions or authorization rules.
What if the approver is away?
Assign several users to the role or delegate temporarily per policy.
Is every approval logged?
Yes, with user and time.
