Skip to content
RosuiiRosuii

Restaurant VAT Audit Preparation Checklist Bangladesh: Build a Traceable File

A practical audit-readiness checklist that connects each VAT return figure to restaurant sales, purchases, invoices, payments and named evidence.

By 5 min read
Share
Restaurant VAT Audit Preparation Checklist Bangladesh: Build a Traceable File

Last verified: 2026-08-31

A restaurant VAT audit preparation checklist should answer one question quickly: can every material return figure be traced to dated business evidence? Build the file from the return backwards to POS sales, applicable VAT invoices, purchase records, bank or treasury evidence and documented adjustments. Do not wait for an information request to discover missing periods or unexplained branch totals.

NBR's taxpayer guidance says taxable businesses should ask for Mushak 6.3 during purchases, issue it during sales, keep purchase and sales records, calculate and pay net VAT and submit the return. Audit readiness is the operating discipline that connects those duties. It does not replace advice about a specific notice.

Create an audit file index before collecting documents

Use one index row per file and include the exact storage link. A folder full of scans is not an audit trail if nobody can map a return line to the supporting transaction.

Freeze a read-only copy of each submitted period. If a correction is later advised, preserve the original, the corrected version, the authority and the explanation.

FolderMinimum index fieldsOwner
RegistrationBIN, business name, branches, effective changesTax owner
ReturnsPeriod, submission reference, version, preparerAccountant
SalesPOS summary, VAT invoice series, channel and branchFinance/POS
PurchasesSupplier, invoice, receipt, goods/service and postingProcurement
PaymentsChallan/reference, date, amount and bank evidenceTreasury
AdjustmentsReason, original document, approval and treatmentTax adviser
CorrespondenceNotice, response, attachment list and delivery proofAuthorised contact

Prove sales completeness across every channel

List dine-in, takeaway, own online ordering, Foodpanda or other marketplaces, catering, staff meals, complimentary items and manual fallback bills. Reconcile order counts and values by branch and day before rolling them into the tax period.

Investigate missing invoice numbers, duplicate numbers, after-close orders, deleted drafts, voids, refunds and cash sales posted on another date. Record the result; do not silently force the totals to agree.

Sources for this section: NBR: 10 Responsibilities of Taxpayers

Build the purchase and input-evidence pack

For each purchase category, connect the supplier invoice to receipt of goods or service, approval, ledger posting and payment where relevant. Keep supplier identity, invoice date and number, taxable values and the restaurant entity or branch that received the supply visible.

Separate missing, incomplete, duplicated and disputed invoices into an exception queue. An operational purchase entry alone does not prove the VAT treatment; ask the restaurant's adviser to decide admissibility.

Reconcile the return and payment trail

NBR specifically asks taxpayers to check that return and payment information is posted properly in the VAT Online system. Save the confirmation with the period file and investigate mismatches promptly.

The reviewer should be able to reproduce the return from the frozen reports, not from an undocumented spreadsheet value.

ControlEvidenceException question
OutputSales bridge and invoice seriesWhich channel or date differs?
InputPurchase register and document packIs the document complete and eligible?
AdjustmentOriginal transaction and approvalWhy, when and under which treatment?
Net payableReturn calculationDoes it match the filed version?
PaymentTreasury/bank referenceWas it posted to the correct account and period?
Online statusPortal confirmationDoes the account show return and payment correctly?

Sources for this section: NBR: 10 Responsibilities of Taxpayers

Maintain one exception and remediation register

Give every gap an ID, period, amount if known, risk description, responsible person, due date and closure evidence. Categories may include missing invoice, sequence gap, channel mismatch, wrong branch, late posting, disputed adjustment and portal mismatch.

Do not mark an item closed because an email was sent. Closure should state what was corrected, which document now supports it and whether professional or authority guidance is still pending.

Run a mock trace in both directions

Select a sample of return totals and trace down to transactions, then select source transactions and trace up to the return. Include busy days, month end, manual fallback periods, refunds and large or unusual purchases.

Record time taken and blockers. Slow retrieval often reveals inconsistent file names, inaccessible staff drives or reports that were regenerated after the period instead of preserved.

Control responses to an actual notice

Log the received date, issuing office, requested periods, requested records, response deadline and authorised adviser. Use a numbered attachment schedule and retain proof of what was delivered and when.

Do not send an unreviewed data dump or alter source records. Preserve originals, create working copies and have the authorised professional confirm scope, privilege, personal-data handling and wording.

Monthly readiness checklist

  • Freeze branch and channel sales reports
  • Review invoice sequence gaps and voids
  • Complete purchase-document exceptions
  • Tie return, payment and portal status
  • Close or age every reconciliation difference
  • Back up the indexed period pack with controlled access
  • Record reviewer, date and unresolved advice points

How we calculated and verified this

This article turns NBR's public duties to obtain and issue applicable VAT invoices, keep purchase and sales records, calculate tax, pay and submit returns into a restaurant audit-readiness workflow. It is an operator checklist, not an NBR audit notice or legal opinion.

No universal audit period, document demand or outcome is promised. The registered person's current NBR correspondence, VAT adviser and applicable law control the real scope.

A strong audit file is built monthly, not assembled under deadline pressure. Keep each period reproducible, each exception visible and each response controlled.

Use Rosuii reports as operating evidence, then have the restaurant's VAT professional approve the statutory classification and submission.

Related guides

See this workflow in Rosuii: Keep sales, purchase and branch reports organised in Rosuii

Sources checked

Start using Rosuii for free

Last updated:

Frequently asked questions

What should a restaurant keep for VAT audit preparation?
Keep registration and change records, filed returns, sales and invoice-series reports, purchase evidence, payments, reconciliations, adjustments, correspondence and an indexed exception register.
Is a POS sales report enough for a VAT audit?
No single report proves the whole treatment. Reconcile POS data to channels, applicable VAT invoices, adjustments, the filed return and payment evidence.
How often should the audit file be updated?
Complete the period pack as part of each monthly close and update it when a correction, payment posting or authority correspondence changes the record.
Does this checklist replace a VAT adviser?
No. It organises evidence. A qualified adviser should interpret the current law and any specific NBR request.
Should original records be changed before responding?
Preserve originals. Document corrections separately and follow professional and authority guidance.

Run your restaurant on Rosuii

POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.

Start free