MULTI-COMPANY OPERATIONS

Run every company in its own right.
Run the group with one clear view.

TEZ ERP keeps legal entities, books, GST registrations, branches, departments, stock, users and approvals distinct where they must be—and connected where management needs control.

Each company operates within its own financial and operational context. Group leadership sees performance, exposure, inventory, commitments and exceptions across the organisation without waiting for separate reports.

Show Us Your Group Structure Explore Multi-Company Capabilities ↓
MULTI-COMPANY MULTI-BRANCH MULTI-GSTIN GROUP REPORTING RBAC APPROVALS
THE REAL CHALLENGE

The challenge is not creating another company.
It is keeping control as the group becomes more complex.

A growing business group may have:

Every company needs independence. But management cannot afford isolated data, duplicated masters, inconsistent reports and fifteen different versions of the truth.

TEZ creates one governed operating environment in which every transaction retains its correct ownership while authorised management can see the larger group position.

Separate where accountability requires it.

Connected where management needs it.

ONE SYSTEM. THREE LEVELS OF TRUTH.

Multi-company operations require more than consolidation.

Every legal entity retains its own:

  • Books of accounts
  • Transactions
  • Customers and vendors
  • GST information
  • Cash and bank accounts
  • Receivables and payables
  • Inventory ownership
  • Voucher numbering
  • Financial reports
  • Statutory responsibility

A transaction entered for one company is posted to that company's books.

Within the company, every transaction can carry its relevant operating context:

  • Branch
  • Plant
  • Warehouse
  • Department
  • Region
  • Cost centre
  • User
  • Manager
  • Stock location

This tells management not only which company owns the transaction, but also where it originated and who is responsible for it.

Authorised leadership can review companies together for management visibility across:

  • Sales
  • Purchases
  • Expenses
  • Profitability
  • Cash and bank
  • Receivables
  • Payables
  • Stock
  • Orders
  • Approvals
  • Exceptions

The organisation can move from the group number to the company, branch, department and source transaction behind it.

THE OPERATING HIERARCHY

Define ownership before defining reports.

GROUP → COMPANY / LEGAL ENTITY → BRANCH / PLANT / LOCATION → DEPARTMENT → WAREHOUSE / STOCK AREA → USER & ROLE → TRANSACTION

These levels are not interchangeable.

Company

Which legal entity owns the transaction?

Branch

At which operating location did it occur?

Department

Which team is responsible for it?

Stock Location

Where is the material physically or operationally held?

User & Role

Who can create, review, approve or report on it?

TEZ maps these dimensions into the transaction so management does not have to reconstruct them later.

LOCAL EXECUTION. CENTRAL CONTROL.

A branch should be able to work without becoming a data island.

Local teams can enter transactions directly within their permitted company, branch and department. Head Office receives the information as part of the same operating environment. This means:

Local Teams Can

  • Create permitted transactions
  • Work with applicable customers and vendors
  • View authorised stock
  • Raise indents
  • Process orders
  • Record receipts and expenses
  • Attach supporting documents
  • Review their pending work

Company Management Can

  • Monitor all branches within the company
  • Review company-level stock and exposure
  • Approve relevant transactions
  • Control books and reporting
  • Analyse branch and department performance
  • Investigate exceptions

Group Leadership Can

  • Compare companies
  • Review consolidated management information
  • Monitor group receivables and payables
  • Understand stock distributed across the group
  • Identify pending approvals
  • Examine company and branch performance
  • Move from a summary to the originating transaction

Data is captured where the activity happens. Control remains where authority belongs.

DIFFERENT TEAMS. DIFFERENT WORKING VIEWS.

One ERP should not mean one screen for everybody.

Group CFO

Reviews consolidated and company-wise financial position, working capital, receivables, payables, cash, bank, stock value and profitability.

Financial Controller

Reviews books, approvals, reconciliation, voucher history, locked periods and exceptions across permitted entities.

Company Finance Team

Works with the transactions, books, statutory reports and banking activity belonging to the relevant legal entity.

Branch Manager

Monitors branch sales, purchases, collections, expenses, stock, orders, indents and pending approvals.

Department Head

Reviews the activities, transactions and approvals belonging to the department.

Procurement Team

Reviews group stock, branch requirements, pending indents, purchase orders, GRNs and vendor commitments.

Warehouse Team

Works with inward stock, indents, stock transfers, goods in transit, physical inventory and stock variances.

Sales Team

Views permitted customers, orders and stock information without receiving access to sensitive group financial information.

