Mushak 6.3 VAT Invoice: NBR-Compliant POS Setup (2026)

Mushak 6.3 is the VAT invoice, or VAT challan, that a registered business in Bangladesh issues when it makes a taxable supply. The National Board of Revenue lists issuing and requesting it as a standing responsibility of taxpayers, on both purchases and sales (National Board of Revenue, retrieved 2026-08-13).

For years, plenty of businesses treated it as a monthly paperwork exercise: sell all month, then have an accountant reconstruct challans before the return was due. That approach stopped working in 2026. Manual VAT return filing was eliminated as of 1 July 2026, with filing moving to the NBR online portal (PwC Worldwide Tax Summaries, retrieved 2026-08-13). When returns are digital and matched against invoice data, invoices reconstructed after the fact become a liability.

This guide covers what has to be on the invoice, how to configure a POS or inventory system to produce it correctly, and the specific configuration errors that create problems at audit.

Key Takeaways

Mushak 6.3 is the VAT invoice issued on a taxable supply. NBR lists issuing and requesting it as a standing taxpayer responsibility (NBR, retrieved 2026-08-13).

Bangladesh runs multiple VAT rates. The standard rate is 15%, with reduced rates of 1.5%, 2%, 2.4%, 4.5%, 5%, 7.5% and 10% on specified supplies, plus 4% turnover tax for the BDT 3m to 5m band (PwC, retrieved 2026-08-13). A single-rate POS cannot cover this.

Manual VAT return filing was eliminated from 1 July 2026 (PwC, retrieved 2026-08-13). Invoice data now needs to be clean at the point of sale.

NBR extended a deadline to 30 June 2026 for uploading previously filed paper returns into the e-VAT system, warning that businesses missing it risked frozen closing balances and lost refund eligibility (VATupdate, retrieved 2026-08-13).

Configure the VAT rate on the product, not on the invoice. Rate assignment at sale time is the single most common source of understated output VAT.

Who Has to Issue a Mushak 6.3?

Your obligation follows your registration status, which follows your turnover.

VAT registration is required when turnover exceeds BDT 5 million. Businesses with turnover between BDT 3 million and BDT 5 million fall under turnover tax at 4% and register for an Enlistment Certificate instead (PwC Worldwide Tax Summaries, retrieved 2026-08-13).

The practical reading for a growing retailer: if you are approaching BDT 5 million in annual turnover, set your system up for full VAT invoicing before you cross the line, not after. Retrofitting VAT configuration onto a year of existing transactions is painful, and the transactions you already recorded without VAT treatment do not get easier to fix with time.

What Goes on the Invoice

A Mushak 6.3 documents a sale in enough detail that an inspector can reconstruct the VAT calculation without asking you anything. Published descriptions of the form cover seller and buyer information, a description of the goods or services, quantity, unit price, total value, and the VAT applied (ACE Advisory, retrieved 2026-08-13).

In system terms, that means your POS output needs to carry:

Field group	What your system must supply
Seller identity	Registered business name, address, and Business Identification Number (BIN)
Buyer identity	Name and address, plus the buyer's BIN where the buyer is registered
Document control	Invoice serial number and issue date and time, unique and unbroken
Line detail	Description, quantity, unit of measure, unit price
Tax computation	Taxable value, VAT rate applied, VAT amount, and any supplementary duty, per line
Totals	Total value excluding VAT, total VAT, and total payable

Two of these deserve specific attention because they are where systems most often fall short.

Serial numbering must be unbroken and sequential. If your POS restarts numbering each day, or each terminal keeps its own independent counter, you will be unable to demonstrate completeness. Use a single sequence per registered entity, or a prefixed sequence per terminal that is provably continuous. Gaps invite questions you do not want to answer.

Per-line VAT, not invoice-level VAT. An invoice containing a 15% item and a 5% item cannot be represented by one tax total. The VAT must be computed and shown per line, then summed.

