Claiming VAT input tax credit in Odoo: the rebate your supplier can quietly take back.

The basic mechanics of input tax credit

Input tax credit, commonly called VAT rebate in Bangladesh practice, is the mechanism that keeps VAT a tax on value added rather than a cascading tax on every transaction in a supply chain. A VAT-registered business pays VAT to its suppliers on purchases (input tax), collects VAT from its own customers on sales (output tax), and remits to NBR only the net difference, having first offset the input tax it already paid against the output tax it collected. The eligibility condition that anchors this entire system is registration: a business must hold a valid VAT registration, a Business Identification Number (BIN), to claim rebate at all. An unregistered person cannot claim input tax credit under any circumstance, no matter how well-documented the purchase.

This mechanism is what makes VAT compliance in Odoo a two-sided problem rather than a one-sided one. The site's existing Mushak 6.3 Odoo Bangladesh guide covers the issuing side: configuring Odoo to generate compliant Mushak 6.3 invoices when your business is the seller collecting VAT from customers. This article covers the other half of the same transaction type, the claiming side: how your business, as the buyer, records and protects the input tax credit you are entitled to on VAT you pay to your own suppliers.

The documentation that qualifies for rebate

Three categories of documentation support a valid input tax credit claim, and the correct one depends on the transaction type:

An invoice that is missing, incomplete, issued by an unregistered party, or otherwise defective provides no valid basis for a rebate claim, regardless of whether VAT was genuinely paid in the underlying commercial transaction. This is a harder line than many businesses initially assume, and it is why the documentation discipline described later in this article matters as much as the accounting entries themselves.

From Mushak 6.3 to Mushak 9.1

Mechanically, claiming the rebate means transferring the exact details from the supplier's Mushak 6.3 challan, invoice number, date, the supplier's BIN, the taxable value, and the VAT amount, into the designated input tax section of the Mushak 9.1 return form for the relevant tax period. This is a reconciliation exercise at its core: every input tax figure claimed on the return needs to trace back to a specific, valid invoice held in the business's own records, and NBR's audit process is fundamentally about testing that traceability, not simply verifying the arithmetic on the return itself.

This is precisely where the quality of a business's underlying purchase ledger determines whether return preparation is routine or painful. A business that has recorded every purchase in Odoo with the Mushak 6.3 details captured cleanly at the time of entry can generate the Mushak 9.1 input tax section from a filtered report in minutes. A business that has been recording purchases loosely, batching vendor bills without capturing invoice-level VAT detail, faces a manual reconciliation exercise against a stack of paper invoices every single filing period, which is exactly the failure mode this article is written to prevent.

The rebate isn't really claimed at return time. It's claimed the moment the purchase invoice is entered correctly, or it becomes a reconstruction project later.

The real risk: supplier non-deposit reversal

This is the part of input tax credit that deserves far more attention from Bangladesh businesses than it typically gets, and it is the reason I am centering this entire article around it rather than treating it as a footnote. Holding a facially valid Mushak 6.3 invoice, correctly filled out, from a supplier who is genuinely VAT-registered, does not fully insulate your rebate claim. If NBR later discovers that the supplier collected VAT from you but did not actually deposit it with the government, your rebate claim, the one your business made in good faith based on a document that looked entirely valid, can be reversed. Interest and penalty are then applied to your business, the buyer, even though the underlying non-compliance was entirely the supplier's doing.

The uncomfortable reality is that a buyer has no direct, real-time way to verify that a supplier has deposited VAT for a specific invoice at the moment the purchase happens. What a buyer can do is manage the exposure systematically: favoring suppliers with an established compliance track record, watching for red flags (unusually aggressive pricing that might be explained by a supplier planning to skip VAT deposit, resistance to providing standard documentation, a pattern of BIN or registration irregularities), and treating any NBR notice about a specific supplier's non-compliance as an immediate trigger to review every open claim tied to that supplier, not just the specific invoice named in the notice.

Structuring the Odoo purchase workflow for input VAT tracking

The foundational configuration decision, covered in Odoo Accounting Setup for Bangladesh and NBR VAT Compliance in Odoo, is making sure input VAT is tracked as a distinct, invoice-level tax line rather than absorbed into a generic expense total. Every vendor bill entered in Odoo Accounting should carry: the correct input VAT tax applied at the line level (Accounting > Vendor Bills, with the appropriate Bangladesh VAT tax configured per product or product category), a reference field capturing the supplier's Mushak 6.3 invoice number and date, matched against the actual physical or digital document, and the supplier's BIN validated and stored on the vendor's Contact record rather than re-typed inconsistently on every bill.

