Case Study 03

Managing a Multi-Company Group with ERPNext

AMHZ Group needed a connected ERP environment for group management while giving each business the workflows and controls required to operate its own way.

One ERP foundation. Different workflows for every business.

Conceptual representation · not a system screenshot
  1. Multi-company group AMHZ Group
  2. Group Administration Accounting · HR · Procurement · Executive Office
  3. AMH Contracting Business Workflows
  4. Import & Export Business Workflows
  5. One foundation ERPNext
The Business

A group, not a single business.

AMHZ Group operates across different businesses, each with its own operational requirements. The ERP needed to provide centralized management without forcing every company into the same workflow.

Client
AMHZ Group
Platform
ERPNext
Scope
Group Administration · Accounting · HR · Procurement · Workflows · Attendance
Engagement
ERP Implementation · Customization · Workflow Design · Attendance Integration · Training
Locations
  • Egypt
  • Saudi Arabia

Group Administration

Accounting, HR, procurement and management follow-up.

AMH Contracting

Business-specific operational workflows and approvals.

Import & Export

Different operational processes and approval requirements.

The Approach

ERPNext configured around the way the group works.

Instead of forcing every process into the same pattern, ERPNext was configured around the group's management structure and each company's operational requirements.

01

Group Administration

  • Accounting
  • HR
  • Procurement
  • Management
02

Business Operations

  • Contracting
  • Import & Export
03

People & Attendance

  • Employees
  • Biometric Attendance
  • Work Locations
04

Approvals & Workflows

  • Requests
  • Review
  • Approval
  • Execution
The Challenge

Different businesses. One management structure.

The challenge was not simply putting multiple companies into an ERP. Each business had to follow the process that matched the way it actually worked, while management retained a centralized view.

01

Group Administration

Central management, accounting, HR and procurement.

02

Different Workflows

Each business follows its own operational path.

03

Approval Controls

Requests move through defined approval stages.

04

Distributed Workforce

Attendance needs to work across employees and different work locations.

Group level

A central ERP foundation for group operations.

Group-level functions were organized inside one ERP environment, giving management a common operational foundation while allowing individual companies to follow their own processes.

Organized in one ERP environment

  • Accounting
  • HR
  • Procurement
  • Executive Office
  • Business Operations
  • Attendance
Business-Specific Workflows

The ERP adapted to each business.

The same ERP foundation supported different operational workflows for the group's businesses.

Business

AMH Contracting

  • Business-specific workflow
  • Operational requests
  • Approval stages
  • Management follow-up
  • Employee / site operations
Business

Import & Export

  • Business-specific workflow
  • Operational requests
  • Approval stages
  • Management follow-up
  • Process tracking
Workflow Automation

Every request follows the right approval path.

Requests are routed through defined stages based on the business process, so the right people review and approve each step before the process moves forward.

The general path · the number of approval levels depends on the process

  1. 1

    Request

    A request is raised for the process that needs it.

  2. 2

    Review

    The responsible people review the request.

  3. 3

    Approval

    The request is approved at the defined stage.

  4. 4

    Next Approval

    Further approval where the process requires it.

  5. 5

    Execution

    The approved request is carried out.

  6. 6

    Recorded

    The outcome is recorded in ERPNext.

Examples

Leave request
  1. Employee
  2. Review
  3. Approval
  4. Recorded
Procurement
  1. Request
  2. Review
  3. Approval chain
  4. Purchase process
Business operation
  1. Request
  2. Business review
  3. Management approval
  4. Execution
HR & Attendance

Attendance connected to the workforce.

Employee attendance was connected to the ERP environment through biometric devices, bringing attendance records into the same operational system used to manage employees.

  1. Person Employee
  2. Device Biometric device
  3. Platform ERPNext
  4. Record Attendance record
  5. Used by HR

Attendance data becomes part of the employee's operational record instead of remaining isolated from the ERP.

Location-based attendance

Attendance controlled by location.

Employees working at different sites can be assigned to their relevant work location, allowing attendance to be controlled according to the location defined for them.

Conceptual · location control mechanism, not a map of AMHZ locations
  1. Employee
  2. Assigned work location
  3. Attendance
  4. Location check
  5. Accepted
HR processes

HR processes with defined approval paths.

  • Leave Requests
  • Employee Requests
  • Approval Workflow
  • HR Follow-up
  1. Request
  2. Approval workflow
  3. HR follow-up
Procurement

Procurement with controlled approvals.

  1. Purchase request
  2. Review
  3. Approval
  4. Procurement process
Architecture

One system. Multiple operational layers.

AMHZ Group

Group Administration

Accounting · HR · Procurement

AMHZ Group

Business Operations

Contracting · Import & Export

Carried by ERPNext

People & Attendance

Employees and attendance records

One foundation

ERPNext

Group administration and business operations run on the same ERP foundation.

Implementation

Implementation included the people behind the system.

The project was not only about configuring ERPNext. The implementation included preparing the workflows, configuring the system, integrating attendance, and training the teams that would use it.

  1. 1

    Configure

    ERPNext configured around the group's processes.

  2. 2

    Train

    Teams trained on the workflows and system usage.

  3. 3

    Adapt

    Processes adjusted according to operational requirements.

The Result

What changed.

01

Centralized Operations

Group-level processes organized within one ERP environment.

02

Defined Approvals

Requests follow structured approval workflows.

03

Business-Specific Processes

Each company operates through workflows adapted to its needs.

04

Connected Workforce

Attendance and employee operations are connected to the ERP.

05

Trained Teams

Users were trained on the configured workflows and system.

ERP should fit the business — not the other way around.

AMHZ Group needed ERPNext to support different businesses, management layers, employees and operational workflows without losing control.