FBR e-Invoicing 2026: Every Pakistani Restaurant's SRO 288 Survival Guide

# FBR e-Invoicing 2026: Every Pakistani Restaurant's SRO 288 Survival Guide

If you run a restaurant in Pakistan and you haven't yet wired your POS into PRAL — you're already late.

SRO 288(I)/2026 is here, FBR has started field audits in DHA Karachi and Gulberg Lahore, and the days of paper-strip thermal receipts are officially over. Every sales-tax-registered restaurant now has to push every single sale, in real-time, into PRAL — Pakistan Revenue Automation Limited's e-invoicing system. No exceptions, no "we'll do it next quarter."

We've spent the last six months building InvoiceSync, an FBR-compliant invoicing terminal for Pakistani restaurants. In that time we've talked to dozens of owners — from karahi joints in Tariq Road to fine-dining spots in F-7 — and the same three questions keep coming up. This post answers all of them, in detail, with no compliance jargon.

The short version: every Tier-1 retailer and every sales-tax-registered restaurant must transmit each tax invoice to PRAL at the moment of sale, receive a unique IRN (Invoice Reference Number) back, and print a verifiable FBR QR code on the customer's receipt.

The long version is in the SRO itself, but here are the parts that actually matter for your day-to-day operation:

1. Real-time only. Batch uploads at end-of-day are not compliant. Each invoice must be posted before the customer leaves with a printed receipt.

2. Cancellations have a 72-hour window. If you need to void or amend an invoice, you have 72 hours to do it through PRAL. After that, the invoice is locked.

3. The IRN must appear on the printed receipt. Along with the FBR QR code that the public can scan to verify the invoice on FBR's portal.

4. Connectivity failures don't excuse you. If PRAL is down, you queue and retransmit — but the FBR system still expects to receive that invoice within the SLA.

We've seen the audit notices being issued in Karachi over the last three months. Here's the real picture:

We've personally seen a mid-size BBQ joint in Bahria Town hit with PKR 1.8M in penalties for 60 days of non-compliant invoicing. They thought "we'll integrate next month" — six weeks later, the field officer arrived.

PRAL provides free integration to "registered persons" under Rule 150XF. If you have an in-house dev team, this works. But understand what you're signing up for:

If your CTO is sitting idle and your dev team has nothing else to do, this is the cheapest option in raw rupees. It is not the cheapest option in opportunity cost.

Pakistan has a small set of FBR-licensed integrators. They charge per-invoice or per-restaurant fees, and they handle the PRAL complexity for you. The downsides: most of them give you a basic invoicing API and nothing else — you still have to build your own POS, your own customer experience, your own payment integration, your own audit dashboard.

Here's what we built for our pilot restaurant: a single terminal where the cashier rings up the order, the GST math is automatic, the invoice posts to PRAL behind the scenes in under 2 seconds, the receipt is generated with the FBR QR + a Raast P2M payment QR, and the whole thing lands on the customer's WhatsApp before they've stood up to leave.

We did this because the restaurants we talked to didn't want a "PRAL integration." They wanted a working tax-invoice terminal that happened to be FBR-compliant. That's a very different product.

Regardless of which path you choose, run through this checklist with your accountant on Monday morning:

1. Confirm your STRN and NTN are active in FBR's portal. Restaurants that registered years ago and haven't filed lately sometimes find their STRN has been suspended.

2. Confirm your business is correctly classified — restaurants fall under specific provincial sales tax + federal sales tax on services rules. If your tax filings have been misclassified, fix it before PRAL onboards you.

3. Pick your tax rate. Most restaurants in Punjab, Sindh, and Islamabad fall under 16-17% GST on food services. If you're claiming a reduced rate, document the basis.

4. Audit your menu pricing. PRAL submissions include item-level GST. If your prices are "tax-inclusive" without itemization, you'll need to re-decompose them at the POS layer.

5. Get your customer phone number capture process right. WhatsApp delivery is increasingly expected, and customer phone numbers feed into the FBR submission as well.

6. Plan for offline mode. What happens when PRAL is down or your internet drops? Your POS must queue invoices safely and retry — without printing receipts that will later fail to post.

Below is the same merchant terminal our pilot restaurant uses every night. Click around, ring up an order, watch it post to FBR, see the dual QR generate, send it on WhatsApp. This is the actual product — sample data, real flow.

If you're a restaurant owner reading this on a Sunday night and quietly panicking — first, take a breath. The path forward is well-trodden. Second, book a free consultation with us. We'll review your current POS, your STRN status, and your operational flow, and tell you honestly whether you need InvoiceSync, a different integrator, or just a better accountant.

The only wrong move now is doing nothing. FBR has been clear. The audits are happening. The penalties are real. But so are the tools, and the deployment timelines are measured in days, not months.

Try the InvoiceSync demo above or send us a WhatsApp — we'll show you the same terminal that's posting invoices to PRAL every night in Karachi, right now.