System Administrator

Controls company, branch, department, module and transaction access through users, roles and privileges.

The ERP remains common. The working context changes according to responsibility.

GROUP-WIDE STOCK VISIBILITY

Know what the group owns—and which company or location holds it.

Stock may be distributed across:

TEZ allows authorised users to review stock at the appropriate level.

Company Stock

Stock owned or maintained by the selected company.

Branch or Warehouse Stock

Stock physically or operationally available at the selected location.

Department Stock

Stock assigned to a particular department or internal stock area.

Consolidated Stock

The combined stock position across the companies or locations available to the user.

Goods in Transit

Material issued from one location but not yet received at the destination.

This distinction helps management answer: Do we need to purchase this item?

or Does another company, branch or warehouse already hold it?

BOOK STOCK VERSUS ACTUAL STOCK

Group stock is only reliable when system quantity and physical quantity can be compared.

Book Stock

The quantity TEZ computes from recorded inward, outward, production, transfer, return and adjustment transactions.

Actual Stock

The quantity physically counted or scanned at the company, branch, warehouse or department.

Variance

The difference between the book quantity and the physical count.

TEZ Physical Inventory helps teams record stock for the relevant company, branch and department and compare it with stock computed by the ERP.

Variances can identify:

Management sees the group stock position without losing the location responsible for a discrepancy.

MOVE STOCK ACROSS THE GROUP WITHOUT LOSING THE TRAIL

Internal movement still requires accountability.

Branches and departments can raise indents when they require material. The responsible team can then determine whether the requirement should be fulfilled through:

Where stock is available, a transfer can be created against the indent. The system retains the movement context:

Source company or branch → Destination branch → Source department → Destination department → Item and quantity → Batch or serial number → Indent reference → Dispatch information → Transit status → Receipt or acceptance → Supporting documents

The issuing location remains accountable for dispatch. The receiving location remains accountable for receipt.

Group management retains visibility over the complete movement.

CENTRAL PROCUREMENT ACROSS MULTIPLE COMPANIES AND BRANCHES

Purchase after understanding the group requirement.

A central procurement team may need to consider:

TEZ brings this operating information together so procurement can determine whether to:

This helps reduce unnecessary purchasing without removing local accountability.

APPROVALS & ROLE-BASED ACCESS

Different companies and departments may require different authorities.

TEZ can require transactions created by selected users to be reviewed by their reporting managers or authorised senior team.

Approvals can be viewed using company, branch, department, user, voucher, amount and date filters.

Depending on the configured workflow, an unapproved transaction can be prevented from moving to the next stage. Examples include restricting:

  • Printing or emailing an unapproved voucher
  • Invoicing an unapproved sales order
  • Creating a challan from an unapproved order
  • Creating a purchase order from an unapproved sales order
  • Creating a work order from an unapproved order
  • Creating a GRN against an unapproved purchase order
  • Making payment against an unapproved purchase
  • Editing an approved voucher

Approval is not merely a status. It determines whether the process can continue.

Where the group requires multi-stage, value-based or exception-based approvals, the workflow can be configured or customised around the approved authority matrix.

Access should match responsibility—not designation alone. TEZ allows the organisation to define reusable roles and assign applicable privileges. A user's access can be controlled according to:

  • Company
  • Branch
  • Department
  • Module
  • Transaction type
  • Master
  • Report
  • Approval authority
  • Create, edit, delete, print or export permission

For example:

Branch Sales Executive

Can create sales orders and view permitted stock for the assigned branch. Cannot access group financial statements or another company's banking information.

Company Accountant

Can work with accounting transactions and reports for the assigned company. Cannot alter group-level security controls.

Group Controller

Can review multiple companies, pending approvals, financial reports, voucher history and period controls.

Warehouse User

Can work with indents, inward stock, transfers and physical inventory for the assigned location. Cannot access unrelated financial or commercial information.

Roles can be reused as the group adds users, helping maintain consistent access control at scale.

GROUP REPORTING

15 companies should not require 15 reporting exercises.
Start with the group. Move to the source.

Authorised users can review information for:

Applicable reporting can cover:

The information path should remain:

GROUP SUMMARY → COMPANY → BRANCH → DEPARTMENT → VOUCHER → UNDERLYING TRANSACTION

A group report should not become another spreadsheet that nobody can explain.

CONSOLIDATED MANAGEMENT VISIBILITY

Compare companies without confusing their books.

