Most of what gets written about FBR digital invoicing focuses on the invoice itself: what fields it needs, how the QR code works, what the tax rate rules are. There is a quieter requirement that sits underneath all of that and has nothing to do with invoices at all: the connection between your system and FBR has to come from a fixed, known internet address.
What "static IP" actually means here
A normal home or small business internet connection is usually dynamic, your router gets handed a different public IP address from time to time, sometimes every time it reconnects. A static IP is the opposite: an address that stays the same permanently, assigned specifically to your connection by your internet provider. FBR and PRAL require your submissions to come from one of these fixed addresses, not a rotating one.
Why FBR insists on it
Before your system can post a single invoice, that fixed address has to be registered and whitelisted on FBR's side. This is a security control as much as a technical one: FBR wants to know in advance exactly which network a given business's traffic will come from, rather than accepting API calls from anywhere on the internet. Once whitelisted, requests from that address are trusted as belonging to your registered integration. Requests from anywhere else are not.
Where to get one
A static IP is a product your internet service provider sells, it is not something FBR issues you, and it is not automatically included with a normal broadband or fibre connection. In Pakistan this typically means a business or dedicated internet plan through a provider like PTCL, Storm Fiber, Transworld, or Fiberlink, rather than a standard home package. If you are not sure whether your current connection already has one, that is the first question to put to your ISP, some business-grade plans include a static IP by default, others require requesting it as an add-on.
Where this fits in the integration timeline
Get this sorted early, before sandbox testing rather than after. The static IP has to be whitelisted with FBR/PRAL as part of setting up your integration, and that whitelisting is a step with its own turnaround time. Businesses that leave it until they are ready to go live often find it is the one piece still pending after everything else, the invoice data, the product catalogue, the tax mapping, is already working.
What happens if your IP changes
If your connection loses its static assignment, gets migrated to a new address by your ISP, or you switch office locations and providers, submissions will start failing even though nothing about your invoicing setup itself has changed. This is a common cause of a previously working integration suddenly breaking, and the fix is administrative rather than technical: re-register the new address with FBR/PRAL and wait for it to be whitelisted again.
One less thing to configure yourself
Invoices go out from AxiomSquare's own servers, so you are not the one buying a static IP or managing a connection to FBR. Your business still needs its own FBR credentials, but the networking side is ours to handle.
See AxiomSquareGeneral information, not tax advice. Confirm current integration requirements with FBR/PRAL or your tax consultant.