corporate-credit-risk-monitoring
Monitor credit risk for corporate and business borrowers — financial analysis, internal ratings, covenants, collateral, and obligor watchlists. Use when managing SME, mid-market, or large corporate credit exposures after sanctioning.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- corporate-credit-risk-monitoring
- description
- Monitor credit risk for corporate and business borrowers — financial analysis, internal ratings, covenants, collateral, and obligor watchlists. Use when managing SME, mid-market, or large corporate credit exposures after sanctioning.
03 SKILL.md 正文
Corporate Credit Risk Monitoring
Overview
Corporate credit risk monitoring assesses whether business obligors continue to meet repayment capacity and contractual terms. It relies on financial statements, qualitative factors, covenant tests, and relationship intelligence — not only payment status.
When to Use
- SME, commercial, and large corporate lending portfolios
- Term loans, working capital facilities, trade finance, and guarantees
- Periodic review / annual renewal cycles
- Watchlist and special-mention management for business accounts
Core Practices
- Assign and refresh internal credit ratings or risk grades
- Review financial statements on an agreed frequency (quarterly/annual)
- Test covenants and track headroom (leverage, DSCR, current ratio, etc.)
- Monitor obligor and group exposure vs sanctioned limits
- Track collateral valuation and security perfection status
- Capture qualitative events: management change, lost customers, litigation, sector shocks
- Escalate to watchlist / restructuring based on clear triggers
- Document periodic review outcomes and rating migrations
Key Analytical Areas
- Earnings quality, cash flow, and leverage trends
- Liquidity and refinancing risk
- Customer/supplier concentration
- Group contagion and related-party exposure
- Industry and geographic risk factors
- Management integrity and transparency of information
Principles
- Payment current ≠ credit healthy for corporates (covenant and cash flow lag)
- Group and connected-party exposure must be aggregated
- Stale financials are themselves a risk signal
- Relationship managers and credit risk need shared early-warning ownership
- Downgrade and watchlist actions should be evidence-based and timely
Verification
- [ ] Rating/review calendar is enforced for material exposures
- [ ] Covenant breaches and near-breaches are detected promptly
- [ ] Limit utilization and group exposure are visible
- [ ] Watchlist criteria are explicit and applied consistently
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.