A community bank closes a mortgage loan. The lending team has done its work. But for the operations staff, the real grind is just starting. Every data field from the loan origination system needs to reach the core banking platform for servicing. Borrower names, interest rates, escrow details, payment schedules. At banks still running disconnected systems, someone types every field by hand from one screen to another. Industry data puts the error rate on manual re-entry between 1% and 5%, and each mistake triggers a correction cycle that delays loan boarding by days.
For community banks competing with national lenders on speed and accuracy, that post-closing bottleneck is a strategic liability. First Citizens Bank in Mason City, Iowa, decided to eliminate it by deploying MortgageExchange, ABT's cloud-managed integration platform, to connect Empower LOS directly to Finastra Fusion Phoenix.
First Citizens Bank: Technology Investment at Community Scale
First Citizens Bank is a family-owned community bank headquartered in Mason City, Iowa, with eight locations across North Iowa and Minnesota. With over $1.8 billion in assets and more than 200 employees, First Citizens operates at the scale where technology investments produce measurable returns while maintaining the personal service of a locally owned institution.
The bank has partnered with Finastra for nearly 30 years to power its core operations. In 2023, First Citizens migrated Finastra's Fusion Phoenix to the cloud on Microsoft Azure, gaining faster access to platform updates and reducing on-premises infrastructure costs. On the lending side, the bank uses Empower LOS from Dark Matter Technologies for mortgage origination.
Advanced platforms on both sides. But historically, no automated connection between them. Every closed loan required manual re-entry from Empower into Phoenix. The same bottleneck that thousands of community banks face nationwide, costing hours of staff time per day and introducing compliance risk at every keystroke.
The Disconnect Between Origination and Servicing
Loan origination systems and core banking platforms were not built to talk to each other natively. A community bank running Empower for origination and Finastra Fusion Phoenix for servicing has two independent data stores that need to share loan information at the moment of closing.
Without automation, the post-closing process looked like this at First Citizens:
- A loan closes in Empower. Staff print or copy the loan data on screen.
- The same staff open Phoenix and manually enter every data point: borrower information, loan terms, escrow details, payment schedule, insurance information.
- A second person reviews the entry for errors. Under time pressure, that review is often cursory.
- Discrepancies surface days or weeks later when statements don't match or a regulatory report pulls conflicting data from the two systems.
For a bank handling hundreds of mortgage closings per month, this process consumed significant staff hours and created compliance risk that grew linearly with loan volume. Every new loan was another manual handoff waiting to go wrong.
How MortgageExchange Connected Empower to Phoenix
First Citizens partnered with Access Business Technologies to deploy MortgageExchange between Empower LOS and Finastra Fusion Phoenix. MortgageExchange is ABT's cloud-managed integration platform, purpose-built for financial services, that connects 40+ mortgage technology systems including every major LOS and core banking platform.
The data flow after MortgageExchange:
- Loan closes in Empower. MortgageExchange receives the complete loan record automatically.
- Rules-based validation runs. Every field is checked: required fields present, values within expected ranges, data types correct. MortgageExchange understands mortgage-specific business rules, not just generic data transformation. It knows what a valid escrow calculation looks like and which fields are required for FFIEC reporting.
- Exceptions flag immediately. A missing field, out-of-range value, or data format mismatch gets flagged for human review instead of silently passing through to the core.
- Clean data flows into Phoenix. No re-keying. No second-person verification of manually entered data. The validated loan record posts directly into Phoenix for servicing.
- Full audit trail. Every transfer is logged with what was sent, when, and whether any exceptions were raised. That documentation feeds directly into examination readiness.
For First Citizens Bank, this eliminated 100% of manual re-entry for post-closing loan boarding. Loans that took hours to board now completed in minutes. Staff time shifted from clerical data entry to customer service and exception handling.
The Business Impact Beyond Efficiency
Eliminating manual re-entry was the obvious win. The downstream benefits matter more to bank leadership.
Compliance and Audit Readiness
When origination and servicing records are populated from the same automated data source, they match. Regulatory reports pulling from Phoenix align with origination records in Empower. FFIEC examiners and OCC reviewers see consistent data across systems. The audit trail from MortgageExchange provides documentation that manual processes never could.
For community banks under federal examination, data consistency between systems isn't optional. It's a regulatory expectation. The NCUA's first year of mandatory incident reporting revealed 1,072 incidents at credit unions, with 70% involving third-party vendors. Banks face similar scrutiny from OCC and FDIC examiners focused on vendor management and integration security.
Customer Experience
Borrowers expect their new mortgage to appear in online banking promptly after closing. MortgageExchange delivers that experience by boarding loans in minutes, not days. Welcome letters, payment schedules, and online account access happen on time because the data arrived in Phoenix immediately.
For community banks competing against national lenders with fully digital experiences, post-closing speed is a retention factor. A smooth onboarding experience validates the borrower's choice to work with a community institution rather than a national bank.
Scalability Without Headcount
Manual re-entry doesn't scale. When loan volume increases during refinance booms or purchase season, the only option is overtime or temporary staff. MortgageExchange handles increased volume without additional headcount. The same pipeline that processes 50 closings per month handles 200 without configuration changes.
For community banks planning growth through acquisition or expanded lending programs, integration scalability is infrastructure that needs to be in place before volume increases, not retrofitted under pressure.
Security at the Integration Layer
Every data transfer between origination and servicing systems carries sensitive borrower information: Social Security numbers, financial details, property records. MortgageExchange enforces security controls at the same level as the systems it connects.
- Encryption. Data encrypted in transit (TLS 1.2+) and at rest. No plaintext borrower data moving between systems.
- Authentication. Both endpoints authenticate before data flows. Service accounts with dedicated credentials, monitored and rotated on schedule.
- Access controls. Integration service accounts have minimum necessary permissions. No shared credentials between integration and user-facing systems.
- Monitoring. Connection health, data throughput, error rates, and authentication events tracked continuously. Failures alert the operations team before they affect loan processing.
Because MortgageExchange operates within ABT's managed IT environment, integration security is part of the same monitoring and incident response framework that covers Microsoft 365, endpoints, and network infrastructure. No blind spots between systems.
Why Community Banks Are Moving Away From Point-to-Point Connectors
Community banks evaluating LOS-to-core integration typically see three options:
- Custom point-to-point. A developer writes a connector between your specific LOS and core platform. Fragile, expensive to maintain, breaks when either vendor releases an update. The bank is one developer departure away from losing the institutional knowledge that keeps it running.
- Vendor-maintained middleware. The LOS or core vendor offers an integration product. Better than custom, but typically maintained by one side with limited visibility into the other. When the LOS vendor updates their API, the middleware vendor may lag months behind.
- MortgageExchange through ABT. A managed integration platform built for financial services, with pre-built connectors for 40+ systems, mortgage-specific validation rules, and ongoing maintenance. Updates on either side are coordinated proactively. Security monitoring is integrated with the rest of the bank's infrastructure.
The 2026 outlook for community banking makes integration capability more urgent. Core systems averaging 20 to 40 years old can't support the real-time operations and data analytics that competitive institutions require. Every technology investment a community bank makes depends on the systems being connected. MortgageExchange is how that connection happens without building and maintaining custom plumbing.
ABT serves 750+ financial institutions as a cloud-first MSP and Tier-1 Microsoft CSP, with deep experience connecting LOS platforms, core banking systems, and the compliance infrastructure that holds them together.
The Bottom Line
First Citizens Bank eliminated the post-closing bottleneck between Empower LOS and Finastra Fusion Phoenix by deploying MortgageExchange. The result: loans boarding in minutes instead of hours, data accuracy that passes examination scrutiny, and staff freed from clerical re-entry to focus on customers.
For community banks wrestling with disconnected origination and servicing systems, the integration gap isn't a minor inefficiency. It's a structural drag on speed, accuracy, and compliance that compounds with every loan closed.
Talk to an ABT specialist about MortgageExchange integration for your bank. Or get a free Microsoft 365 Security Assessment to evaluate your current technology stack.
Frequently Asked Questions
Related Articles
- Breaking the Mortgage Data Bottleneck: Patelco Credit Union's Integration Success
- How Bay Federal Credit Union Streamlined Post-Closing with MortgageExchange
- Lafayette Federal Credit Union Integrates Corelation Keystone and Calyx Path with MortgageExchange
How does MortgageExchange connect Empower LOS to Finastra Fusion Phoenix?
MortgageExchange sits between Empower and Finastra Fusion Phoenix as a cloud-managed integration layer. When a loan closes in Empower, MortgageExchange receives the complete loan record, validates every field against mortgage-specific business rules, and posts the clean data directly into Phoenix. The entire transfer is encrypted, authenticated, logged, and completed without manual intervention.
What compliance benefits does automated LOS-to-core integration provide community banks?
Automated integration through MortgageExchange ensures origination and servicing records match because both are populated from the same validated data source. FFIEC examiners and OCC reviewers see consistent data across systems. The audit trail documents every transfer with timestamps, validation results, and exception flags. This eliminates the data discrepancies that manual re-entry introduces and simplifies examination preparation.
Why did First Citizens Bank choose MortgageExchange over building a custom integration?
Custom integrations require specialized knowledge of both the LOS and core APIs, which change with every vendor update. MortgageExchange includes pre-built connectors for 40+ mortgage technology systems with mortgage-specific validation rules. ABT maintains all connectors as vendors release updates, so the bank never falls behind on compatibility. The managed approach lets the bank's IT team focus on customer-facing technology.
How does MortgageExchange handle loan data security between bank systems?
MortgageExchange encrypts all data in transit using TLS 1.2+ and at rest on Microsoft Azure. Both endpoints authenticate before any data flows. Service accounts use dedicated credentials monitored and rotated on schedule. MortgageExchange operates within ABT's managed IT environment, so integration security shares the same monitoring, alerting, and incident response framework covering the bank's Microsoft 365 tenant and endpoints.
Can MortgageExchange scale with increasing mortgage loan volume at community banks?
MortgageExchange runs in ABT's cloud environment on Microsoft Azure and scales automatically with loan volume. The same integration pipeline handling 50 closings per month handles 200 or more without configuration changes or additional infrastructure. Community banks planning growth through acquisition or expanded lending programs get integration scalability built in from day one.

