Multi-branch companies and groups

ERP for multi-branch companies and groups in Saudi Arabia

ArkanERP is built on how a company divides: the company, then its structural projects, then the cost centers that stand for its branches. Each branch has its warehouses, cash boxes, payment methods and prices, and an employee tied to a cost center sees and works only in it. One workspace holds several companies, each branch has its own e-invoicing setup, and management sees everything.

Challenges this business knows well

  • Branch staff who see everything

    In traditional programs a user sees the whole company's customers and stores, or is shut out of the screen entirely, with nothing in between.

  • Every branch with its own prices and boxes

    Prices, payment methods and cash boxes differ between branches, managed by hand in lists outside the system.

  • Entries no one reviews

    With many branches and accountants, vouchers post without anyone matching them, and mistakes surface only at closing.

  • Group companies in separate programs

    Each company sits in its own program or database, so the group's financial statements are put together by hand.

How ArkanERP solves them

  • Company, projects, cost centers

    Each company has structural projects, each project has cost centers, and warehouses and cash boxes are tied to cost centers. Financial statements and reports read per level or for the group.

    General accounting
  • Users kept to their branch

    A user tied to a cost center sees only its warehouses, customers and documents, and the cost center is filled and locked on their documents. An admin grants or blocks each screen and its operations per user.

    Permissions and control
  • Prices, payment methods and boxes per branch

    A price per warehouse, payment methods limited per cost center, and a cash box per branch showing its own balance and movement, even when boxes share one account.

    Cash boxes and banks
  • Review and posting by scope

    An approval scope per group of cost centers: an accounts manager matches, a reviewer approves, and a mismatch goes back to its creator with the reason. A creator never matches their own voucher, nor does the matcher review it.

    Review and posting
  • E-invoicing per branch

    Each seller branch can have its own address, identifiers and ZATCA invoicing unit, and the VAT and submission reports filter by branch.

    ZATCA e-invoicing
  • Communication between branches

    Chat between staff, groups, and voice and video calls inside the system, with late work escalated to management.

    Chat and calls

The systems this business uses

Common questions

Can I run more than one company in one subscription?

Yes. One workspace holds several companies, each with its chart of accounts, and each user is given the companies they work in.

Do branch staff see other branches' data?

No, once tied to their branch's cost center. They see only its warehouses, customers and documents, while general management sees every branch.

Can I block a user from one screen despite their role?

Yes. Screen access grants or blocks each screen and its operations (read, create, edit, approve) per user, on top of what their roles give.

Who approves documents in ArkanERP?

Users make, managers approve: user roles cannot submit or cancel, their manager does. Posted entries then go through matching and review by the branch's scope.

Do reports show each branch and the whole group?

Yes. Financial and stock reports filter by company, project, cost center and warehouse, or combine for the whole group.