Product records
HS Code and UOM Preparation for FBR Digital Invoices
Prepare product HS codes, units of measure, quantities, sale types and rates before FBR digital invoicing, with a reusable dealer checklist.
By Digital Invoice PK by Xinuty · Published · Updated
Prepare product data once, then review it on each sale
HS code and UOM preparation is easier before you start a queue of FBR digital invoices. List your regular products and identify who can confirm their classification and tax treatment. An HS code classifies the goods; a stock keeping unit identifies your own product. They serve different purposes.
Digital Invoice PK stores product details including HS code, UOM, rate description and sale type. The invoice form lets you review these values alongside quantity and tax amounts. Use the saved record as a starting point and check it against the transaction.
A checklist for each product
Work through your common products before onboarding. Keep unresolved classification questions on a separate list so an operator does not improvise an answer at the invoice screen.
| Field | Preparation task |
|---|---|
| Product description / SKU | Distinguish the goods actually supplied, including relevant pack size or variant. |
| HS code | Confirm classification using appropriate records and advice. Preserve the confirmed code's formatting. |
| UOM | Confirm the accepted unit used for this product and how your selling quantity converts to it. |
| Sale type and rate | Confirm transaction-specific treatment; do not choose the default only because it is preselected. |
| Other applicable values | Review any retail/notified value, withholding, further/extra tax, FED or SRO information with the responsible person. |
Use reference values without guessing classification
The FBR technical specification includes reference services for units, rates and HS-code/UOM combinations. Ask your onboarding team to check the current accepted values for the products you sell. A value that appears in a reference list still needs to match your goods and transaction.
Do not pick a nearby-looking code solely to clear an error. Keep a record of the classification decision and revisit it when the product changes. A sandbox example is useful for testing the connection, but its HS code is not a recommendation for your inventory.
Official reference: FBR / PRAL: Technical Specification for DI API, version 1.12
Keep quantity consistent with the unit
A common preparation mistake is using the order's pack count with a unit that describes individual pieces. Decide how the sale is measured before calculating its line value.
Separate products that have different treatment
FBR's FAQ explains that different SKUs can share an HS code while differing in sale type and rate. Keep descriptions and line treatment distinct when that applies. Sharing a code is not enough reason to merge two products into one invoice line.
Before validation, compare each line with its product record. Review the description, quantity, UOM, rate and sale type together. If an error names a particular line, correct that line and its source record rather than replacing every product's data.
Official reference: FBR Digital Invoicing FAQs
Official sources and review dates
The links below support the official guidance in this article. Product instructions describe the Digital Invoice PK workflow; examples are illustrative. Check the official material for updates relevant to your business.
- FBR / PRAL: Technical Specification for DI API, version 1.12
The API document linked by FBR's Technical Assistance page when checked. Document last updated 24 July 2025; check FBR for replacements before implementation. Checked .
- FBR Digital Invoicing FAQs
Official explanations of digital invoicing and transaction-specific buyer information. The Sales Tax Act and Rules take precedence over the FAQ. Checked .