Mushaks (Bangladesh VAT Forms) — Complete User Guide — Two Accounts Web

A comprehensive guide to NBR Mushak forms the system can produce — what you do to reach them under Reports > Mushaks, every field on each form, how the feature is enabled and configured, how each form is calculated from your own data, and how the output aligns with Bangladesh’s VAT law.

Table of Contents

1. What Are Mushaks?
   • The Eleven Forms at a Glance
   • Document Forms vs. Register Forms
2. Enabling the Feature
   • Not a Customize-Menu Switch
   • Permission Gate
3. Related Configuration in Settings
   • Business Details (country, name, address, BIN)
   • Customer and Supplier BIN
   • Tax Codes and Rates
   • Supplementary Duty Setup (domestic and import)
   • Inventory and Opening Balances
   • Date and Number Format
4. Creating, Filling, and Printing a Mushak
5. Common Calculation Rules
   • VAT Rate Resolution
   • Amounts That Include Tax
   • Supplementary Duty
   • Stock Register Rules
   • Rounding and Formatting
6. Field-by-Field Guide to Each Form
   • 6.1 Mushak 4.3 — Input-Output Co-Efficient Declaration (Rule 21)
   • 6.2 Mushak 6.1 — Purchase Accounts Book (Rules 40/41)
   • 6.3 Mushak 6.2 — Sales Accounts Book (Rules 40/41)
   • 6.4 Mushak 6.2.1 — Purchase and Sale Ledger for Traders (Rules 40/41)
   • 6.5 Mushak 6.3 — Tax Challan / Withdrawal Certificate / Tax Invoice
   • 6.6 Mushak 6.4 — Declaration for Supplies to a Contractor
   • 6.7 Mushak 6.5 — Stock Transfer Challan
   • 6.8 Mushak 6.6 — Goods Delivery Challan / Purchase Goods Receipt
   • 6.9 Mushak 6.7 — Credit Note (Goods Return) Memo
   • 6.10 Mushak 6.8 — Debit Note (Goods Return) Memo
   • 6.11 Mushak 6.10 — Large-Invoice Disclosure (Above BDT 200,000)
7. Validation of Calculation
8. Sample Data and Output
   • Mushak 6.3 — Tax Challan
   • Mushak 6.1 — Purchase Register
   • Mushak 6.2.1 — Trader Ledger with SD
   • Mushak 6.10 — Two-Lakh Disclosure
9. Effects on the Rest of the System
10. Behaviour Nuances and Cautions
11. VAT Regulation Compliance

1. What Are Mushaks?

Mushak (মূসক, “Musak”) is the collective name Bangladesh’s National Board of Revenue (NBR) uses for the statutory forms and registers that VAT-registered businesses must keep and file. Two Accounts ^web can manage these prescribed NBR forms automatically from the data already entered on sales invoices, purchase invoices, letters of credit, production orders, inventory transfers, credit notes, debit notes, and the general ledger — or you can fill any of them manually.

1.1 The Eleven Forms at a Glance

1.2 Document Forms vs. Register Forms

The eleven forms fall into two groups, and it helps to understand which is which before using them:

• Document forms (4.3, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8) are produced one at a time, each attached to one source document (a finished item, or a sales invoice, production order, inventory transfer, purchase invoice, credit note, or debit note). Open the record, choose the source, and the form fills itself.
• Register / listing forms (6.1, 6.2, 6.2.1, 6.10) are produced for a period and (for the registers) one inventory item. They are running books that recompute opening–purchase/production–sale–closing from the ledger.

2. Enabling the Feature

2.1 Not a Customize-Menu Switch

Unlike many reports, the Mushak section is not toggled from the Customize Menu on the navigation bar. Instead, every Mushak report and the Settings data-entry area become available automatically when the business’s country is set to Bangladesh:

1. Go to Business Details.
2. Set the Country to Bangladesh.
3. Save.

Once the country is Bangladesh:

• Under Reports, a “Mushaks” category appears listing all eleven forms.

If the country is not Bangladesh, the whole Mushaks area is hidden — there is no navigation-bar switch that overrides this.

