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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Configure This Workstation's POS Experience.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Configure POS Behavior for a Company.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Create a Customer.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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 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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Update the Active Company's Identity and Branding.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Configure This Workstation's POS Experience.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Register a Printer.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Configure Diagnostic Logging Safely.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Synchronize Offline POS Sales.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Understand Company, Location, Terminal, and Licence Identities.

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.

Before saving, check that the correct company is open and that you have permission to complete this task.

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.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

What to do next

Configure POS Behavior for a Company.