The new rule changes how integration investments are documented
Businesses subject to mandatory integration with the Federal Board of Revenue often make substantial investments in specialised software, electronic devices, interfaces and production-monitoring equipment. Implementing a system requires more than buying a computer or signing a subscription: the business may need to configure software, connect its transactional data, verify transmission and commission the connection with FBR's systems. Section 64D of the Income Tax Ordinance, 2001 recognises certain eligible investments through a tax credit. The Finance Act 2026 substituted the section, broadening the earlier focus on point-of-sale machines to mandatory electronic integration for specified reporting or monitoring purposes.
On 26 October 2026, FBR issued S.R.O. 1904(I)/2026 inserting Rule 33U into Chapter VIIA of the Income Tax Rules, 2002. This is the final rule following consultation through draft S.R.O. 1692(I)/2026. The rule does not merely provide administrative guidance: it specifies eligibility conditions, evidence of activation, permitted cost components, expenses to exclude, the correct claim year and information to be supplied on the income-tax return or an IRIS schedule.
Begin with the legal duty, not the technology invoice
Rule 33U(1)(a) requires that the person be required under the Income Tax Ordinance, the Sales Tax Act, 1990 or the Federal Excise Act, 2005 to integrate with the Board's computerised system. The integration must concern real-time production monitoring or recording or reporting sales or receipts. Purchasing an enterprise resource planning platform for ordinary accounting purposes does not by itself establish the condition. Even a software package advertised as FBR-compatible is insufficient without a relevant statutory integration duty affecting the claimant.
The appropriate starting document is therefore the notification, order or statutory rule making integration obligatory for the particular business. Counsel should identify the person to whom the obligation attaches, the covered transactions or production facilities, the regulatory timetable and the system in which the required data must be transmitted. Where a corporate group uses a central technology provider, the applicant and the person legally required to integrate may differ. The contract, tax registrations, invoices and system record should consistently identify the proper taxpayer.
Successful installation within the tax year matters
Sub-rule (1)(b) requires the resource to be acquired, installed or implemented and successfully installed, integrated and configured with FBR's computerised system in the relevant tax year. Sub-rule (4) places the claim in the income-tax return for that year. A project commissioned after year-end may therefore present a different timing question from one for which the supplier was paid before year-end. Procurement, payment, testing and successful activation are separate events and should not be treated as interchangeable.
Businesses should use contractual milestones to record software delivery, configuration, successful integration testing and final go-live confirmation. If the same project covers multiple branches or systems brought online on different days, the finance team should identify the resource and supporting activation date for each relevant component. The rule also prohibits claiming the same expenditure more than once under section 64D. Internal tax schedules should use consistent identifiers to prevent a second claim for an already credited resource.
Direct and exclusive use is a strict boundary
Rule 33U(1)(c) states that the relevant equipment, hardware, software or electronic component must be used directly and exclusively for required integration. A dedicated fiscal interface or monitoring device may meet this test more readily than a general accounting system that serves payroll, inventory, sales forecasting and other functions. The extent of ordinary commercial use is therefore central to the legal characterisation of the asset, not just to the accountant's allocation of cost.
Rule 33U(3)(d) provides a limited route for separately identifiable components of general-purpose systems that are dedicated exclusively to the integration. For example, a documented and separately priced integration connector may warrant distinct analysis even when installed within a larger business platform. By contrast, assigning an arbitrary percentage of the cost of an entire enterprise system is difficult to reconcile with the language of the rule. Procurement documentation should distinguish dedicated resources at the outset and preserve their technical specifications.
Which one-time costs can be included
Rule 33U(2) includes acquisition or purchase price and one-time amounts directly attributable to installing, configuring, developing interfaces, integrating, testing and implementing the electronic resource, insofar as necessary to bring it into operation for the mandatory integration. It recognises that software deployment may involve an identifiable implementation project beyond purchase of a licence. The test is whether the expenditure was necessary and directly attributable, not whether the supplier chose to call it an integration fee.
A vendor invoice should therefore show individual components and deliverables. A separately billed dedicated software licence, implementation work required to configure FBR data exchange and testing directly connected with successful activation may be distinguishable from consultancy on the company's wider financial systems. Where the supplier provides a bundled price, the company should seek substantiated allocations rather than make unsupported estimates after filing its return. Records should demonstrate what was actually acquired, what it was used for and when it became operational.
What the final rule expressly excludes
Sub-rule (3) requires the investment base to be reduced by discounts, rebates, refunds, grants and subsidies received or receivable in respect of the resource. Any tax or duty refundable, adjustable or recoverable by the taxpayer is also excluded. Operating expenses, routine maintenance, repairs, annual maintenance, post-commissioning support and recurring service charges are not eligible expenditure for this purpose. Internet, telecommunications, utility costs, salaries, training, consumables and financing costs are likewise excluded.
These distinctions can make an appreciable difference. An initial contract may include installation and one year of software support; the existence of one invoice does not make every charge a qualifying one-time investment. Likewise a later supplier rebate may reduce the relevant amount. Businesses should record gross cost, any recoverable tax, each reduction and the final eligible base separately. The legal review should expressly test the categorisation of recurring services and components with mixed commercial functions.
A system-confirmed activation record is essential
Rule 33U(1)(d) requires an integration, activation, commissioning or configuration record generated or confirmed by the computerised system of FBR. The record must identify the taxpayer, electronic resource and date of activation. A vendor's letter reporting that development is complete may support the factual history, but it should not automatically be substituted for evidence generated or confirmed by the regulator's system. The distinction prevents a project from being claimed solely on the strength of internal implementation statements.
During the project handover, management should request the resource identifier and the available FBR acknowledgement or system confirmation. If the technology provider manages the integration on behalf of the taxpayer, the contract should require delivery of this evidence. Resource identifiers, activation dates and the identity of the registered taxpayer should then be reconciled across FBR records, vendor certificates, invoices and the eventual IRIS claim. Missing information should be resolved before the return is submitted.
Prepare a single evidential file before filing
Rule 33U(1)(e) requires tax invoices, bills, agreements, licences or other acquisition documentation, evidence of payment or liability where applicable, and such other evidence as reasonably establishes the amount actually invested. Rule 33U(5) requires details in the return or an IRIS schedule, including the resource description, vendor information, invoice or agreement reference, date of acquisition or implementation, invested amount, integration or resource number and activation or commissioning date.
An effective compliance record combines the legal instrument imposing the integration obligation, internal purchase approval, supplier contract, separately stated invoices, proof of payment, technical configuration record, FBR system confirmation, and the allocation schedule used in computing the claim. Each should tell the same story. Inconsistencies in dates or descriptions may undermine an otherwise legitimate claim. The files should remain accessible to the tax team even if the software vendor or implementation personnel later change.
Illustrative calculation and its limitations
Consider a company that incurs Rs 800,000 for a dedicated fiscal integration licence, Rs 350,000 for one-time interface development and configuration, and Rs 150,000 for equipment used exclusively for the mandatory integration. It also pays Rs 120,000 for annual support, Rs 40,000 for staff training and Rs 30,000 for internet connectivity. Assuming the statutory conditions are met, the example has a potentially eligible investment base of Rs 1,300,000 before discounts, grants and recoverable taxes. The prescribed ten-percent section 64D rate produces an illustrative credit of Rs 130,000.
This does not mean that Rs 130,000 is an unrestricted refund or that a claim is automatically allowed. Section 64D itself governs computation and application against the relevant normal tax, and Rule 33U(6) explicitly requires computation under section 64D(2), (3) and (4). Taxpayers must apply the operative statutory text to their actual return, check whether conditions concerning normal tax affect utilisation, and establish the investment amount through documents. A hypothetical example cannot determine the allowable result for an individual taxpayer.
Claim risks and verification by the Commissioner
Sub-rule (6) provides that the Commissioner may verify the claim against records maintained under section 174. The most obvious audit issues include a disputed statutory duty to integrate, missing system-confirmed commissioning evidence, shared-use hardware, costs incorrectly described as one-time expenditure, timing differences between invoice and activation, and duplicate expenditure recorded in different tax years. Related-party contracts and services procured through a group technology company may require additional proof of which person acquired the qualifying resource.
Any response to a tax authority's query should address the relevant element of Rule 33U directly and identify the evidence supporting it. General statements that a business invested in digital transformation are not a substitute for compliance with the rule's precise conditions. The tax team should preserve a reconciled resource schedule and a written explanation of the classification of each material cost, especially where a component is part of a wider system.
What businesses should do now
Companies facing mandatory FBR integration should first identify every operative requirement affecting their premises or reporting activities. They should then prepare a register of integration assets, separate dedicated hardware and software from multi-use systems, confirm activation through the FBR platform and reconcile supplier documentation with the tax-year return. Contracts for new implementations should call for itemised billing and delivery of system-generated activation records as express handover obligations. Routine support, training and ordinary connectivity should be tracked separately.
The notified Rule 33U offers a detailed framework but not a blanket incentive for any technology expenditure. The sustainable approach is to prove the statutory duty, the successful and timely integration, direct and exclusive resource use, and a correctly calculated one-time investment base. S.R.O. 1904(I)/2026 should be read with section 64D as amended and any later operative instruments before a claim is filed. This publication describes the law as verified on 28 October 2026 and does not substitute for advice on a particular return.
When the issue arises in practice.
We examine the applicable rule, integration records and expenditure schedule against the actual circumstances.
DISCUSS THIS MATTERThis publication is general information, not legal advice on any particular matter.
Read the current governing law and subsequent amendments. How we prepare legal commentary ↗