Decision engine (rules engine)
Also known as: Rules engine · Decisioning engine · Policy engine · Business rules engine
The component that turns risk signals into a verdict — approve, decline, review or ask for more verification — applying rules and models automatically and consistently to every case.
Legal basis
OMG — Decision Model and Notation (DMN)
Gathering signals is not enough; something has to decide. The decision engine is where policy becomes action: if the score is below x, decline; if liveness failed but the document passed, send to review; if the customer is low-risk, approve straight through. It applies the same logic to every case, which makes the decision auditable and reproducible — unlike an analyst deciding case by case.
A good engine separates the rules from the code that runs them, so the risk team can adjust thresholds and conditions without waiting on engineering — the idea behind standards such as DMN (*Decision Model and Notation*). Combined with orchestration, it closes the loop: orchestration collects the signals, the engine decides, and the decision returns to the flow in real time.
Frequently asked questions
What does a decision engine do in risk decisioning?
It converts the collected signals into an automated verdict — approve, decline, review or request more verification — applying rules and models consistently to every case. Separating the rules from the code lets the risk team tune policy without reprogramming the system.