Loan approvals now respect roles and your Credit Product Policy

Loan approvals now respect roles and your Credit Product Policy

About 4 minutes · Released in 26.06.01.06

Summary

Loan approvals in CAMS now enforce who is allowed to approve what. Previously, any administrator with access to the loan module could approve a loan at any stage — including final approval and disbursement — and could skip intermediate steps. With this release, approvals follow the rules set in your Credit Product Policy (CPP) and each user's role: an officer can only act at the stages their role permits, and no one can jump past a step that hasn't been approved yet.

The result is a cleaner, auditable approval chain — the kind your auditors and board expect — with no change to how you create loans day-to-day.

Every approval moves through defined stages

Open a loan application and you can see exactly where it stands: a five-step workflow — Application → KYC & Documentation → Fee & Payments → Sanctions & Approval → Disbursement — showing the current step, who it's assigned to, and the actions available (Approve, Reject, Hold).

What changed in this release:

• Role-based limits are enforced. A user can only Approve/Reject/Hold at the stages their role permits. Loan-module access alone no longer grants approval at every stage — including final approval and disbursement.
• No skipping stages. Intermediate steps can't be bypassed; disbursement only happens once the earlier stages are genuinely approved.
• Full accountability. Every action is recorded under Approval history and Audit history on the application.

See the whole pipeline at a glance

The Loan Applications queue shows each application's stage and status, so officers act on the right items in the right order — and managers can see what's waiting where.

Governed by the Credit Product Policy

Every loan product is governed by a Credit Product Policy — its interest method and rate, the allowed loan amount and tenure, and the provisioning rules that follow. Each policy itself carries an Approved status before it can be used.

You'll find these under Settings → Policies → Credit Product Policy. Because the policy is approved first and the workflow above enforces it, every loan inherits a known, agreed set of rules — and the loan record even stores the Product Policy Version it was booked against.

What this means for you

• Stronger credit governance — approval authority matches each person's role, end to end.
• A clean audit trail — every stage is approved by someone permitted to, and the action is recorded.
• No new steps for staff — you create and submit loans exactly as before; the controls work in the background.

Part of release 26.06.01.06