2.3 Permission Gate

Even with the country set to Bangladesh, an item is not shown to a user unless the user’s permissions allow viewing that area (or the user has full access). If a form is missing for a user who should see it, check the user’s permissions rather than the country setting.

3. Related Configuration in Settings

What appears on each form, and how accurately figures are computed, depends on several Settings ahead of time.

3.1 Business Details

Where: Business Details.

• Country — must be Bangladesh for the feature to be visible (the master switch, Section 2.1).
• Name and Address — printed at the top of every form (“Name of organization”, “Address”).
• BIN (Business Identification Number) — printed as the “BIN” / “Registration No” on the government forms. Enter the correct BIN here; it is read directly for the forms.

3.2 Customer and Supplier BIN

Where: Customer and Supplier records.

Each Customer and Supplier record carries a BIN field. The forms print the buyer’s/seller’s name, address, and BIN from the linked customer or supplier, and the register forms use the supplier/customer from the transaction. Keep BINs current so the forms are filing-ready.

3.3 Tax Codes and Rates

Where: Settings > Tax Codes.

VAT and supplementary duty rates on the forms come from the tax code assigned to the invoice line or item. The rate rules used on Mushak forms are:

• Zero rate → no VAT (0%).
• Total rate → 100%.
• Custom rate → the single rate entered, or the sum of the component rates if the code is made of several parts.
• Otherwise → treated as 0% for Mushak purposes.

Assign the correct tax code on sales/purchase lines and on items so the amount columns are right.

3.4 Supplementary Duty

Supplementary duty (SD) appears on 6.3, 6.1, 6.2, 6.2.1, 6.6, 6.7, and 6.8. It is recognized in two ways:

• Domestic SD — book SD on the invoice/credit/debit-note line to the balance-sheet account “Supplementary Duty Payable (Domestic)”. The system recognizes such a line as SD for the same item.
• Import SD — record SD as a Letter of Credit cost line with cost type/code “SD”, on a CIF/goods base. When several goods are covered by one LC, any SD not directly assigned is spread across the goods in proportion to their CIF value (consistent with cost allocation).
  • SD amount here is computed either as base × rate ÷ 100 (when the base excludes tax) or base × rate ÷ (100 + rate) (when the base includes tax).

3.5 Inventory and Opening Balances

Where: Inventory items and opening balances.

The register forms (6.1, 6.2, 6.2.1) compute opening stock from the item’s opening inventory and prior general-ledger movements, then run to a closing quantity/value. Mushak 4.3 and 6.5 use the item’s unit cost (moving-average cost from the cost-of-goods-sold engine, falling back to purchase/sales unit price). Give items sensible units and opening values so the registers are meaningful.

3.6 Date and Number Format

Where: Date and Number Format, and the base currency decimals configuration in Settings.

Every form formats dates and amounts using the business’s date format, number format, and base-currency decimal places. A mismatched locale can produce unfamiliar date or number layouts on the printed form.

4. Creating, Filling, and Printing a Mushak

1. Confirm the country is Bangladesh (Section 2.1).
2. Go to Reports > Mushaks.
3. Choose the form you need (for example Mushak 6.3). The list of saved forms of that type appears, with a “New Mushak…” button.
4. Click New. Fill the record’s fields — for document forms, pick the source (sales invoice, production order, inventory transfer, purchase invoice, credit/debit note, finished item); for register forms, pick the Item and the From/To dates.
5. Save. The record appears in the list.
6. Open (View) the record. The system renders the official government layout (English or Bengali according to your language), fills the header and line columns from your data, and adds a “Print Mushak” button.
7. Print or export to PDF for filing and record-keeping.

5. Common Calculation Rules

The forms do not invent numbers. Every amount is derived from posted source data using a small, consistent set of rules.

5.1 VAT Rate Resolution

The VAT rate on a line = the rate of the line's tax code, resolved as:

  Zero rate   = 0%
  Total rate  = 100%
  Custom rate = the single rate, or the sum of the component rates, of the code
  Otherwise   = 0% for Mushak purposes

