What your bank can do vs what AIS operates
This page is a RACI-style view in plain English. It helps workshops start in the right place.
What your bank can do (examples)
- Approve credit policies and model risk governance decisions.
- Configure product parameters your contract allows (limits, cutoffs, workflow flags-confirm scope).
- Assign bank users and roles in Decision PRO (or your identity integration) per your security model.
- Define reporting packs for committees and audit sampling.
What AIS typically operates
- Platform reliability and release engineering for AIS components.
- Baseline product features shared across customers (unless you have a dedicated instance with different rules-confirm).
- Support according to your SLA tier (placeholder until inserted from contract).
Approvals you should expect to see on the bank side
- Policy version approval before production use.
- Model promotion approval (or reliance on AIS change control-contractual).
- Integration approval for new channels feeding AIS.
:::tip What this means for you
If a workshop cannot name the bank approver for a decision type, pause and clarify before configuration continues.
:::
Reporting
- Bank-facing reports usually combine AIS outputs with core banking facts-your analytics team often owns the final management view.
- AIS may provide standard exports or APIs for building those views-confirm with your AIS account team.