Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Pakistan · South Asia
Sales tax in Pakistan is not one tax with one collector. Tax on goods is federal and filed with the Federal Board of Revenue; tax on services is a provincial subject, and Sindh, Punjab, Khyber Pakhtunkhwa, Balochistan and the Islamabad Capital Territory each levy their own through their own authority, at their own rate, on their own return. A business selling both, across provinces, is filing with several governments on the same month's trading. Our invoice line carries a tax rate and nothing that says which of them it is owed to — and a further provision makes what you charge depend on something we hold nothing about at all.
Where the cost actually lands
The consequence of an unattributed figure is not a wrong invoice. It is what happens at the end of the month.
A business selling goods and services across provinces prepares several returns for one month of trading — federal for the goods, and provincial for the services in each province it operated in. Each return needs the portion of the month that belongs to it.
If the system stores a tax figure without an authority, that split has to be produced some other way: by product category, by customer, by exporting to a spreadsheet and applying rules that live in somebody's head. It is entirely doable and a great many businesses do it. What it is not is reproducible — because the rules that produced last month's split are not written anywhere the system can re-apply.
The failure mode is therefore not an error. It is that the split cannot be re-derived a year later when somebody asks how a figure was arrived at, and the person who knew has moved on.
So the honest framing is that we are usable here and not sufficient on our own. The invoice is right, the ledger is right, and the attribution that turns a month of trading into several returns happens outside the system and stays outside it.
What this costs you in practice
A tax amount that does not record which government it is owed to cannot be grouped into returns by the system that produced it. The number is right and it is anonymous.
When the month-end attribution happens in a spreadsheet, the rules that produced it are not stored anywhere. Next year's question about this year's figure has no answer except whoever remembers.
What you charge can turn on whether your customer is registered and on the active taxpayer list. If there is no field for either, the input to that decision is not merely unchecked — it is unrecordable.
The distinction that decides which government collects is not a category label; it is a constitutional divide. A catalogue that cannot express it cannot route a figure to the right authority.
Running the operation, not filing for it
Pakistani distribution is a genuinely hard operational problem before it is a tax one, and that half of the product has none of the limitations above.
Inventory
Stock across provinces, planned per location
Lead times are set per location rather than nationally, so a warehouse three provinces away is planned on its own clock. Replenishment runs against consumption instead of a fixed reorder point, which is what makes a spread network plannable rather than reactive.
Procurement
Receiving matched at the door, with tolerances
What arrived against what was ordered, with the discrepancy recorded where it happened rather than argued about later from an inbox — which matters most where the distance between the order and the goods is greatest.
Sales
Customer records that hold the account, not just the order
Credit position, history and correspondence against the customer rather than scattered across the people who dealt with them. The gap is named above and named plainly: no tax registration or status field, which in this market is a real one.
Assets
Vehicles and equipment with their intervals attached
What has to be inspected, when it is due, and what was found last time — carried on the asset rather than in a maintenance file that belongs to one person.
Four items, and none of them is Pakistani in any deep sense. They are here because a distribution business across four provinces asks for exactly these things, and because the tax section above should not be mistaken for the whole product.
Scope, in three parts rather than two
Three columns, because "no" means two entirely different things and one list hides which is which. The middle column is work that has not been done and has a price. The right-hand column is work we would decline from a paying customer — and it is the one worth demanding from every other vendor you talk to, because a page without it has not told you where its edges are.
Running in the product today
Not built yet — and commissionable
What we would decline, and would rather say now
The first and fourth rows of the middle column are one piece of work — put a jurisdiction and an authority on the tax figure itself — and the return-splitting problem largely dissolves once a figure knows where it belongs. The goods-versus-services classification is the natural companion and the customer registration fields are small and independent. All commissionable now with a written specification, a timeline and a price; Kenya's eTIMS transmission and our payroll engine are the evidence that we build this way rather than describe it.
Read the middle column against your own situation before concluding. A business selling only goods, only federally, has none of these problems — the invoice is right and the return is one return. The gap widens with every province and every service line you add, which is the honest way to size it rather than a blanket yes or no.
How this starts
Not whether the system supports Pakistani sales tax — ask whether a stored tax amount records which authority it is owed to. It has a yes-or-no answer and it decides whether month-end is a query or a spreadsheet.
Open a customer record and look for somewhere to put a sales tax registration number and an active-taxpayer status. If neither exists, the input to a charging decision is not being stored, and no amount of process fixes an absent column.
For any system already in use, including your own. If the answer is a spreadsheet and a person, ask whether the rules are written down. The exposure is not this month — it is the question asked in eighteen months by somebody who was not there.
Read before you shortlist
Sales tax on goods is federal in Pakistan and sales tax on services is provincial, levied by five separate authorities. So which government a figure belongs to depends on what you sold — and most systems store the amount without storing the answer.
The month-end spreadsheet is usually accurate. The problem is that the rules inside it are not written anywhere the system can apply again — so next year's question about this year's figure has no answer except whoever remembers.
Ask what a stored tax figure knows about its destination — then ask whether the vendor would classify goods versus services for you. The right answer to the second is no, and the first question tells many readers to skip ahead.
Pakistan adds a further 4% when the buyer has no registration number or is not an active taxpayer — and "active" lapses because of a return somebody else did not file. Until 2022 the clause turned only on holding a number, which a checkbox models correctly. One sentence in a Finance Act turned an attribute into a status, and no software was notified.
Bangladesh puts suppliers on one of two registers. A registered supplier charges VAT you reclaim; an enlisted one charges a turnover tax you cannot. Two quotes at the same figure are therefore not the same cost, the cheaper-looking one is usually the smaller business, and no purchasing comparison we have seen can tell them apart.
Bhutan's GST commenced on 1 January 2026 at 5%. Its own Act had said 7% since 2020, and 7% was never charged for a single day — so a researcher who goes to the primary source, reads it properly and stops there publishes a forty per cent error. Going to the statute is necessary. It is not sufficient.
What a Pakistani finance manager asks first
No, and the honest version has two parts. We do not file with any authority in Pakistan, federal or provincial — that is a boundary rather than a backlog, because filing is a specialist integration with its own certification and liability and a system that half-does it looks finished while not being. Separately, our tax figures do not record which authority they belong to, so we cannot even produce the split that feeds a return. That half is on the roadmap and commissionable now — a jurisdiction and an authority on the tax figure itself, as a written specification with a timeline and a price. Kenya's eTIMS transmission is the evidence we build this rather than talk about it.
Very little, and we would rather say so than let a page about federalism imply a problem you do not have. If everything you sell is a good and everything is federal, there is one authority, one return, and the attribution question does not arise — the invoice is right and the split is not a split. The gap on this page widens with every province and every service line you add, which is the honest way to size it. The customer registration point below may still reach you.
Not today — the customer record has no tax registration field and no status field, so this is an absent column rather than a screen we render badly. It matters here because what you charge can depend on whether the buyer is registered and active, which makes it an input to a calculation rather than a piece of filing. On the roadmap and commissionable now, and it is small work: two fields on the customer, with the date you checked. What we would not do is check the register for you — see the next answer.
No, and this one is a boundary rather than a backlog. We will hold the number you recorded and the date you checked it. We will not treat our copy of somebody else's register as authoritative for your charging decision, because your exposure would then depend on our data-refresh schedule — a real risk, moved somewhere you cannot see it, in exchange for a convenience. Check at source, record what you found, and let the system hold the record rather than the judgement.
No. This one is a boundary rather than a backlog, and the distinction protects you rather than us. It is a constitutional question in Pakistan rather than an accounting preference, it determines which government you owe, and the authorities themselves do not always agree about particular cases — so any answer we generated would be a guess wearing the appearance of a system output, and the failures would be silent and in your filings. What we would build, and what is on the roadmap and commissionable now, is the field itself: somewhere to record the determination you were given, with the date it was made, so the calculation can use it and you can show where it came from. A vendor that decided this for you would be carrying a liability it cannot carry, and you would not find out until it mattered.
Usually as separate organizations, each with its own configuration and reporting, consolidated when a whole-business view is wanted. It works and it is a real architecture rather than a workaround — but it is not free, because the entities are separate for every purpose and consolidation is a report rather than a ledger. The alternative people actually use is one organization plus a month-end spreadsheet, which is faster to set up and has the re-derivation problem this page describes. Neither is wrong; they trade different things.
Not today. Two halves, and they have different answers. A boundary rather than a backlog: we will not fold a translation into a standard implementation, because a half-translated operational system is worse than an English one — it teaches people to distrust the screens they can read. On the roadmap and commissionable now: as its own project with a specification and a price, scoped to the screens your people actually work in. English is widely used in Pakistani business documentation, which makes this less pressing here than in some markets, and that is a reason to be honest about the priority rather than to pretend it is solved.
The distribution operation. Stock and lead times per location so a network across provinces is planned rather than reacted to, receiving matched at the door with the discrepancy captured where it happened, customer accounts that hold credit position and history rather than scattering them across salespeople, and assets carrying their own inspection intervals. In a market where the fiscal question is genuinely multi-authority and specialist, buying the operations layer separately from the filing layer is a legitimate architecture — and it is the recommendation more often than a vendor page will admit.
It is one question with a yes-or-no answer, and in a country with five revenue authorities it decides whether month-end is a query or a spreadsheet. If our answer is disqualifying for the filing half, that is a fair conclusion and better reached from this page than from an implementation.