Banks: detecting cross-default clauses and covenants before granting a loan
Cross-default, security ranking, explicit financial covenants: a first scan before credit analysis.
A financing contract rarely contains a single isolated risk clause. An overly strict financial covenant, a poorly calibrated cross-default clause, an ambiguous security rank: these are the combinations that turn a standard file into one that needs watching.
A first automated scan of these points, before the full file analysis, helps prioritize the review.
Quick check: Analyze a financing contract on subblink — cross-default, security ranking, explicit financial covenants.
1. Cross-default clause
The problem
A cross-default clause makes a financing contract automatically due if the borrower is in default on another commitment, sometimes with no direct link to the current contract. Poorly calibrated, it can trigger a cascade of maturity events.
What subblink detects
The sectorDimensions.bankingRisk.crossDefault field flags the explicit presence of such a clause in the contract text — a signal to check systematically before granting or renewing a loan.
2. Security ranking and priority
The problem
In case of default, the actual repayment order depends on the security's rank — first rank, subordinated, or unspecified in the contract. An "unspecified" security is a point of attention, not a guarantee.
What subblink detects
The security rank mentioned in the contract (sectorDimensions.bankingRisk.securityRank), with an explicit flag if no rank is indicated.
Legal reminder (Switzerland)
A chattel pledge requires a transfer of possession to the creditor (Art. 884 CC); a pledge of receivables and securities requires a written document and, depending on the type of security, delivery or registration (Art. 900-901 CC). The commissory pact — direct appropriation of the asset by the creditor — is void (Art. 894 CC): only realization through debt enforcement proceedings or an agreed private sale is admitted.
3. Explicit financial commitments (covenants)
The problem
A debt-ratio or interest-coverage covenant, poorly calibrated against the borrower's business seasonality, can trigger a technical default without any real deterioration of credit risk.
What subblink detects
The financial covenants explicitly mentioned in the contract text (sectorDimensions.bankingRisk.financialCovenants) are listed, for calibration review by the credit team.
4. Borrower's total financial exposure
The problem
An isolated covenant is easy to read. The cumulative financial exposure across several contracts of the same borrower (financing, guarantees, off-balance-sheet commitments) is harder to visualize quickly.
What subblink detects
The total amount committed and cumulative penalties identified in each contract (professionalDimensions.financialExposure) — to be manually aggregated with the borrower's other commitments for a consolidated view.
Bank checklist: before granting or renewing financing
- Cross-default clause present or absent, and its exact scope
- Security rank explicitly specified
- Financial covenants listed and calibration checked by the credit team
- Total financial exposure and cumulative penalties identified
- Applicable law and competent jurisdiction in case of dispute
Upload the financing contract to subblink for this first scan.
FAQ: subblink for banks
Does subblink replace credit analysis?
No. It flags risky clauses explicitly present in the contract text (cross-default, security rank, covenants). Credit analysis — solvency, history, consolidated guarantees — remains a distinct business exercise.
Is the indicated security rank enforceable against third parties?
No, it's a flag based on the submitted contract's text. Actual enforceability depends on registration with the relevant register (reservation-of-title register, land registry, etc.), to be checked separately.
Can subblink analyze a bank pool or syndicated financing?
Yes, within the limits of the submitted contract. A consolidated view across several contracts of the same file still needs to be assembled manually.
Is the contract data retained?
No, the contract text is not stored after processing — only aggregated, anonymized data feeds the internal benchmarks.
Conclusion
A poorly calibrated covenant or an overly broad cross-default clause aren't always obvious at first glance in a 40-page contract.
Systematically flagging these points, before the full credit analysis, helps make sure nothing slips through.