The practical build I recommend uses Odoo's standard Vendor Bills workflow with a mandatory attachment policy: no vendor bill gets posted without the actual Mushak 6.3 document attached directly to the bill record in Odoo. This single discipline, trivial to describe, consistently under-enforced in practice, is what turns "we probably have that invoice somewhere" into "here is the exact document, attached to the exact accounting entry, for any invoice NBR asks about." When Mushak 9.1 preparation time arrives, a filtered Vendor Bills report by tax period, with attachments already linked, replaces what would otherwise be a physical document hunt.

BIN validation at the vendor level

Since an unregistered supplier cannot legally issue a valid Mushak 6.3 in the first place, validating a supplier's BIN before relying on their invoices for rebate purposes is a basic control, not an optional nicety. In Odoo, this means capturing the supplier's BIN as a required field on the vendor Contact record (a custom field via Studio if not already present in the localization), and building a simple onboarding step, checking the BIN against NBR's own registration lookup where available, before the vendor is approved for VAT-bearing purchases. A vendor record without a validated BIN should be a visible flag to accounting staff, not a silent gap discovered only when a rebate claim is later questioned.

Control point	Where it lives in Odoo	What it prevents
BIN captured & validated	Vendor Contact record (custom field)	Claiming rebate on invoices from unregistered or invalid suppliers
Mushak 6.3 attached to bill	Vendor Bill attachment	Missing documentation at audit time
Input VAT tax line applied	Vendor Bill line-level tax	Input tax buried in expense totals, invisible for Mushak 9.1 prep
Supplier compliance flag	Vendor Contact tag/note	Continuing to route volume to a supplier with a known non-deposit history

Flagging and monitoring risky suppliers

A practical risk-management technique I set up for clients handling meaningful purchase volume is a simple supplier compliance tag in Odoo Contacts: a visible flag (via a contact tag or a custom Studio field) marking any supplier who has ever had an invoice questioned by NBR, been named in a non-deposit notice, or shown other red flags like inconsistent BIN details across invoices. This is not about blacklisting a supplier automatically, sometimes a good supplier resolves a compliance lapse and remains reliable, but it ensures that procurement and accounting staff see the flag at the point of raising a new purchase order, rather than discovering months later that the same supplier's non-compliance pattern repeated across several transactions before anyone noticed.

Pair this with a periodic review (quarterly is reasonable for most mid-size businesses) of purchase concentration by supplier, since rebate exposure from a non-deposit reversal scales with how much volume flows through any single supplier relationship. A business that has diversified its VAT-bearing purchases across several compliant suppliers carries less concentrated exposure than one that has consolidated a large share of purchasing with a single vendor whose own VAT compliance the buyer cannot directly control.

Retention rules and evidentiary weight

Mushak 6.3 invoices must be preserved for a minimum of 5 years. Both physical and digital copies are acceptable as retained records, which is a meaningful practical relief given how much paper a busy purchasing operation generates, but the original supplier-signed version carries the most evidentiary weight if a specific claim is ever challenged. My standard recommendation is a hybrid approach: scan and attach every Mushak 6.3 directly to its corresponding Odoo vendor bill at the time of entry (satisfying the digital retention requirement and making the document instantly retrievable), while also maintaining the physical originals in an organized, dated filing system for at least the full 5-year window, specifically for the subset of invoices tied to larger transaction values or suppliers with any compliance history worth flagging under the system described above.

Assembling the Mushak 9.1 from a clean ledger

When the purchase ledger has been maintained with the discipline described above throughout the tax period, generating the Mushak 9.1 input tax section becomes a matter of running a filtered Vendor Bills or Purchase report in Odoo Accounting for the relevant period, grouped by tax rate, with invoice references and supplier BIN already attached to each line. The person preparing the return transcribes from a clean, complete source rather than reconciling a stack of loose invoices against bank statements and guessing at what might be missing.

This is the single clearest before-and-after contrast I use when explaining the value of this setup work to a client's finance team: a business with disciplined per-invoice VAT tracking in Odoo can typically prepare the input tax section of a Mushak 9.1 return in under an hour. A business reconstructing it manually from paper and memory routinely spends multiple days per filing period, and still faces meaningfully higher error and omission risk in the final figures submitted to NBR.

Handling Bill of Entry and VDS rebates differently in Odoo

