Why default workflows rarely fit
Most ERP platforms ship with a generic approval workflow — a purchase order goes to one manager, an expense claim needs one sign-off. Real businesses rarely work that way: approval thresholds change by amount, different departments have different sign-off chains, and some requests need to skip a step entirely under specific conditions. Workflow configuration is where the system starts matching how decisions are actually made in your business.
What we configure
- Multi-level approval chains with amount-based or role-based routing
- Escalation rules — what happens if an approval sits untouched for too long
- Conditional routing — different paths depending on department, value or request type
- Task assignment and reassignment when staff are unavailable
- Notification rules tied to each stage of the workflow
Typical workflows we set up
Purchase order approvals with value-based routing, expense claim sign-off chains, leave request approvals tied to reporting structure, vendor onboarding approvals, and document review chains for contracts or compliance paperwork. Each is configured against your actual organisational structure, not a generic template.
Keeping workflows maintainable
We document every configured workflow so your team can make small adjustments themselves — changing an approver when someone leaves, adjusting a threshold — without needing to call us for every minor change. Bigger structural changes (adding a new approval stage) are usually still worth having us handle.
Engagement & pricing
Priced per workflow configured, based on how many approval levels and conditional rules are involved. Straightforward single-chain approvals are quicker to configure than multi-department workflows with several conditional branches.
Getting workflow configuration right the first time
The biggest risk in workflow configuration isn't technical — it's mapping an approval chain that looks right on paper but doesn't match how decisions actually get made under pressure. We validate configured workflows with the people who'll use them before calling the work done, not just with whoever signed off the original requirement document.
ERP platforms we work with
We're not tied to one platform — we implement and configure whichever fits your business, including:
Frequently asked questions
Yes — we document configured workflows so your admin team can make routine adjustments like changing an approver or threshold without needing us involved for every change.
That's normal — we map the actual exceptions during requirement gathering rather than assuming a standard chain, and configure conditional routing to handle them.
Workflow configuration can be done on an existing ERP system, whether we implemented it or not.
Workflow configuration focuses specifically on approval and routing logic inside your ERP. Business process automation is broader — it can include automation outside the ERP as well, such as notifications or data sync between systems.
Yes — conditional routing lets different departments or locations follow different approval paths within the same overall system, rather than forcing every branch onto one identical chain.
Talk to us about workflow configuration.
Free scoping call — we'll tell you what's actually needed for your setup, no obligation.