5.2 Amounts That Include Tax

Depending on the invoice’s pricing convention, the unit price may or may not already contain VAT:

If the price EXCLUDES tax:
     Taxable value  = price per unit × quantity
     VAT            = taxable value × rate / 100

If the price INCLUDES tax:
     Price is backed out first:
        Price excluding tax = price × 100 / (rate + 100)
     VAT            = price × rate / (rate + 100)

On sales registers the same tax is computed on (taxable value + supplementary duty):
     VAT = (value + SD) × rate / 100      (or the inverse formula when tax is included)

5.3 Supplementary Duty

Domestic SD = the amount on the invoice line booked to the domestic SD-payable account
Import SD    = SD cost lines on the Letter of Credit; unallocated SD is spread across
               the goods in proportion to their CIF value.

SD amount formulas (same for domestic and import displays):
     base excludes tax:  SD = base × rate / 100
     base includes tax:  SD = base × rate / (100 + rate)

5.4 Stock Register Rules

Opening quantity/value = the item's opening balance (prior movements as of the day before the
                         period), from the inventory opening and the general ledger.

For each purchase (6.1 / 6.2.1), the register records:
     Quantity added, value excluding all taxes, SD, VAT, supplier, and the invoice reference.

For each sale (6.2 / 6.2.1), it records:
     Quantity, taxable value, SD, VAT, purchaser, and the invoice reference.

Production orders:
     6.1 records the bill-of-materials (raw materials) consumed as stock consumption;
     6.2 records finished goods produced as an addition to saleable stock.

Running balance:
     Total stock     = Opening + additions
     Closing stock   = Total − consumption (or sales for 6.2 / 6.2.1)
     Closing value   = closing quantity at the item's moving-average cost

5.5 Rounding and Formatting

All money amounts are rounded to the base currency decimal places as it is displayed and totalled, using the date/number format configured for the business. Quantities are shown with their own quantity formatting. This keeps every figure on the printed form consistent with the rest of the accounts.

6. Field-by-Field Guide to Each Form

6.1 Mushak 4.3 — Input-Output Co-Efficient Declaration (Rule 21)

Purpose: A manufacturer’s declaration of the raw materials/inputs required to make one finished product or service, including wastage and value addition. Submitted within 15 days of first supply (and anew when input prices change materially).

Fields you set on the record

Printed form columns

Header: organization name, address, BIN, date of submission, date of first delivery. Table (per NBR): SL No · HS Code · Name and description of the supplyable product/service (with brand) · Unit of supply · Materials used (Description · Quantity with wastage · Purchase price · Amount of waste · Rate %) · Value addition (Particulars · Value) · Remarks. Sign-off: name/designation/signature/seal of the person in charge, with the special notes (15-day rule, 7.5% price-change rule, supporting Mushak 6.3 / bill of entry).

How it is filled

Material value   = quantity × the item's unit cost
                    (from the costing engine; fallback to the default purchase unit price)
Damage %         = damaged quantity / quantity × 100
Direct total      = sum of the direct expense lines
Indirect total    = sum of the indirect expense lines
Grand total       = total material value + direct total + indirect total + expected profit

6.2 Mushak 6.1 — Purchase Accounts Book (Rules 40/41)

Purpose: For producers/processors: a running per-item purchase register of raw materials and inputs.

Fields you set on the record

Printed form columns (NBR numbering)

How it is filled

Reads purchases (purchase invoices, expense claims, letters of credit, and purchase-type journal adjustments) for the item in the period; supplier comes from the supplier or the payable line’s party; import SD comes from the LC’s SD cost allocation; opening stock comes from the inventory-opening provider; consumption comes from production orders’ bill of materials.

6.3 Mushak 6.2 — Sales Accounts Book (Rules 40/41)

Purpose: For producers: the running per-item sales register of produced/sold goods.

