PRAL as a Licensed Integrator: What Merchants Should Know

Rule 150XF introduced through S.R.O. 69(I)/2025 provides that PRAL acts as a licensed integrator for specified Chapter XIV purposes and provides free-of-cost integration services to registered persons on demand.

FBR’s Digital Invoicing User Manual presents API integration through PRAL or another licensed integrator. Another integrator may charge fees. Verify the current list and selection in the taxpayer’s portal rather than relying on a vendor statement.

The PRAL route described in the manual includes taxpayer and technical details, business nature and sector, hosting and IP information, sandbox credentials, assigned scenario testing and production access after successful testing.

A merchant still needs product and buyer mappings, an approved invoice trigger, Shopify extraction, exception handling, invoice rendering, reconciliation and staff training. Paid software can solve those commerce tasks without changing PRAL’s regulated role.

The taxpayer should control portal access and know which party stores tokens, uses whitelisted IPs and handles support. Document the route and check it after vendor or infrastructure changes.

Before opening the portal, collect the registered person’s legal and contact data, nominated technical contact, actual system-provider details, cloud or on-premises model, stable outbound IPs, business nature and sector. Have the tax adviser approve the business selections because they determine which sandbox scenarios are relevant.

After submission, retain screenshots or exports of the selected route, approval status, sandbox endpoint details and assigned scenarios without exposing tokens. Build test payloads from controlled sample orders, record every response and have tax, operations and technical owners sign off before production.

Know where PRAL or FBR support cases are raised and which merchant email receives replies. A software vendor can help diagnose payloads, but the taxpayer should remain able to view and pursue its integration case. Record case numbers beside affected invoices.

When changing software, hosting or outbound IP, ask which portal and PRAL steps must be repeated. Do not assume the existing token and approval automatically cover a different technical route. Run regression scenarios and a controlled production check after an approved change.

Keep a current contact sheet for merchant, PRAL or integrator, software, accounts and adviser escalation, including an alternate contact for leave or staff turnover.

Review that sheet during each access review and after any provider, employee or registered-person detail changes.