Way4Tech
๐Ÿ‡ง๐Ÿ‡ฉ E-invoicing in Bangladesh

Odoo e-invoicing in Bangladesh

The Bangladesh e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.

Scheme

No national e-invoicing scheme. The live obligations are the Mushak 6.3 VAT challan (เฆฎเง‚เฆธเฆ• เงฌ.เงฉ) and, in named sectors, EFD/SDC point-of-sale reporting

Authority: National Board of Revenue (NBR), เฆœเฆพเฆคเง€เฆฏเฆผ เฆฐเฆพเฆœเฆธเงเฆฌ เฆฌเง‹เฆฐเงเฆก

Where it stands

As of 22 August 2026 Bangladesh has no clearance or reporting e-invoicing mandate. A VAT-registered seller issues a Mushak 6.3 challan on paper or from its own software, and the only real-time reporting to NBR runs through EFD/SDC hardware in sectors NBR has named one by one.

Who has to comply

Every VAT-registered business must issue Mushak 6.3 for taxable supplies. EFD/SDC installation is imposed sector by sector, most recently on VAT-eligible hotels and restaurants located on highways, announced by NBR in early March 2025.

Every requirement, in full

5 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in Bangladesh gets costed against.

  1. 1 Mushak 6.3 challan showing buyer and seller details, description, quantity, unit price, total value and VAT.
  2. 2 No XML or JSON schema, no digital signature or seal, no clearance step, no accredited intermediary, no NBR-assigned document ID.
  3. 3 EFD/SDC devices in mandated sectors push point-of-sale data to NBR. This is device-level reporting, not ERP-to-authority integration, so an Odoo build does not replace the device.
  4. 4 Mushak 9.1 VAT return is filed through the NBR VAT online portal. PwC states manual return filing is completely dispensed with from 1 July 2026.
  5. 5 An NBR reform panel recommended e-invoicing for VAT in February 2025. Nothing has been enacted, so treat any e-invoicing roadmap as unfunded planning.

Checked Localization notes on this page checked on 22 August 2026.

Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.

How we build e-invoicing for Bangladesh

The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.

  1. 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
  2. 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
  3. 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
  4. 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.

What we need from you to quote it

Bring these to the first call and you get a scoped, priced e-invoicing plan for Bangladesh instead of a range.

  • โœ“ Your tax registration details and the entity each one belongs to.
  • โœ“ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
  • โœ“ Any registration, certificate or portal credential the authority has already issued you.
๐Ÿ‡ง๐Ÿ‡ฉ

Scope e-invoicing for your Bangladesh rollout.

Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.