# Integration and Synchronization Recovery

Resolve rounding, message delivery, e-commerce, offline POS, and tax integration problems.

# Quantity, Unit, Price, Discount, Tax, and Rounding Reference

### Quantity, Unit, Price, Discount, Tax, and Rounding Reference

### Overview

This guide will help you review transaction calculations consistently and identify whether a difference comes from units, pricing, discounts, taxes, or rounding.

Numeric differences have an identifiable calculation source.

### Who can do this

You need access to Underlying transaction/report access; override rights are separate.

### Before you start

Know base/transaction unit, conversion, quantity precision, price level, currency, discount order, tax inclusivity/rate/base, and company decimal places.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

Open the relevant transaction lines and corresponding detail report.

### Quantity, Unit, Price, Discount, Tax, and Rounding Reference

#### Step 1: Convert quantity to the verified base or comparison unit

#### Step 2: Confirm selected price/cost source and unit

#### Step 3: Apply line and header discounts in the verified order

#### Step 4: Determine tax-inclusive versus tax-exclusive calculation

#### Step 5: Apply additional charges/withholding as configured

Apply more charges/withholding as set up.

#### Step 6: Round at the actual line/document stage using company decimal places

#### Step 7: Compare line sum with document/report totals

### Check your work

Representative lines and document totals reproduce independently within the verified rounding rule.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- Do not force agreement with unrelated discounts or charges.
- Multi-unit and tax-inclusive comparisons are common sources of apparent differences.

### Related guides

