Everyday Invoicing
The short version
- You can integrate through PRAL or a licensed integrator, and since STGO 01 of 2026, through more than one.
- Judge software by its failure handling — retries, the 24-hour offline deadline, unconfirmed submissions — not by the demo.
- Ask who holds your token and data, where it is stored, and how you get it back if you leave. You must keep records for six years.
- Check it already supports credit/debit notes and advance receipts electronically, required since SROs 1666 and 1667 of 2026.
Your options
To report invoices to FBR you connect to PRAL's digital invoicing API. You can do that through PRAL's own offering, or through software from a licensed integrator — only an integrator with a valid FBR licence may configure a registered person's e-invoicing software. Since STGO 01 of 2026 you may use one or more integrators, which helps businesses running separate systems for different branches or activities.
In a demo, every product sends an invoice and gets a green tick. What separates them is what happens on a bad day. These are the questions to ask.
Reliability: what happens when things go wrong
1. What happens to an invoice when the internet or FBR's server is down?
FBR's own documentation states its system does not retry failed uploads. Good answer: invoices are queued and retried automatically until accepted. Bad answer: "the user resends it".
2. How do you protect us from the 24-hour offline deadline?
Rule 150XC gives 24 hours to transmit invoices raised during an outage. Good answer: undelivered invoices are flagged well before the deadline, by name and by age.
3. What if an invoice is sent but no reply comes back?
The expensive case. Resending blindly can report the same supply twice. Good answer: the invoice is marked unconfirmed and blocked from automatic retry until someone checks IRIS.
4. How do you catch errors before FBR rejects them?
Good answer: invoices are validated against FBR's own error rules — required fields, rate/SRO combinations, arithmetic to the paisa — before sending.
Correctness: getting the tax right
5. Where do rates, sale types and SRO schedules come from?
Good answer: read from FBR's reference APIs for your province and the invoice date, not typed in from memory or a spreadsheet.
6. Do you support credit notes, debit notes and advance receipt invoices?
Required electronically since SROs 1666 and 1667 of 2026. Also ask about federal excise and Islamabad services if they apply to you.
7. How do you help with the 72-hour correction window?
Good answer: every accepted invoice shows how long is left to correct it.
8. Can our month-end return come from the same data?
Good answer: monthly totals grouped by rate, reconciling to the invoices FBR accepted, plus a full export — the cleanest defence against the mismatches FBR's risk system looks for.
Security and ownership
9. Where is our FBR token stored, and who can use it?
Your token lets anyone file invoices under your NTN. It should be stored securely, used only for your filings, and never shared across clients.
10. Is our data in a shared database with other companies?
Shared, multi-tenant systems are common and can be fine — but ask how your data is separated and who at the vendor can see it. A dedicated installation removes the question.
11. How long do you keep our records, and how do we get them if we leave?
Rule 150S(1) requires invoices and FBR responses to be kept for six years. Ask for nightly backups and a full export — database and CSV — on exit.
Getting live
12. Will you take us through the sandbox scenarios to a production token?
FBR won't issue a production token until every scenario for your business activity and sector passes. Good answer: the vendor tells you exactly what to declare in IRIS, loads your products with the right HS codes and units, and works through the scenarios with you. Also ask about the static IP whitelisting your registration requires.
We built our system around these twelve questions: automatic retries, offline-deadline warnings from 18 hours, unconfirmed-invoice protection, pre-send validation, rates read from FBR, a 72-hour countdown, month-end totals by rate, and your own private installation with nightly backups. See what it does.
Khulasa — Roman Urdu
Integrator chunne se pehle sirf demo na dekhein — yeh poochein ke internet band hone par invoice ka kya hota hai, 24 ghante ki offline deadline se pehle warning milti hai ya nahi, aur jab FBR jawab na de to invoice dobara to report nahi ho jati.
Yeh bhi poochein ke aap ka FBR token aur data kahan mehfooz hai, chhe saal ka record kaise rakha jata hai, aur credit/debit notes electronic tor par bante hain ya nahi.
Frequently asked questions
Is PRAL's own e-invoicing option free?
PRAL has offered its route as a free-of-cost option. Licensed integrators charge for software that adds features such as product and buyer records, automatic retries, printing, reports and support.
Can I use more than one integrator?
Yes. Sales Tax General Order 01 of 2026 allows a registered person to use one or more licensed integrators where necessary.
Can my existing ERP be integrated with FBR?
Usually, through a licensed integrator that connects your ERP to PRAL's API. Ask how failures, retries and corrections are handled between the ERP and FBR — that is where integrations break.
Sources and further reading
- Business Recorder — FBR allows registered persons to engage licensed integrators
- Express Tribune — Trader e-invoice deadline extended (licensed integrators and PRAL)
- Faubix — FBR digital invoicing deadlines and notifications
This article explains rules as we understand them on the date shown. It is not tax advice. Notifications change — check the current SRO or general order, and your own position with your tax adviser.
