Policies, approvals, and reporting
Banks govern credit through policies and committees. AIS should reflect what was approved-not invent policy on the fly.
Policies (business sense)
- A policy is the set of rules your committee agrees applies to a product or segment (eligibility, limits, pricing bands, exception paths-examples only).
- AIS implements approved policy versions in software. When policy changes, your bank needs a controlled promotion process (often mirrored in IT change control).
:::note What this means for you
Treat every production policy version like a regulated release. Someone with committee authority should sign alignment before customers are impacted.
:::
Approvals (typical pattern)
| Decision | Bank owner | AIS role |
|---|---|---|
| New product on AIS | Bank product + risk | AIS implements after contract scoping |
| Model or scorecard refresh | Bank model risk | AIS deploys approved artifacts per runbook |
| Hotfix for a production defect | Bank + AIS jointly | Per incident process |
Your approval matrix - confirm with your AIS account team.
Reporting
- Operational reporting: volumes, turnaround times, queue depths.
- Risk reporting: decision distributions, exception rates, stability metrics (exact KPIs depend on contract).
- Audit reporting: evidence trails for sampled decisions.
AIS may provide exports or APIs; your bank often merges AIS outputs with core data for management packs.
How rules are usually layered (high level)
Product documentation describes a single evaluation spine for many loan events: regulatory or hard policy gates first (where configured for your jurisdiction), then score and default-risk enrichment when enabled, then product rules, then workflow automation. The intent is predictable ordering so committees can reason about what blocked a case.
- Not legal advice: names like “NBE” refer to National Bank of Ethiopia-style checks only where your program implements them-other countries use different labels and tests.
- Bank sign-off: capture which layers are mandatory for each product line and which are advisory in workshops with AIS.
Next: Verification & evidence · Overview