S.R.O. 1852(I)/2025 Explained for Pakistani Businesses

S.R.O. 1852(I)/2025 is an FBR notification issued under section 50 of the Sales Tax Act, 1990 read with sub-rule (2) of rule 150Q of the Sales Tax Rules, 2006. It directs specified sales-tax registered persons to complete registration and testing for integration of their hardware and software through a licensed integrator or PRAL and to issue electronic invoices by category-based dates.

The crucial drafting point is that it says it is issued in supersession of S.R.O. 1413(I)/2025 dated 1 August 2025. That means a deadline article based only on S.R.O. 1413 is not the final 2025 timetable. Earlier S.R.O. 709(I)/2025 is also part of the historical rollout, but it should not be used in isolation to determine a current deadline.

The table separates registration, testing and issuance. Registration is the administrative and technical enrolment step. Testing is the sandbox process used to prove the assigned scenarios. Issuance is the date by which the category must issue electronic invoices. A screenshot that shows one date without its column heading can easily mislead an operations team.

For each date, preserve the whole row and column from the official PDF. Do not copy a date from a social post into a project plan. Confirm what FBR treated as completion of registration and testing for your selected integrator, because submitting an application and obtaining an approved or successful status are not necessarily the same event.

The notification’s table includes public companies; companies grouped by turnover declared in sales-tax returns for the preceding twelve months; importers; specified individuals and associations of persons; and registered persons not listed above. Some characteristics can overlap. For example, a company may also be an importer, so category selection should not be guessed from a single label.

Give your adviser the legal form, importer status and a twelve-month sales-tax return summary. Ask for a written category conclusion and which row controls if more than one description appears relevant. This is especially important where turnover is near a boundary or returns have been amended.

S.R.O. 69(I)/2025 created the licensing framework in Chapter XIV and expressly provides for PRAL to act as a licensed integrator. FBR’s Digital Invoicing User Manual describes a choice between PRAL and another licensed integrator. The merchant then supplies technical details, completes IP whitelisting and performs scenario-based sandbox testing through the applicable process.

Do not confuse the licensed-integrator selection with the software interface your staff will use. Your Shopify connector may prepare and transmit orders while the licensed integrator fulfils the regulated integration role. Ask for an architecture diagram showing the merchant, Shopify, software provider, licensed integrator or PRAL, and FBR.

The timetable does not map Shopify products, determine whether a buyer is registered, decide the correct rate, resolve COD invoice timing or clean customer addresses. Nor does it determine whether your business should have been registered under a different provision. Those are legal, tax-data and operational tasks around the notification.

It also does not make every online summary reliable. FBR FAQs and third-party explainers can be useful, but if dates conflict, read the supersession language in the official instrument and check for any later SRO, Sales Tax General Order, amendment, court order or clarification.

First, confirm category and dates. Second, nominate the merchant’s tax and technical owners. Third, select the licensed-integrator route and secure portal access. Fourth, map products and buyer data. Fifth, whitelist stable outbound IPs. Sixth, pass each assigned sandbox scenario. Seventh, obtain production credentials and run controlled live tests.

Finally, reconcile daily and keep a failure queue. The legal milestone may be a date, but compliance becomes a recurring operation. Staff changes, new products, altered tax treatments and infrastructure deployments can all break a connection that worked on launch day.

A Shopify merchant should translate the notification into observable controls: which orders qualify, when an invoice is triggered, which fields are sourced from Shopify, which mappings come from tax configuration, where the FBR result is stored and who handles a rejection. If you cannot answer those questions, “integration complete” is premature.

Use the official PDF as the source for scope and dates, your adviser for application to your facts, and the FBR technical material for API behaviour. Use ComplyStream’s Shopify guide to understand the commerce workflow. None of those sources should silently substitute for the others.

Keep the official S.R.O. 1852(I)/2025 PDF, the adviser’s category conclusion, portal registration status, integrator selection, IP approval, scenario results and production activation record in one controlled folder. Add the people responsible and the dates each step was completed. This evidence is more useful than a chat message saying the integration was “done.”

When a later instrument appears, do not delete the earlier evidence. Record what changed, who reviewed the effect and the date the operating procedure was updated. That history lets accounts explain why a deadline, mapping or workflow used at one time differs from the process used today.