← Back to articles

Tax mapping

FBR Sale Type, Tax Rate, SRO and Scenario ID: A Decision Guide

Learn why sale type, tax rate, SRO schedule, SRO item and sandbox scenario should be selected as a connected tax decision.

Learn why sale type, tax rate, SRO schedule, SRO item and sandbox scenario should be selected as a connected tax decision.

Treat the fields as a decision chain

Sale type, rate, SRO schedule and SRO item are not independent labels. They describe the legal and reference-data path used for a transaction. Start with the real supply and approved tax treatment, then select values supported by current reference data. Never reverse the process by trying combinations until one passes.

What scenario ID does

The published API examples show scenarioId in sandbox payloads, and the user manual links scenario testing to the business nature and sector selected during onboarding. A scenario proves that a representative test case can move through the sandbox. It should not be copied into production as a substitute for determining the actual sale type and tax treatment.

Use dated reference data

Rates and SRO relationships can depend on date, transaction type and origination. Cache reference data carefully, record when it was obtained and refresh it under a controlled process. If a rate changes, preserve the values and source used for historical invoices instead of rewriting old records.

Connect HS code and UOM without guessing

Classification and unit choices must also make sense for the item. Use the Pakistan HS Code Finder as a candidate-search aid, then verify the classification and permitted unit against official sources and professional advice. A relevance score is not a legal classification decision.

Approval and audit evidence

For non-standard, exempt, reduced-rate or schedule-based transactions, store the decision owner, supporting notification or advice, applicable dates, sale type, rate and SRO details. Revalidate the mapping when the product, supply chain, province, customer status or law changes.

Official sources and review note

  1. FBR/PRAL DI API Technical Specification
  2. FBR/PRAL Digital Invoicing User Manual

Reviewed against these public sources on 21 October 2026. This article is educational information, not tax or legal advice. Confirm the latest law, notifications, technical documents and professional advice applicable to your business.

An independent commercial software solution. Not an official FBR or government website.
Recent articles

All articles

Related searches

Focused topics covered by this page and its related digital invoicing, tax and business guidance.

FBR sale typeFBR tax rate APISRO schedule itemFBR scenario IDHS code UOM Pakistan
Chat on WhatsApp