If you are setting up FBR digital invoicing for your business, you will encounter the term "PRAL Technical Specification V1.12" repeatedly. This document is the technical foundation of Pakistan's entire digital invoicing system — and understanding what it covers will help you choose the right software and avoid the most common compliance mistakes.
PRAL stands for Pakistan Revenue Automation Limited. It is a subsidiary of FBR responsible for building and maintaining the technology systems that power Pakistan's tax administration — including the digital invoicing gateway that every compliant business must connect to.
When your invoicing software submits an invoice to FBR, it is actually communicating with PRAL's servers. PRAL built the gateway, defined the data format, and maintains the technical specification that all software must follow.
PRAL Technical Specification V1.12 is the formal technical document that defines exactly how every digital invoice must be structured and submitted to FBR's gateway. Think of it as the rulebook — if your invoice does not follow this specification precisely, it is rejected regardless of how accurate your commercial data is.
Version 1.12 is the current version as of 2025. FBR updates the specification periodically as the system evolves, which is why your invoicing software must be kept current. Using software built on an older version of the specification is a common cause of rejections.
PRAL Technical Specification V1.12 covers every technical aspect of digital invoice submission:
Every invoice must be submitted as a JSON (JavaScript Object Notation) data packet. The specification defines the exact field names, data types, and character limits for every piece of information in the invoice. There is no flexibility here — a field named incorrectly or a value exceeding the character limit causes rejection.
The specification lists every mandatory field. These include seller NTN, buyer type, buyer NTN (for registered buyers), invoice date and time, invoice number, line items with HS codes and quantities, tax rates, and totals. Missing any mandatory field results in rejection.
One of the most important parts of the specification is the definition of 28 invoicing scenarios. Each scenario covers a specific combination of transaction type, buyer type, and tax treatment. Your software must correctly identify which scenario applies to each transaction and include the correct scenario ID in the invoice.
The specification maps every HS code (product classification code) to a specific approved Unit of Measure. Submitting an invoice with a UoM that does not match the approved UoM for the HS code is one of the most common rejection reasons. The specification covers all 8,521 HS codes in FBR's system.
The specification defines precisely how tax must be calculated and rounded for each line item and for the invoice total. FBR's system recalculates the tax independently and compares it to your submitted figures. Any discrepancy — even a rounding difference of one rupee — causes rejection.
Every invoice must have a unique sequential number within your NTN. The specification defines the format this number must follow. Reusing an invoice number — even for a corrected version of a rejected invoice — causes rejection.
Invoice timestamps must be in a specific format and must fall within a defined window relative to the submission time. Invoices with timestamps that are too old or inconsistent with the submission time are rejected.
The specification defines how software must authenticate with PRAL's gateway using API credentials issued by FBR. These credentials include an API token and seller ID. The specification covers the authentication header format, token validation, and how to handle authentication failures.
The specification defines two gateway endpoints — sandbox for testing and production for live submissions — and documents every response code FBR's system can return. Understanding these response codes is essential for diagnosing and fixing rejections.
FBR updates the PRAL Technical Specification as Pakistan's digital invoicing system evolves. Each version may add new scenarios, change field requirements, update HS code mappings, or modify validation rules. Software built on an older version may pass validation for some invoices but fail on others — particularly if you are dealing with product categories or scenarios that changed between versions.
As of 2025, V1.12 is the current required version. Always verify that your invoicing software explicitly states which version of the PRAL Technical Specification it implements.
Panther FBR Enterprise V10.1 is built on PRAL Technical Specification V1.12 in full. Every aspect of the specification is implemented directly in the software:
Most importantly, Panther FBR Enterprise validates every invoice against the full specification locally before sending it to FBR. If anything does not comply with V1.12, you see a plain explanation of what is wrong and what to fix — before FBR ever sees the invoice.
Download the 7-day free trial at fbr.pecsglobal.com or WhatsApp us at +92 307 3812493 to ask about your specific setup.