A validation rule tests data or a transaction against defined conditions before it is accepted, saved or progressed. It helps prevent incomplete, inconsistent or unauthorized records from entering a workflow.
Which checks can validation rules perform?
- Required field and format
- Range and threshold
- Cross-field consistency
- Reference-data match
- Eligibility and status
- Duplicate and date logic
Validation vs. approval
Validation checks whether data meets defined rules. Approval records an authorized decision. A record can pass validation and still require human approval.
Hard stop vs. warning
A hard stop blocks progress. A warning alerts the user but permits a documented override. Use hard stops for conditions that must never proceed and warnings for contextual judgment.
How should rules be governed?
Assign owners, rationale, severity, effective dates, tests and version history. Align the implemented rule with written policy and downstream system behavior.
How should failures be handled?
Give a specific message, preserve entered data where safe and explain the correction path. Monitor recurring failures for poor design, bad source data or attempted circumvention.
