Important Update on Sales Tax Invoice Upload in IRIS 2025

Important Update on Sales Tax Invoice Upload in IRIS

Uploading sales tax invoice data into FBR’s Sales Tax Invoice Management System (STIMS) on the IRIS portal has always been a crucial part of tax compliance for registered taxpayers in Pakistan. However, following the Federal Board of Revenue’s (FBR) implementation of a new invoice upload template effective July 1, 2025, many users have been encountering a frustrating and persistent error:

“Invalid – The calculated percentage sales tax does not match.”

Despite ensuring correct values and re-uploading with rounded figures, a vast majority of invoices—sometimes exceeding 90%—are being marked invalid. This article explores the root causes, FBR’s recent changes, the technical implications, and most importantly, how to resolve this issue correctly.

The IRIS portal is Pakistan’s integrated tax administration system, used for income tax returns, withholding statements, and sales tax return filing. For VAT-registered businesses, uploading invoice-level data through the Sales Tax Invoice Management System (STIMS) is mandatory to ensure documentation, transparency, and auditability.

The uploaded data is used for:

• Sales tax return calculations (Form STR)
• Auto-adjustment of input tax for buyers (purchase listings)
• Cross-matching of buyer and seller data
• GST reconciliations

Uploading correct invoice-level details is not just a regulatory requirement but an operational necessity for maintaining the tax chain and avoiding unnecessary notices or penalties.

---

The New Update: FBR’s Revised Template (Effective 1st July 2025)

As of 1st July 2025, FBR silently introduced a new STIMS data upload format applicable to all registered sales tax filers. The update was aimed at standardizing and improving the accuracy of tax computations.

Key Technical Changes Introduced:

1. Mandatory Two Decimal Precision:
   • Both the Value of Goods and the Tax Amount fields must be entered with two decimal places (e.g., 1000.00, 170.50).
   • Rounded figures (e.g., 1000, 171) are now rejected.
2. Validation Against Calculated Tax %:
   • The system now calculates the implied tax rate from the uploaded values.
   • If this implied tax % doesn’t match standard sales tax slabs (e.g., 17%, 16%, 18%) within a strict margin (usually ±0.01%), the invoice is marked invalid.
3. No Rounding Allowed:
   • Rounding off tax amounts or goods value, even by one rupee or less, is now causing validation errors.
   • Previously accepted uploads with approximations (e.g., rounding 169.99 to 170) are no longer valid.
4. Enhanced Validation Engine:
   • FBR’s backend now includes automated reconciliation and flagging mechanisms to detect even minimal discrepancies.
   • This is likely tied to improved AI-based audit and analytics tools implemented by the tax authority in 2025.

---

What This Means:

When you upload invoice data, FBR’s system performs an internal calculation:

Calculated Tax Rate = (Tax Amount / Value of Goods) * 100

It then compares this with the standard tax percentage you selected (e.g., 17%).

Example:

• Value of Goods = 1000.00
• Tax Amount = 170.00

The calculated tax rate is:

(170 / 1000) * 100 = 17%
✅ This will pass validation.

Now consider:

• Value of Goods = 1000
• Tax Amount = 171

Calculated tax rate:

(171 / 1000) * 100 = 17.1%
❌ This will trigger the error.

Even worse:

• Value = 999
• Tax = 171

(171 / 999) * 100 = 17.1171%
❌ Significant deviation – invoice will be rejected.

---

Common Mistakes Being Made by Users:

1. Using Rounded Values from ERP or Accounting Software:
   • Many ERPs like QuickBooks, Odoo, and even Excel templates round figures to the nearest rupee by default.
   • These rounded figures were previously acceptable but no longer pass under new validations.
2. Mismatch in Tax Slabs:
   • For example, mistakenly uploading 17% tax data under the 16% category or vice versa.
   • Even a small mismatch can cause implied tax rate deviation and thus error.
3. Improper Formatting:
   • Not using two decimal points in .csv or Excel uploads.
   • Formatting like 1000 instead of 1000.00 is now invalid.
