What is Decision engine?
Technology
A decision engine is software that automates credit application assessment by applying business rules, scoring models and external data to return a decision — approve, decline or refer — in milliseconds. Unlike custom-built code, it lets the risk team configure and change policies without engineering involvement.
Decision engine or decisioning engine: is there a difference?
No — they name the same component. The market uses decision engine, decisioning engine, credit decision engine, credit policy engine and credit decision system interchangeably, and in Spanish-speaking Latin America the same software is called motor de decisiones or motor decisional. All of them describe the system that takes a credit application, pulls whatever data the policy requires, applies the rules and models, and returns a decision with its limit and terms — recording which version of the policy resolved each case.
Why it matters
Centralising credit decisions in an engine separates the policy (what gets decided) from the infrastructure (how it runs). That brings speed to iterate and, more importantly, control: every rule, change and outcome is versioned and auditable.
- Decides in milliseconds, at scale.
- Risk teams change policies without waiting on IT.
- Every decision is traced and explainable to auditors.
Common questions
How is it different from building in-house?+
Custom-built logic couples the policy to the codebase: every change goes through an engineering release and traceability depends on team discipline. A decision engine decouples the policy, versions it, makes it auditable, and lets you iterate without deploying code.
Related terms
Batch processing
Batch processing evaluates many cases at once against a policy, instead of answering application by application. It is used to re-score a portfolio, build pre-approved campaigns and test a new policy on historical volume.
Decision tree
A decision tree is the visual representation of a credit policy as a sequence of conditions (if/then) leading to an outcome. In a no-code engine it is built by dragging blocks, which lets business and risk teams design and read the logic without writing code.
Policy versioning
Policy versioning is the practice of storing every change to a credit policy as an identifiable version — with author, date and reason — and being able to tell which one was live at any point in time. It makes policies comparable, revertible and auditable without ambiguity.
Back to the full glossary, read the guides or see the decision engine.
Want to see it in your operation?
We review how you decide today and show you how it would work in the engine, with your own sources and policies.