A finance team's weekly regulatory routine

Most finance teams in Bangladesh follow regulation reactively: a client, an auditor or a bank asks about a change, and someone goes looking. A short weekly routine turns that into a habit that costs less than one surprise. Here is one that works with a spreadsheet; the software only makes it faster.

Monday, 20 minutes: scan the index pages

• Bangladesh Bank circular archive. Filter mentally by department prefix. FEPD and FEOD for anything cross-border; BRPD and DOS if you are a bank; PSD if you move money. On 12 October 2026 the archive showed 32 circulars in the previous 30 days, so expect several per week.
• NBR SRO lists for VAT, customs and income tax. Outside June these are often empty for weeks; check anyway, and remember the income-tax list has lagged.
• BSEC rules and regulations list if you are listed or regulated by BSEC; two or three instruments a month is typical.

Write down, for each new item: regulator, type, number, date, link, and a one-line "why it might matter to us". Leave the effective date blank unless the document states it.

Tuesday, 10 minutes: decide

For each item, one of three outcomes: ignore (with the reason), watch (someone reads the full document by Friday), or act (open a task with an owner and a date). The reason matters later when an auditor asks why nothing was done.

Friday, 10 minutes: close the loop

• Tasks opened this week: status, blockers, evidence attached.
• Anything "watched" that turned out to matter: convert to a task.
• Anything amended or reissued during the week: update the register with the new version and note what changed.

Monthly, before the 15th

Reconcile VAT changes against the Mushak 9.1 return. Confirm that any rate or VDS change with a stated effective date in the previous month is reflected.

The register columns that pay for themselves

Regulator, document type, number, issue date, effective date (stated or blank), status (in force, amended, superseded, withdrawn), supersedes, owner, decision, decision date, evidence link. That is the structure RuleScan AI keeps for you, with the official link, the file hash and every version attached.