Skip to content
POS and retail

What Belongs on a Compliant FBR Receipt

IRN, QR code, FBR logo, tax breakdown — a field-by-field checklist for what a legally valid FBR-compliant receipt or invoice must actually show.

Sources: 2

The three non-negotiable elements

Whatever your industry (pharmacy, school, retail counter), an FBR-verified receipt carries three things: an FBR invoice reference number (IRN, roughly 22 characters), a QR code, and the FBR Digital Invoicing logo. Ask your tax advisor which fields apply to your sales, since a document missing one of them may not count as a valid invoice.

Our FBR Compliance Hub has the primary-text references. If your current receipt template does not carry all three, it needs work.

Tax fields: rate, amount, price base

Beyond the three headline elements, a compliant invoice needs to show its tax math clearly: the applicable tax rate, the tax amount charged, and the price base the tax was calculated on. That last part matters more than it sounds — for certain categories (3rd-Schedule goods like many pharmaceuticals, for instance), tax is calculated on a declared retail price rather than the actual sale price, and a receipt that doesn't reflect the correct price base is one of the most common sources of downstream rejection. We cover this specific failure mode in our guide to fixing FBR error 0102.

Buyer information: when it's required, and when it isn't

Whether a receipt needs the buyer's NTN or CNIC depends on the transaction type and whether the buyer is registered for sales tax — this is one area where a single blanket rule doesn't hold across every sale. Business-to-business invoices to registered buyers typically carry more identification detail than a walk-in retail or clinic sale to an individual customer. Rather than assume one field requirement covers every transaction your business runs, confirm the current rule for each of your actual sales patterns — a mixed-model business (say, a pharmacy selling to both walk-in customers and institutional buyers) may legitimately need different receipt detail for different sales in the same day.

Item-level detail: codes, description and quantity

Every line item on a compliant invoice needs enough detail for FBR's validation to check it against the applicable tax treatment — typically a PCT or HS code, a clear description, quantity, and unit price. This is where generic invoicing templates built for a different market often fall short: a line item that just says "service" or "item" with no code attached is exactly the kind of gap that produces a rejection with no obvious explanation.

Common template mistakes that cause rejections downstream

Common template mistakes that lead to rejections:

  • Missing or placeholder product/service codes — a line item with no PCT/HS code, or a copy-pasted code that doesn't match the actual item.
  • Price-base mismatches — invoicing at the sale price when the tax should be calculated on a declared retail price (3rd-Schedule goods especially).
  • Incomplete buyer fields — missing NTN/CNIC where the transaction type actually requires it.
  • A self-generated QR code — the QR must come from FBR's validated response for that specific invoice, not from a template your own system produces independently. A QR that does not verify against FBR's system is a real problem, not a cosmetic defect; see our guide on verifying an FBR invoice QR code.

A printable pre-launch checklist

Before your invoicing template goes live, confirm each of the following against a sample invoice:

  1. IRN present and correctly formatted
  2. QR code present and generated as part of FBR's validated response
  3. FBR Digital Invoicing logo displayed
  4. Tax rate, tax amount, and correct price base shown per line item
  5. Product/service code (PCT/HS) present on every line
  6. Buyer identification fields correct for the transaction type
  7. Quantity and unit price clearly itemized

Run a handful of real invoices — not test data — through this checklist before you fully switch over, across the actual range of transactions your business handles.

Where Aboha fits

Tasdeeq by Aboha is live today: each counter receipt carries its FBR invoice number and QR code at payment. Aboha Digital Invoicing is coming soon and will check each sales-tax invoice against FBR rules before sending it.

If you'd like your current invoice or receipt template reviewed against this checklist, contact us and we'll walk through it together.

Frequently asked questions

Is a handwritten receipt ever still legal?

For sales-tax-registered persons in scope of digital invoicing, the expectation is that the receipt comes from the digital invoicing process, carrying the FBR invoice number and QR code, rather than a handwritten or generic printed slip. Ask your tax advisor how this applies to your business.

Does every receipt need the buyer's NTN?

Requirements differ for registered vs. unregistered buyers and by transaction type. Confirm the current field requirements for your specific sales pattern rather than assuming one rule fits every sale.

Sources

  1. FBR Digital Invoicing FAQs
  2. SRO 69(I)/2025 — legal root, Section 50 Sales Tax Act 1990 + Chapter XIV Sales Tax Rules 2006

This article is informational and is not tax or legal advice. Confirm your specific obligations with FBR or your tax advisor.

Related reading

Back to the blog

Check how FBR integration applies to you

Book a demoWhatsApp us