• Record fields: Item (a sale item), From Date, To Date, Description.
• Columns (21): Opening stock qty/value · Production qty/value · Total produced (qty = 3+5, value = 4+6) · Purchaser name/address/reg-no · Challan number & date · Description · Quantity · Taxable value · SD · VAT · Closing qty (7−15) / value (8−16) · Comments.
• How it is filled: Reads sales invoices (credits negated), production orders (finished goods added), and sale-type journal adjustments; opening stock from the inventory provider; SD from domestic SD lines or the import SD rate; VAT from the tax lines on the sales.

6.4 Mushak 6.2.1 — Purchase and Sale Ledger for Traders (Rules 40/41)

Purpose: The combined register for registered persons not involved in processing (traders/merchants).

• Record fields: Item (an inventory item), From Date, To Date, Description.
• Columns (~26): Opening stock qty/value · Purchase qty/value · Total stock qty/value · Seller name/address/reg-no · Purchase challan/bill-of-entry number & date · Description · Quantity · Taxable value · SD · VAT · Purchaser name/address/reg-no · Sales invoice number & date · Closing stock qty/value · Comments.
• How it is filled: Both sides — purchases (purchase invoices, expense claims, letters of credit, purchase adjust entries) and sales (sales invoices, sale adjust entries) for the item in the period; opening from the inventory provider; import SD rate / domestic SD handling as elsewhere; sales tax computed on (value + SD).

6.5 Mushak 6.3 — Tax Challan / Tax Invoice cum Withdrawal Certificate

Purpose: The VAT tax invoice (challan) issued with each taxable sale — the primary document carrying the VAT to the buyer. Withdrawal certificate wording and the registered person’s / buyer’s details appear in the NBR’s layout.

Fields you set on the record

Printed form layout

Header: Government of Bangladesh / NBR, “Tax Challan (Mushak 6.3) — with written permission of the officer-in-charge, a copy shall be issued”; registered person’s name, BIN, issuing address; buyer’s name, BIN; delivery destination; invoice no, date & time of issue; vehicle nature & number.

Columns (13): 1 SL No · 2 Goods/Service description (with brand) · 3 Unit of supply · 4 Quantity · 5 Unit price (value excluding all tax) · 6 Total price · 7 Total price discount · 8 Total price excluding discount · 9 SD rate · 10 SD amount · 11 VAT rate / specific tax · 12 VAT amount · 13 Value including all duties and taxes. Totals row at bottom; signature/designation/officer-in-charge/seal.

How it is filled

Qty         = the quantity on the invoice line (default 1)
Unit price  = the line unit price; if the invoice includes tax, the price is
              backed out:  price × 100 / (rate + 100)
Total price = qty × unit price
Discount    = per the invoice discount (percent of amount or a flat amount)
Net         = Total price − discount
SD          = domestic SD lines for that item (rate % = SD / Net × 100)
VAT         = computed on (Net + taxable SD) × rate/100, or × rate/(rate+100)
              when the price includes tax; fallback to the invoice's total VAT
Grand total = Net + SD + VAT

6.6 Mushak 6.4 — Declaration for Supplies to a Contractor

Purpose: Declaration when goods/services are supplied or transferred for use by a contractor.

• Record fields: Date, Reference, Contractor (Customer, Supplier, or Other/Contact), the chosen party plus (for “other”) the contact name, BIN, and address, and the Production Order.
• Columns: SL No · Item Name · Description · Quantity · Comment (“Production: <finished item>”). Totals row sums quantity.
• How it is filled: Rows come from the production order’s bill of materials. Header carries the registered person’s name/BIN/address and the contractor’s details (+BIN).

6.7 Mushak 6.5 — Stock Transfer Challan

Purpose: Invoice for the transfer of goods between locations of a centrally registered organization.

• Record fields: Issue Date, Reference, Inventory Transfer, Description. Header shows From Location / To Location.
• Columns: SL No · Goods description (with brand/unit) · Quantity · Value Excluding Tax · Amount of Applicable Tax · Comments. Totals row at the bottom.
• How it is filled: From the inventory transfer lines. Value = quantity × unit cost (moving-average cost; fallback to purchase then sales unit price); Tax = value × the item’s default tax-code rate / 100.

