What is Batch processing?
Technology
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.
Why it matters
Online decisioning answers whoever is applying right now. Batch is for looking at the whole portfolio: who qualifies for a limit increase, who is worth pre-approving, how a new policy would have behaved across thousands of real cases.
It is also the least risky way to estimate the impact of a change before exposing it to customers.
- Portfolio re-scoring and pre-approved campaigns.
- Impact estimation before publishing a policy.
- Works on historical volume, without touching live operations.
Common questions
How is it different from online processing?+
Online answers a single application in milliseconds, inside the customer's flow. Batch processes a large set of cases on a schedule and returns a report with the results.
Related terms
Decision engine
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 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.
Want to see it in your operation?
Transform your credit assessment process with the decision engine.