SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Business analysis glossary

Regulatory Requirement

What it is

A regulatory requirement is a requirement that comes from a law, a regulator's direction or an industry standard rather than from a business preference. Examples include customer verification rules, data retention periods, consent rules and mandatory reports. It must be met exactly, by the stated date, and evidence of meeting it is often needed.

Why it matters

Regulatory requirements cannot be negotiated away or deprioritised, and missing them can stop a product. Analysts must cite the source of each regulatory requirement, confirm its interpretation with the compliance or legal team and trace it to design and testing. When rules change, impact analysis starts from these links.

Example

A new regulator circular changes how quickly failed UPI transactions must be reversed. The analyst at Tapti Payments records it as a regulatory requirement, links the circular, writes a measurable rule with the turnaround time stated in it, gets compliance to confirm the reading and traces it to the reversal batch job and its tests.

CHECK BEFORE CONTINUING

Keep your work safe