6.8 Mushak 6.6 — Goods Delivery Challan / Purchase Goods Receipt

Purpose: Records goods purchased and received against a purchase invoice (and confirms the seller’s tax challan).

• Record fields: Date, Reference, Mushak 6.3 Received indicator (with the seller’s 6.3 number and issue date when yes), Supplier, Purchase Invoice.
• Columns: SL No · Supplier Name · Supplier BIN · Received Mushak 6.3 number · Received 6.3 date · Value including price and SD · Value of the supply (total) · Amount of VAT · Amount of VAT withheld at source. Totals row.
• How it is filled: Value = sum of the purchase-invoice non-tax line amounts; SD from the domestic SD lines; VAT = the tax amount from the invoice’s general-ledger tax lines.

6.9 Mushak 6.7 — Credit Note (Goods Return) Memo

Purpose: Memo issued when goods are returned / a credit note is issued against a sales invoice.

• Record fields: Issue Date, Reference, Credit Note Number, Customer, Credit Note, optional Vehicle Nature and Number. Header carries buyer name/BIN/address, invoice and credit-note references and dates.
• Columns (per NBR): SL No · Related Tax Invoice No & Date · Reasons for issuing the credit note · For the supply in the invoice (Price excluding all taxes · Quantity · VAT · SD) · For the credit note (Value incl. VAT & SD · Quantity · VAT · SD).
• How it is filled: Reads the GL of the linked sales invoice and the credit note; amounts = non-tax line sums (invoice side negated for the return), quantities summed, VAT = tax amounts, SD = domestic SD lines mapped by item.

6.10 Mushak 6.8 — Debit Note (Goods Return) Memo

Purpose: The mirror of 6.7 on the purchase side — memo when goods are returned to a supplier (debit note) against a purchase invoice.

• Record fields: Issue Date, Reference, Debit Note Number, Supplier, Debit Note, optional Vehicle Nature and Number.
• Columns: As 6.7, comparing the purchase invoice supply vs the debit note: price excl. tax, quantity, VAT, SD, for both sides, plus the related tax invoice no/date and reasons.
• How it is filled: From the GL of the purchase invoice and the debit note, using the same rules as 6.7.

6.11 Mushak 6.10 — Large-Invoice Disclosure (Above BDT 200,000)

Purpose: Period disclosure of purchases and sales whose tax invoices have value above two hundred thousand taka (BDT 200,000), per Rule 42.

• Record fields: From Date, To Date, Description.
• Layout: Part A — Purchase Information; Part B — Sales Information. Each row: SL No · Invoice No · Issue Date · Value · Buyer’s/Seller’s Name · Address · BIN / National ID.
• How it is filled: Groups the period’s transactions by document; a transaction is listed only when its total value (excluding tax, inventory-based) exceeds the 200,000 threshold. Purchases come from purchase invoices, expense claims, letters of credit, and purchase-adjusted journal entries; sales from sales invoices and sale-adjusted journal entries. Party name/address/BIN from the linked supplier/customer (or the payable/receivable line party).

7. Validation of Calculation

Every auto-filled figure on a Mushak is computed from the same data that feeds your general ledger and VAT accounts — nothing is typed in or guessed. The checks that guarantee consistency are:

1. VAT amounts equal the ledger tax lines. The VAT columns read the tax transactions already posted on the invoice/receipt; the rate displayed is resolved from the tax code’s defined rate (zero/total/custom including summed components). The printed VAT therefore always matches the VAT already booked.
2. SD follows the SD accounts. Domestic SD comes from lines booked to the domestic SD-payable account; import SD comes from LC cost lines coded “SD”, allocated across goods by CIF. The forms never invent an SD rate.
3. Stock registers reconcile to inventory. Opening + additions − consumption/sales = closing, calculated with the item’s real unit cost; totals on the register tie to the inventory movements used elsewhere in the system.
4. Document forms tie to their source document. A 6.3 totals to the selected sales invoice; a 6.6 totals to the purchase invoice; 6.7/6.8 reconcile invoice vs credit/debit note; 6.5 totals to the transfer’s lines.
5. Disclosure threshold is objective. 6.10 lists only documents whose value, net of taxes, crosses 200,000 taka — a crisp, auditable rule.

