FBR Digital Invoicing for Mobile Phone Dealers & Distributors (SN015, Ninth Schedule)
How mobile phone importers, distributors and shops invoice under FBR Digital Invoicing: scenario SN015, sale type Mobile Phones, the NINTH SCHEDULE reference with alphanumeric serials like 1(A), and the SRO-pairing errors 0077/0078 that reject phone invoices.
Mobile phones have their own sale type
Cellular mobile phones are taxed under the Ninth Schedule to the Sales Tax Act, and FBR's Digital Invoicing sandbox gives them a dedicated scenario: SN015, sale type "Mobile Phones". In PRAL's canonical sample the line carries rate 18%, sroScheduleNo "NINTH SCHEDULE" and sroItemSerialNo "1(A)" — proof that FBR's serial field accepts alphanumeric values, not just plain numbers.
"Mobile" is also a named sector on FBR's Digital Invoicing registration form, and SN015 appears in the required sandbox list for manufacturers, importers, distributors, wholesalers and retailers across sectors. A phone importer or distributor should expect to clear it before the production token is issued.
The rejections phone dealers hit most
Error 0077 — "Valid SRO/Schedule No. is mandatory where rate is not 18%" — and its pair 0078 for the item serial: whenever the schedule reference applies, sroScheduleNo and sroItemSerialNo must both be filled, exactly as FBR's reference APIs spell them. Sending the schedule without the serial (or vice versa) rejects the line.
Error 0052 fires when the HS code does not match the sale type — phone lines belong in HS heading 8517 — and error 0002 rejects malformed buyer registration numbers, which matters because shops often sell to individuals against a 13-digit CNIC. For walk-in consumers the buyer is simply "Unregistered" with the CNIC or a placeholder per FBR's rules, and further tax may apply on top of sales tax for unregistered business buyers.
Who in the phone chain posts what
Importers and official distributors invoice wholesale quantities under SN015 with the Ninth Schedule reference. Retail chains registered as retailers can also see the retail scenarios (SN026 standard rate to end consumers) in their matrix — a phone shop's mixed counter of handsets and accessories can legitimately post different sale types on different lines: the handset under Mobile Phones, chargers and covers as standard-rate goods.
PTA type-approval and DIRBS registration are separate, telecom-side obligations tied to the IMEI — they do not replace the FBR invoice. The sales tax side is the digital invoice with its IRN and QR code; a compliant dealer produces both paper trails.
Practical setup for a phone business
Load each model as a stock item with HS code, sale type Mobile Phones and the Ninth Schedule fields saved once — IMEI or model variant can live in the product description, which FBR accepts as free text and buyers use to match warranties. High unit values make arithmetic errors expensive: 18% of the exclusive value must equal salesTaxApplicable to the rupee, or calculated-tax error 0104 rejects the line.
Digi Invoice ships the Mobile Phones sale type with the schedule pairing enforced, auto-calculates the tax per line, and its pre-post validation catches a missing serial or a wrong buyer registration format before FBR sees the payload — so a counter sale posts in seconds with the QR printed on the receipt.