The form itself is periodically revised. Before you finalise your print template, download the current version from NBR or your VAT consultant and match the layout field for field.

Configuring VAT Rates Correctly

This is the step that determines whether the rest works.

Bangladesh does not operate a single VAT rate. Alongside the 15% standard rate there are reduced rates of 1.5%, 2%, 2.4%, 4.5%, 5%, 7.5% and 10% applied to specified goods and services (PwC Worldwide Tax Summaries, retrieved 2026-08-13).

Set this up in four steps.

Step 1: Build a rate table. Create each rate you actually use as a named entity in the system, for example "VAT 15% standard" and "VAT 5% reduced." Do not type rates into transactions.

Step 2: Assign a rate to every product. Rate assignment belongs on the item master. When a cashier scans a barcode, the correct rate should arrive with the product automatically, with no decision required at the counter.

Step 3: Handle exempt and zero-rated separately. Exempt supplies and zero-rated supplies are not the same as a 0% VAT rate, and treating them identically will distort your input tax position. Give each its own code so your reports can distinguish them.

Step 4: Decide inclusive or exclusive pricing, once. Bangladeshi retail commonly quotes VAT-inclusive prices to consumers, while B2B invoicing is usually exclusive. Your system should let you set this per price list rather than per transaction. Mixing the two inside one price list produces rounding differences that accumulate into a reconciliation problem nobody can trace.

On rounding: pick one rule, apply it per line, and never re-round the total. Rounding line VAT, summing, and then rounding again produces a total that disagrees with the sum of its parts, which is exactly the kind of discrepancy an automated e-VAT system flags.

Connecting Invoices to the Mushak 9.1 Return

Your VAT return is Mushak 9.1 for manufacturers and service providers claiming input tax credit, or Mushak 9.1.1 for other registered persons. The default is a quarterly return within 15 days following the quarter end, with monthly filing due by the last day of the following month (PwC Worldwide Tax Summaries, retrieved 2026-08-13).

The point of connecting your invoicing system to this is that the return should be a report, not a research project. To get there, three things must hold:

Every sale produces a document. No cash sales entered as "miscellaneous income" outside the invoicing module.
Every purchase records its input VAT. Input tax credit you cannot evidence is input tax credit you cannot claim. Record the supplier's BIN and their invoice number on your purchase entry.
The output VAT summary is generated from transaction data. If your accountant is retyping figures into a return, an error has to happen eventually.

Run the VAT summary report weekly during your first quarter on a new system, not monthly. A configuration error found in week one costs an afternoon. The same error found on the filing deadline costs considerably more.

What Changed in 2026, and What It Means for You

Two developments reshaped the practical compliance picture.

Online filing became the default. Manual VAT return filing was eliminated as of 1 July 2026, with returns filed through the NBR portal (PwC Worldwide Tax Summaries, retrieved 2026-08-13).

Historical paper returns had to be digitised. NBR extended to 30 June 2026 the deadline for businesses to upload previously filed paper VAT returns into the e-VAT system, adding a "Hard Copy Return Entry" sub-module for the purpose. Businesses missing the deadline risked having May 2026 closing balances frozen and losing eligibility for VAT refund claims (VATupdate, retrieved 2026-08-13).

Separately, NBR has continued extending mandatory Electronic Fiscal Device and Sales Data Controller installation to more categories of business, including hotels and restaurants located on highways (Bangladesh Sangbad Sangstha, retrieved 2026-08-13). Whether EFD or SDC applies to you depends on your sector and location, so confirm your position with NBR or a VAT consultant rather than assuming.

The direction of travel is consistent: transaction-level data, submitted digitally, matched centrally. Systems that produce clean data at the moment of sale are aligned with that. Systems that rely on month-end reconstruction are not.

Six Configuration Errors That Cause Problems

Using one VAT rate for the whole catalogue. The most common and most expensive. It understates or overstates output VAT on every affected line, every day, until someone notices.

Letting cashiers override the tax rate. Rate selection should not be an option at the counter. Lock it to the item master and require a supervisor role for any exception.