8. Sample Data and Output

The samples below use base currency BDT, a Bangladesh business ABC Traders Ltd (BIN 001234567-0101) in Dhaka, and simplified but fully verifiable numbers.

8.1 Mushak 6.3 — Tax Challan

Setup:

Calculation:

Total price        = 500 × 92.00           = 46,000.00
Discount           = 0.00
Net                = 46,000.00
SD rate / amount   = – / 0.00
VAT rate           = 5%
VAT                = 46,000.00 × 5 / 100  = 2,300.00
Value incl. tax    = 46,000.00 + 0.00 + 2,300.00 = 48,300.00   ✓

Mushak 6.3 output (columns 1–13):

Verification: VAT = 46,000 × 5% = 2,300 ✓; total = 46,000 + 2,300 = 48,300 ✓ (matches the invoice’s posted VAT and total).

8.2 Mushak 6.1 — Purchase Register (item “Raw Material RMX”)

Setup: Period 01-Jan-2026 to 31-Mar-2026. Opening stock 100 units @ 500.00 = 50,000.00. A purchase on 05-Jan: 200 units @ 520.00 = 104,000.00 (excl. tax), VAT 5% = 5,200.00, from supplier S. A production order on 20-Feb consumes 150 units.

Opening          qty 100  value  50,000.00
Purchase          qty 200  value 104,000.00   VAT 5,200.00
Total stock      qty 300  value 154,000.00
Consumption      qty 150  value (avg 513.33 × 150 =) 77,000.00
Closing          qty 150  value 154,000.00 − 77,000.00 = 77,000.00

Checks:  15 = 3 + 11 = 100 + 200 = 300 ✓    16 = 4 + 12 = 154,000 ✓
         19 = 17 − 15 = 150 ✓               20 = 18 − 16 = 77,000 ✓
         Closing value ÷ closing qty = 77,000 ÷ 150 = 513.33 (average cost) ✓

The printed register shows one row for the purchase and one for the consumption, with the supplier’s name/address/reg-no in columns 7–9 and the VAT (5,200.00) in column 14.

8.3 Mushak 6.2.1 — Trader Ledger with SD

Setup: Period 01-Jan to 31-Mar. Opening stock 0. Purchase of 1,000 units @ 200.00 = 200,000.00 with SD 10% = 20,000.00 and VAT 15% on (value + SD) = 220,000 × 15% = 33,000.00. Total sold 600 units.

Purchase   qty 1,000  value 200,000.00   SD 20,000.00   VAT 33,000.00
Sale       qty   600  taxable value 120,000.00 + SD (proportionate) 12,000.00
           VAT = (120,000 + 12,000) × 15% = 19,800.00
Total stock qty 1,000 ; Closing qty 400 ; Closing value 80,000.00

Checks:  Total (qty)  = 0 + 1,000 = 1,000 ✓   Closing = 1,000 − 600 = 400 ✓
         Closing value = 400 × 200.00 = 80,000.00 ✓
         Sales VAT = (data value + SD) × rate / 100 = 132,000 × 15 / 100 = 19,800.00 ✓

The register lists the purchase row (seller info, challan ref/date) and a sale row (purchaser info, sales invoice ref/date), with SD and VAT in their own columns.

8.4 Mushak 6.10 — Two-Lakh Disclosure

Setup: Period 01-Jan-2026 to 31-Mar-2026. Documents in the period:

Mushak 6.10 output:

Verification: Only documents above BDT 200,000 are listed (PI-89 and SI-106 are excluded because they are below the threshold); names/addresses/BINs come from the linked parties.

9. Effects on the Rest of the System

Mushak forms are derived and printed — they post nothing and change nothing. Their genuine value is the audit and reconciliation link they create:

10. Behaviour Nuances and Cautions

