← Back to articles

Invoice format

Sales Tax Invoice Format in Pakistan: A Field-by-Field Guide

Understand the seller, buyer, invoice and line-item fields that belong in a controlled sales tax and digital invoice workflow.

Understand the seller, buyer, invoice and line-item fields that belong in a controlled sales tax and digital invoice workflow.

Start with four data groups

A useful invoice format separates seller details, buyer details, the invoice header and line items. The official API model includes seller NTN/CNIC, business name, province and address; buyer identification, name, province, address and registration type; invoice type, date and reference; and detailed item values. A printable invoice is the human-facing record, while the structured payload is the machine-facing record. They should reconcile.

Seller and buyer details

Store controlled seller details at company or branch level instead of retyping them. For buyers, capture the identity and status supported by the transaction. FBR's FAQ specifically discusses NIC or NTN for certain supplies by a manufacturer or importer to an unregistered distributor. An API field that can technically be blank does not remove a transaction-specific legal requirement.

Invoice header controls

Use a permanent internal invoice number, a valid invoice date, the correct document type and a related reference where an adjustment requires it. Do not reuse a number after a failed transmission. Keep internal status, validation status and the external FBR result separate so staff can see whether a record was never sent, rejected, pending or accepted.

Line-item controls

Each item needs a clear description and the relevant classification, unit, quantity, value and tax treatment. The published API model contains HS code, product description, rate, UOM, quantity, value excluding sales tax, applicable tax, withholding, extra or further tax, discount and conditional SRO fields. Not every field applies to every transaction, but every populated value should have a source.

Design for review and printing

Use labels that finance staff and customers can understand. Show amounts consistently, preserve the returned invoice identifier and provide QR output only from confirmed response data. Before finalizing a template, compare it with current official requirements and test it with ordinary, multi-item, discounted and adjustment transactions.

Official sources and review note

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

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.

sales tax invoice format PakistanFBR invoice formattax invoice required fieldsdigital invoice template Pakistan
Chat on WhatsApp