FBR Provincial Code Numbers, State Codes and Buyer Types
FBR provincial code numbers used in digital invoicing rate lookups (Punjab 7, Sindh 8, KPK 6, Islamabad 5, Balochistan 2), the province names invoices carry, and buyer registration types.
Quick provincial code lookup for FBR digital invoicing
Numeric province IDs used by FBR's Digital Invoicing reference lookups:
- AJK: 4
- Balochistan: 2
- Islamabad: 5
- Gilgit-Baltistan: 9
- KPK: 6
- Punjab: 7
- Sindh: 8
- FATA/PATA: none listed
Source: PRAL DI API specification v1.12, section 5.1 and the province reference it describes. Checked 2 October 2026. What was and was not verified.
Provinces and their FBR state codes
Province appears twice on an FBR digital invoice — once for the seller and once for the buyer — and it is not free text. The specification describes both fields as the “province from reference API 5.1”.
These numbers are identifiers inside FBR's Digital Invoicing reference data. They are not postal codes, dialling codes or the province codes used on other government forms.
| Province | State code |
|---|---|
| AZAD JAMMU AND KASHMIR | 4 |
| BALOCHISTAN | 2 |
| CAPITAL TERRITORY | 5 |
| GILGIT BALTISTAN | 9 |
| KHYBER PAKHTUNKHWA | 6 |
| PUNJAB | 7 |
| SINDH | 8 |
| FATA/PATA | — |
FATA/PATA has no code in this reference. It is in the province list Bizio Invoicing offers, but the province reference our integration reads does not give a numeric code for it, so a lookup that needs the number has nothing to send. That describes the reference as we have it today, not every future FBR dataset — and we would rather show a gap than invent a number.
Province name or numeric code: which goes where
The two forms are used in different requests. The invoice carries names; the rate lookup takes a number.
// Rate lookup (section 5.8): the supplier's province as a number
GET /pdi/v2/SaleTypeToRate?date=24-Feb-2024&transTypeId=18&originationSupplier=8
// Invoice (section 4): provinces as names
{
"sellerProvince": "Sindh",
"buyerProvince": "Sindh"
}This is a partial illustration built from the specification's own samples, with Sindh's code substituted into the lookup. It is not a complete invoice payload and not a rate for any real transaction. The specification's invoice samples write the name as “Sindh” while its province reference returns “SINDH”; Bizio Invoicing's province selector uses the reference spelling.
Buyer registration types
Every buyer on an invoice carries a registration type as well as a registration number, and the two have to agree. The specification documents two values for the registration-type field:
- Registered
- A buyer with a sales tax registration of their own. Their registration number has to be a valid one.
- Unregistered
- A buyer with no sales tax registration. The specification makes some buyer details optional in this case.
Additional categories in Bizio Invoicing and its Excel template
Bizio Invoicing's customer selector and upload template offer two further categories. They are application categories; do not read them as extra official values of the API field. If your buyer falls into one of them, confirm the treatment with your adviser — the sandbox guide explains the same distinction for testing.
- Unregistered Distributor
- An additional category offered in Bizio's customer selector and Excel template. It is not listed as a registration-type value in the v1.12 specification.
- Retail Consumer
- An end consumer. Also a Bizio selector and template category rather than a registration-type value listed in the v1.12 specification.
Where the other lists come from
The two lists above are stable enough to publish. Most of FBR's other reference data is not, and is better read live than copied into a web page: the HS code list runs to thousands of entries, the valid units depend on the code, and rates depend on the sale type and sometimes the province.
Bizio Invoicing reads those from FBR directly rather than from a list maintained by hand. If you need to understand the relationships between them, the guide to HS codes and units covers the ones that trip people up.
Sources and review
- Technical Specification for DI API v1.12 (PRAL), linked from FBR's Digital Invoicing technical assistance page: province reference (section 5.1), rate lookup (section 5.8) and the buyer and province invoice fields (section 4).
- Verified in the document: codes 7 (Punjab) and 8 (Sindh), which are the two rows its sample response prints; the Registered and Unregistered registration types; province names in the invoice and a province ID in the rate lookup.
- From Bizio Invoicing's integration, not the printed sample: the remaining province codes. They are the values our software uses for the same reference, and the same ones the invoice form sends. Confirm them against the live reference for your own token before relying on them elsewhere.
Checked by the Bizio Invoicing team on 2 October 2026. Published for convenience, not as an authority — where a filing depends on one of these values, FBR's current documentation is the thing to check. To report an error, contact us.
Frequently asked questions about provincial codes
- What is the FBR provincial code number for Punjab?
- The numeric province code for Punjab in FBR's Digital Invoicing province reference is 7. It is the value sent as the province ID when PRAL's rate lookup (SaleTypeToRate) is queried.
- What is the provincial code number for Sindh?
- The numeric province code for Sindh in FBR's Digital Invoicing province reference is 8. Both 7 (Punjab) and 8 (Sindh) appear in the sample response printed in PRAL's API specification v1.12.
- What is the provincial code number for Khyber Pakhtunkhwa (KPK)?
- Bizio's FBR integration uses 6 for Khyber Pakhtunkhwa, the value from FBR's province reference API. The printed specification sample shows only Punjab and Sindh, so confirm other provinces against the live reference for your own token.
- What is the provincial code for Islamabad Capital Territory?
- Bizio's FBR integration uses 5 for Capital Territory (Islamabad), the value from FBR's province reference API. It is a Digital Invoicing reference ID, not a postal or dialling code.
- When should I use the province name versus the numeric state code?
- The invoice itself carries province names in the sellerProvince and buyerProvince fields. The numeric code is used when querying PRAL's SaleTypeToRate reference, which takes the supplier's province as an ID.
Read next
Ready to file your first invoice?
Tell us your business name and registration number and we will set up your account. You start in sandbox mode, so nothing is filed for real until you are ready to switch to production.
WhatsApp +92 339 4453223 · bizio.official1@gmail.com