'Qurbani Tax' sparks uproar at Bhatta Market
Citizens term tax unprecedented; say no such fee exists at other cattle markets

In a controversial move, the Rawalpindi Cantonment Board (RCB) has imposed an additional two percent tax on buyers purchasing sacrificial animals from the Bhatta Ground cattle market for Eidul Azha. The move has triggered protests and clashes between citizens and contractor staff.
According to details, the cantonment board this year awarded the Bhatta Ground cattle market contract - not just for Eidul Azha but for the entire year - to a large consortium operating under Haji Ismail & Co for Rs3.05 billion. Under the agreement, weekly cattle markets can also be held every Tuesday and Wednesday, while the contract includes a three-year extension clause with a 10 per cent annual increase.
However, for the first time, a clause has reportedly been included in the contract imposing a two percent "sale fee" on buyers purchasing animals for religious sacrifice. Citizens have termed the levy unprecedented, claiming no such tax exists in other cattle markets across Rawalpindi, Islamabad or Punjab.
The tax is allegedly being collected forcibly by contractor staff. Buyers are first congratulated on their purchase and asked the price of the animal. They are then informed that two per cent of the amount must be paid as tax before the animal can be taken out of the market.
Witnesses said arguments often escalate into scuffles and physical altercations. One buyer, Rashid, a resident of Rawalpindi's Gawalmandi area, said he was asked to pay Rs6,000 as tax.
When contacted for comment, contractor partner Mustafa Baloch could not be reached despite repeated attempts. However, Assistant Engineer Naveed Hussain, the cantonment official overseeing the contract, confirmed that Clause 9 of the agreement makes buyers liable to pay the two per cent sale tax and authorises the contractor to collect it.



















COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