Guide

Sales tax invoice, explained field by field

What has to be on a valid sales tax invoice, why each field exists, and a worked example showing how the numbers actually come together.

By FBR Invoice Atsolhive Team · Updated July 15, 2026 · 5 min read

The required fields

A valid sales tax invoice needs, at minimum: the seller's NTN and STRN, the buyer's registration details (if registered), an invoice number and date, a description of each item sold, the HS code and quantity per item, the value excluding sales tax, the sales tax rate and amount per item, and the final total including tax. Missing any of these is usually enough to cause a validation failure on submission.

Why the HS code drives everything else

The HS code assigned to each item determines its sales tax rate, and in some cases whether further tax, withholding tax, or an SRO-specific exemption applies. Get the HS code right, and the rest of the tax calculation follows automatically; get it wrong, and every downstream number on the invoice is wrong too, even if the arithmetic itself is done correctly.

A worked example, with numbers

Example: A wholesaler sells 200 units of an item with a value (excluding tax) of PKR 500 per unit, under an HS code that carries an 18% standard sales tax rate. The value excluding tax is PKR 100,000. Sales tax at 18% is PKR 18,000. The final invoice total is PKR 118,000. If that same item actually fell under a 17% or 15% category due to a misassigned HS code, every one of those downstream numbers would be incorrect — not because of a math mistake, but because of the code assigned at the very first step.

Registered vs. unregistered buyers

A sale to a registered business buyer needs that buyer's NTN and registration type captured accurately on the invoice — this is what allows the buyer to claim input tax where applicable. A sale to an unregistered or walk-in customer doesn't need those details, but still needs the same accurate tax calculation on the seller's side.

Where these invoices usually go wrong in practice

In manually prepared sales tax invoices, the most common failure points are an HS code assigned from memory rather than looked up, a buyer NTN transposed or outdated, and a tax rate applied uniformly across a mixed order when different line items actually carry different rates.

FAQs

Frequently asked questions

The NTN (National Tax Number) is a business's general tax identifier; the STRN (Sales Tax Registration Number) specifically identifies sales tax registration status, and both typically appear on a compliant sales tax invoice.
Yes — the HS code per item is what determines the correct tax rate, and it's expected as part of a properly structured sales tax invoice.
Each line item is taxed according to its own HS code and rate; the invoice total reflects the sum of those individually correct amounts, not one blanket rate applied to everything.
In Pakistan's regulatory context, yes — a sales tax invoice specifically needs to meet FBR's structured requirements (HS codes, tax breakdown, registration details) that a generic invoice format doesn't automatically include.
Yes, but the buyer-registration fields simply won't apply; the seller still needs to calculate and record the correct tax.
It can trigger a rejection during FBR submission if caught immediately, or surface as a discrepancy during later reconciliation or audit if not.
In a properly built digital invoicing platform, yes — the HS code, tax rate, and totals are calculated automatically once the item and buyer are selected.

Ready to stop doing this by hand?

Get started and see FBR Invoice Atsolhive handle it for your business.