FBR e-invoicing is already in force for the sales-tax-registered categories covered by S.R.O. 1852(I)/2025. The phased rollout ended on 31 December 2025, so those dates are completed compliance milestones, not deadlines still approaching in 2026.
The covered categories were required to register, test their connection through PRAL or an approved licensed integrator, and begin issuing structured electronic sales tax invoices by the date assigned to them. An integrated person also has a tight correction window: a bona fide invoice error can be cancelled, deleted, or edited through FBR's system within 72 hours of generation; a later change requires prior approval from the concerned Commissioner Inland Revenue.
Confusion persists because FBR's online FAQ still cites the original dates from S.R.O. 709(I)/2025. That schedule did not remain the final position. A June extension intervened, S.R.O. 1413(I)/2025 introduced a later phased timetable, and S.R.O. 1852(I)/2025 expressly superseded S.R.O. 1413. A current compliance assessment should therefore start with the later notification and subsequent operating orders, not an older FAQ answer or a software provider's summary.
For a finance team, the immediate questions are practical: which S.R.O. 1852 category covers the registered person, which approved connection route is being used, whether invoice data is produced in FBR's structured format, and who owns real-time submission, reconciliation, rejection handling, and corrections.
Which FBR deadline applies, and why older dates still appear
The apparent deadline conflict is a version-control problem. S.R.O. 709(I)/2025 set the initial integration dates, and FBR later allowed more time in June. S.R.O. 1413(I)/2025 then introduced a phased schedule. The governing rollout notification, S.R.O. 1852(I)/2025, expressly superseded S.R.O. 1413 and replaced its timetable.
That sequence matters because FBR's digital-invoicing FAQ still displays the S.R.O. 709 dates of 1 June 2025 for corporate registered persons and 1 July 2025 for non-corporate registered persons. Those dates explain what a searcher may find, but they are not the final category schedule.
S.R.O. 1852 assigned separate dates for registration, testing, and issuance. All of them have now passed:
| Category of registered person | Registration completed by | Testing completed by | Electronic invoices required by |
|---|---|---|---|
| Public companies | 15 October 2025 | 25 October 2025 | 1 November 2025 |
| Companies other than public companies with turnover above PKR 1 billion | 15 October 2025 | 25 October 2025 | 1 November 2025 |
| Importers | 15 October 2025 | 25 October 2025 | 1 November 2025 |
| Companies other than public companies with turnover above PKR 100 million and not above PKR 1 billion | 25 October 2025 | 31 October 2025 | 15 November 2025 |
| Companies other than public companies with turnover not above PKR 100 million | 15 November 2025 | 25 November 2025 | 1 December 2025 |
| Individuals and associations of persons with turnover above PKR 100 million | 10 October 2025 | 25 October 2025 | 1 November 2025 |
| Registered persons not listed above | 10 December 2025 | 25 December 2025 | 31 December 2025 |
For the turnover-based categories, the notification uses turnover declared in sales tax returns for the preceding twelve months. A business should not select a row from its legal form alone when turnover or importer status changes the category.
The FBR FAQ is useful for definitions and practical explanations, but its own disclaimer says it is a ready reference rather than a legal document. It also states that the Sales Tax Act, 1990 and Sales Tax Rules, 2006 prevail if there is a contradiction or error. For an FBR e-invoice deadline extension question in 2026, the defensible approach is to preserve the older dates as history and apply S.R.O. 1852's later, superseding timetable.
Who is covered and what counts as an FBR electronic invoice
S.R.O. 1852 applies through defined categories of sales-tax-registered persons. It directs the persons in its table to register, complete integration testing through PRAL or a licensed integrator, and issue electronic invoices by the assigned dates. Public-company status, importer status, legal form, and turnover declared in the preceding twelve months all affect where a registered person falls.
The table should not be paraphrased into a broader claim that ignores those distinctions. Where registration status, turnover measurement, or category overlap is uncertain, the notification and FBR's current legal material should be checked against the business's facts, with professional advice where needed.
Coverage is only half of the requirement. The invoice itself must be electronic in substance, not just appearance. FBR defines it as a tax invoice created digitally in a specified, structured format. Copying or scanning a paper invoice, saving it as a PDF, or photographing it does not make it an electronic invoice under the FAQ's definition.
This distinction separates two different records:
- The structured invoice data sent to FBR contains the fields and classifications used by the digital-invoicing system.
- A PDF or printed rendering is a human-readable representation that a customer or AP team may retain, review, or match to the supply.
The broader principles in how structured e-invoicing differs from a PDF invoice explain why a digital file is not necessarily a compliant structured invoice. In the FBR regime, the decisive questions concern the specified data format, the approved connection, and transmission to FBR's computerized system.
The settled sales-tax mandate should also remain separate from S.R.O. 288(I)/2026, which was identified during research as proposed amendments concerning online integration under the Income Tax Rules. Without a later final instrument establishing those amendments, draft material is not a sound basis for expanding the obligations described here.
PRAL, licensed integrators, manual entry, and the FBR API
The registered person remains responsible for compliance even when another party configures the connection. Its finance and systems teams must produce the correct invoice data, complete the applicable testing, control production access, and respond to rejected or incorrect submissions.
PRAL is itself a licensed integrator. FBR's FAQ says PRAL provides integration services free of cost on demand, while other licensed integrators may charge for configuration and integration. A provider's licence status should be checked in FBR's live list of licensed integrators, not in a static vendor list copied into an implementation plan. Sales Tax General Order 01 of 2026 also permits a registered person to engage one or more FBR-approved or notified licensed integrators wherever required.
FBR's current digital-invoicing user-manual page links to a manual whose integration screen shows two modes: API Integration and Manual Invoice Generation. The existence of the manual-generation option does not establish that it is suitable or sufficient for every taxpayer, transaction volume, or system environment. A business considering it should confirm the applicable process with FBR, its tax adviser, or an approved integrator.
For API integration, the business selects a licensed integrator and provides technical details for its ERP or invoicing system. The PRAL route includes sandbox testing. In that environment, the taxpayer submits scenario-based invoice data for the selected business nature and sector; successful testing leads to production access. The implementation is therefore more than connecting an endpoint: tax scenarios, reference data, field mappings, and exception responses must be tested against the business's actual supplies.
FBR's technical specification describes real-time sharing of structured invoice data through a Web API. Developers should use the current FBR digital-invoicing technical documentation for object models, sandbox scenarios, validation methods, reference data, security requirements, and error codes. Copying endpoints or sample payloads into a general compliance guide would create a version that can drift from the live specification.
“FBR e-invoicing software” is therefore not the name of one downloadable FBR application. The FAQ says there is no downloadable software. A covered business uses an ERP, POS, invoicing system, or the officially available manual mode as applicable, with the required approved integration arrangements confirmed for its circumstances.
Controls finance teams need after go-live
Technical acceptance does not prove that an invoice is commercially or tax-correct. FBR's DI specification describes invoice-data sharing as real-time through its Web API, but the source transaction, buyer details, item classification, values, and tax treatment still originate in the business's systems and processes.
Timing is a finance control, not merely an integration setting. FBR's FAQ states that digital invoices are issued at the statutory time of supply: the earlier of receipt of payment or delivery of goods, as provided by section 2(44) of the Sales Tax Act, 1990. A batch process that waits for month-end or a later accounting event can therefore transmit accurate data at the wrong time.
The same FAQ says a digital invoice is required for all sales reported in Annexure-C of the sales tax return. Its answer covers local and export sales within that reporting population rather than treating exports as outside e-invoicing by default.
A workable control design connects the FBR response to the accounting record:
- Reconcile the FBR-assigned invoice reference to the sales ledger and the source order or dispatch record.
- Retain submission, validation, and rejection responses with the related invoice record.
- Route rejected or incomplete submissions to a named owner and monitor them to resolution.
- Restrict changes to buyer registrations, HS codes, units of measure, tax rates, and other master data that shape the payload.
- Compare digital-invoice totals and counts with Annexure-C and investigate differences before filing.
On the buyer side, an FBR reference should not replace invoice validation controls before payment. AP should still confirm the legal supplier, invoice reference, invoice and supply dates, buyer identity, taxable value, tax treatment, quantity, and duplicate risk against the underlying order, receipt, contract, or other evidence of supply.
The 72-hour rule for correcting an electronic invoice
FBR's Sales Tax General Order 01 of 2026 allows an integrated person to cancel, delete, or edit a valid electronic sales tax invoice generated because of a bona fide mistake through FBR's computerized system within 72 hours from its generation. After that period, the cancellation, deletion, or edit requires prior approval from the concerned Commissioner Inland Revenue, in the manner and subject to the conditions FBR specifies.
The clock runs from generation, so a business needs the FBR timestamp rather than an informal estimate based on when a user noticed the error. The correction process should identify an accountable reviewer, escalate errors as soon as they are detected, preserve the original and corrected invoice references, and record what made the mistake bona fide.
Not every commercial change is simply a data-entry correction. FBR's FAQ points to debit or credit notes under section 9 of the Sales Tax Act, 1990 where an issued tax invoice must change because a supply was cancelled, goods were returned, the nature or value of the supply changed, or another event altered the amount reportable in the invoice or return. Finance teams should classify the event before choosing an edit, cancellation, debit note, or credit note path.
The March 2026 order also addresses complex implementations: a registered person may engage one or more licensed integrators approved or notified by FBR wherever required. Using multiple integrators does not remove the need for one correction log and a consistent control owner across every channel.
Match each implementation task to the right FBR source
FBR's materials serve different purposes. A compliance file should identify which source supports each decision instead of treating the first search result as authoritative for everything.
| Task | First-party source | What to use it for |
|---|---|---|
| Confirm the statutory framework | FBR digital-invoicing legal provisions | Locate the Act, Rules, integration instruments, and related legal material; read this with the later S.R.O. 1852 timetable and the March 2026 order cited above. |
| Classify the registered person and final rollout date | S.R.O. 1852(I)/2025 | Apply the category, turnover basis, and completed registration, testing, and issuance dates. |
| Verify a provider's current licence | FBR's licensed-integrator directory | Check the live FBR list rather than a vendor's claim or an archived comparison. |
| Follow registration screens and route selection | FBR digital-invoicing user manual | Review the IRIS flow, integration modes, licensed-integrator selection, and sandbox setup presented in the current manual. |
| Build and test the API connection | FBR digital-invoicing technical assistance | Obtain the current object models, validation methods, reference APIs, scenarios, and error codes. |
| Check plain-language definitions and operating answers | FBR digital-invoicing FAQ | Use the explanations for orientation, while respecting its disclaimer and checking legal claims against governing instruments because its enforcement dates are obsolete. |
The implementation owner can turn that source hierarchy into a short action sequence:
- Classify the registered person under S.R.O. 1852 using legal form, importer status, and the applicable turnover measure.
- Confirm the required invoice and integration route against current FBR material and qualified professional advice where the facts are uncertain.
- Assign separate system and finance owners for configuration, source-data quality, submission monitoring, ledger reconciliation, and corrections.
- Complete the applicable registration and testing steps, using the live technical specification rather than copied API details.
- Document time-of-supply controls, Annexure-C reconciliation, rejection handling, buyer-side validation, and the 72-hour correction escalation.
Invoice Data Extraction
Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.
Related Articles
Explore adjacent guides and reference articles on this topic.
Sri Lanka Tax Invoice Format: 2026 VAT Checklist
Current Sri Lanka tax invoice format requirements for VAT-registered businesses, including the 1 July 2026 date, mandatory fields, and AP checks.
IR330C Form Explained: NZ Contractor Tax Notification
What the IR330C tax rate notification for contractors is, who fills it in, how the withholding rate choice works, and why it goes to the payer, not IRD.
Denmark Digital Bookkeeping for Foreign VAT-Registered Firms
Compliance paths for foreign VAT-registered businesses under Denmark's Bookkeeping Act: registered Danish systems, self-certification, OIOUBL, penalties.