TEZ can provide management views across configured companies while preserving the underlying entity-level transaction. This helps leadership compare:

Formal statutory consolidation may additionally require configured treatment for intercompany eliminations, group adjustments, currency translation and other accounting policies. These requirements are mapped separately with the finance team.

Management visibility can be immediate. Statutory consolidation must remain policy-correct.

COMMON STANDARDS WITHOUT FORCING IDENTICAL OPERATIONS

Connected does not have to mean identical.

Different companies may have different:

  • Products
  • Customers
  • Vendors
  • GST registrations
  • Voucher numbering
  • Approval authorities
  • Departments
  • Warehouses
  • Reporting requirements
  • Operating processes

Common controls may include:

  • Master naming standards
  • Item classification
  • Reporting structures
  • User roles
  • Approval principles
  • Document requirements
  • Period controls
  • Audit requirements

TEZ allows the group to standardise what should be common while retaining entity-specific applicability where required.

Company-specific differences remain within the appropriate entity context.

CASE STUDY

VK / Vinay Electricals

Sister concerns operating through TEZ ERP.

15+ Branches
400+ Users

VK Electricals and Vinay Electricals operate through a distributed organisation involving sales branches, stock locations, manufacturing operations and multiple functional teams.

  • Separate company and branch responsibility
  • Large-scale user access
  • Branch stock visibility
  • Indents and material requirements
  • Stock transfers
  • Central and local procurement
  • Sales-order execution
  • Manufacturing coordination
  • Department-wise activities
  • Approvals
  • Management reporting

Different users work within the company, branch, department and function relevant to them. Management retains wider visibility across the operating structure.

A selling branch such as Kerala may receive an order for 500 units while holding 200 units locally.

The group must determine:

  • What the customer ordered
  • What the branch already holds
  • What quantity is actually short
  • Whether another location can fulfil the shortage
  • Whether the Daman manufacturing operation must produce it
  • Whether an intercompany commercial document is required
  • What material must be procured
  • Where the finished stock must ultimately be transferred

This is not simply an inventory question or a production question. It is a multi-company operating question.

The workflow must connect customer demand, branch stock, intercompany responsibility, production planning, procurement, stock movement and final fulfilment without losing the originating reference.

TEZ provides the operating foundation, and customer-specific workflows can be extended around this foundation where the group's process requires it.

TEZ can support a substantial multi-branch and multi-user organisation without turning every company or branch into a disconnected installation.

The growth and operational achievement belong to VK/Vinay Electricals.

TEZ's role is to support the visibility, traceability and control required to operate at that scale.

ADD A COMPANY WITHOUT ADDING ANOTHER SILO

Expansion should follow an established control model.

When a new company or location is added, the implementation should define:

The new company begins within the group's governance structure instead of developing an isolated way of working.

HOW WE DESIGN MULTI-COMPANY OPERATIONS

We begin with ownership—not software menus.

Step 1

Map the Legal Structure

Identify companies, sister concerns, GST registrations and statutory responsibility.

Step 2

Map the Operating Structure

Identify branches, plants, warehouses, departments, regions and cost centres.

Step 3

Define What Is Common

Determine which masters, policies, classifications and reports should be standard across the group.

Step 4

Define What Must Remain Separate

Identify entity-specific books, registrations, users, approvals, numbering and reporting.

Step 5

Map Intercompany Activity

Document how orders, purchases, material, services and payments move between entities.

Step 6

Define the Authority Matrix

Identify who creates, reviews, approves, modifies and reports on each transaction type.

Step 7

Design Group Reporting

Begin with the decisions management must make, then work backwards to the transaction data required.

This is how a multi-company ERP becomes an operating system rather than a collection of company databases.

OUR APPROACH

Standard where possible.
Configured where necessary.
Customised where it creates control.

TEZ provides the core structure for:

We configure the structure around your companies, users, responsibilities, reports and approval rules.

Where your group has a distinctive intercompany or cross-functional process, TEZ can be customised around the approved workflow.

Big enough to handle complex requirements. Focused enough to give every client individual attention.

TEZ ERP FOR MULTI-COMPANY OPERATIONS

Every company retains its identity.
Every team knows its responsibility.
Management sees the group clearly.

Your group structure Your list of companies and GST registrations Your branch and warehouse map Your approval matrix Your user-role structure Your intercompany processes Your current management reports One workflow that your present system cannot handle properly

We will show you how to structure it in TEZ.

Request a Multi-Company Operating Blueprint Book a Group Workflow Demo