AWRA OpsHub Search

Two Suppliers, Same Price, Different Cost

In Bangladesh a supplier sits on one of two registers, and only one of them puts a tax on your invoice that you can take back. Two quotes at the same number are not the same cost, and the difference is invisible in every procurement comparison we have ever seen.

Procurement Insights Washingtone Aura 12 min read

Procurement compares prices. That is the whole job, and it works because a price is assumed to mean the same thing whoever quoted it. In Bangladesh it does not. Two suppliers can quote the same figure for the same goods and leave you with different costs, because one of them is on a register that makes their tax reclaimable and the other is on a register that does not.

Nothing about this is hidden. It is in the definitions section of the governing Act, in plain language, and it is still the kind of thing a purchasing system will not tell you — because the fact lives on the supplier record and the consequence lands in the cost of goods, and almost no system connects those two places.

One Act, two taxes, two registers

Bangladesh's Value Added Tax and Supplementary Duty Act, 2012 does something most VAT statutes do not: it defines "tax" as covering more than one tax. Section 2(24) reads it as meaning VAT, turnover tax and supplementary duty together, and section 2(43) then defines turnover tax separately as the tax imposed under section 63. So the word "tax" in that Act is a category, and two of the things in it work in opposite ways.

VAT registration Turnover tax enlistment
The Act's word for the party Registered Enlisted
Which section puts them there Section 6, or section 8 voluntarily Section 10(1)
What they charge VAT at 15% under section 15(3) Turnover tax under section 63(1)
What it is charged on The value of the taxable supply The turnover of their economic activity
Can they take credit for tax on their own inputs Yes — section 46(1) Not through section 46
Can you take credit for the tax on their invoice Yes, it is VAT There is no VAT on it to credit

Section 46(1) is the hinge and it is worth reading exactly: "a registered person shall be entitled to an input tax credit against the Value Added Tax imposed on a taxable supply or a taxable import". Two conditions are doing work there and they are usually collapsed into one. You have to be registered, and the tax you are claiming has to be Value Added Tax. A turnover tax is not Value Added Tax, and no amount of your own registration changes that.

You are not choosing between two prices. You are choosing between a price with a tax you get back and a price with a tax that has already become part of what you paid.

Why a purchasing comparison cannot see it

Put it in the terms a buyer actually works in. A requisition goes out, two suppliers respond, both quote the same figure for the same specification, and the comparison screen shows two identical numbers. One of those suppliers is registered and one is enlisted. The registered supplier's invoice carries VAT that you will recover; the enlisted supplier's carries a tax on their turnover that you will not, and which is therefore simply part of the price of the goods.

The two quotes are not comparable, and the direction is consistent: the enlisted supplier is more expensive than they look. Not by a headline amount that anybody argues about, but quietly, in a way that turns up much later as a margin that will not reconcile.

This also cuts the other way and that half is more interesting. A supplier who is enlisted rather than registered is, by section 10(1), a business whose turnover sits between two thresholds — a smaller supplier. So a procurement policy that quietly prefers the cheaper-looking quote is, in Bangladesh, a policy with a size bias built into it that nobody wrote down and nobody intended.

Three states, not two

Almost every supplier master in every system we have looked at models tax status as one boolean: registered, or not. Bangladesh needs three positions — registered, enlisted, or neither — and the middle one is not a partial version of either neighbour. An enlisted supplier is fully compliant, holds a certificate, files returns, and gives you nothing to reclaim.

Why there are no thresholds or turnover-tax rate in this post

We read this Act at the National Board of Revenue, which publishes it as an unofficial English translation of the 2012 text, with a 2013 footer and almost no amendment apparatus. Its structures are current. Its numbers are not — the turnover tax rate and both thresholds in that document have since been moved by Finance Acts, and printing them would be publishing a figure that was accurate in 2013 with the authority of a statute. The 15% in section 15(3) is the one figure that has not moved. If you need the current thresholds, they are a Finance Act question and not an Act question, and that distinction is the subject of the next post in this series.

What our own system does on the purchase side

The honest version, read from the schema on the day this was written.

Purchase-side tax — what is and is not built

What AWRA OpsHub does today

  • Landed cost with your own cost types, allocated across received batches by value or by quantity. This is the mechanism by which an unrecoverable charge can genuinely reach the cost of an item, and it works.
  • A per-item purchase price and a computed total cost on every purchase order line, so the cost side of the item is real rather than inferred from the sell side.
  • A supplier record with an active flag and a blacklist flag, which is enough to stop buying from somebody and is not a tax fact about them.