4. Lack of Awareness of the New Rule:
   • FBR has not issued an explicit circular about this update, so many taxpayers and accountants remain unaware.

---

The Bigger Picture: Why FBR Tightened This?

The changes aim to:

• Eliminate fake, over- or under-invoiced transactions
• Detect and block bogus refund claims
• Streamline buyer-seller reconciliation
• Facilitate upcoming implementation of real-time invoice reporting (E-Invoicing Lite)

By enforcing strict decimal compliance, FBR ensures:

• Higher audit accuracy
• Reduced human error
• Standardized invoice data for analytics

---

Solution:

Step-by-Step Instructions:

1. Export Invoice Data with Decimal Precision:
   • Ensure all invoice exports from your accounting system retain at least 2 decimal places.
   • In Excel or CSV templates, use format:
     =TEXT(A1,"0.00")
2. Avoid Manual Rounding:
   • Never round values manually.
   • If system-generated tax amount is 170.01, do not change it to 170.
3. Cross-Verify the Tax Rate:
   • Confirm that: (Tax Amount / Value of Goods) * 100 = Your Applicable Tax % Use Excel formulas to auto-check this.
4. Validate Before Upload:
   • Create a helper column in Excel for calculated tax rate.
   • Highlight invoices where calculated tax % ≠ expected %.
5. Ensure Consistent Decimal Format in Upload Files:
   • Before uploading .csv, open in Notepad and confirm format like: 12345,Customer A,1000.00,170.00,17
6. Test Upload with 1 Invoice First:
   • Instead of uploading 1,000 invoices and encountering mass rejection, test 1 or 2 for format validation.
7. Adjust ERP Settings (if applicable):
   • Change invoice settings to display and export tax values up to 2 decimal places.
   • If using Odoo or similar, update tax configuration or use precision settings.

---

Additional Considerations (Post-July 2025)

Auto-verification Enhancements:

FBR has introduced auto-verification and input linkage. Your customers may not be able to claim input tax if your invoice is rejected, even for decimal rounding. This impacts:

• B2B trust
• Business relations
• Compliance ratings (in case risk-based audit begins)

E-Invoicing Integration Coming:

FBR is preparing for phase-wise e-invoicing enforcement, where real-time invoice data is pushed to the tax portal. Clean data practices now will ensure your readiness when e-invoicing becomes mandatory.

Avoid Penalties:

Continuous uploading of invalid data could flag your account for non-compliance and result in:

• Audit selection
• Refund delays
• Show-cause notices

---

Real-World Tips from Tax Practitioners

1. Use Power Query or Excel Macros to:
   • Format all numeric columns
   • Validate implied tax % automatically
2. Always keep a backup of original and corrected files with timestamps for audit trails.
3. Log invalid rows after each upload and fix only those instead of uploading all again.
4. Stay updated with IRIS notifications or subscribe to FBR alerts for changes.
5. Use STIMS “Invoice Validation” tool (if available) before final submission.

---

Conclusion

The “Invalid – The calculated percentage sales tax does not match” error has become a major obstacle for thousands of businesses attempting to fulfill their statutory obligations through the IRIS portal. However, the issue is not a bug—it is the result of FBR’s stricter validation logic introduced in July 2025 to improve tax documentation and enforcement.

By ensuring exact two-decimal precision, verifying tax rate calculations, and adjusting your data upload process accordingly, you can eliminate these errors entirely. It’s a small shift in data preparation but a crucial one that protects your compliance, improves refund accuracy, and prepares you for future digital tax reforms.

---

Summary Checklist 🧾

Task	Action
Decimal Precision	Always upload Value of Goods and Tax Amount with two decimal places
Tax Rate Verification	Ensure (Tax Amount / Value of Goods) * 100 = Tax %
Formatting	Use proper numeric formats in Excel/CSV
ERP Settings	Update export settings to maintain decimal precision
Test Upload	Start with a few lines before uploading bulk data
Backup	Maintain version history of upload files

---