What is FBR Digital Invoicing?

Under statutory notifications issued under the Sales Tax Act, 1990 (including S.R.O. 1525(I)/2023 and subsequent directives), the Federal Board of Revenue (FBR) in Pakistan introduced digital electronic invoicing. Specified categories of registered persons—including Tier-1 retailers, manufacturers, and fast-moving consumer goods (FMCG) distributors—must integrate their point-of-sale and ERP platforms directly with FBR's computerised systems.

Rather than filing aggregate monthly sales returns (Annexure-C) weeks after the period closes, businesses transmit itemized sales transaction data electronically in real time or near real-time.

How the Digital Invoicing Workflow Operates

A compliant digital invoicing process consists of four sequential stages:

  1. Invoice Generation in ERP: The sales team or ecommerce pipeline confirms a commercial sale, detailing customer NTN/CNIC, registered address, HS codes, items, quantities, unit prices, sales tax rates, and further tax/withholding amounts.
  2. Pre-Flight Validation: Before dispatching the HTTP API payload to FBR/PRAL, the ERP validates every data element against statutory schemas, verifying active tax filer status, allowable Units of Measure (UOM), nearest-rupee rounding, and applicable SRO schedule definitions.
  3. API Submission & Invoice Number Assignment: The ERP signs and submits the JSON payload to FBR's Digital Invoicing endpoint. Upon successful receipt, FBR returns a unique Digital Invoice Number and security verification data.
  4. Printing & QR Code Generation: The sales invoice displays the FBR-assigned unique registration number and an encrypted QR code containing cryptographic verification parameters for end-buyer inspection via the Tax Asaan mobile application.

The Cost of Post-Submission Rejections

In legacy systems with bolt-on converter tools, invoices fail at the FBR gateway due to minor discrepancies (e.g. invalid UOM codes or unregistered NTNs). These rejections invalidate delivery notes, delay trucks at provincial check posts, and create reconciliation mismatches between internal ledgers and tax records. Novus ERP solves this by enforcing live validation prior to API submission.

Critical Schema & Tax Configuration Requirements

1. NTN and CNIC Format Verification

Corporate buyers require a 7-digit NTN plus a 1-digit check number (XXXXXXXX-X). Individual retail buyers without an NTN require a valid 13-digit Computerized National Identity Card (CNIC) number where required by the Sales Tax threshold regulations.

2. Standardized Units of Measure (UOM)

FBR specifies precise alphanumeric keys for units of measure (e.g., KGS for kilograms, MTR for meters, NOS for numbers). Custom organizational units (such as 'bag' or 'bale') must be strictly mapped to canonical FBR UOM dictionaries.

3. SRO Schedules & Concessional Rates

Items subject to concessional rates (e.g., under Fifth, Sixth, or Eighth Schedules, or special industrial export schemes) require explicit SRO identifiers. Transmitting an invoice with a reduced tax rate without a matching valid SRO code causes immediate system rejection.

Component Regulatory Requirement Novus ERP Implementation
Validation Timing Zero tolerance for schema errors at gateway Client-side pre-flight check before API call
FBR Invoice ID Mandatory on customer delivery document Stored directly in sales invoice header record
Audit Storage Complete transaction history for audit Raw JSON request and response payloads stored permanently
Tax Calculations Exact rounding per statutory schedules Nearest-rupee rounding calculated at line and document boundary