How to connect your POS to FBR digital invoicing

Connecting a point of sale system to FBR digital invoicing takes five steps: put your sales tax registration and NTN in order, obtain an integration token from the FBR portal, map every product to an HS code, unit of measure, sale type and tax rate, pass FBR's sandbox scenarios, then switch to live submission. Businesses using already integrated software do the first and third steps only.

Step 1. Get your credentials and registration in order

You need an active sales tax registration and your NTN, plus your login for the FBR portal. If your registration details are out of date, for example an old business address or a changed name, fix that first. FBR checks the seller details on every invoice, and a mismatch here causes rejections later that are hard to diagnose.

Step 2. Obtain an integration token

FBR issues a token that identifies your business to its system. Every invoice you submit carries this token. If you are building the integration yourself, you request it from the FBR portal. If you use ready software, the setup screen walks you through generating it and pasting it in once. You keep this token private, the same way you would treat a password.

Step 3. Set up your products and tax rates

This is the step that decides whether your first week is smooth or painful. FBR wants each line item mapped to the correct HS code, unit of measure, sale type and tax rate. For anything on a reduced rate or an exemption, it also wants the SRO schedule and item number. Get this right in your product list once, and every invoice after that fills itself in. A few pointers:

• Use the real HS code for the product, not a close guess.
• For standard-rate goods, the sale type is straightforward and no SRO is needed.
• For third schedule or reduced-rate items, note the SRO details from your tax consultant and store them against the product.

Step 4. Test before you go live

FBR provides a sandbox, and good software provides a validation mode. In both, an invoice is checked and returns the same errors it would in real life, but nothing is filed. Send a handful of invoices that cover your common cases: a standard sale, a reduced-rate item, a walk-in customer with only a CNIC, and a registered buyer with an NTN. Fix whatever comes back. Most errors at this stage are a wrong buyer registration type or a missing code, and they are quick to correct once you see the message.

Step 5. Switch to live and watch the first invoices

When your test invoices come back clean, move to live submission. Watch the first day or two closely. If a real invoice is rejected, the FBR response tells you why in plain terms, for example that the buyer's registration type does not match their profile. You correct the field and resubmit. After a short settling-in period, submission becomes background noise you stop thinking about.

Build it yourself, or use software

If you have a developer, you can talk to the PRAL API directly. Budget time for token handling, the JSON payload format, retry logic for dropped connections, and keeping up with FBR's format changes. If you would rather not maintain that, use software that already handles submission, the QR code, error messages and record keeping. For a business that just wants compliant invoices at the counter, the software route is usually the better use of time.

General information, not tax advice. Your obligations depend on the FBR notifications for your sector.