• Country-gated, not Customize-gated. The whole feature appears when Business Details Country is Bangladesh; there is no navigation-bar toggle, and user permissions must also allow the area.
• Mushak 6.3 is a tax challan per invoice, not a periodic VAT return; there is no input-tax-credit or closing VAT balance inside these forms.
• Registers are per-item. 6.1/6.2/6.2.1 each cover one item for a period; run one per item (or per relevant item) to cover a full book.
• Opening balances matter. Without correct opening stock, register closing figures will be wrong — set opening inventory before relying on 6.1/6.2/6.2.1.
• BINs must be current. The forms print BIN from Business Details, Customer, and Supplier records; blank or stale BINs produce incomplete forms.
• SD must be booked correctly. Domestic SD must sit on the SD-payable account lines; import SD must be coded “SD” on LC cost lines, or the SD columns will be empty.
• Tax codes drive rates. A line without the right tax code shows 0% — check the code on the invoice line or item.
• Amounts-include-tax handling. When your invoices price goods tax-inclusive, the forms back the price out automatically; verify the convention matches how you enter invoices.
• 6.10 is threshold-based. Only documents above BDT 200,000 appear; smaller documents are intentionally excluded for Rule 42.
• Printing in Bengali needs Bengali fonts/language support on the computer used to print.
• Forms are read-only outputs. Corrections are made on the source documents/invoices, not on the printed form.

11. VAT Regulation Compliance

The forms follow the structure prescribed under Bangladesh’s VAT law, so the output is recognizable and filing-ready.

11.1 Value Added Tax and Supplementary Duty Act, 2012 — prescribed forms

Requirement: VAT-registered persons must maintain the registers and issue the documents prescribed by the Act and its Rules — the “Mushak” forms.

Alignment: The system reproduces the official layouts: the tax/invoice challan (Mushak 6.3), the purchase and sales books (6.1, 6.2), the traders’ ledger (6.2.1), the declaration of inputs/outputs (4.3), contractor supplies (6.4), stock transfers (6.5), delivery challans (6.6), credit and debit notes (6.7, 6.8), and the large-invoice disclosure (6.10), matching the letter and column structure of the NBR forms in English and Bengali.

11.2 Rules 21, 40, 41, 42 — the discipline behind the forms

Requirement: Rule 21 — input-output co-efficient declaration within 15 days of the first supply (and on material price change); Rules 40/41 — the purchase/sales books and challans; Rule 42 — disclosure of invoices above two lakh taka.

Alignment: 4.3 captures the declaration (with the 15-day and 7.5% price-change notes on the form), 6.1/6.2/6.2.1/6.3 implement the books and challan, and 6.10 enforces the 200,000-taka threshold, all derived from the same books the Act requires you to keep.

11.3 Correct tax computation basis

Principle: VAT is chargeable on the taxable value; where the price includes tax, the tax must be imputed (value × rate/(rate+100)); supplementary duty is levied on the value including duties on the relevant base.

Alignment: The forms apply exactly these mechanics — taxable value exclusive of tax, VAT and SD computed on the correct base (including the SD-inclusive-in-base cases), and the grand total of value plus duties and taxes carried on each line and totalled.

11.4 Supporting-document chain (audit trail)

Principle: Every book entry and disclosed invoice should trace to a supporting document (invoice, bill of entry, or Mushak 6.3).

Alignment: Each form links back to its source document and ledger lines: 6.3 to the sales invoice, 6.6 to the purchase invoice and the seller’s received 6.3, 6.7/6.8 to the credit/debit note, and the registers to their transactions. This creates the authentic-document trail NBR expects.

11.5 Cost allocation for imported goods — consistent with IAS 2

Principle: The cost of imported goods includes purchase price, import duties and taxes not recoverable (such as supplementary duty), allocated across goods on a reasonable basis.

Alignment: Import SD is captured from letter-of-credit cost lines and, when not directly assigned, allocated across the goods in proportion to their CIF value — the same basis required for inventory cost allocation, keeping 6.1/6.2.1 SD figures defensible.

End of Mushaks (Bangladesh VAT Forms) Guide