For many financial institutions, a core processor conversion is one of the largest and most complex technology investments they will make. Whether moving to a new platform from Fiserv, Jack Henry, FIS, Corelation, or another provider, these projects often require significant investments in technology, personnel, training, consultants, and operational resources.
Most institutions devote considerable attention to selecting the right provider, negotiating contracts, and planning the implementation. However, the accounting treatment of conversion-related costs is often overlooked until the project is already underway. That can create challenges when management, auditors, or regulators begin evaluating which costs can be capitalized and which must be expensed.
Under current accounting guidance, including ASC 350-40 and ASU 2018-15 for qualifying cloud-based solutions, the key consideration is whether a cost creates or enhances the software asset. While that sounds straightforward, the reality is that a core conversion includes hundreds of individual activities, each of which may have a different accounting outcome.
While the accounting implications are important, they’re only part of the picture. A successful core conversion requires coordination across accounting, operations, compliance, risk management, internal audit, and executive leadership. Institutions that take a comprehensive approach are often better positioned to manage costs, maintain effective oversight, and avoid surprises throughout the implementation process.
Understanding the Full Cost of a Core Conversion
One of the biggest surprises institutions encounter during a core conversion is that the total project cost is often significantly higher than the contract price presented by the provider.
Beyond software licensing and implementation fees, institutions frequently incur costs related to consultants, training, project management, data conversion, process redesign, vendor integrations, internal labor, deconversion activities, and post-conversion support.
From an accounting perspective, these costs are not all treated the same.
Under current accounting guidance, costs that directly create or enhance the software asset are typically eligible for capitalization. This often includes implementation activities such as software configuration, customization, interface development, programming, testing, and certain direct implementation costs.
However, many other costs associated with the conversion must be expensed as incurred. Training, vendor evaluations, contract negotiations, change management activities, and most data conversion efforts generally fall into this category.
As a result, leadership teams should not assume that the majority of project costs will be capitalized. Depending on the scope of the conversion, a substantial portion of spending may flow directly through the income statement during the implementation period.
Contract Terms Matter More Than Many Institutions Realize
The accounting impact of a core conversion can begin long before implementation starts.
Providers often offer incentives designed to make a conversion more attractive, including implementation fee waivers, credits, contract incentives, or favorable pricing structures. While these arrangements can help reduce upfront costs, institutions should take a closer look at the overall economics of the agreement.
What appears to be a waived fee may ultimately be recovered through recurring processing charges or other contractual terms. Likewise, deconversion fees payable to an outgoing provider can significantly increase the overall cost of the project, even though those costs typically do not create a future asset and are generally expensed.
Because of this, institutions should carefully review pricing schedules, statements of work, incentives, amendments, and termination provisions before finalizing contracts. These details not only affect project economics but can also influence future accounting conclusions.
Data Conversion Continues to Be a High-Risk Area
Few aspects of a core conversion require as much effort as moving data from one platform to another.
Data often needs to be cleansed, mapped, reconciled, validated, and tested before the new system can go live. While these activities are critical to a successful conversion, they are also one of the most scrutinized areas from an accounting standpoint.
Institutions are often surprised to learn that many data conversion activities are generally not capitalizable, even when they consume significant resources and represent a major project milestone.
Because auditors and regulators frequently focus on costs categorized as data conversion, institutions should maintain clear documentation supporting how these costs are tracked, evaluated, and classified throughout the project.
Internal Audit Can Add Value Before the Conversion Begins
While accounting is an important consideration, focusing solely on financial reporting can leave institutions exposed to broader project risks.
A core conversion touches nearly every function within the organization, including deposits, lending, treasury management, digital banking, financial reporting, cybersecurity, compliance, and vendor management. The scale of change creates opportunities for operational disruptions, control gaps, and unforeseen risks if not carefully managed.
This is why involving internal audit early in the process can be so valuable. Rather than waiting until after implementation, internal audit can help institutions identify higher-risk areas, evaluate project governance structures, assess key controls, and determine whether additional oversight or testing may be needed during critical phases of the conversion.
We frequently work with institutions before a core conversion begins, helping management evaluate project risks and adjust audit plans accordingly. In many cases, this includes modifying the timing of audits, increasing focus on certain operational areas, or providing independent insight into project readiness and control design.
By involving internal audit from the outset, institutions can strengthen governance, improve accountability, and help reduce surprises during implementation.
Looking Ahead to Future Accounting Changes
Financial institutions planning large technology initiatives should also keep an eye on evolving accounting guidance.
ASU 2025-06 modernizes the accounting framework for internal-use software by removing the project stage framework and replacing it with a principles-based approach. The standard is expected to affect future technology projects, including core conversions. Although it is not expected to significantly change which costs are capitalized, it may affect when capitalization begins and could require institutions to revisit how they track project expenditures and document decision-making throughout the project lifecycle.
Organizations should consider establishing disciplined processes for project accounting, cost tracking, and documentation for future implementations sooner rather than later.
What Boards & Executive Teams Should Be Asking
As institutions evaluate a core conversion, leadership should look beyond timelines and implementation milestones and ask:
- Do we understand the full economic cost of the conversion?
- Which costs are likely to be capitalized versus expensed?
- Are contract incentives and fee structures fully understood?
- How are we tracking project costs and supporting accounting conclusions?
- Have we identified operational, compliance, and cybersecurity risks associated with the conversion?
- Is internal audit sufficiently involved in project oversight?
- Do we have the governance structure necessary to support a successful transition?
The Bottom Line
A core processor conversion is much more than a technology project. It is a significant financial, operational, and governance initiative that requires thoughtful planning long before the system goes live.
By understanding the accounting implications of project costs, evaluating contract terms carefully, maintaining strong documentation, and involving internal audit early in the process, financial institutions can better manage risk and position themselves for a smoother, more successful conversion.
As institutions navigate these decisions, it’s also important to stay informed about broader accounting and regulatory developments affecting the banking industry. Our article, OCC Updates Bank Accounting Advisory Series, explores recent OCC guidance and other considerations that may be relevant to financial institution leaders.
If you have any questions or are interested in learning more, we are here to help. Please do not hesitate to reach out to discuss your specific situation.
This material has been prepared for general, informational purposes only and is not intended to provide, and should not be relied on for, tax, legal or accounting advice. Should you require any such advice, please contact us directly. The information contained herein does not create, and your review or use of the information does not constitute, an accountant-client relationship.