Restarting invoice numbers. Per-day or per-terminal resets destroy sequence continuity. Fix it before you have a year of history.

Not capturing buyer BIN on B2B sales. Your business customer needs it for their input tax credit. Omitting it turns into a support call and a credit note.

Deleting instead of crediting. A posted invoice should never be deletable. Errors are corrected with a credit note that references the original. If your system allows hard deletes of posted documents, disable that permission for everyone.

Ignoring returns and exchanges. A sales return reverses output VAT. If your returns process bypasses the VAT module, your output VAT will be overstated and your stock will be wrong at the same time. This is one of the specific edge cases worth testing during evaluation, as covered in our Bangladesh inventory software buyer's guide.

Frequently Asked Questions

What is the difference between Mushak 6.3 and Mushak 9.1?

Mushak 6.3 is the VAT invoice issued for an individual taxable supply. Mushak 9.1 is the periodic VAT return that summarises your output tax, input tax and net position for a tax period, with Mushak 9.1.1 used by other registered persons (PwC Worldwide Tax Summaries, retrieved 2026-08-13). One is a transaction document, the other is a period summary built from those documents.

Can I issue a Mushak 6.3 from a mobile POS?

The form requirements concern the content of the document, not the device that prints it. A mobile or tablet POS is acceptable provided it produces all required fields, maintains an unbroken serial sequence, and retains the record. Confirm any device-level requirements that apply to your sector with NBR, particularly if EFD or SDC rules cover your business.

What happens if my internet is down at the time of sale?

Issuing the invoice and filing the return are separate obligations. A POS that operates offline can still produce a compliant invoice with a correct serial number and print it for the customer, then sync to the server when connectivity returns. Given rural internet penetration of 36.5% in Bangladesh (Future Startup, retrieved 2026-08-13), offline invoice generation is a practical necessity outside major cities.

How long should I keep VAT records?

Record retention periods are set in the VAT and Supplementary Duty Act and its rules, and the practical answer depends on your registration type and any open assessments. Confirm the applicable period with your VAT consultant. As a system requirement, choose software that retains full transaction history and lets you export it, rather than one that archives or purges old periods automatically.

Does turnover tax enlistment require Mushak 6.3?

Turnover tax under the BDT 3 million to 5 million band operates differently from full VAT registration, and the documentation obligations differ accordingly (PwC Worldwide Tax Summaries, retrieved 2026-08-13). Verify which documents apply to your enlistment with NBR or a consultant before configuring your system.

Can one system handle several businesses with different BINs?

Yes, if it isolates them properly. Each registered entity needs its own BIN, its own invoice sequence, and its own VAT reporting, with no possibility of a document from one entity appearing in another's return. That separation is an architectural property, which we cover in multi-tenant versus single-tenant inventory software.

Getting This Right the First Time

The compliance work compounds. An invoice template configured correctly today produces clean data for every sale you make from now on, and a VAT return that takes minutes. A template configured carelessly produces a growing pile of transactions that someone will eventually have to unpick, usually under deadline pressure.

The setup sequence, in order: register your rates, assign one to every product, lock rate selection away from the counter, verify your print template against the current NBR form, and run the VAT summary weekly for the first quarter.

If you are also standing up stock control at the same time, the Bangladesh inventory software buyer's guide covers the wider evaluation, and multi-warehouse inventory management covers what changes once you invoice from more than one location.

PicoStore issues Mushak 6.3 invoices from the point of sale, supports per-product VAT rates, and posts every transaction to a double-entry ledger. Start free and print a test invoice against your own product list today.

This article summarises publicly available information on Bangladeshi VAT practice as at 13 August 2026 and is general information, not tax or legal advice. VAT rules change, and application depends on your sector and registration status. Verify your obligations with a licensed VAT consultant or directly with the National Board of Revenue.

Sources

Mushak 6.3 VAT Invoice: How to Make Your POS NBR-Compliant in 2026