it is working but with some a little deviation in reporting
in screenshot you will see what is my original invoice values and what are reported. difference is little but i think it should be rectified
in screenshot you will see what is my original invoice values and what are reported. difference is little but i think it should be rectified
Yes, this issue arises due to differences in rounding behavior between Manager and the FBR Invoice.
That’s why creating a similar invoice manually through the FBR Portal is essential — it helps us understand how the portal calculates all the values, especially taxes and totals. This way, we can align our conversion logic accordingly and ensure consistent results.
From the screenshot you shared, it seems we may need to apply
RoundDownfor theSalesTaxApplicablevalue. However, this is still just a guess — the best approach remains creating a similar invoice manually via the FBR portal to confirm how the system calculates the values.
Support for Withholding Tax (WHT) has been included from the beginning. @khurram_Shahzad is currently testing it.
1 Like
at manual portal system is not accepting Value of Sales Excl. ST in decimals. i checked through fbr iris portal which is currently used for invoices when i entered 77,288.13 it only accepted and corrected to 77,288
Good, this confirms what is stated in the Guide, that the data type for SalesTaxApplicable is indeed an integer.
Based on what you’ve shared, I suspect we need to apply RoundDown when calculating the SalesTaxApplicable value.
The WHT implementation has successfully passed verification testing by @khurram_Shahzad.
@khurram_Shahzad, could you please test the Withholding Tax (WHT) using an invoice that contains more than one item? The WHT amount is distributed proportionally to each item based on its net amount.
We will use the following approach to calculate taxes:
-
WHT, ExtraTax, and FurtherTax will be calculated using standard rounding to 2 decimal places.
* SalesTax and FED Payable will be calculated using round down with no decimal places (integer values only). -
SalesTax and FED Payable will be calculated using round down to 2 decimal places.
Ok let me test and I will share the results soon.
2 Likes
I am getting this same error again.
Withholding tax is validated but there is something I noticed. In FBR JSON the value of withheld tax is being calculated on tax excluding value instead on total value of the invoice.
"quantity": 1,
"totalValues": 11005,
"valueSalesExcludingST": 11005,
"fixedNotifiedValueOrRetailPrice": 0,
"salesTaxApplicable": 1980,
"salesTaxWithheldAtSource": 605.28,
Actually withholding tax amount should be (11005+1980)*5.5/100 = 714.18
But it is calculating value on ex value
11005*5.5/100 = 605.28
@Mabaega please check this.
Thank you for sharing your business data.
The error was not caused by WHT, but by the SalesTaxApplicable field. I had previously applied an incorrect rounding method, and have now reverted it to decimal mode with round down to 2 decimal places.
As for the WHT calculation, it remains unchanged: it is still calculated based on the Net Amount before Sales Tax, multiplied by the WHT rate.
Could you please verify this invoice directly on the portal?
I noticed a possible difference in how the WHT is calculated.
It seems Manager uses (Amount + Sales Tax) × WHT Rate,
whereas the extension currently applies the WHT Rate to the net amount before Sales Tax.
"items": [
{
"hsCode": "5205.1200",
"productDescription": "Abc",
"rate": "18%",
"uoM": "KG",
"quantity": 1,
"totalValues": 11005,
"valueSalesExcludingST": 11005,
"fixedNotifiedValueOrRetailPrice": 0,
"salesTaxApplicable": 1980.9,
"salesTaxWithheldAtSource": 605.28,
"extraTax": 0,
"furtherTax": 0,
"sroScheduleNo": "",
"fedPayable": 0,
"discount": 0,
"saleType": "Goods at standard rate (default)",
"sroItemSerialNo": ""
},
{
"hsCode": "5208.1200",
"productDescription": "Fabric",
"rate": "18%",
"uoM": "Meter",
"quantity": 1,
"totalValues": 11005,
"valueSalesExcludingST": 11005,
"fixedNotifiedValueOrRetailPrice": 0,
"salesTaxApplicable": 1980.9,
"salesTaxWithheldAtSource": 605.28,
"extraTax": 0,
"furtherTax": 0,
"sroScheduleNo": "",
"fedPayable": 0,
"discount": 0,
"saleType": "Goods at standard rate (default)",
"sroItemSerialNo": ""
}
]
1 Like
Do we need to use this “Pakistan FBR.manager”? or other method FBR Extension 25.07.09.004
I am on latest server version and I dont see any option to upload extension, so I dont know how to use Pakistan FBR.manager
You can try both methods and choose whichever suits your requirements.
Please note that the FBR Extension is still in SandBox mode and not recommended for Production use yet.
There are still several components, such as ExtraTax and FED Payable, that require further testing.
1 Like
ok, i will use it for testing only, but still , how can i upload extension? theer is no such option in settings>extension
do i need to upload it to server directly ?
Check this integration guide https://fbrextension.azurewebsites.net/
1 Like
I was talking about this, how to use that?
If you’re referring to the business data mentioned above, it means you’re using the FBR Extension (https://fbrextension.azurewebsites.net/).
To try it out, you just need to create a new Business Database following the guide provided on the website above.
2 Likes
I would like to clarify a common point of confusion that seems to be recurring — particularly in response to @Khurram_Shahzad’s recent remarks.
Sales Tax Withheld at Source (STWHT) and Income Tax Withholding (WHT) are two entirely different concepts :
- Sales Tax Withheld at Source typically refers to 1/5th or 1/10th of the applicable sales tax, which is withheld by government clients when making payments. This is relevant to FBR digital invoicing and should be reportedin the relevant salesTaxWithheldAtSource field.
- Income Tax Withholding (commonly 4.5% or 5.5%) is a separate tax on the gross invoice amount under Income Tax Ordinance, and does not need to be reported in FBR’s e-invoicing system .
It’s important to distinguish these when working with digital invoices to ensure compliance and correct reporting.
Hope this clears up the confusion.
1 Like
In order to align the WHT calculation between the Manager invoice and the FBR invoice, it is necessary to avoid using the WHT Type set to “Rate”. Instead, the WHT should be manually calculated based on the Amount before Sales Tax, and the WHT Type should be set to “Amount”.
===
"items": [
{
"hsCode": "5205.1200",
"productDescription": "Abc",
"rate": "18%",
"uoM": "KG",
"quantity": 1,
"totalValues": 11005,
"valueSalesExcludingST": 11005,
"fixedNotifiedValueOrRetailPrice": 0,
"salesTaxApplicable": 1980.9,
"salesTaxWithheldAtSource": 605.27,
"extraTax": 0,
"furtherTax": 0,
"sroScheduleNo": "",
"fedPayable": 0,
"discount": 0,
"saleType": "Goods at standard rate (default)",
"sroItemSerialNo": ""
},
{
"hsCode": "5208.1200",
"productDescription": "Fabric",
"rate": "18%",
"uoM": "Meter",
"quantity": 4,
"totalValues": 60000,
"valueSalesExcludingST": 60000,
"fixedNotifiedValueOrRetailPrice": 0,
"salesTaxApplicable": 10800,
"salesTaxWithheldAtSource": 3300,
"extraTax": 0,
"furtherTax": 0,
"sroScheduleNo": "",
"fedPayable": 0,
"discount": 0,
"saleType": "Goods at standard rate (default)",
"sroItemSerialNo": ""
}
]
exaclty iam telling the same this withholding tax is income tax withholding which different what fbr needs that one is sales tax wht which is 1/5th of gst
Here it’s amount should be based on sales tax applicable*1/5
10800*1/5 = 2160
3300 is incorrect.
As per @uzair94 clarification.
@Mabaega please confirm your understanding.
In my view, there should be a simple checkbox option at the customer or invoice level within the extension labeled something like:
“Customer Deducted Sales Tax Withholding” — Yes/No .
Once this is checked, the system should automatically:
- Determine the applicable rate (either 1/5th or 1/10th of the sales tax), based on preset conditions or configurations.
- Calculate and populate the salesTaxWithheldAtSource field accordingly.
This will greatly ease the process for businesses dealing with government clients, where STWHT is a regular occurrence, and will help ensure accuracy and compliance during FBR invoice submission.