Branches

What Branches is for

Branches maintains the operating locations that belong to an AkshaERP Organization.

A Branch can represent a main office, sales location, Book House, edition center, regional office or another operating location used by the business.

Find and open a Branch

Open Access Management and choose Branches. Use search, sorting and paging to find the operating location.

Click the row or choose Open from the row action menu.

Create a Branch

Choose Create and enter Organization, Branch Code, Branch Name and Branch Type.

A new Branch starts as Active.

Branch Code

Use a short stable Branch Code. It can contain letters, numbers, underscore and dash.

Branch Code must be unique inside the selected Organization. The same Code can exist in another Organization when that is the approved business design.

Organization and Branch Type

Every Branch belongs to an Organization. An Active Branch requires an Active Organization.

Branch Type classifies the operating location. Configured examples can include Branch, Edition Center, Sales and MAIN.

Address, contact and legal information

Maintain Branch location, communication, legal and billing information when applicable.

• Address, City, State, Country and Postal Code
• Phone, Email and Website
• Legal Name and Invoice Display Name
• GSTIN, PAN, CIN and GST State Code
• Tax Registration Type
• Billing Contact, Billing Phone and Billing Email

Branch payment accounts

Branches can maintain payment details used by finance and customer-facing payment instructions.

• Bank
• UPI
• QR
• Cheque
• Payment Link
• Other supported payment details

Primary payment account

A Branch can maintain multiple payment accounts, but only one Active payment account should be marked Primary.

Bank setup requires appropriate bank/account details. UPI and QR setups use the approved UPI or QR information configured for the Branch.

Print settings

Branch print/output setup can include Invoice Display Name, Billing Contact, Billing Phone, Billing Email, Invoice Footer Note, Payment Instructions and Branch Time Zone.

The exact values used depend on the business document or report being produced.

Review Branch Usage

For an existing Branch, open Usage before restructuring or retiring the operating location.

• User assignments and Default User assignments
• Current Employees
• Stores and Active Stores
• Warehouses and Active Warehouses
• Sites and Active Sites
• Cost Centers and Active Cost Centers
• Payment Accounts and Active Payment Accounts
• Business Units using the Branch as Default Branch
• Active Attendance Policies
• Active Document Term Profiles

Activate and deactivate

Deactivate a Branch when it should no longer be available for new active business setup.

Activate returns a valid inactive Branch to service.

• Deactivation is blocked while User Branch assignments remain.
• Current Employee assignments can block deactivation.
• Active Stores, Warehouses, Sites or Cost Centers can block deactivation.
• Active Branch payment accounts can block deactivation.
• Active Business Unit defaults, Attendance Policies or Document Term Profiles can block deactivation.

Active choices and historical records

Inactive Branches stop appearing in normal Active Branch searches used for new setup.

Existing records that already reference an inactive Branch can continue to display the stored Branch identity.

Default Branch for a User

User Branch access maintains Default Branch per Organization.

A User can therefore have one default Branch in Organization A and another default Branch in Organization B. Within the same Organization, select only one default Branch for that User.

History

History shows Branch master activity such as Create, Update, Activate and Deactivate, including when the action happened, who performed it and a summary.

Save, Apply and Close

Recommended setup sequence

• Confirm the Organization exists.
• Search to make sure the Branch does not already exist.
• Confirm the final Branch Code.
• Choose the correct Organization and Branch Type.
• Enter Branch Name and general details.
• Maintain legal/contact information where required.
• Configure payment and print settings where required.
• Save or Apply.
• Configure Users, Stores, Warehouses, Sites and other Branch-scoped setup.
• Review Usage before any later lifecycle change.

Common mistakes

• Creating a near-duplicate Branch instead of reusing the existing operating location.
• Choosing the wrong Organization and expecting to move the Branch later.
• Using a temporary Branch Code.
• Assuming identical displayed Branch Names mean the same Branch without checking Code.
• Entering unverified bank, UPI or QR details.
• Marking more than one Active payment account as Primary.
• Trying to deactivate before active dependencies are resolved.
• Treating User Default Branch as global instead of per Organization.