The Mushak 6.3 workflow described above covers the bulk of routine domestic purchase rebate claims, but imports and VAT-deducted-at-source transactions need their own handling inside Odoo rather than being forced into the same document-attachment pattern. For imports, the Bill of Entry is generated through the customs clearance process rather than issued by a private supplier, which means the natural place to attach it in Odoo is the purchase order or the landed cost record tied to that shipment, covered in more depth in Odoo Landed Costs & Duty Drawback. The input VAT recoverable on an import should be tracked as its own tax line distinct from customs duty, since duty and VAT have different treatment for rebate purposes and conflating them on a single landed cost line makes the Mushak 9.1 import section harder to populate accurately.

For VDS transactions, where your business deducted VAT at source on a payment to a supplier and holds a Mushak 6.6 certificate as the supporting document, the Odoo entry needs to reflect that the VAT was withheld and remitted directly by your business rather than paid to the supplier as part of the invoice value. This is a different accounting treatment from a standard Mushak 6.3 purchase, and conflating the two in the chart of accounts is a common error I see in businesses that have not deliberately separated VDS-related input tax tracking from ordinary purchase VAT tracking. Setting up a distinct tax code or account for VDS-based input tax claims, mirroring the AIT withholding treatment described in AIT Withholding Tax Configuration in Odoo Bangladesh, keeps this reconciliation clean rather than blended into the general purchase VAT total.

Where enforcement is heading

NBR's digitization push, the VAT Online system and the broader move toward e-filing referenced elsewhere on this site, is steadily increasing the traceability NBR itself has into the chain between a supplier's declared sales and a buyer's claimed input tax credit. As that visibility improves on NBR's side, the mismatch between a buyer's rebate claim and a supplier's actual deposit record becomes easier for NBR to detect systematically rather than only through targeted audits, which makes the non-deposit reversal risk discussed in this article more, not less, relevant going forward. Businesses that build clean, invoice-level VAT tracking and supplier risk monitoring into their Odoo workflow now are positioning themselves ahead of an enforcement environment that is only going to get more precise about catching exactly this kind of mismatch.

Frequently asked questions

What documents are required to claim a VAT input tax credit (rebate) in Bangladesh?

A business must hold valid VAT registration (a BIN) to claim a rebate at all; unregistered persons cannot claim input tax credit. The supporting documentation depends on the transaction type: a valid Mushak 6.3 tax invoice from a registered supplier for domestic purchases, a Bill of Entry for imports, or a Mushak 6.6 VDS certificate where VAT was deducted at source. Without one of these as the underlying evidence, the rebate claim has no valid basis even if the VAT was genuinely paid.

Can NBR reverse a VAT rebate that was already claimed and approved?

Yes, and this is the most important practical risk in the entire input tax credit system. Even where a buyer holds a facially valid Mushak 6.3 invoice from a registered supplier, if NBR later discovers that the supplier did not actually deposit that collected VAT with the government, the buyer's own rebate claim can be reversed, with interest and penalty applied to the buyer, not just the non-compliant supplier. This means a buyer's rebate claim is only as safe as its supplier's own VAT compliance history, which is outside the buyer's direct control but not outside its ability to monitor and manage as a risk.

How long must Mushak 6.3 invoices be kept for VAT rebate purposes?

Mushak 6.3 invoices must be preserved for a minimum of 5 years. Both physical and digital copies are acceptable as retained records, but the original supplier-signed version carries the most evidentiary weight if the claim is ever questioned during an NBR audit. A business relying solely on a digital scan without retaining the original signed document takes on avoidable evidentiary risk in a dispute.

How is the input tax credit actually entered on the VAT return in Bangladesh?

The exact details from the supplier's Mushak 6.3 challan (the invoice number, date, supplier BIN, and VAT amount) are entered into the designated input tax section of the Mushak 9.1 return form. This is a line-by-line reconciliation process, which is exactly why a business's own purchase ledger needs to hold this data cleanly per invoice throughout the tax period; reconstructing it retroactively from a disorganized pile of supplier invoices at return-filing time is where most manual VAT rebate errors originate.

How is this article different from the site's existing Mushak 6.3 setup guide?

The existing Mushak 6.3 Odoo Bangladesh guide on this site covers the issuing side: configuring Odoo to generate compliant Mushak 6.3 invoices when your business sells to customers and collects VAT. This article covers the claiming side: how your business, as a buyer, structures its Odoo purchase and accounting workflow to properly record, validate, and claim input tax credit on the VAT you pay to your own suppliers, and how to manage the risk that a supplier's non-deposit later reverses your rebate.