Credit policy
How to structure credit authority, committee and exceptions
Authority should reflect total exposure, complexity and deviation from policy.
Short answer: how do you build a credit approval authority matrix?
List each decision type, measure total exposure after the transaction, assign authority by value and risk, and create higher routes for exceptions, conflicts and complex cases. Then document substitution, quorum, deadlines, minutes and periodic review.
Keep three mechanisms separate:
- authority: delegated power for a role or body to decide within boundaries;
- committee: a collective decision for cases reserved by policy;
- exception: specific, temporary authority to deviate from a rule.
A second signature is not automatically a committee, and an exception does not permanently enlarge the approver's authority.
| Decision type | Dimensions to assess | Possible route |
|---|---|---|
| New limit within policy | Exposure, risk, term and minimum evidence | Defined individual or joint authority |
| Renewal without increase | Behaviour, evidence freshness and material change | Simplified route only where policy permits |
| Permanent increase | Total exposure after increase and concentration | Authority corresponding to the new total |
| Temporary increase | Increment, purpose, order and expiry | Specific authority and automatic return to base limit |
| Policy exception | Bypassed rule, additional risk and protection | Higher level or committee according to materiality |
| Corporate group | Consolidated exposure and sub-limits | Authority for the consolidated total |
| Conflict case | Commercial or personal interest of a decision-maker | Recusal and independent substitute |
| Complex or material case | Multiple risks, security or portfolio impact | Committee with quorum and minimum information |
1. Inventory the decisions permitted by policy
Do not begin with job titles. List new limits, increases, reductions, renewals, declines, term changes, security, releases, restructures and exceptions. State whether each can be automatic, individual, joint or collective.
The matrix does not replace credit policy. It assigns authority for decisions the policy already defines.
2. Use total post-transaction exposure
Include the effective limit, balances, committed orders, new request and group exposure required by policy. Looking only at the increment can let a lower-level role change a total exposure far beyond its authority.
Prevent splitting by order, channel or related entity when consolidation is required. The system should detect concurrent requests and approved changes not yet effective.
3. Combine value with risk and deviation
Two requests of equal amount may need different routes. Consider risk grade, term, security, concentration, evidence quality, sector, currency and exceptions. A small request with conflict or contradictory evidence should escalate.
Prefer testable criteria: “security outside the approved list” is clearer than “weak security”. Where judgement remains, define who exercises it and what reasoning must be recorded.
4. Define individual, joint and committee authority
An individual role decides within scope. Joint authority requires two genuine reviews; state whether limits combine or the lower one controls — never assume addition. A committee decision follows its quorum and voting rules.
Documented delegation, segregation, exception escalation and periodic review also appear in prudential guidance such as the SAMA rulebook on delegation of authority. Banking rules do not automatically apply to every B2B supplier; use them only as a governance reference and confirm the applicable framework.
Governance is not sending everything to directors; it sends each decision to the right authority with the necessary evidence.
— NicePayer
5. Prevent self-approval and conflicts
The person requesting or commercially benefiting from an exception should not be the sole decision-maker. Define incompatibilities across request, analysis, approval, documentation and operational release. Small teams need compensating review and stronger history.
A conflicted member should recuse, be excluded from quorum where applicable and be replaced under a prior rule. Preserve the recusal and actual composition.
6. Design the committee before it meets
Define mandate, reserved matters, members, alternates, chair, secretary, quorum, voting, ties, frequency and deadlines. Specify asynchronous voting, extraordinary meetings and ratification of urgent decisions.
Circulate the business credit analysis report in advance and stop a decision without minimum evidence. Minutes record attendees, conflicts, evidence considered, material questions, votes, dissent, decision, conditions and validity; they need not transcribe the whole discussion.
7. Make every exception expire
Record the bypassed rule, business reason, added risk, mitigant, amount, covered transaction, approver, start and end. A longer term for one order does not authorise all future orders.
At expiry, remove future authority without erasing existing exposure. An unmet condition should trigger the policy route. Previous exceptions remain visible to the next decision-maker.
8. Govern temporary delegation and absence
Holiday or absence cover needs a start, end, scope and delegating authority. Do not allow delegation chains without policy or shared credentials.
Define what happens when a role is vacant, quorum fails or a deadline passes. Commercial urgency does not create informal authority.
9. Set turnaround targets without weakening review
Set expected time by case, minimum information and ownership for returning incomplete files. Separate queue time from analysis time. Exceptions may need a different target.
If almost everything reaches the highest level, bands, data or delegation may be unsuitable. If nothing escalates, check whether total exposure and exceptions are detected.
10. Review the matrix with evidence
Track volume and time by authority, declines, returns, exceptions, changed decisions, conflicts, cases above authority and subsequent outcomes. Approval rate alone does not measure effectiveness.
Review after changes in structure, product, market, risk appetite or exception patterns. Preserve the version used for each decision.
How NicePayer supports credit governance
NicePayer credit policy services can structure criteria, authority, committee and exceptions around the operation. In software, routing, reports, votes, reasons, conditions and decisions stay connected to the proposal.
The tool executes the configured matrix; it does not decide what authority the company should delegate. Accountability remains with designated people and bodies.
Frequently asked questions
What is a credit approval authority matrix?
It maps decision types and levels of exposure, risk or exception to roles or bodies authorised to decide.
Can two approvers add their authorities together?
Only where policy expressly permits it. Two signatures should not automatically create authority neither participant holds.
When should a case go to committee?
When policy reserves material exposure, complexity, group risk, conflict or significant exceptions. Not every request needs a committee.
Who should sit on a credit committee?
It depends on mandate. Define necessary expertise, independence, alternates and conflicts rather than inviting people case by case.
Does an exception create precedent?
Not automatically. It is specific and temporary. Repetition is a signal to review policy, not implicit authority for new cases.
How do you stop the committee becoming a bottleneck?
Delegate routine cases, require complete files, prepare agendas, use targets by band and monitor returns without removing controls.
Conclusion
A strong matrix distributes power without diluting accountability. Each proposal reaches the right authority by value, risk and deviation; committee time serves genuine deliberation; and exceptions end with their cases.
Good authority distributes decision power without creating doubt about accountability.
— NicePayer