- [Change Sale Line Quantity, Price, Discount, Tax, or Location](https://docs.muhasiberp.com/link/528)
- [Allocate Purchase Discount, Tax, Cost, and Location](https://docs.muhasiberp.com/link/381)
- [Read Report Totals, Signs, Running Balances, and Age Buckets](https://docs.muhasiberp.com/link/482)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Change Sale Line Quantity, Price, Discount, Tax, or Location**](https://docs.muhasiberp.com/link/528).</div>

# Resolve SMS or Email Delivery Problems

### How to Resolve SMS or Email Delivery Problems in Muhasib ERP

### Overview

This guide will help you determine whether a message failed check, gateway/SMTP submission, provider acceptance, or final delivery and retry safely.

If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.

The send has a known outcome or is escalated without duplicate messaging.

### Who can do this

You need access to Relevant send, settings, inquiry, and diagnostic.

### Before you start

Have recipient, sanitized content, timestamp, company/location/terminal, gateway/server, local result, provider/message ID, and consent.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

Open SMS Inquiry or email/provider evidence plus the needed settings.

### Resolve SMS or Email Delivery Problems

#### Step 1: Validate recipient address/number and consent

#### Step 2: For SMS, confirm gateway is assigned to the terminal's location

For SMS, confirm gateway is assigned to the terminal's location and restart occurred.

#### Step 3: Check URL/method/parameters or SMTP host/port/TLS/authentication

#### Step 4: Determine whether provider accepted the request

#### Step 5: Check provider delivery/bounce status separately

#### Step 6: Retry only a confirmed failed recipient once

### Check your work

One local send maps to at most one accepted provider message and intended recipient evidence.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- “Sent” can mean submitted, not delivered.
- Never expose credentials or private message bodies in tickets.

### Related guides

- [Review SMS History and Delivery Evidence](https://docs.muhasiberp.com/link/263)
- [Configure Email Delivery](https://docs.muhasiberp.com/link/264)
- [Retry a Partially Successful Integration Safely](https://docs.muhasiberp.com/link/258)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Review SMS History and Delivery Evidence**](https://docs.muhasiberp.com/link/263).</div>

# Resolve E-Commerce Synchronization Problems

### How to Resolve E-Commerce Synchronization Problems in Muhasib ERP

### Overview

This guide will help you resolve missing, rejected, duplicated, or state-mismatched Shopify/WooCommerce orders without losing either system's evidence.

If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.

The order is retrieved/converted once, intentionally excluded, or escalated with complete evidence.

### Who can do this

You need access to E-Commerce Orders, integration settings/inquiry, and relevant POS/master permissions.

### Before you start

Have provider/store, external ID, status, timestamps, cursor/window, local record/sale, sanitized error, mappings, and last successful run.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

E-Commerce Orders, integration settings/logs, Sale Inquiry, and provider admin/API evidence.

### Resolve E-Commerce Synchronization Problems

#### Step 1: Confirm intended company/store/environment

#### Step 2: Check credentials, endpoint/API version/scopes, network, and provider availability

#### Step 3: Confirm order status/window/paging eligibility

#### Step 4: Search Muhasib by external ID before retrieval or conversion retry

#### Step 5: Correct customer/item/tax/shipping/payment mappings for rejected orders

#### Step 6: Reconcile provider and Muhasib states; retry only confirmed failures

### Check your work

Each allowed external ID maps to one intended local order/sale and all totals/statuses compare and confirm.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- Avoid overlapping background and manual synchronization.
- Do not use the source-visible sale delete action to fix duplicates.

### Related guides

- [Synchronize E-Commerce Orders](https://docs.muhasiberp.com/link/268)
- [Reconcile E-Commerce Orders and Muhasib Sales](https://docs.muhasiberp.com/link/271)
- [Diagnose an External Integration Failure](https://docs.muhasiberp.com/link/257)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Synchronize E-Commerce Orders**](https://docs.muhasiberp.com/link/268).</div>

# Resolve Offline POS Synchronization Problems

### How to Resolve Offline POS Synchronization Problems in Muhasib ERP

### Overview

This guide will help you recover failed or partial offline POS synchronization while protecting successful records and local pending data.

If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.

Pending data is reconciled without intentionally duplicating previously uploaded records.

### Who can do this

You need access to Offline sync plus relevant central inquiry/correction rights.

### Before you start

Preserve local data/logs and record central database/company, pending counts/references by family, last run, successes, errors, and connectivity.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

Sync Offline POS Data plus central Sale, return/credit, Quotation, and Temporary Sale inquiries.

### Resolve Offline POS Synchronization Problems

#### Step 1: Stop automatic retry while classifying outcomes

#### Step 2: Confirm central server/database/company and stable connectivity

#### Step 3: Match each offline reference to central records by family

#### Step 4: Exclude confirmed successes

#### Step 5: Correct master, stock, period, permission, or validation errors

#### Step 6: Retry one confirmed failure and reconcile before the rest

### Check your work

Original pending population equals central successes plus remaining/documented failures for each family.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- Closing the sync form stops its form timer.
- Never clear/reinstall local offline data before checking.

### Related guides

- [Recover from Partial Offline POS Synchronization](https://docs.muhasiberp.com/link/274)
- [Monitor Automatic Offline POS Synchronization](https://docs.muhasiberp.com/link/273)
- [Prevent and Resolve Duplicate Transactions](https://docs.muhasiberp.com/link/585)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Recover from Partial Offline POS Synchronization**](https://docs.muhasiberp.com/link/274).</div>

# Resolve Tax Integration Problems

### How to Resolve Tax Integration Problems in Muhasib ERP

### Overview

This guide will help you classify and resolve a tax-integration check, transport, rejection, unknown, or local/provider mismatch safely.

If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.

One local transaction reaches one known authority state or is escalated with evidence.

### Who can do this

You need access to Tax integration inquiry/retry, source-sale correction, and responsible tax approval.

### Before you start

Preserve local transaction, request/reference, response code/message, timestamps, sanitized payload evidence, provider query result, tax values, and ledger state.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

Open source sale, tax/FBR report/history, settings, and authorized authority query/retry tools.

### Resolve Tax Integration Problems

#### Step 1: Confirm company, registration, connector, environment, and endpoint

#### Step 2: Classify local validation, authentication/network, rejected, accepted-not-stored, or unknown outcome

#### Step 3: Query provider status by original reference

#### Step 4: Correct rejected seller/buyer/item/unit/scenario/tax mappings at source

#### Step 5: Retry only confirmed unaccepted eligible records once

Retry only confirmed unaccepted allowed records once.

#### Step 6: Use official correction/cancellation/credit rules for accepted wrong invoices

### Check your work

Local/provider identifiers, statuses, lines, taxable values, taxes, totals, and ledgers compare and confirm.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- Never retry accepted or unknown submissions blindly.
- Never delete stored responses to force submission.

### Related guides

- [Recover from Tax Submission Failure](https://docs.muhasiberp.com/link/282)
- [Review FBR Tax Transactions](https://docs.muhasiberp.com/link/281)
- [Prepare Muhasib for Tax Integration](https://docs.muhasiberp.com/link/275)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Recover from Tax Submission Failure**](https://docs.muhasiberp.com/link/282).</div>