Skip to main content

Approval Workflows Overview

What are Approval Workflows?​

Control and automate approval processes for transactions across your organization. Configure multi-level approval hierarchies based on transaction value and department, ensuring proper authorization before documents are processed or payments are released.


Who Uses This?​

System Administrators

Set up and maintain approval rules across all departments and workflows

Finance Heads

Define financial approval limits and multi-level authorization thresholds

Department Heads

Configure department-specific approval chains and value-based routing

Business Owners

Establish governance policies and approval controls across the organization


Key Features​

Workflow Configuration​

Value-based routing automatically assigns approvers based on transaction amount brackets

Department-specific rules allow different approval chains for different functional areas

Multi-level hierarchy supports sequential approval flows from L1 to L3 roles

Control & Flexibility​

No approval option for low-value transactions to streamline operations

Unlimited value ranges per workflow to match your authorization matrix

Instant activation - workflows take effect immediately after configuration


How It Works​

Typical Configuration Flow

Select workflow type - Choose the document type requiring approval (Purchase Order, Sales Order, Bill, etc.)

Define value brackets - Set start and end amounts for different approval levels

Assign approvers - Configure single or multi-level approval chains using department roles

Activate workflow - Rules apply immediately to all new transactions matching the criteria


Available Workflows​

Workflow TypeApplied ToConfiguration Type
Purchase OrderAll purchase orders to suppliersValue + Department based
Purchase RequestInternal material requisitionsValue + Department based
Sales OrderCustomer orders before invoicingValue + Department based
BillSupplier bills before paymentValue + Department based
Bill of MaterialBOM creation and modificationsDepartment based only
ItemNew item master creationDepartment based only
SupplierNew supplier master creationDepartment based only
Goods Receipt NoteIncoming material acceptanceValue + Department based
Purchase ReturnReturns to suppliersValue + Department based
Sales ReturnReturns from customersValue + Department based
ExpenseBusiness expense claimsValue + Department based

Workflow Logic​

Value-Based Workflows​

For transactions with monetary values (Purchase Orders, Bills, Sales Orders):

Configuration Options:

  • Set multiple value brackets with different approval chains
  • Example: ₹0-10,000 (No Approval), ₹10,001-100,000 (L1-Admin), ₹100,001+ (L1-Admin → L2-Purchase → L3-Finance)
  • No upper limit on final bracket - use very high values like 10,000,000,000

How System Routes:

  • System checks transaction total amount
  • Matches amount to configured value bracket
  • Routes to first approver in the chain
  • After approval, routes to next level if configured
  • Document proceeds only after all approvals completed

Department-Based Workflows​

For master data (Items, Suppliers, BOM):

Configuration Options:

  • Single approval chain per department
  • No value brackets (applies to all records)
  • Example: All BOM approvals go through Admin department's L1 role

How System Routes:

  • System checks department of user creating the record
  • Routes to configured approval chain for that department
  • Sequential approval if multi-level configured

No Approval Required​

When to Use:

  • Low-value transactions below approval threshold
  • Trusted departments with full authorization
  • Streamlined processes for routine operations

How to Configure:

  • Set value bracket with "No Approval Required" option checked
  • No approvers assigned for this bracket
  • Documents auto-approved and proceed immediately

Getting Started​

TaskGuideTime Required
Add New WorkflowHow to Add Guide10 minutes
Edit Existing WorkflowHow to Edit Guide5 minutes
View Workflow DetailsHow to View Guide2 minutes
Understand Field DefinitionsField Reference5 minutes


Quick Tips​

Best Practices

Start with simple single-level approvals and add complexity only when needed for control

Use "No Approval Required" for low-value transactions to avoid approval bottlenecks and speed up operations

Document your approval matrix outside the system for quick reference during configuration and audit reviews


Need help? Contact support at support@bizconnekt.com