Feature map: models, rules and execution
FICO describes a platform that combines decision management, analytics, model development and deployment. Its legacy strengths include scorecards and configurable decision strategies; platform materials describe tools to build, govern and operationalize predictive models and decisions. These are vendor-described product capabilities, not independent evidence of improved approvals or lower loss. [1]
A bank should identify which component performs which function: data preparation, score computation, policy rules, workflow routing, explanation, deployment and monitoring. An “AI platform” label can mask multiple models, business rules and human overrides. Inventory each model and material rule, define its owner, intended use, fallback and change authority, then map dependencies to customer outcomes.
Compeer: agricultural lending has a seasonal operating problem
FICO’s April 13, 2026 release describes Compeer Financial, a member-owned Farm Credit cooperative, using the platform for agricultural lending. It reports 95% straight-through processing for loans under $500,000 and roughly 800 hours of underwriter time saved monthly across the described operation. Its more-than-$10-billion milestone concerns automated lending application throughput, not a disclosed $10 billion of funded or retained loans. These are vendor/customer-reported measures. [4]
Bill Moore, identified as Compeer’s Chief Risk Officer, says: “In agriculture timing is everything.” The short quotation is customer commentary carried in FICO’s release. It illustrates why seasonal capacity matters without proving that faster decisions caused better credit outcomes. [4]
Analysis: underwriting demand can bunch around a business cycle. Automation may help a lender absorb the peak while reserving staff for unusual cases. A useful evaluation would compare peak-period queue age and exception quality alongside mature losses, rather than applying an average handling-time saving uniformly to every application.
Bradesco: orchestration connects eligibility to a lending offer
FICO’s May 19, 2026 release describes Banco Bradesco using a cloud-based eligibility engine for Brazilian payroll-deductible lending. The workflow connects government employment/payroll information with customer and risk data and evaluates both employee and employer. This is a specific decision-orchestration example; it does not establish that every Bradesco loan is decided by the same system or that vendor technology alone caused portfolio growth. [5]
The agricultural and payroll examples solve different problems. One highlights seasonal lending capacity; the other connects eligibility checks and a time-sensitive offer process. Neither demonstrates that the same rules, data access or product design can be transferred unchanged into U.S. consumer lending. The lender must validate its own data permissions, reason codes and decision policy.
Scroll horizontally to see all columns.
| Evidence in a customer story | Reasonable interpretation | Additional evidence needed |
|---|---|---|
| Higher automated-processing share | The workflow handles more decisions without a manual step | Separate approvals, declines and referrals; review override outcomes. |
| Application throughput | More application value passes through the process | Funded balances, repeat submissions, withdrawals and later performance. |
| Faster eligibility checking | Data and rules can reach an offer sooner | Data freshness, unavailable-source fallback and completion rates. |
Current guidance and the production decision
The April 17, 2026 interagency revised model-risk guidance supersedes SR 11-7 and SR 21-8. The Federal Reserve’s SR 26-2 letter says it is expected to be most relevant to Fed-regulated banking organizations above $30 billion and emphasizes tailoring to risk, size and complexity. The older SR 11-7 source remains historical context; it should not be described as the current standalone guidance. This does not make the Federal Reserve letter a blanket requirement for every Farm Credit cooperative or foreign bank. [6]
A production review should distinguish a predictive model from the rules and workflow that consume it. Test whether a changed data feed changes eligibility, whether explanations reflect the actual decision and whether an unavailable dependency has a controlled fallback. A platform can support those controls; a vendor case study is not regulatory approval or independent validation of the buyer’s implementation.
Governance and validation questions
FICO has marketed features for AI models; the release explains the vendor’s approach but does not establish that any particular lender’s reasons are legally sufficient. A creditor remains responsible for accurate, specific reasons and fair-lending compliance. Model documentation, independent validation, input lineage, stability testing, overrides and outcome monitoring must fit the actual use. [2][3]
A controlled pilot should compare the platform decision with a current baseline using the same applicant population, outcome definitions and observation window. Track approval, pricing, fraud, , disparate outcomes, reason-code fidelity, latency and change failures. Validate the model separately from the decision strategy; a good score can still be used in a harmful policy.
Costs, lock-in and evidence
Enterprise deployment may require implementation services, data integration, licensing and specialist staff. A unified platform can reduce fragmentation, while increasing switching costs and making platform-wide failures consequential. Require exportable model artifacts, audit logs, rollback and tested continuity before relying on it for time-sensitive credit decisions. Public pages do not disclose a universal price.
Independent bank case studies with denominators, comparison groups and matured outcomes would strengthen a performance conclusion. Until then, attribute feature descriptions and customer claims to FICO. Evaluation criteria should include model governance, not only interface breadth.
Sources
- FICO — Platform overviewSourceBack to text: ↑
- FICO — Explainable AI product releaseSourceBack to text: ↑
- Federal Reserve/OCC — SR 11-7 model risk guidance archive and current statusOfficial source · Updated publisher linkBack to text: ↑
- FICO: Compeer Financial lending implementation; April 13, 2026; vendor/customer-reported resultsSourceBack to text: ↑1↑2
- FICO: Bradesco payroll-lending implementation; May 19, 2026; vendor/customer descriptionSourceBack to text: ↑
- Federal Reserve SR 26-2: Revised Guidance on Model Risk Management; April 17, 2026Official sourceBack to text: ↑