I’d also like to hear opinions from users…
We have 722 SRO Item Serial Numbers — would it be better to display all of them in a combo box to help prevent typing errors by users?
perfect idea but SRO are continuously updated
Mine are not automatically created. Please send me sample business file
Failed to convert to FBR format: HTTP 400: Bad Request - {“errors”:{“invoiceData”:[“The invoiceData field is required.”],“lines[0].taxCode.reportingCategory”:["Error converting value "8421c3d7-43fd-48c1-bac0-33c119b3996f" to type 'FBRExtension.Models.Mana
Iam getting this error
Can you show the Invoice Edit Form where this error occurred?
Also, please share the Edit Form of the Tax Code you created.
Select the Sale Type on the Tax Code you are using.
In the future, users will be expected to set up their own Tax Codes according to their specific needs. The default Tax Codes may be removed from the business template data.
As for Tax Categories, it seems there will be changes on Manager’s side, so we will not be using them in the FBR Extension.
@Ealfardan, should we remove all Tax Codes and Tax Categories from the Business Template Data for Pakistan?
I suggest that Pakistan use Multiple Rate Tax Codes to accommodate Extra Tax and Further Tax.
Let start with this
Pakistan FBR.manager (40 KB)
@Mabaega Great the system works in the file you provided. however when testing in my live system it is not working the extension is picking hs code but not copying that to fbr json kindly see screenshots for help.
Hi @Mabaega,
Sorry for my lag in response. I was attending a family funeral.
Anyway, I need to examine this file
Which I can do the day after tomorrow.
I think we could use feedback from Pakistani users such as @uzair94, @Syed_Salman_Ali and @Khurram_Shahzad as well. That’d be very useful.
That could work, however, we need to understand how Extra Tax and Further Tax work. Are they codified and known?
If not then these tax codes will have to be the responsibility of users, or isn’t it?
I have taken a look and it looks good. This way, we don’t have to overcomplicate things with an extensive list of mostly unused tax codes with unnecessarily verbose names.
So I guess this would be true
But how can we pick out Extra Tax and Further Tax?
We only currently have the Account field to systematically distinguish tax components. Does this mean that we need to create a separate account for each type of tax? i.e. Tax Payable, Extra Tax Payable and Further Tax Payable
You need to fill in the HS Code and UoM on the Inventory Item, as it seems that HS Code and UoM are tied to the item itself.
I’ve displayed them on the invoice line so that they can be shown in the Invoice View, but the data is still sourced from the Inventory Item fields.
I will add logic so that if HS Code or UoM is not found on the Inventory item, it will fallback to using the values provided on the Invoice Line.
Could anyone share a sample JSON file of an invoice that was created manually through the PFBR portal?
I am specifically looking for examples that include:
-
ExtraTax
-
FEDPayable
I’d like to understand how these taxes are represented and how they are calculated within the invoice JSON structure. Any clarification or examples would be highly appreciated.
Thank you!
i am out of station right now, as soon as i get any system i’ll update
sorry but in my business we dont use extra tax or further tax so. will not be able to help in this matter
great idea let me know when you have updated it then i will try
{
“success”: false,
“data”: {
“dated”: “2025-07-23 14:37:55”,
“validationResponse”: {
“statusCode”: “01”,
“status”: “Invalid”,
“errorCode”: null,
“error”: “”,
“invoiceStatuses”: [
{
“itemSNo”: “1”,
“statusCode”: “00”,
“status”: “Valid”,
“errorCode”: “”,
“error”: “”
},
{
“itemSNo”: “2”,
“statusCode”: “01”,
“status”: “Invalid”,
“errorCode”: “”,
“error”: “DUPLICATE INVOICE EXISTS”
},
{
“itemSNo”: “3”,
“statusCode”: “01”,
“status”: “Invalid”,
“errorCode”: “”,
“error”: “DUPLICATE INVOICE EXISTS”
},
{
“itemSNo”: “4”,
“statusCode”: “01”,
“status”: “Invalid”,
“errorCode”: “”,
“error”: “DUPLICATE INVOICE EXISTS”
},
{
“itemSNo”: “5”,
“statusCode”: “01”,
“status”: “Invalid”,
“errorCode”: “”,
“error”: “DUPLICATE INVOICE EXISTS”
},
{
“itemSNo”: “6”,
“statusCode”: “01”,
“status”: “Invalid”,
“errorCode”: “”,
“error”: “DUPLICATE INVOICE EXISTS”
}
]
}
},
“message”: “Validation failed, please review the server response for details”
}
got this error i think system is not accepting multiple items invoice
one more thing i noticed that UOM is binded to hs codes i think we need to feed those binding lists into system so to avoid confusion
Please make sure to add the UoM and HS Code to the Inventory Item. These values will then be automatically populated on the invoice line when the item is selected.
I cannot determine the cause of the error you encountered without reviewing both the Manager Invoice JSON and the corresponding FBR Invoice JSON. You need to ensure that the data entered in Manager is accurate and complete.
If you are still receiving an error message, I recommend creating an invoice manually in the FBR Portal. This will help you verify whether the invoice created in Manager is valid or if there is an issue with the conversion process from the Manager invoice format to the FBR format.
You are having this error because you may be selecting same item on multiple lines.
In my testing I received the same error in case of selecting same items on multiple lines.