Yes. Finance and risk professionals will find that support assumption setup, calibration, and review do not require advanced modeling expertise. Built-in documentation and transparent logic make it easy for teams to understand results, explain changes, and collaborate across departments.

Model IQ includes built-in model validation support, including version control, change tracking, and full audit trails. Teams can compare their assumptions over time, document rationale, and retain historical versions without manual files or spreadsheets.

Model IQ is purpose-built for banking use cases, not generic AI modeling. It supports flexible scenario analysis and integrates directly with CECL, ALM, liquidity, and planning workflows. Assumptions flow through the platform without exports, rekeying, or reconciliation, eliminating handoffs that would otherwise slow teams.

CECL stands for Current Expected Credit Loss. It is the accounting standard under ASC 326 that replaced the older incurred loss model for estimating loan losses: instead of waiting until a loss is probable, every institution must estimate lifetime expected credit losses on its entire loan portfolio from the moment a loan is originated.

For large banks, CECL is a modeling exercise handled by dedicated risk teams. For community banks and credit unions, it is usually run by the CFO personally, using a spreadsheet or a point solution purchased to get into compliance quickly. That makes the quarterly process operationally fragile, hard to document consistently, and stressful to defend during audits or exams.

CECL matters for community banks not just because it is a regulatory requirement, but because it creates ongoing operational and governance demands that most small finance teams were not built to handle. Institutions that treat CECL as a repeatable, documented process supported by the right tools get cleaner audit opinions and more confident responses to examiner questions.

CECL compliance deadlines passed years ago, but the operational burden has not gone away. Economic volatility has increased scrutiny on reserve adequacy and methodology justification, which keeps the workload high even for institutions that have been compliant for years.

The core challenge is that CECL requires community banks to do three things at once: estimate lifetime credit losses using forward-looking economic assumptions, document those assumptions so auditors and examiners can independently verify them, and repeat that process accurately every quarter without errors.

Common problems that persist in 2026 include:

• Limited historical loss data: many community banks have too few loan defaults in their history to build statistically robust models.
• Lack of internal credit modeling expertise.
• A manual, quarterly process run in Excel or a basic vendor tool.
• Difficulty validating and documenting Qualitative and Environmental (Q and E) factor adjustments.
• Ongoing uncertainty about what an examiner will challenge next quarter.

Many institutions completed their initial CECL transition during or after COVID, when actual loan losses were abnormally low. Depending on methodology quality, some under-reserved during that transition and have seen volatile CECL estimates ever since, which generates recurring questions from auditors, regulators, and boards.

At most community institutions, the CFO owns the CECL process entirely; it is not a delegated function the way it often is at larger banks.

The economic buyer for a CECL solution is almost always the CFO, with the CEO as an approver on larger deals. Key influencers include the Controller, the Credit Risk Manager, the Chief Credit Officer, and sometimes external auditors who can informally validate which vendor solutions they have seen used successfully in exams. The actual users of the system are typically the CFO and Controller, along with a small finance or accounting team.

This buyer profile shapes how CECL should be sold: community bank CFOs are not looking for enterprise software with a long implementation project. They want a solution that is defensible, repeatable, and simple enough for their existing team to run every quarter.

Empyrean CECL addresses five recurring problems in community bank CECL processes:

• Spreadsheet fragility. Excel has no workflow, version control, or audit trail, so a single formula error or file issue can compromise a quarter's work. Empyrean replaces manual spreadsheet processes with an automated, governed workflow.
• Missing audit trail. Every assumption, methodology choice, and calculation is captured in real time and available for examiner review, instead of being reconstructed after the fact.
• Key-person risk. At most community banks, one or two people understand how the CECL model works. Empyrean embeds the process in the system rather than in a spreadsheet only one person understands.
• Disconnected systems. Because Empyrean CECL runs on the same data platform as Empyrean ALM, liquidity, and planning, CECL assumptions and results do not need to be reconciled against other systems.
• Rigid implementations. Empyrean supports a start-simple-and-grow approach: banks can launch with foundational CECL compliance and add scenario analysis and methodology sophistication over time, without a rip-and-replace event.

Empyrean CECL supports the methodologies most commonly used by community and mid-sized financial institutions: Weighted Average Remaining Maturity (WARM), Probability of Default and Loss Given Default (PD/LGD), Static Pool and Cohort analysis, and Discounted Cash Flow (DCF).

Empyrean does not force a single method. Community banks with limited historical loss data often start with WARM and bring in peer Call Report data for benchmarking. Institutions with more data and more complex portfolios can use PD/LGD or DCF for specific pools while keeping simpler methods for others.

Empyrean also supports institutions that bring their own credit risk parameters, such as internally developed PD and LGD estimates, as well as institutions that need to source those parameters externally. Institutions that need to load and derive credit risk parameters internally may also use Empyrean Model IQ alongside CECL.

Empyrean CECL is built around the three things auditors and examiners evaluate most in a bank's CECL process: transparency, consistency, and documentation.

• Transparency: every number in the CECL calculation has a clear lineage. Empyrean provides a complete, always-current audit trail of inputs, assumptions, and outputs, so a reserve estimate can be traced back to its source without the CFO reconstructing the logic from memory.
• Consistency: Empyrean's structured workflow applies the same methodology the same way each quarter, so changes in reserve levels reflect changes in the portfolio or economic assumptions, not inconsistencies in how the model was run.
• Documentation: assumption choices, Q and E factor adjustments, and scenario selections are recorded as they are made. When an examiner asks how a number was calculated, the documentation is already generated.

