Pakistan · South Asia

Your invoice knows the rate. It does not know who the money belongs to.

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.

See what decides the destination Talk to us about Pakistan

Destination, not amount

What decides who the money belongs to

Not the amount, and not the customer's address on its own. Two properties of the transaction decide which government a figure is owed to, and a system that records neither cannot attribute the figure at all.

Was it a good or a service?

What decides it

This is the constitutional divide rather than an accounting nicety. Goods are federal and filed with the Federal Board of Revenue. Services are a provincial subject entirely — a different government, a different registration, a different return, and a rate the province sets for itself.

What we hold

An item carries a free-text category and a tax treatment of standard, zero-rated or exempt. Nothing classifies it as a good or a service in a way that reaches tax, so the property that decides the payee is not held anywhere the calculation can see.

Which province?

What decides it

For services, which provincial authority depends on where the service was rendered or received, and the provinces do not agree with each other about the answer in every case. A business operating in three provinces deals with three authorities.

What we hold

Our per-organization rate carries a country, a region and a city — three columns describing one place, the organization's own. Nothing on the invoice line records which jurisdiction that line's tax belongs to.

Is the buyer registered and active?

What decides it

A further tax applies on supplies to a person who has not obtained a registration number or is not on the active taxpayer list. So what you charge depends on the status of the party you are charging — and that status changes over time without you doing anything.

What we hold

The customer record has no tax registration field and no status field. Not a weak screen — no column. So the input to that decision is not merely unchecked, it is unrecordable.

Three questions, and our invoice line answers none of them. It stores a rate. That is enough to charge the right amount, provided somebody outside the system worked out what the right amount was, and it is not enough to say which of five governments the resulting figure is owed to.

Worth separating this cleanly from the neighbouring argument on our Brazil page, because the two look similar and are not. Brazil is about composition — several taxes stacked on one line, where our line holds one. Pakistan is about destination — one tax, and which government it belongs to. A system could fix either without touching the other, and Pakistan's is the smaller of the two.

Where the cost actually lands

What that costs in practice, which is filing rather than charging

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

Four consequences of a figure with no owner

A figure with no owner

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.

A split that cannot be re-derived

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.

A rate that depends on the buyer

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.

Goods and services in one catalogue

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

The half of this we are actually strong at

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

What runs today, what we would build, and where we stop on purpose

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.

Scope in Pakistan, including the figure with no owner

Running in the product today

A tax rate on every invoice line, stored at the moment the document is raised, so what you charge is right and stays right.
Separate organizations with their own rates and reporting, which is the workable shape for a business filing in more than one place today.
Stock and lead times per location, so a spread distribution network is planned rather than reacted to.
Receiving matched against purchase orders with tolerances and the discrepancy captured where it happened.
Customer records holding credit position, history and correspondence against the account rather than the salesperson.

More we can add — and commissionable now

An authority recorded against a tax figure, so a month of trading can be grouped into the returns it belongs to by the system that produced it.
A goods-versus-services classification that reaches the tax calculation, rather than a free-text category that does not.
A tax registration number and an active-taxpayer status on the customer record. Both are columns this adds.
A tax jurisdiction on the invoice line rather than only on the organization, so a line can say where its tax belongs.

What we would decline, and would rather say now

We will not maintain provincial rate tables for you. Five authorities set their own rates and change them on their own schedules; treating our copy as current would move a live compliance risk onto our release cycle where you cannot see it.
We will not check a customer against the active taxpayer list. We will hold the number and the date you checked it. Making your charging decision depend on our copy of somebody else's register is a dependency we would rather you did not have.
We do not file in Pakistan with any authority, federal or provincial, and are not a substitute for the software or the professional that does.
We will not decide whether what you sell is a good or a service. It is a constitutional question with real consequences and occasional genuine disagreement between authorities. We would build the field; we would not populate it with a guess.

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 distance 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

Three questions, none of which needs a proposal

Ask what a tax figure knows about its own destination

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.

Look for the customer's registration field

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.

Ask how last year's split was produced

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

Guides for this market

Accounting Insights

A Figure With No Owner

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.

Jan 10, 2026 · 10 min Read

Reports & BI

The Split That Cannot Be Re-Derived

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.

Mar 12, 2026 · 9 min Read

Implementation & Rollout

Buying Operations Software in Pakistan: A Straight Guide

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.

Mar 17, 2026 · 11 min Read

Point of Sale

The Cheque in the Drawer Is a Dated Risk

Hold a cheque too long and the drawer can be discharged to the extent of the damage your delay caused. A cheque carries three dates and a payment row here has one column — and the till cannot take one at all.

Jul 20, 2026 · 12 min Read

Helpdesk & Support

The Complaint That Starts No Clock

Indian e-commerce rules give a grievance officer 48 hours to acknowledge a complaint and one month to redress it. Three settings in an ordinary help desk decide whether either period is measured — and the one that matters is not a clock.

Jul 11, 2026 · 11 min Read

Point of Sale

When the Line Drops

An offline till is not one feature. It is four, they fail independently, and most systems claiming offline mode have built one or two. Here is the honest map of which are here — none — and what that means before you buy anything.

Jun 24, 2026 · 11 min Read

What a Pakistani finance manager asks first

Answered by destination, including where our figures have none

Can we use your system to file our sales tax returns?

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.

We sell goods only, federally. Does any of this affect us?

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.

Can you record whether our customer is an active taxpayer?

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.

Would you verify customers against the active taxpayer list?

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.

Will you tell us whether what we sell is a good or a service?

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.

How do businesses handle the multi-province problem on your system today?

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.

Is there an Urdu-language interface?

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.

What should we actually buy you for?

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.

Ask what a tax figure knows about where it is going.

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.

Talk to us about Pakistan See plans & pricing