FBR POS integration is one of those topics where the available information is either a legal document nobody can read or a vendor promising it is "fully handled." Here is a practical explanation of what it is, what it means operationally, and the one question that matters most when choosing software in Pakistan.
What it is
The Federal Board of Revenue operates a system for electronic reporting of point-of-sale invoices. Where it applies, each invoice you issue carries an FBR invoice number and a QR code, and is reported to the FBR's system — so a client can verify their invoice, and the FBR sees sales as they happen rather than reconstructed at year end.
Whether it applies to you
We are going to be honest rather than helpful-sounding here: we cannot tell you whether your salon is currently obliged to integrate. It depends on your business category, tier and turnover, and the rules change.
Confirm your position with the FBR or your tax advisor. Be sceptical of any vendor — us included — who tells you what the law requires of your specific business. Vendors know software. Your tax advisor knows your obligation.
What we can tell you is what integration means once it applies to you, and what to look for in software.
What it means day to day
Done properly, almost nothing changes for the person at the counter. They bill as they always have. The invoice number and QR code appear on the receipt automatically. The invoice reports itself.
Done badly, compliance becomes a second system: bill in one place, re-enter in another. That is where the errors, the wasted hours and the discrepancies come from — and it is entirely avoidable.
The question that actually matters
Ask any vendor selling you an FBR-integrated POS this: "What happens when the internet goes down?"
In Pakistan this is not hypothetical. Load-shedding and ISP outages are routine. A cloud-only POS has a genuinely bad answer, because two things break simultaneously:
- You cannot bill. The client is standing there. The queue is building. It is 7pm on Saturday.
- You cannot report. Compliance is now also broken.
An offline-safe POS separates the two. Billing is local: receipts print, the queue moves, business continues. Invoices queue and report to the FBR automatically on reconnect. You lose neither the sale nor the compliance.
This is the difference between software designed for Pakistan and software designed elsewhere and sold here.
What to look for
| Requirement | Why it matters |
|---|---|
| Integration inside checkout | No second system, no re-entry, no divergence between your books and your reporting |
| Offline-safe billing | Outages stop neither sales nor compliance |
| Automatic queued reporting | Nothing forgotten, nothing double-sent |
| One source of truth | What you report and what your Trial Balance says come from the same transaction |
| Per-branch handling | Groups need per-branch reporting with consolidated visibility |
| Local support | When something breaks at 8pm Saturday, a ticket queue in another time zone is not an answer |
The hidden benefit
There is an upside worth naming. Salons running a POS for compliance and a separate book for management always end up with two versions of reality, and spend real effort reconciling them.
When your POS runs a genuine double-entry engine, what you report to the FBR and what appears on your Balance Sheet are the same transaction viewed two ways. Compliance stops being a tax on your time and becomes a by-product of keeping proper books — which you should be doing anyway.
Where TressyPOS sits
FBR POS integration is included in every plan, built into checkout, on an offline-safe engine, backed by full double-entry accounting, supported from Faisalabad on WhatsApp. Whether you need it today is a question for your tax advisor. Being ready when you do costs you nothing.