Excel is free, familiar, and functionally capable of producing a CECL estimate, but it is operationally fragile in ways that matter more as institutions grow and regulatory scrutiny increases.

• No workflow: files get emailed, renamed, and edited without version control, and a formula can be accidentally overwritten.
• No audit trail: when an examiner asks a bank to walk through its methodology, the answer is often a manual reconstruction from memory and notes.
• No scalability: a portfolio that doubles in size requires double the manual data entry and reconciliation, and double the opportunity for error. Many institutions comfortable with Excel at $500 million in assets find it unmanageable at $1.5 billion.

Empyrean CECL automates the calculations and documentation, creates institutional knowledge that survives staff turnover, and scales as the loan portfolio grows. The move from Excel to Empyrean is a shift from a personal, manual process to a governed, repeatable one.

Empyrean CECL is built on Empyrean Dataverse, the same underlying data platform as Empyrean's ALM, liquidity, and planning modules. This shared architecture is what differentiates Empyrean from other CECL vendors serving community and mid-sized financial institutions.

In practice, the economic assumptions driving a CECL estimate, such as interest rate forecasts, prepayment expectations, and credit loss projections, are the same assumptions used in the institution's ALM model and budget. There is no separate data feed, no reconciliation spreadsheet, and no risk that a CECL reserve and an ALM stress test are built on different views of the economy.

For CFOs managing CECL, ALM, and budgeting at the same time, this integration removes one of the most time-consuming parts of the quarterly close: explaining why numbers from three different systems do not agree. It also means CECL results can flow directly into profitability analysis and balance sheet planning.

Yes. Empyrean CECL supports institutions that bring their own credit risk parameters, including internally developed probability of default and loss given default estimates, proprietary prepayment assumptions, and institution-specific Q and E factor frameworks.

Institutions that prefer to use peer Call Report data as a benchmark rather than building their own loss history can do that instead. The right choice depends on the institution's data availability, portfolio complexity, and what examiners in that region have been comfortable with.

Empyrean does not impose a black-box model that the CFO cannot explain. Every assumption in the CECL estimate can be documented, justified, and traced, so if an examiner asks why a specific Q and E adjustment was made, the answer is in the system rather than in the CFO's memory.

“Start simple and grow” is Empyrean's approach to reducing CECL implementation risk. Many community banks hesitate to adopt a vendor CECL solution because they fear the learning curve, implementation complexity, and disruption to their quarterly close.

Empyrean lets institutions start with straightforward CECL compliance and add sophistication over time: a bank can launch using the WARM methodology with conservative assumptions, complete its first quarterly close, and then incrementally add approaches such as PD/LGD for specific loan pools or scenario analysis as the team builds confidence.

This reduces adoption risk during the first, already-stressful CECL close, and it avoids a rip-and-replace event as the institution grows. A bank that starts at $1 billion in assets and grows to $3 billion does not need a new CECL platform; Empyrean scales with it. This phased approach also aligns with what auditors and examiners typically expect: there is no regulatory requirement to use the most complex methodology available, only that the methodology chosen is appropriate, consistently applied, and thoroughly documented.

Empyrean CECL is built for community banks and credit unions with a sweet spot in the $500 million to $10 billion asset range. The ideal profile includes institutions that:

• Currently run CECL in Excel or a basic standalone tool.
• Already use Empyrean ALM or Planning and want to unify balance sheet management on one platform.
• Use, or are considering, the WARM methodology, or want to bring their own credit parameters.
• Have experienced examiner or auditor scrutiny on their CECL process and need a more defensible, governed approach.

Empyrean CECL is not currently the right fit for institutions over $10 billion in assets, institutions that need Empyrean to build complex custom models on their behalf (those institutions may need Model IQ alongside CECL), or institutions committed to the nCino ecosystem that prefer Visible Equity for that reason.

Existing Empyrean ALM and Planning customers are the most natural fit. Because CECL runs on the same Dataverse platform, onboarding is faster, data is already in the system, and the integration benefits are immediate rather than requiring a separate project.

Empyrean CECL provides a structured Q and E factor framework that captures the rationale for each adjustment at the time it is made and stores that documentation in the audit trail, so the answer to an examiner's question is already on file rather than reconstructed from memory or email.

Q and E factors are one of the most judgment-intensive parts of any CECL process, and one of the areas where community bank CFOs most often feel exposed. Adjustments must be justified, documented, and defensible, and examiners increasingly focus on whether they are applied consistently with appropriate supporting rationale.

The framework supports both qualitative adjustments based on internal factors, such as changes in underwriting standards or portfolio concentration, and environmental adjustments based on external factors, such as regional economic conditions or industry-specific stress. It is flexible enough to accommodate institution-specific factor definitions while maintaining the structured documentation examiners expect.

A successful CECL outcome means the CFO can complete the quarterly close without a fire drill, every assumption is documented and traceable before the auditor asks to see it, and the CFO can walk an examiner through the methodology clearly and calmly, without calling a vendor or searching for last quarter's spreadsheet version.

Success is not about having the most sophisticated model. It is about confidence, control, and consistency, including consistency between the bank's CECL numbers and what its ALM model and budget say about the economic environment. Inconsistencies across risk and finance functions are a red flag for examiners and auditors, and an integrated platform removes that risk.

A well-run CECL process is a quiet one: it runs in the background, produces defensible results, and does not consume the CFO's personal time every quarter. That is what Empyrean CECL is designed to deliver.