Administration & Essentials
Muhasib ERP outcome-based user guide.
- Administration Concepts
- Understand Company, Location, Terminal, and Licence Identities
- Update the Active Company's Identity and Branding
- Add a Company Workspace
- Companies and Branding
- Update or Retire a Company Workspace
- Create a Location
- Configure Location Printing and SMS
- Update or Retire a Location
- Locations, Terminals, and Printers
- Register a Printer
- Resolve Muhasib Printing Setup Problems
- Register a Muhasib Terminal
- Update or Retire a Terminal
- Create and Activate a Fiscal Year
- Change the Active Fiscal Year
- Update or Retire a Fiscal Year
- Fiscal Years and Working Periods
- Users, Roles, and Permissions
- Maintain Contact Types
- Configure an SMS Gateway
- Create a System User
- Update, Disable, or Retire a System User
- Update Your User Profile and Password
- Create a User Role
- Grant and Revoke Muhasib Permissions
- Audit a User's Effective Access
- Global Application Settings
- Configure POS Behavior for a Company
- Configure Purchase and Inventory Behavior
- Configure Customer, Credit, Loyalty, and Party Rules
- Configure Receipt and Invoice Content
- Configure Transaction Numbering
- Configure Item Label Printing
- Configure Tax Integrations
- Configure E-Commerce and Offline POS Synchronization
- Configure Centralized Multi-Company Behavior
- Manage Global and Instance Settings
- Workstation and Instance Settings
- Configure This Workstation's POS Experience
- Configure the Quick Launcher
- Configure Diagnostic Logging Safely
- Numbering and Document Output
- Backup, Restore, and Day End
- Create and Verify a Manual Backup
- Restore a Muhasib Database Safely
- Configure Automatic Backups and Retention
- Complete Day-End Activity Safely
- User Activity and Troubleshooting
Administration Concepts
Understand company and system identities, update branding, and add a company workspace.
Understand Company, Location, Terminal, and Licence Identities
Understand Company, Location, Terminal, and Licence Identities
Overview
This guide will help you choose the correct Muhasib scope when configuring access, devices, transactions, printing, and licensing.
Transactions and reports can be scoped differently by company, location, terminal, user, and licence. A correct licence does not automatically grant role permission, and a terminal master record does not by itself prove licence activation.
Who can do this
You need access to No write permission is required to understand the model. Viewing each record depends on its module permission.
Before you start
Identify the connected database and active company shown in Back Office.
Where to find it
Use Licence Information, company selection, Essentials Setup, and User Management to inspect each identity. This concept article has no single write path.
Understand Company, Location, Terminal, and Licence Identities
Step 1: Confirm the connected database
Step 2: Confirm the active company before changing records
Step 3: Identify the location where work and inventory should be recorded
Step 4: Match the computer's application-terminal record to that location and printer
Step 5: Review Licence Information separately to confirm primary/additional-terminal status
Review Licence Information separately to confirm primary/more-terminal status.
Step 6: Check the user's assigned role, companies, and action permissions
Check your work
You can name the database, company, location, application terminal, licence-terminal type, and user role involved in the intended task.
If something goes wrong
- If the same word “terminal” appears in licensing and setup, check which identity the screen uses.
- If a company is missing, check role assignment and licence scope before creating another.
Related guides
- Select a Company Workspace
- Register a Muhasib Terminal
- Review and Maintain Muhasib Licence Access
- Audit a User's Effective Access
What to do next
Update the Active Company's Identity and Branding
How to Update the Active Company's Identity and Branding in Muhasib ERP
Overview
This guide will help you update the current company's identity, contact, currency display, and logo.
Muhasib updates the active company and reloads company settings. Existing transaction values should not be assumed to change, but reprinted documents may use current branding; check this in your Muhasib installation.
Who can do this
You need access to Company and Branding Settings.
Before you start
Switch to the correct company. Prepare approved legal/contact details and a company logo near the shown 270 x 100 size. Review currency changes with the financial administrator.
Where to find it
Back Office → Settings → Company and Branding Settings.
Update the Active Company's Identity and Branding
Step 1: Confirm the active company
Step 2: Review Company Name, Address 1/2, Phone 1/2, Email, and Website
Step 3: Review Currency Name, Code, Symbol, Symbol in Words, and Decimal Places
Step 4: Select or replace the logo when required
Step 5: Choose Update
Step 6: Confirm the update prompt
Step 7: Wait for the successful-update message
Check your work
Reopen the settings and preview an approved test receipt/invoice to confirm the intended identity and formatting.
If something goes wrong
Related guides
What to do next
Add a Company Workspace
How to Add a Company Workspace in Muhasib ERP
Overview
This guide will help you add another company record to the connected Muhasib database.
Muhasib creates the company and associates the super-administration role. Initial location, terminal, accounts, payment types, and other defaults are not clearly created by this form in this workflow and must be set up separately when absent.
Who can do this
You need access to Company and Company Add.
Before you start
Make sure a separate company is required, capacity is available, and the super-administration role exists. Prepare identity, contact, currency, registration/tax, and logo information.
Where to find it
Back Office → company/setup administration → Company Settings.
Add a Company Workspace
Step 1: Choose New Record
Step 2: Enter a unique Company Name
Step 3: Enter Address 1, Phone 1, and Email; add secondary contact
Enter Address 1, Phone 1, and Email; add secondary contact fields as needed.
Step 4: Enter Currency Code, Currency Name, Currency Symbol, Currency Symbol in
Enter Currency Code, Currency Name, Currency Symbol, Currency Symbol in Words, and Decimal Places.
Step 5: Enter Registration No., NTN, and STRN where applicable
Enter Registration No., NTN, and STRN where needed.
Step 6: Select the company logo if required
Step 7: Choose Save and wait for confirmation
Check your work
Find the company in Company Records and check its assignment through an authorized test role before switching into it.
If something goes wrong
- Use a unique company name.
- A missing super-administration role blocks creation; do not repair roles with direct SQL.
- If plan capacity is reached, resolve the entitlement rather than deleting another company.
Related guides
- Understand Company, Location, Terminal, and Licence Identities
- Update the Active Company's Identity and Branding
- Create a Location
- Create a User Role
What to do next
Companies and Branding
Maintain companies and locations, including branding, printing, SMS, and safe retirement.
Update or Retire a Company Workspace
How to Update or Retire a Company Workspace in Muhasib ERP
Overview
This guide will help you update an existing company or determine safely whether it can be retired.
Updates reload company settings. Source blocks deletion of the active company and checks dependencies before removing a company record, but the complete dependency and cascade behavior is not yet proven.
Who can do this
You need access to Company Update for changes; Company Delete plus explicit business approval for removal.
Before you start
Back up the database. Confirm record ID and name, switch away from the company being considered, and review users, transactions, locations, terminals, accounts, inventory, integrations, and reports.
Where to find it
Back Office → company/setup administration → Company Settings.
Update or Retire a Company Workspace
Step 1: Filter by ID or Company and select the exact record
Step 2: For an update, change only approved fields, choose Update, and confirm
Step 3: For retirement, first disable operational access through approved users/roles/integrations where
For retirement, first disable operational access through approved users/roles/integrations where supported.
Step 4: Attempt Delete only after explicit approval and dependency review
Step 5: Stop if Muhasib reports that the company is current or in use
Check your work
Reopen the company and validate reports, branding, role assignments, and switching behavior. For approved removal, compare and confirm all retained history in a cloned environment first.
If something goes wrong
- Never remove a company to solve a licence limit without business-data review.
- Switch to another company before attempting an approved removal.
- Treat any unexpected successful deletion in test as a critical finding.
Related guides
What to do next
Create a Location
How to Create a Location in Muhasib ERP
Overview
This guide will help you create a company location suitable for POS, storage, warehouse, kitchen, or another set up purpose.
Muhasib creates a location under the active company. It can then be assigned to terminals and used by inventory/POS workflows according to features and settings.
Who can do this
You need access to Location and Location Add. Printer or SMS quick-add also requires the corresponding master permission.
Before you start
Prepare a unique location code/name, purpose, contact/tax details, printer choice, storage/POS classification, and logo. Register the printer first when needed.
Where to find it
Back Office → Essentials Setup → Manage Locations.
Create a Location
Step 1: Choose New Record
Step 2: Enter Location Code and Short Description; add Long Description
Step 3: Set Warehouse/Storage and POS switches accurately
Step 4: Choose the Location Purpose
Step 5: Select a printer or No printing facility
Step 6: Select an SMS gateway when licensed and required
Step 7: Enter addresses, phones, email, website, registration number, NTN, and STRN
Enter addresses, phones, email, website, registration number, NTN, and STRN as needed.
Step 8: Select a logo if needed
Step 9: Choose Save
Check your work
Find the new record, reopen it, and confirm terminal assignment and stock/POS visibility using controlled data.
If something goes wrong
- If storage controls are absent, check inventory entitlement.
- If SMS is absent, check SMS feature and permission.
- Do not duplicate a location because a role cannot see it.
Related guides
- Register a Printer
- Configure Location Printing and SMS
- Register a Muhasib Terminal
- Update or Retire a Location
What to do next
Configure Location Printing and SMS
How to Configure Location Printing and SMS in Muhasib ERP
Overview
This guide will help you associate a location with an approved printer and optional SMS gateway.
The location references the selected printer and SMS gateway. Actual transaction output can also depend on terminal printer assignment, report type, receipt settings, permissions, and integration settings.
Who can do this
You need access to Location Update plus view access to Printer; SMS Settings and its licensed feature when SMS is used.
Before you start
Create and test the Muhasib printer record. Configure SMS only with non-production credentials and a sandbox/test recipient.
Where to find it
Back Office → Essentials Setup → Manage Locations.
Configure Location Printing and SMS
Step 1: Select the exact location
Step 2: Under Select Printer, choose the approved logical printer or No
Under Select Printer, choose the approved logical printer or No printing facility.
Step 3: Under SMS Gateway, choose the approved gateway when available
Step 4: Use a plus button only when authorized to create the
Step 5: Choose Update and confirm
Step 6: Reopen the location to confirm both associations
Check your work
Print a sanitized test document and send only an approved test SMS. Confirm the correct queue/gateway and record the result.
If something goes wrong
- If the printer is missing, check it is enabled and available to the Windows account.
- If SMS controls are hidden, check feature and permission before editing roles.
Related guides
- Register a Printer
- Resolve Muhasib Printing Setup Problems
- Configure an SMS Gateway
- Configure Receipt and Invoice Content
What to do next
Update or Retire a Location
How to Update or Retire a Location in Muhasib ERP
Overview
This guide will help you update a location or determine whether it can be retired without compromising inventory or history.
The deletion path checks dependencies and can remove related item-location rows in some conditions. This behavior is too consequential to use without clone-based tests and checking.
Who can do this
You need access to Location Update; Location Delete plus explicit business approval for removal.
Before you start
Back up the database and review terminals, item stock, transactions, registers, printers, SMS, users, and reports tied to the location.
Where to find it
Back Office → Essentials Setup → Manage Locations.
Update or Retire a Location
Step 1: Filter and select the exact location by ID/code/name
Step 2: For changes, edit approved fields, choose Update, and confirm
Step 3: Before retirement, move or close dependent terminals/registers and reconcile stock
Before retirement, move or close dependent terminals/registers and compare and confirm stock through supported inventory workflows.
Step 4: Choose Delete only after explicit approval
Step 5: Stop if Muhasib reports a dependency
Check your work
For updates, reopen the record and test assigned terminal/output. For approved retirement, compare and confirm stock, stock ledger, location reports, and historical transactions.
If something goes wrong
- Do not use deletion as an inventory-transfer mechanism.
- Resolve stock with supported adjustment/transfer workflows.
- If dependency text is unclear, preserve it and contact support.
Related guides
- Create a Location
- Register a Muhasib Terminal
- Transfer Stock Between Locations
- Create and Verify a Manual Backup
What to do next
Locations, Terminals, and Printers
Register and maintain printers and terminals, fix printing, and manage location-linked setup.
Register a Printer
Register a Printer
Overview
This guide will help you register an installed Windows printer for Muhasib receipts or standard documents.
Muhasib stores a logical printer record. Output still depends on location/terminal associations and document/label settings.
Who can do this
You need access to Printer and Printer Add.
Before you start
Install and test the printer in Windows under the account running Muhasib. Know whether it is a receipt or standard printer.
Where to find it
Back Office → Essentials Setup → Manage Printers.
Register a Printer
Step 1: Choose New Record
Step 2: Enter a clean, recognizable Printer Name and optional Description
Step 3: Under Select Printer, choose the installed Windows queue
Step 4: Select Receipt Printer or Standard Printer
Step 5: Turn Enabled on
Step 6: Choose Save
Step 7: Assign the logical printer to the required location and/or terminal
Check your work
Print a sanitized receipt or standard report to the intended device/PDF test sink.
If something goes wrong
- If a queue is absent, install it in Windows and reopen the form.
- If output uses the wrong layout, check printer type and receipt/label settings.
Related guides
- Configure Location Printing and SMS
- Register a Muhasib Terminal
- Resolve Muhasib Printing Setup Problems
- Configure Item Label Printing
What to do next
Resolve Muhasib Printing Setup Problems
How to Resolve Muhasib Printing Setup Problems in Muhasib ERP
Overview
This guide will help you isolate whether a printing failure comes from Windows, Muhasib printer registration, assignment, permissions, or document settings.
If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.
Correcting the relevant mapping allows Muhasib to send output to the intended queue. Renaming/removing a Windows printer can leave the stored logical mapping invalid.
Who can do this
You need access to The task's print permission; printer maintenance requires Printer access/update.
Before you start
Record the document type, company, location, terminal, logical printer, Windows queue, and whether other Windows applications can print.
Where to find it
Back Office → Essentials Setup → Manage Printers, Locations, and Terminals as needed.
Resolve Muhasib Printing Setup Problems
Step 1: Print a Windows test page under the Muhasib user account
Step 2: Confirm the Windows queue still has the same installed name
Step 3: Open Manage Printers and verify the logical record is enabled
Open Manage Printers and check the logical record is enabled and points to that queue.
Step 4: Confirm receipt-versus-standard printer type
Step 5: Verify the active location and terminal assignments
Step 6: Check the user's Print Reports permission where applicable
Check the user's Print Reports permission where needed.
Step 7: Review receipt or label dimensions/settings for the document type
Step 8: Retry with sanitized test output
Check your work
The correct content, paper size, orientation, margins, barcode, and destination are produced once without duplicate jobs.
If something goes wrong
- Do not repeatedly send jobs to an unknown queue.
- Use an approved PDF/test sink before testing physical stock or labels.
- Printer setup does not grant report access.
Related guides
- Register a Printer
- Configure Location Printing and SMS
- Configure Receipt and Invoice Content
- Configure Item Label Printing
What to do next
Register a Muhasib Terminal
Register a Muhasib Terminal
Overview
This guide will help you register a Windows computer in Muhasib and associate it with a location and printer.
Muhasib stores an application terminal linked to location and printer. This record participates in company/terminal checks and POS operations but may be distinct from WLM primary/more activation identity.
Who can do this
You need access to Terminal and Terminal Add. Location/printer quick-add requires those master permissions.
Before you start
Create the location and printer first. Record the Windows computer name exactly and check licence-terminal status separately.
Where to find it
Back Office → Essentials Setup → Manage Terminals.
Register a Muhasib Terminal
Step 1: Choose New Record
Step 2: Enter the System / Computer Name without a leading space
Step 3: Select the terminal's Location
Step 4: Select the terminal's Printer when applicable
Select the terminal's Printer when needed.
Step 5: Choose Save
Step 6: Restart or re-enter company context if the workflow requires registration
Restart or re-enter company context if the workflow requires registration to reload.
Check your work
Reopen the record and sign in/select the company from that computer. Confirm location and print behavior with test data.
If something goes wrong
- Use the actual Windows computer name expected by the application.
- If company selection loops, review both application registration and licence activation.
Related guides
- Create a Location
- Register a Printer
- Activate an Additional Muhasib Terminal
- Update or Retire a Terminal
What to do next
Update or Retire a Terminal
How to Update or Retire a Terminal in Muhasib ERP
Overview
This guide will help you update or retire an application-terminal record without disrupting an active working period.
Source blocks terminal deletion during an active working period and blocks deletion of the terminal currently in use. Application-record removal is not proven to deactivate the licence terminal.
Who can do this
You need access to Terminal Update; Terminal Delete plus explicit operational approval for removal.
Before you start
Where to find it
Back Office → Essentials Setup → Manage Terminals.
Update or Retire a Terminal
Step 1: Select the exact terminal by ID/computer name
Step 2: For an update, change the approved computer name, location, or
For an update, change the approved computer name, location, or printer and choose Update.
Step 3: For retirement, verify no working period is active
Step 4: Confirm you are not logged in from the terminal being removed
Step 5: Choose Delete only after explicit approval
Step 6: Handle licence deactivation separately through Licence Information when authorized
Check your work
Confirm other terminals can enter the company, printing/location assignments remain correct, and historical reports keep expected terminal context.
If something goes wrong
- If blocked by an active period, close POS registers and end it through the supported workflow.
- Do not transfer/deactivate the primary licence unless that is the intended separate outcome.
Related guides
- Register a Muhasib Terminal
- End a POS Working Period
- Review and Maintain Muhasib Licence Access
- Create and Verify a Manual Backup
What to do next
Create and Activate a Fiscal Year
How to Create and Activate a Fiscal Year in Muhasib ERP
Overview
This guide will help you create a fiscal-year date range and make it the active year used by needed Muhasib transactions and reports.
The fiscal year becomes available for transaction check, stock adjustment, accounting, and reporting. Activating it can deactivate the previously active year.
Who can do this
You need access to Fiscal Year and Fiscal Year Add.
Before you start
Confirm the organization's approved financial year dates and whether another year is active. Back up the database before changing live financial settings.
Where to find it
Back Office → Essentials Setup → Manage Fiscal Year.
Create and Activate a Fiscal Year
Step 1: Choose New Record
Step 2: Enter Start Date and End Date
Step 3: Enter a clear Description
Step 4: Turn Currently Active on when this year should be used now
Step 5: Choose Save
Step 6: If Muhasib reports another active year, confirm the switch only
If Muhasib reports another active year, confirm the switch only after checking current operations.
Check your work
Reopen Fiscal Year Records and confirm the dates/status. Create no financial data solely for testing; use approved sample transactions and reports.
If something goes wrong
- Correct reversed dates before saving.
- If an active year is already correct, do not confirm replacement.
- A missing active year can block transactions and Day End.
Related guides
- Change the Active Fiscal Year
- Update or Retire a Fiscal Year
- Start a POS Working Period
- Complete Day-End Activity Safely
What to do next
Change the Active Fiscal Year
Change the Active Fiscal Year
Overview
This guide will help you make an existing fiscal year active after confirming that current operations are ready for the change.
Muhasib updates active-year status and may deactivate the prior year. The source does not prove that already-open forms immediately reload the new context.
Who can do this
You need access to Fiscal Year and Fiscal Year Update.
Before you start
Close or save transactions, identify open working periods/registers, compare and confirm the prior year, and confirm the approved effective date with the financial administrator.
Where to find it
Back Office → Essentials Setup → Manage Fiscal Year.
Change the Active Fiscal Year
Step 1: Select the intended fiscal-year record
Step 2: Verify its Start Date and End Date
Step 3: Turn Currently Active on
Step 4: Choose Update and confirm the save
Step 5: When warned that another year is active, confirm only when
When warned that another year is active, confirm only when the switch is intentional.
Step 6: Reopen affected transaction/report forms or restart if required
Check your work
Confirm only one intended year is active, then run approved date-filtered reports and a non-posting check test.
If something goes wrong
- Do not change year merely to enter an out-of-period transaction.
- If transactions remain on the old context, close/reopen forms and follow restart guidance.
Related guides
What to do next
Update or Retire a Fiscal Year
How to Update or Retire a Fiscal Year in Muhasib ERP
Overview
This guide will help you correct an unused fiscal year or determine whether it can be removed safely.
Update changes the set up period. Delete runs multiple dependency checks and should be treated as irreversible until recovery is proven.
Who can do this
You need access to Fiscal Year Update; Fiscal Year Delete plus explicit financial approval for removal.
Before you start
Back up the database. Review sales, purchases, expenses, vouchers, accounting, stock adjustments, manufacturing, and other records within the period.
Where to find it
Back Office → Essentials Setup → Manage Fiscal Year.
Update or Retire a Fiscal Year
Step 1: Select the exact fiscal year
Step 2: For correction, edit dates/description/status, choose Update, and confirm
Step 3: Do not shorten a range around existing transactions without financial
Do not shorten a range around existing transactions without financial review.
Step 4: For retirement, deactivate it and confirm that it has no
For retirement, deactivate it and confirm that it has no dependent records.
Step 5: Choose Delete only after explicit approval
Step 6: Stop if Muhasib reports any dependency
Check your work
Compare and Confirm period-based reports before and after an approved change. Make sure the intended current year remains active.
If something goes wrong
- Never remove a year to hide transactions or reporting discrepancies.
- If dependency checks disagree with reports, preserve both results for support.
Related guides
What to do next
Fiscal Years and Working Periods
Open and close POS working periods and understand the controls around active business dates.
Start a POS Working Period
How to Start a POS Working Period in Muhasib ERP
Overview
This guide will help you start the working period required for needed POS operations.
Muhasib creates a work-period record and marks it active. A concurrent attempt is rejected when another user has already started one.
Who can do this
You need access to Access to Working Period and the required POS/register operation permissions.
Before you start
Confirm the active fiscal year, company, location, terminal, business date, and that another user has not already started the period.
Where to find it
Back Office → Sales & Customers → Working Period.
Start a POS Working Period
Step 1: Open Working Period
Step 2: Review the current status and timestamp
Step 3: If no period is active, choose Start Period
Step 4: Wait for the successful-start message
Step 5: Open the required POS register through its supported workflow
Check your work
Reopen Working Period and confirm Active status/start time. Confirm authorized POS entry can proceed.
If something goes wrong
- If already started, refresh rather than creating another period.
- If the fiscal year is missing, configure it before transactions.
Related guides
- Create and Activate a Fiscal Year
- End a POS Working Period
- Create a POS Sale
- Sign Out and Exit Muhasib ERP Safely
What to do next
End a POS Working Period
How to End a POS Working Period in Muhasib ERP
Overview
This guide will help you close all POS registers and end the active working period safely.
Muhasib records the period end. It refuses to end while one or more POS registers remain open and can detect if another user ended it concurrently.
Who can do this
You need access to Working Period access and permission to close relevant POS registers.
Before you start
Finish or hold active sales correctly, compare and confirm drawers/registers, print required closing reports, and make sure all terminals have synchronized permitted work.
Where to find it
Back Office → Sales & Customers → Working Period.
End a POS Working Period
Step 1: Close every POS register belonging to the current work period
Step 2: Open Working Period and confirm the active period
Step 3: Choose End Period
Step 4: Confirm the ending prompt
Step 5: If Muhasib reports open registers, cancel and close each named/affected
If Muhasib reports open registers, cancel and close each named/affected register.
Step 6: Retry and wait for the successful-end message
Check your work
Confirm inactive/ended status and compare and confirm the Daily Closing or working-period sales report.
If something goes wrong
- Do not force-close Muhasib to bypass open registers.
- If another user ended the period, refresh and check reports rather than retrying.
Related guides
What to do next
Users, Roles, and Permissions
Create users and roles, manage passwords and permissions, and audit effective access.
Maintain Contact Types
How to Maintain Contact Types in Muhasib ERP
Overview
This guide will help you create or update reusable classifications for contact information.
The type becomes available to dependent contact-entry workflows. Deletion is blocked when source dependency checks find use.
Who can do this
You need access to Contact Type plus Add, Update, or Delete for the intended action.
Before you start
Agree on a short, non-duplicative naming convention and identify existing party records that use the type.
Where to find it
Back Office → Essentials Setup → Manage Contact Types.
Maintain Contact Types
Step 1: Choose New Record or select an existing type
Step 2: Enter a clean Short Description and applicable long description
Enter a clean Short Description and needed long description.
Step 3: Choose Save for a new type or Update for a change
Step 4: For approved removal, select the exact type and choose Delete
Step 5: Stop if Muhasib reports the type is in use
Check your work
Reopen the record and confirm it appears correctly in a controlled party/contact workflow.
If something goes wrong
- Do not create near-duplicate names to bypass a visibility problem.
- Reclassify dependencies through supported forms before any approved removal.
Related guides
What to do next
Configure an SMS Gateway
How to Configure an SMS Gateway in Muhasib ERP
Overview
This guide will help you configure a reusable SMS gateway request and check it using synthetic data.
The gateway can be selected by locations and used by allowed SMS workflows. Saving does not prove the endpoint accepts or correctly interprets the request.
Who can do this
You need access to SMS Settings and SMS Settings Add/Update.
Before you start
Get the vendor's endpoint, request method, recipient parameter, success code, required parameters/headers, and test credentials. Never use production recipients during setup.
Where to find it
Back Office → Essentials Setup → Manage SMS Settings.
Configure an SMS Gateway
Step 1: Choose New Record
Step 2: Enter a Short Description and URL
Step 3: Enter the Send To parameter name
Step 4: Select the Request Type/method
Step 5: Enter the expected Success Code
Step 6: Configure only the vendor-required additional parameter key/value pairs
Configure only the vendor-required more parameter key/value pairs.
Step 7: Configure required header key/value pairs
Step 8: Enter the supported message parameter/template behavior
Step 9: Choose Save
Step 10: Associate the gateway with a test location and send one
Associate the gateway with a test location and send one approved test SMS.
Check your work
Confirm one sandbox/test message, expected success code, and SMS inquiry/log result without exposing credentials.
If something goes wrong
- Compare method, parameter names, encoding, headers, and success code with vendor documentation.
- Do not place secrets in screenshots or article examples.
Related guides
- Configure Location Printing and SMS
- Send a Message to Multiple Recipients
- Review the SMS Inquiry
- Configure Diagnostic Logging Safely
What to do next
Create a System User
How to Create a System User in Muhasib ERP
Overview
This guide will help you create an active Muhasib user, assign a role, and control whether the account may sign in.
Muhasib creates the user and role association. Company access and operation rights come from the role; active and allow-login states also control authentication.
Who can do this
You need access to System Users and System Users Add.
Before you start
Create the least-privilege role first. Prepare the user's authorized identity/contact data and a unique username. Communicate credentials securely.
Where to find it
Back Office → User Management → Manage System Users.
Create a System User
Step 1: Choose New Record
Step 2: Enter First Name and applicable Last Name, National ID, phone,
Enter First Name and needed Last Name, National ID, phone, mobile, email, and address.
Step 3: Enter a unique User Name
Step 4: Enter a password of at least five characters or the
Enter a password of at least five characters or the stronger organizational minimum.
Step 5: Confirm the password
Step 6: Select the intended User Role
Step 7: Set Active User and Allow Login according to the approved
Set Active User and Allow Login according to the approved start date/access state.
Step 8: Choose Save
Check your work
Use a controlled sign-in to confirm the intended companies and least-privilege access. Do not test with production credentials on an untrusted device.
If something goes wrong
- Correct invalid email, missing username/password, short password, mismatch, or missing role.
- If user capacity is reached, resolve the licence instead of deleting an account casually.
Related guides
- Create a User Role
- Grant and Revoke Muhasib Permissions
- Audit a User's Effective Access
- Sign In to Muhasib ERP
What to do next
Update, Disable, or Retire a System User
Update, Disable, or Retire a System User
Overview
This guide will help you change a user's identity or access, disable sign-in, or retire the account while preserving audit history.
Updates change authentication/access state. Source blocks deletion of a super administrator and states that historical transactions are retained for other users, but the exact removal implementation remains under verification.
Who can do this
You need access to System Users Update; System Users Delete plus explicit account-retirement approval.
Before you start
Identify the user by stable record ID and username. Review active sessions, assigned role/companies, transaction ownership, audit requirements, and replacement responsibility.
Where to find it
Back Office → User Management → Manage System Users.
Update, Disable, or Retire a System User
Step 1: Filter and select the exact user
Step 2: For profile/access changes, edit approved fields, role, Active User, or
For profile/access changes, edit approved fields, role, Active User, or Allow Login.
Step 3: Change the password only through the authorized credential-reset process
Step 4: Choose Update and confirm
Step 5: For immediate access suspension, disable Allow Login and/or Active User
For immediate access suspension, disable Allow Login and/or Active User before considering removal.
Step 6: Choose Delete only with explicit approval and after reading the
Choose Delete only with clear approval and after reading the transaction-history warning.
Check your work
Confirm sign-in is allowed or denied as intended and that historical reports/activity still identify the user.
If something goes wrong
- Do not delete an account solely to revoke access; disabling is safer when supported.
- Do not reassign a user to a broad role as a temporary fix.
Related guides
What to do next
Update Your User Profile and Password
How to Update Your User Profile and Password in Muhasib ERP
Overview
This guide will help you update your own Muhasib profile and password.
Muhasib updates the current user record. Muhasib's check requires First Name, password, minimum length, and confirmation match. Whether an unchanged password must be re-entered may differ by installed version.
Who can do this
You need access to My User Profile.
Before you start
Choose a private password that follows organizational policy. If this device remembers credentials, plan to update or clear the remembered value.
Where to find it
Back Office → Settings/User menu → My User Profile.
Update Your User Profile and Password
Step 1: Open your profile
Step 2: Review and update authorized identity/contact fields
Step 3: Enter the required current/new password value according to the target-runtime
Enter the required current/new password value according to the target-system form.
Step 4: Use at least five characters and follow any stronger policy
Step 5: Enter the same value in Confirm Password
Step 6: Choose Update and confirm
Step 7: Sign out and test the new password when instructed
Check your work
Sign out and sign in with the intended password. Confirm profile changes and remembered-device behavior.
If something goes wrong
- Correct mismatch before retrying.
- Never send passwords through support channels.
Related guides
What to do next
Create a User Role
How to Create a User Role in Muhasib ERP
Overview
This guide will help you create a least-privilege role, assign companies, and prepare it for user assignment.
The role becomes available for users. Permission nodes absent because of the current plan cannot be granted through the role.
Who can do this
You need access to System Users Rights and System Users Rights Add.
Before you start
Define the job outcome, required companies, modules, reports, add/update/delete/custom actions, and segregation-of-duties restrictions.
Where to find it
Back Office → User Management → User Roles and Permissions.
Create a User Role
Step 1: Choose New Record
Step 2: Enter a unique Role Name and useful Description
Step 3: Select only the companies required by this role
Step 4: Expand the permission tree
Step 5: Grant base system access and the minimum module/view permissions
Step 6: Grant Add, Update, Delete, printing, email, SMS, and custom rights
Grant Add, Update, Delete, printing, email, SMS, and custom rights only when the job requires them.
Step 7: Choose Save
Step 8: Assign a controlled test user and verify effective access
Check your work
Sign in as the test user and check both allowed and prohibited tasks in each assigned company.
If something goes wrong
- Do not copy the super-administration role for ordinary users.
- A missing node may indicate an unlicensed feature, not a form error.
Related guides
What to do next
Grant and Revoke Muhasib Permissions
How to Grant and Revoke Muhasib Permissions in Muhasib ERP
Overview
This guide will help you change a role's companies and action permissions, then apply the result to affected users.
The role record and rights change for every assigned user. Existing sessions may keep old access until restart/re-login. Licence features still constrain available actions.
Who can do this
You need access to System Users Rights Update.
Before you start
Document the approved access change and identify all users assigned to the role. Finish critical work before forcing a restart.
Where to find it
Back Office → User Management → User Roles and Permissions.
Grant and Revoke Muhasib Permissions
Step 1: Select the exact role
Step 2: Review assigned companies
Step 3: Expand each relevant permission-tree branch
Step 4: Add or remove the smallest specific rights required
Step 5: Review destructive rights such as Delete and broad communication/reporting rights
Review destructive rights such as Delete and broad communication/reporting rights separately.
Step 6: Choose Update and confirm
Step 7: When warned that logged-in users must restart, choose an appropriate
When warned that logged-in users must restart, choose an appropriate safe restart time.
Step 8: Test with a controlled user
Check your work
Confirm allowed actions work and revoked actions are hidden/blocked across each assigned company without granting unrelated access.
If something goes wrong
- If access remains unchanged, restart safely and re-authenticate.
- If a node is absent, check feature entitlement.
Related guides
What to do next
Audit a User's Effective Access
How to Audit a User's Effective Access in Muhasib ERP
Overview
This guide will help you explain and check the actions a user can actually complete without granting unnecessary access.
Effective access is the intersection of account state, role/company rights, plan features/limits, terminal context, settings, and data prerequisites.
Who can do this
Before you start
Record the user, role, company, terminal, plan, intended action, and exact missing/blocked behavior.
Where to find it
Back Office → User Management plus Licence Information and the affected module.
Audit a User's Effective Access
Step 1: Confirm Active User and Allow Login
Step 2: Confirm the user's assigned role
Step 3: Confirm the intended company is assigned to that role
Step 4: Check the parent module/view right
Step 5: Check the exact Add, Update, Delete, Print, Email, SMS, or custom right
Step 6: Confirm the plan includes the feature and has available capacity
Step 7: Check company/location/terminal registration and required configuration/data
Step 8: Restart/re-login after authorized role or licence changes
Step 9: Test both the permitted outcome and a prohibited control action
Check your work
Record a small access matrix showing expected versus observed results. Resolve discrepancies without broadening the role unnecessarily.
If something goes wrong
Related guides
- Understand Why a Module or Action Is Unavailable
- Create a User Role
- Grant and Revoke Muhasib Permissions
- Understand Muhasib Plan Limits and Restricted Access
What to do next
Global Application Settings
Set company-wide rules for POS, purchasing, inventory, customers, documents, tax, and synchronization.
Configure POS Behavior for a Company
How to Configure POS Behavior for a Company in Muhasib ERP
Overview
This guide will help you configure company-wide POS defaults and controls for new sales without assuming they rewrite existing transactions.
Values are stored per company through individual setting writes. A failure can potentially leave only some settings changed. Open POS forms may keep old values.
Who can do this
You need access to Global Configurations plus authorization to change sales, inventory, tax, payment, and commission policy.
Before you start
Back up the database, close POS forms/registers, record current values, and prepare a test customer, item, stock location, payment term/account, service staff member, and tax setup.
Where to find it
Back Office → Settings → Application/Global Settings → POS Settings.
Configure POS Behavior for a Company
Step 1: Confirm the active company
Step 2: Configure the default customer, payment terms, sale type, and applicable
Configure the default customer, payment terms, sale type, and needed service charges.
Step 3: Configure tax timing and whether temporary sales/quotations exclude tax
Step 4: Configure inventory-location selection and the transaction used for inventory calculation
Step 5: Configure duplicate-item quantity behavior, price adjustment, visible price/discount/barcode/quantity/cost/variant fields, and
Configure duplicate-item quantity behavior, price adjustment, visible price/discount/barcode/quantity/cost/variant fields, and empty-cart restrictions.
Step 6: Configure service-staff assignment/commission and sale-return requirements
Step 7: Configure temporary-sale ledger and edit-limit behavior only after reviewing its
Configure temporary-sale ledger and edit-limit behavior only after reviewing its payment/conversion workflow.
Step 8: Save, then close and reopen POS before testing
Check your work
Use a disposable sale to check item selection, calculations, stock location, customer ledger, payment, commission, receipt, return, and cancellation. Compare and Confirm reports/ledgers, then restore the snapshot.
If something goes wrong
- Restore recorded values if totals or stock scope differ unexpectedly.
- Do not combine multiple policy changes in one verification run.
Related guides
- Configure This Workstation's POS Experience
- Configure Purchase and Inventory Behavior
- Configure Receipt and Invoice Content
- Create a POS Sale
What to do next
Configure Purchase and Inventory Behavior
How to Configure Purchase and Inventory Behavior in Muhasib ERP
Overview
This guide will help you configure company-wide purchase and inventory rules with a recoverable verification plan.
New purchases, stock movements, returns, POS activity, inventory calculations, and reports may use the new rules. Source alone does not prove whether historical values are recalculated.
Who can do this
You need access to Global Configurations and business authorization for stock valuation, costing, purchase tax, and item lifecycle policy.
Before you start
Back up the database. Record current settings and compare and confirm stock, item costs, inventory ledger, payables, purchase tax, and General Ledger.
Where to find it
Back Office → Settings → Application/Global Settings → System Settings and Purchase Settings.
Configure Purchase and Inventory Behavior
Step 1: Select the approved inventory-management/calculation method
Step 2: Configure quantity decimal places and item-batch behavior
Step 3: Configure whether item cost is recalculated or changed by Purchase/GRN
Step 4: Configure purchase tax, visible tax controls, and whether tax uses
Configure purchase tax, visible tax controls, and whether tax uses item selling price.
Step 5: Configure display of selling price and selling-versus-cost difference
Step 6: Configure allocation of other purchase discount across line items
Step 7: Review item deletion after transactions, automatic barcode, MRP, multiple images,
Review item deletion after transactions, automatic barcode, MRP, multiple images, and positive selling-price enforcement separately.
Step 8: Save and reopen affected forms
Check your work
In a snapshot, create a small Purchase/GRN and sale/return sequence. Compare and Confirm item cost, stock by location/batch, inventory ledger, purchase tax, payable, COGS, and General Ledger.
If something goes wrong
- Do not change costing methods to repair a single wrong item.
- If historical reports move unexpectedly, restore and escalate before production use.
Related guides
- Configure POS Behavior for a Company
- Create a Purchase
- Create an Inventory Adjustment
- Configure Accounting Settings
What to do next
Configure Customer, Credit, Loyalty, and Party Rules
How to Configure Customer, Credit, Loyalty, and Party Rules in Muhasib ERP
Overview
This guide will help you configure how Muhasib creates parties and applies customer credit, loyalty, and commission rules.
New party creation, sales, returns, ledgers, loyalty balances, and commission reports use needed rules. Existing balances may remain unchanged until recalculation or new activity.
Who can do this
You need access to Global Configurations and authorization from finance/sales management.
Before you start
Record current settings and prepare synthetic customer, supplier, group, commission-agent, service-staff, item, sale, return, and payment data.
Where to find it
Back Office → Settings → Application/Global Settings → Party Settings, Loyalty Points, and needed POS settings.
Configure Customer, Credit, Loyalty, and Party Rules
Step 1: Decide whether the same party may hold customer and supplier roles
Step 2: Configure contact-duplication and mandatory customer-group rules
Step 3: Configure whether credit limits are enabled, the default limit, and
Configure whether credit limits are enabled, the default limit, and exceed-warning behavior.
Step 4: Configure party-ledger transaction detail display
Step 5: Configure commission calculation bases, staff auto-assignment, and return deductions
Step 6: Configure loyalty calculation basis, eligible sale type, currency equivalence, and
Configure loyalty calculation basis, allowed sale type, currency equivalence, and expiry days.
Step 7: Save and reopen customer/POS forms
Check your work
Run controlled creation, sale, payment, return, loyalty-ledger, commission-ledger, and report cases. Confirm both below-limit and over-limit behavior.
If something goes wrong
- Do not edit limits to conceal overdue balances.
- Check plan/permissions if loyalty or commission controls are absent.
Related guides
- Create a Customer
- Configure Customer Credit and Loyalty
- Review the Customer Loyalty Points Ledger
- Pay a Commission Agent
What to do next
Configure Receipt and Invoice Content
How to Configure Receipt and Invoice Content in Muhasib ERP
Overview
This guide will help you control which company, customer, item, tax, balance, and terms information appears on receipts and invoices.
Who can do this
You need access to Global Configurations plus authorization to change customer-facing and tax documents.
Before you start
Record current values. Prepare sanitized sample transactions covering tax, discount, balance, barcode, and long descriptions. Confirm legal document requirements.
Where to find it
Back Office → Settings → Application/Global Settings → Receipt Settings and Invoice Layout Settings.
Configure Receipt and Invoice Content
Step 1: Choose the approved receipt/invoice layout
Step 2: Configure company logo, name, address, contact, email, website, NTN, and
Configure company logo, name, address, contact, email, website, NTN, and STRN display.
Step 3: Configure customer number, CNIC, NTN, address, previous/total balance display
Step 4: Configure item barcode, description, unit price, discounted line price, and
Configure item barcode, description, unit price, discounted line price, and tax-inclusive line/subtotal behavior.
Step 5: Configure tax label or approved custom label
Step 6: Enter footer note and transaction-specific terms and conditions
Step 7: Save and reopen preview/output forms
Check your work
Preview and print/PDF every affected transaction type with sanitized data. Check totals, tax, wrapping, page breaks, barcode, privacy, and company identity.
If something goes wrong
- If identity is missing, also check Company and Branding Settings.
- Do not use a custom tax label that changes legal meaning.
Related guides
- Update the Active Company's Identity and Branding
- Register a Printer
- Configure Item Label Printing
- Print, Export, or Email a Report
What to do next
Configure Transaction Numbering
How to Configure Transaction Numbering in Muhasib ERP
Overview
This guide will help you configure an approved prefix, suffix, and starting number for a transaction family without creating duplicate identifiers.
Relevant new records use the effective settings. Global and local numbering can conflict if precedence/scope is misunderstood.
Who can do this
You need access to Global Configurations or Instance Settings, plus finance/system-owner authorization.
Before you start
Back up the database. Inventory existing highest numbers, offline/pending transactions, all terminals, imports, integrations, and conversion workflows. Stop new entry during the change.
Where to find it
Back Office → Settings → Application/Global Settings → Transaction Settings; or Instance Settings → Transaction Settings when explicitly set up.
Configure Transaction Numbering
Step 1: Select one transaction family
Step 2: Record its current start, prefix, and suffix
Step 3: Determine whether Get Parameters from Instance Config applies
Step 4: Choose a start value above all existing and pending identifiers
Choose a start value above all existing and pending identifiers in the effective scope.
Step 5: Enter approved prefix/suffix values
Step 6: Save and reopen the affected entry form
Step 7: Create one disposable record on each relevant terminal, then test
Create one disposable record on each relevant terminal, then test conversion/import/synchronization.
Check your work
Query the corresponding inquiry/report and confirm uniqueness, ordering, company/terminal scope, and correct converted/source references.
If something goes wrong
- Stop immediately on a duplicate or reset sequence.
- Do not renumber historical records manually.
Related guides
- Configure This Workstation's POS Experience
- Configure E-Commerce and Offline POS Synchronization
- Create and Verify a Manual Backup
What to do next
Configure Item Label Printing
How to Configure Item Label Printing in Muhasib ERP
Overview
This guide will help you configure label dimensions and typography that produce readable item labels on the intended printer.
Item Label Printing uses the active company's layout values with the selected printer/output path.
Who can do this
You need access to Global Configurations, Printer access, and Item Label Printing permission.
Before you start
Register a test printer/PDF sink and get label-stock width, height, margins, rows/columns, and printer specifications. Use synthetic barcodes.
Where to find it
Back Office → Settings → Application/Global Settings → Label Settings.
Configure Item Label Printing
Step 1: Select the intended printer type
Step 2: For a normal printer, enter paper size, stickers per row,
For a normal printer, enter paper size, stickers per row, rows per page, spacing, label size, and margins.
Step 3: For a label printer, enter label size, margins, and line spacing
Step 4: Configure company, item, and price font sizes
Step 5: Configure barcode width and height
Step 6: Save settings
Step 7: Print a small test batch before bulk printing
Check your work
Check alignment across first/last labels, page boundaries, long item names, prices, company text, and scanner readability.
If something goes wrong
- Adjust one dimension at a time.
- Never test a large production batch before scanner verification.
Related guides
What to do next
Configure Tax Integrations
How to Configure Tax Integrations in Muhasib ERP
Overview
This guide will help you configure an allowed FBR Digital Invoicing, FBR, SRB, or PRA integration without exposing credentials or submitting production tax data during testing.
Eligible sales paths can submit data externally and store/render authority responses or barcodes. Retrying incorrectly can duplicate legal submissions.
Who can do this
You need access to Global Configurations, tax feature entitlement, and explicit tax-administrator authorization. Local POS IDs may also require Instance Settings.
Before you start
Use sandbox endpoints and synthetic taxpayer data. Get approved seller/company identity, NTN, address/province, endpoint, POS ID/user/password/token, barcode, and service-fee policy.
Where to find it
Back Office → Settings → Application/Global Settings → Tax Integration; local terminal IDs may be under Instance Settings → Tax Integration Settings.
Configure Tax Integrations
Step 1: Select only the applicable authority/integration
Select only the needed authority/integration.
Step 2: Enter the approved sandbox API path
Step 3: Enter seller/company identifiers and jurisdiction fields
Step 4: Enter protected authentication values without recording them in documentation
Step 5: Configure POS ID and receipt-barcode behavior
Step 6: Configure customer service-fee treatment only when legally approved
Step 7: Save and restart/reopen POS as required
Step 8: Submit one synthetic transaction and test success, rejection, timeout, and
Submit one synthetic transaction and test success, rejection, timeout, and retry.
Check your work
Match Muhasib status/logs and printed barcode/reference to the sandbox authority response, then compare and confirm the local sale and tax reports.
If something goes wrong
- Disable production submission during documentation tests.
- Redact tokens, passwords, NTN/test identifiers where required, payloads, and customer data.
- Follow authority-specific retry rules.
Related guides
- Configure Diagnostic Logging Safely
- Configure Receipt and Invoice Content
- Review Tax Transactions and Summaries
- Request Muhasib Support
What to do next
Configure E-Commerce and Offline POS Synchronization
How to Configure E-Commerce and Offline POS Synchronization in Muhasib ERP
Overview
This guide will help you configure synchronization intervals and mappings while protecting against duplicate or cross-company records.
Background services may fetch/upload data at the set up interval. External status, local transactions, stock, payments, tax, and numbering can all be affected.
Who can do this
You need access to Global Configurations, relevant integration feature/operation permissions, and external-system authorization.
Before you start
Back up all involved databases. Use sandbox stores/endpoints. Prepare mapping rules for company, location, terminal, items, customers, tax, payment, numbering, stock, and order status.
Where to find it
Back Office → Settings → Application/Global Settings → Offline POS Settings or Ecommerce Integration.
Configure E-Commerce and Offline POS Synchronization
Step 1: Confirm the active company and integration direction
Step 2: Configure the sandbox URL/connection and any approved store setting
Step 3: Configure automatic fetch/synchronization only after manual transfer succeeds
Step 4: Set a conservative polling/synchronization interval
Step 5: Configure default tax/type and mapping behavior
Step 6: Save and restart the relevant scheduler when required
Step 7: Transfer one synthetic order/sale
Step 8: Repeat the same transfer to verify deduplication
Step 9: Test timeout, partial response, conflict, and retry
Check your work
Compare and Confirm source and destination IDs, quantities, totals, tax, customer, payment, status, stock, and retry count. Confirm no duplicates.
If something goes wrong
- Disable automatic scheduling before remapping or restoring data.
- Never retry blindly after an unknown response.
Related guides
- Synchronize Offline POS Sales
- Synchronize E-Commerce Orders
- Configure Transaction Numbering
- Configure Diagnostic Logging Safely
What to do next
Configure Centralized Multi-Company Behavior
How to Configure Centralized Multi-Company Behavior in Muhasib ERP
Overview
This guide will help you select the primary company and configure which masters or transactions are shared/visible across companies.
Affected forms may use primary-company masters or expose cross-company transactions. Wrong settings can mix identities, numbering, stock, accounts, tax, or reports.
Who can do this
You need access to Global Configurations, relevant company permissions, and explicit multi-company data-governance authorization.
Before you start
Back up the database. Inventory each company's items, contacts/parties, payment accounts/types/terms, tax, terminals, sales, purchases, roles, numbering, and reporting obligations.
Where to find it
Back Office → Settings → Application/Global Settings → Centralize Company Settings.
Configure Centralized Multi-Company Behavior
Step 1: Confirm every company and choose the approved Primary Company
Step 2: Decide separately whether to centralize items, contacts, parties, payment accounts,
Decide separately whether to centralize items, contacts, parties, payment accounts, payment terms, payment types, tax, and terminals.
Step 3: Decide whether users may see purchases or sales from all companies
Step 4: Change one family at a time
Step 5: Save and restart/re-enter company context where required
Step 6: Test create, select, update, report, permission, and company-switch behavior in
Test create, select, update, report, permission, and company-switch behavior in every affected company.
Check your work
Use an explicit company-by-company matrix to prove allowed sharing and prohibited leakage. Compare and Confirm reports and record ownership.
If something goes wrong
- Restore the prior value if records appear in the wrong company.
- Do not repair cross-company effects with direct database edits.
Related guides
- Understand Company, Location, Terminal, and Licence Identities
- Add a Company Workspace
- Audit a User's Effective Access
- Configure Transaction Numbering
What to do next
Manage Global and Instance Settings
How to Manage Global and Instance Settings in Muhasib ERP
Overview
This guide will help you distinguish company/database-wide settings from workstation-specific settings and change only an approved, evidenced value.
The approved global or local behavior changes for new operations; historical records are not assumed to be recalculated.
Who can do this
You need access to Relevant settings administration plus business-owner approval for the affected module and workstation/company scope.
Before you start
Identify setting key/label, current value, consumer forms/services, scope, default, data/external consequences, restart requirement, rollback value, and test case.
Where to find it
Back Office → Settings → Application/Global Settings or Instance Settings.
Manage Global and Instance Settings
Step 1: Confirm whether the setting belongs to shared database/company behavior or
Confirm whether the setting belongs to shared database/company behavior or this workstation instance.
Step 2: Record the current value and affected consumers without exposing secrets
Step 3: Change one approved setting group at a time
Step 4: Save once and restart only when required
Step 5: Test a representative affected workflow in an isolated environment
Step 6: Reopen the setting and reconcile downstream behavior
Check your work
The stored value, effective scope, consumer behavior, audit evidence, and rollback test match the approved change.
If something goes wrong
- Some setting getters may create defaults, so use a cloned environment for discovery.
- Do not copy instance IDs, tokens, credentials, or connection details into documentation.
Related guides
- Configure POS Behavior for a Company
- Configure This Workstation's POS Experience
- Configure Diagnostic Logging Safely
What to do next
Workstation and Instance Settings
Control this computer’s POS experience, Quick Launcher, and diagnostic logging.
Configure This Workstation's POS Experience
How to Configure This Workstation's POS Experience in Muhasib ERP
Overview
This guide will help you configure POS display, item selection, search columns, temporary-sale behavior, and Quick Pay for this computer.
New POS sessions on this computer use the local selection/display/payment behavior. Company-wide POS settings still apply and can override or complement outcomes.
Who can do this
You need access to Instance Settings plus authorization for local payment and transaction behavior.
Before you start
Record current local settings. Close POS, identify screen resolution/scaling, and prepare approved payment type plus cash/card payment accounts.
Where to find it
Back Office → Settings → Instance Settings → POS Module Settings.
Configure This Workstation's POS Experience
Step 1: Choose automatic POS size or enter the approved manual size
Step 2: Choose the supported current interface; treat UI 2 marked beta
Choose the supported current interface; treat UI 2 marked beta as test-only unless approved.
Step 3: Configure item-search style and visible columns: ID, barcode, name, quantity,
Configure item-search style and visible columns: ID, barcode, name, quantity, selling price, available stock, SKU, UPC, brand, and image as available.
Step 4: Configure prompts for quantity, price, or line-item options after selection
Step 5: Configure barcode/name display and POS minimize behavior
Step 6: Configure temporary sale/default behavior only when entitled
Step 7: For Quick Pay, enable it and select default payment type,
For Quick Pay, enable it and select default payment type, cash account, and card account.
Step 8: Save, close, and reopen POS
Check your work
Run a disposable cash and card sale, check prompts/search columns/layout, and compare and confirm the correct payment accounts.
If something goes wrong
- Restore the previous local values if POS becomes unusable.
- Do not enable beta UI on production terminals without approval.
Related guides
What to do next
Configure the Quick Launcher
How to Configure the Quick Launcher in Muhasib ERP
Overview
This guide will help you select a small set of authorized shortcuts for this workstation.
Selected values are saved locally. Visibility still depends on role, plan, company, and target-form availability.
Who can do this
You need access to Instance Settings plus access to each destination task.
Before you start
List the user's most frequent authorized tasks. A shortcut does not grant permission or satisfy prerequisites.
Where to find it
Back Office → Settings → Instance Settings → Quick Launcher Settings.
Configure the Quick Launcher
Step 1: Review available transaction, master, inquiry, and report shortcuts
Step 2: Select only tasks used on this workstation
Step 3: Keep the selection at or below the form's validated maximum
Keep the selection at or below the form's validated maximum of eight until the target build proves otherwise.
Step 4: Save the instance settings
Step 5: Return to or restart Back Office if required
Step 6: Open each shortcut and confirm its destination
Check your work
Confirm the intended shortcuts appear and unavailable tasks remain blocked.
If something goes wrong
- If the visible launcher ignores these selections, record the system build and treat the form as legacy/unwired pending confirmation.
Related guides
- Use the Muhasib Quick Launcher
- Configure This Workstation's POS Experience
- Audit a User's Effective Access
What to do next
Configure Diagnostic Logging Safely
How to Configure Diagnostic Logging Safely in Muhasib ERP
Overview
This guide will help you enable only the diagnostic detail needed for a controlled investigation, then return logging to its normal level.
The logging framework can emit more detail, increasing storage, privacy exposure, and performance cost.
Who can do this
You need access to Instance Settings and authorization to collect diagnostic or tax-integration data.
Before you start
Identify the issue, reproduction window, approved log destination, retention period, and fields that must be redacted.
Where to find it
Back Office → Settings → Instance Settings → Log Settings.
Configure Diagnostic Logging Safely
Step 1: Record current logging options
Step 2: Select only required levels: Error, Warn, Info, or Debug; use
Select only required levels: Error, Warn, Info, or Debug; use All only for a short approved capture.
Step 3: Enable debugging only when requested by authorized support
Step 4: Enable Tax Logs only in a sandbox or under approved
Enable Tax Logs only in a sandbox or under approved sensitive-data handling.
Step 5: Save and restart if required
Step 6: Reproduce the issue once
Step 7: Collect and sanitize the relevant time window
Step 8: Restore normal logging and remove temporary sensitive copies according to
Restore normal logging and remove temporary sensitive copies according to policy.
Check your work
Confirm the required event appears without credentials, tokens, personal data, or unnecessary transaction content.
If something goes wrong
- Never publish raw logs.
- Do not leave Debug/All/Tax logging enabled indefinitely.
Related guides
What to do next
Numbering and Document Output
Configure document numbers, receipt content, invoice output, labels, and related printing choices.
Backup, Restore, and Day End
Create and verify backups, restore safely, set retention, and complete day-end work.
Create and Verify a Manual Backup
How to Create and Verify a Manual Backup in Muhasib ERP
Overview
This guide will help you create an approved Muhasib database backup and record enough information to check that it is recoverable.
Muhasib asks SQL Server to create a database backup through this workflow. A success message alone does not prove restorability or application consistency.
Who can do this
You need access to Backup & Restore, SQL/file-system access, and organizational backup authorization.
Before you start
Notify users, finish critical transactions, stop or coordinate integrations, confirm free protected storage, and record application/database revision.
Where to find it
Back Office → Essentials Setup → Backup and Restore → Software Backup.
Create and Verify a Manual Backup
Step 1: Confirm the active database/company and backup destination
Step 2: Choose Backup Data
Step 3: Select the approved protected destination/name when prompted
Step 4: Wait for the successful-backup message; do not close Muhasib or
Wait for the successful-backup message; do not close Muhasib or SQL Server during creation.
Step 5: Record timestamp, size, database identity/revision, application build, and checksum when
Record timestamp, size, database identity/revision, application build, and checksum when supported.
Step 6: Copy according to retention/off-site policy
Step 7: Verify restoration only into an isolated disposable SQL environment
Check your work
Confirm the file exists, is non-zero, is protected, and restores into isolation. Launch the matching Muhasib build against the restored clone and run integrity/checking checks.
If something goes wrong
- Never overwrite the only good backup.
- Do not store backups in public/shared folders without protection.
Related guides
- Restore a Muhasib Database Safely
- Configure Automatic Backups and Retention
- Check the Installed Muhasib Version and Database Revision
What to do next
Restore a Muhasib Database Safely
How to Restore a Muhasib Database Safely in Muhasib ERP
Overview
The target database is replaced by backup state, potentially discarding later work. The available workflow shows success/failure handling but does not prove transaction rollback for every failure.
Who can do this
You need access to Backup & Restore, SQL/file-system administration, business-owner approval, and an agreed recovery point.
Before you start
Stop users/services/integrations, create and check a current safety backup, identify target server/database, confirm backup source/checksum/version/revision, and document the data-loss window.
Where to find it
Back Office → Essentials Setup → Backup and Restore → Restore Data.
Restore a Muhasib Database Safely
Step 1: Rehearse the restore into an isolated database first
Step 2: Validate the restored clone with the matching application build
Step 3: Obtain final approval for the exact source file and target database
Step 4: Disconnect all users and background services from the target
Step 5: Open Restore Data and select the approved backup
Step 6: Confirm only when source and target are exact
Step 7: Wait for completion without interruption
Step 8: Reconnect with one administrator and verify before releasing users/services
Check your work
Check database revision, companies/users, record counts, latest transactions, stock, ledgers, reports, attachments/integrations, numbering, and logs. Re-enable services gradually.
If something goes wrong
- Stop on compatibility, checksum, access, partial-restore, or integrity errors.
- Never repeatedly restore over production while diagnosing.
Related guides
- Create and Verify a Manual Backup
- Resolve a Muhasib Startup Interruption
- Configure E-Commerce and Offline POS Synchronization
What to do next
Configure Automatic Backups and Retention
How to Configure Automatic Backups and Retention in Muhasib ERP
Overview
This guide will help you configure scheduled backups to a protected location and check retention without risking the only recoverable copy.
Global settings drive the Back Office automatic-backup service. Retention may remove older scheduled files; independent backups remain necessary.
Who can do this
You need access to Backup & Restore, file-system access, and backup-policy authorization.
Before you start
Choose a durable path writable by the Muhasib process, define interval and retention, estimate space, and keep an independent off-site copy.
Where to find it
Back Office → Essentials Setup → Backup and Restore → Automatic Backup Settings.
Configure Automatic Backups and Retention
Step 1: Select the approved automatic-backup path
Step 2: Set the interval in minutes according to recovery objectives
Step 3: Set how many last good backups to retain
Step 4: Enable Automatic Backup
Step 5: Choose Update and confirm
Step 6: Keep Muhasib running long enough for a scheduled test
Step 7: Verify creation, naming, retention, and restore of a generated backup
Check creation, naming, retention, and restore of a generated backup in isolation.
Check your work
Confirm repeated scheduled backups, retention at the approved count, failure notification/log behavior, and isolated restoration.
If something goes wrong
- An enabled schedule with an unwritable/full path is not protection.
- Do not rely on a folder inside an easily lost workstation as the only backup.
Related guides
What to do next
Complete Day-End Activity Safely
How to Complete Day-End Activity Safely in Muhasib ERP
Overview
This guide will help you run only the required Day-End tasks and compare and confirm their inventory, ageing, batch, and notification results.
Source performs repeated saves while creating/updating inventory and stock-adjustment records, removing item-location rows, changing batches, recalculating ageing, and creating notifications. Atomic rollback is not proven.
Who can do this
You need access to Day-end Activity plus relevant underlying module permissions.
Before you start
Create a verified backup, make sure an active fiscal year, finish/synchronize transactions, close relevant registers/periods, stop integrations, and capture baseline stock/ledgers/ageing/batches/notifications.
Where to find it
Back Office → Essentials Setup → Day-end Activity.
Complete Day-End Activity Safely
Step 1: Review the Work List
Step 2: Select only approved tasks
Select only approved tasks:
- Re-calculate items inventory;
- Calculate ageing invoices;
- Generate ageing invoices notification;
- Generate ageing cheques notification;
- Merge multiple batches of items into single.
Step 3: Confirm baseline reports and backup
Step 4: Choose Start Activity
Step 5: Do not interrupt the process
Step 6: Wait for completion and preserve any error
Step 7: Reconcile every selected outcome before reopening normal work
Check your work
Compare stock report/ledger, batch report, adjustment inquiry, customer/supplier ageing, cheque inquiry, notification counts, and General Ledger where needed. A second controlled run should not create unintended duplicates.
If something goes wrong
- Stop normal work after a partial failure and restore/escalate according to the tested recovery plan.
- Never rerun blindly to clear an error.
Related guides
- Create and Verify a Manual Backup
- Create and Activate a Fiscal Year
- Review and Manage Notifications
- Reconcile the Stock Ledger to Physical Stock
What to do next
User Activity and Troubleshooting
Review user activity and investigate who performed an important action.
Review User Activity
How to Review User Activity in Muhasib ERP
Overview
This guide will help you filter and interpret Muhasib user activity for an authorized audit or support investigation.
The report provides supporting audit evidence. Any deletion can weaken record history and requires separate clear approval.
Who can do this
You need access to User Activity Report. Removing activity also requires Delete User Activity Report and explicit audit-record removal approval.
Before you start
Define the user, company, time range, action, and business question. Follow privacy, employment, audit-retention, and legal policy.
Where to find it
Back Office → Essentials Setup → User Activity Report.
Review User Activity
Step 1: Open the report
Step 2: Select the narrowest approved company/user/date/action filters available
Step 3: Run the report
Step 4: Compare timestamps and descriptions with the underlying record or support
Compare timestamps and descriptions with the related record or support event.
Step 5: Export/print only when authorized and store output securely
Step 6: Do not delete activity during ordinary review
Check your work
Cross-check an approved test action against its activity row, business record, timestamp, user, and company.
If something goes wrong
- Check time zone/date filters and user/company scope.
- Do not treat mutable descriptive logs as the sole financial audit source.