Skip to main content

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

  • Disable production submission during documentation tests.
  • Redact tokens, passwords, NTN/test identifiers where required, payloads, and customer data.
  • Follow authority-specific retry rules.

What to do next