What it does not do

  • Any tax column on the purchase side at all. The purchase order header holds a total and an amount paid; the line holds a price and a total cost. There is no field for tax on either, recoverable or otherwise. Whatever tax a supplier charged you is inside the price or it is nowhere.
  • Any tax registration on the supplier record. No VAT number, no registration status, no register. The distinction this entire post is about cannot be stored against a supplier in our system today.
  • Any automatic routing of an unrecoverable tax into cost. Landed cost is the right mechanism and it is manual: somebody has to know the tax was unrecoverable, know the amount, and enter it as a landed cost. Nothing infers it from who the supplier is.
  • Any comparison that adjusts for recoverability. A quote comparison compares the numbers quoted. It has no way to know that one of them is worth less than it says.

This is scope, not a ceiling

What is not built for your market today can still be built for you

Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a tax authority pipeline, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.

Tax authority pipelines and reporting

Electronic invoicing or invoice registration against your authority's published interface, with retries, a failure queue and a daily report of sales that carry no reference. The regimes across this region differ enough that this is one build per country rather than one build for the region, and the local bench is deep in most of them — so the honest question is usually whether you need this from us at all, or whether you need the operations layer that feeds whatever you already file with.

Local payment rails and bank feeds

Real-time payment collection matched to the invoice, bulk payment files in your bank's format, and statement feeds wired into the Payments Register.

The operational work, which is what most commissions actually are

An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.

Payroll and statutory returns

Statutory payroll and social security schedules computed on live records and produced in the layout each filing body expects. Per-state and per-province variation is the norm rather than the exception here, and it is what makes this a country build rather than a regional one.

Systems you already run

The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.

How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.

Tell us what you need integrated

That first item is the one to sit with. We treat the purchase side as a cost side and the sell side as a tax side, which is a defensible simplification in a country where every registered supplier charges a recoverable tax and the input credit is somebody else's reconciliation. It stops being defensible the moment two suppliers in the same country differ, and Bangladesh is not an edge case — the enlistment regime is ordinary, deliberate policy for smaller businesses, and the same shape exists across South Asia and Latin America under other names.

Four questions to ask a purchasing system

  1. Can a supplier record hold more than "registered: yes or no"?

    Ask for three states, not two, and ask what the third one changes. A dropdown with three values that feeds nothing downstream is the same as a boolean with a longer label. The test is whether anything behaves differently.

  2. Does a quote comparison show cost or price?

    These are the same number in most of the world and that is exactly why the distinction is never built. Ask to see two quotes at the same figure from suppliers with different tax standing, and ask which one the system recommends. If it cannot tell them apart, it is comparing prices and calling them costs.

  3. Where does an unrecoverable tax end up?

    There are only three honest answers: in the item cost, in an expense account, or nowhere. "Nowhere" is common and is not a disaster — but it means the margin on anything bought from that supplier is overstated, and you should know that rather than discover it.

  4. Who is expected to know?

    If the answer is the buyer raising the order, the control is a habit rather than a control. Buyers select on specification, price and lead time. Nobody selects on which register a supplier is enlisted under, and nobody should have to.

The general version

A tax system with two mechanisms running side by side is not unusual and it is not a defect in the country. It is a deliberate accommodation for smaller businesses, and Bangladesh writes it into the same Act rather than hiding it in a concession. What is unusual is how completely it disappears in software, and the reason is structural: the fact lives on the supplier, the consequence lands in inventory cost, and the two are usually built by different people at different times.

The instruction is the same one as always. Before you decide a country is configured, find out whether every supplier in it charges the same kind of tax as every other. If the answer is no, your supplier master has a field it does not have.

Frequently asked questions

Is turnover tax just VAT at a lower rate?

No, and treating it as one is the error this post is about. VAT is charged on the value of a supply and carries an input credit under section 46 of the Act; turnover tax is imposed under section 63 on the turnover of the business and does not sit in that credit machinery. A lower rate you can reclaim and a lower rate you cannot are different amounts of money, and the Act itself defines them as two different taxes under section 2(24).

Why does this post not give the turnover tax rate?

Because the text the National Board of Revenue publishes is the Act as enacted in 2012, and its turnover tax rate and thresholds have been moved by later Finance Acts. We publish a tax figure only with a source and a date behind it. Quoting a superseded number from a real statute is worse than quoting nothing, because the citation makes it look checked.

Does AWRA OpsHub handle any of this?

No. There is no tax field anywhere on our purchase side and no tax registration on our supplier records, so the distinction cannot currently be stored, let alone acted on. Landed cost is the mechanism that would carry an unrecoverable tax into the cost of an item and it works, but somebody has to know to use it. If you buy in Bangladesh this is a manual matter and we would rather say so than describe a feature we intend to build.

Is this only about Bangladesh?

The sections are. The shape is common: many countries run a simplified turnover-based regime alongside a credit-invoice VAT for smaller businesses, under a variety of names. The question to carry to any market is not "what is the rate" but "does every supplier here charge the same kind of tax", and the answer changes what your supplier record needs to hold.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center