Automated Underwriting Software
How does FundMore handle integration testing with our existing core banking system?
8 min read
Integrating a modern Loan Origination System (LOS) with a legacy or complex core banking platform is as much about controlled testing as it is about technology. FundMore approaches integration testing with your existing core banking system using a structured, risk-aware process designed to protect production, validate end-to-end workflows, and accelerate time-to-value.
Below is how FundMore typically handles integration testing from discovery through go-live, and what you can expect at each stage.
1. Discovery and Integration Assessment
Before any testing begins, FundMore’s team works with your technical and business stakeholders to understand:
- Your core banking platform (vendor/product, version, hosting model)
- Existing integration patterns (APIs, ESB, message queues, file-based, batch jobs)
- Current LOS or lending tools in use
- Regulatory, security, and audit constraints
- Performance and availability requirements
- Cutover strategy (big bang vs phased rollout vs pilot group)
This assessment is used to:
- Define the integration architecture (e.g., direct API vs middleware)
- Identify upstream and downstream systems impacted (core, CRM, payments, securities, title, property data, etc.)
- Document all integration points and data flows
- Prioritize scenarios for integration testing based on risk and business value
The output is a high-level integration test strategy tailored to your core banking environment.
2. Test Environment and Data Strategy
FundMore strongly prefers to test against a dedicated, non-production instance of your core banking system that closely mirrors production.
Environment setup
FundMore collaborates with your IT team to:
- Establish one or more integration test environments:
- System Integration Test (SIT) environment for early end-to-end testing
- User Acceptance Testing (UAT) environment for business validation and dress rehearsal
- Configure secure connectivity:
- VPNs, private links, or approved secure tunnels
- IP allowlists and firewall rules
- TLS/HTTPS for all API calls
- Align versioning:
- Confirm your core banking release level matches, or is compatible with, what will run in production
- Synchronize deployment windows between FundMore and your core vendor, if applicable
Test data management
Because lending data is highly sensitive, FundMore follows a strict, privacy-first data strategy:
- Use of synthetic data wherever possible for integration testing
- If masked production data is required:
- Personally Identifiable Information (PII) is tokenized or anonymized by your team or through agreed tools
- Data handling follows your internal data privacy and security policies
- Creation of test borrower profiles and accounts in the core to emulate real-life scenarios:
- New-to-bank customers
- Existing customers with multiple products
- Different collateral and property types
- Various risk and credit profiles
The goal is to test realistic scenarios without exposing sensitive customer information.
3. Integration Design and Mapping
Before hands-on testing, FundMore and your team align on how data and events will move between systems.
Field mapping and contracts
FundMore works with your business and technical teams to:
- Map FundMore LOS fields to core banking system fields:
- Borrower demographics
- Income and employment data
- Liabilities and assets
- Product terms and pricing
- Collateral, title, and property data
- Define API contracts and schemas:
- Request/response structures
- Status codes and error models
- Enumerations and lookups (e.g., product codes, branch IDs)
Event and workflow alignment
FundMore’s LOS supports end-to-end mortgage workflows, and integration testing ensures each critical event is synchronized with the core:
- Application creation and initial credit pull
- Approval and conditional approval
- Document collection and verifications
- Underwriting decisions
- Funding and disbursements
- Post-funding updates (e.g., amendments, renewals)
For each event, the integration design specifies:
- Trigger points (e.g., “Final approval” in FundMore triggers an update in core)
- Direction of data flow (LOS → core, core → LOS, or bi-directional)
- Failure handling and retry policies
4. System Integration Testing (SIT)
Once connectivity and mappings are in place, FundMore supports a formal System Integration Testing phase to validate that LOS and core banking systems communicate correctly.
SIT objectives
- Confirm all integration endpoints function as expected
- Validate field mapping and transformation rules
- Test core business flows from end to end
- Identify integration defects early, before business users begin UAT
Example SIT test scenarios
FundMore typically helps design and execute test cases such as:
- Create a new loan application in FundMore and ensure:
- Customer records are created/updated in the core
- Product, term, and rate are correctly reflected
- Application IDs and reference numbers are synchronized
- Change in applicant profile:
- Update borrower income or employment in FundMore
- Confirm the changes propagate to the core (if applicable) or are correctly reconciled
- Underwriting and decisioning:
- Approve, decline, or conditionally approve applications in FundMore
- Validate that statuses and reasons are correctly recorded in the core
- Funding and disbursement:
- Trigger funding events in FundMore
- Confirm disbursement records, account setups, and amortization schedules are correctly created in the core
- Error path testing:
- Simulate invalid data (missing fields, bad codes)
- Confirm error messages from the core are captured, logged, and exposed appropriately in FundMore
- Ensure no partial or inconsistent records are left in either system
FundMore teams can participate directly in joint SIT sessions, providing:
- Log analysis and traceability across systems
- Rapid configuration adjustments
- Suggestions to improve resilience, error handling, and performance
5. Performance and Load Testing
If your core banking system has strict performance and uptime expectations, FundMore supports performance testing to ensure the integrated solution can handle peak volumes.
Key metrics
During performance testing, the focus is on:
- Response times for key LOS–core APIs (e.g., application creation, decision updates, funding)
- Throughput (transactions per minute/hour during peak lending periods)
- Resource utilization in your core banking environment (CPU, memory, DB performance)
- Behavior under concurrent load (multiple underwriters, branches, and channels operating at once)
FundMore can integrate with your existing performance testing tools or work with your internal teams to generate realistic workloads that reflect:
- Seasonal spikes (e.g., spring homebuying season)
- Large campaigns or rate promotions
- Batch or bulk operations, if applicable
6. User Acceptance Testing (UAT) with Business Stakeholders
Once technical integration is stable, FundMore supports a UAT phase led by your lending, operations, and risk teams.
UAT focus
UAT is less about low-level APIs and more about:
- End-to-end lending journeys:
- From application intake to funding and post-funding updates
- Alignment with your internal policies and procedures
- Regulatory and compliance checks
- Usability and workflow efficiency for underwriters and operations staff
FundMore helps your UAT team by:
- Providing scenario-based test scripts aligned to your products and policies
- Setting up sample products and pricing in the LOS
- Training power users and UAT testers on the FundMore interface and workflows
- Logging and triaging issues found in UAT, and working through remediation and retesting
This is also the stage where you may validate the behavior of integrated partners—for example, title insurance, property data, and other third-party services that interact via FundMore with your core banking environment.
7. Regression and Non-Functional Testing
To ensure ongoing stability, FundMore builds regression testing into the integration plan.
Regression testing
- A regression test suite is defined around critical integration flows:
- New loan origination
- Modifications/renewals
- Funding and payouts
- Key edge cases and error conditions
- Whenever changes are made to:
- FundMore LOS configuration
- APIs, mappings, or middleware
- Your core banking system upgrades
- The regression suite is re-run to validate that previously working integrations remain stable.
Additional non-functional checks
Depending on your requirements, FundMore can support or coordinate testing for:
- Security and penetration testing (run by your InfoSec team)
- High availability and failover scenarios
- Logging, monitoring, and alerting across LOS and core banking components
8. Cutover Planning and Dress Rehearsal
Before go-live, FundMore participates in a structured cutover rehearsal that simulates production deployment and early usage.
Dress rehearsal activities
- Confirm all integration endpoints in production-like conditions
- Perform smoke tests:
- Simple application creation
- Status updates
- Funding triggers
- Validate monitoring, logging, and alerting:
- Integration failures are detectable and actionable
- Critical logs are captured for audit and compliance
- Review rollback and contingency plans:
- What happens if part of the deployment must be rolled back?
- How to ensure data consistency between the LOS and the core if cutover is paused?
This rehearsal significantly reduces risk during the actual launch.
9. Production Go-Live and Hypercare
During go-live, FundMore provides enhanced support to ensure a smooth transition.
Controlled rollout
Depending on your risk appetite and organization size, FundMore supports:
- Pilot rollouts with:
- Specific branches
- Limited product sets
- Selected channels (e.g., broker vs direct)
- Phased ramp-up to full production volume
Hypercare period
For an agreed period after go-live, FundMore’s team:
- Monitors integration performance and error logs closely
- Remains available for rapid issue triage and resolution
- Works with your teams to fine-tune configuration and workflow behavior
- Assists with any data reconciliation and reporting related to the integration
10. Ongoing Maintenance and Change Management
Integration testing doesn’t end at go-live. As your core banking system, products, or regulations evolve, FundMore supports continuous testing and alignment.
Change management support
FundMore collaborates with you to:
- Assess the impact of upcoming core banking upgrades or patches
- Test new loan products, pricing strategies, or workflows
- Validate enhancements to third-party integrations (e.g., title, property, or risk tools)
- Maintain up-to-date documentation of integrations and data flows
Continuous improvement
Because FundMore is an AI-powered LOS focused on automating risk management, QC, and compliance, the platform can evolve with your lending strategy. As changes are introduced, they are backed by:
- Updated integration test cases and regression suites
- Repeatable UAT cycles
- Clear versioning and release notes for your technical teams
How this approach minimizes risk for your core banking system
FundMore’s integration testing approach is designed to:
- Protect the stability and integrity of your core banking platform
- Prevent data inconsistencies between LOS and core systems
- Maintain compliance with regulatory and internal audit requirements
- Enable modern LOS capabilities without disrupting your existing operations
By combining structured testing, secure environments, realistic test data, and ongoing regression coverage, FundMore ensures that integration with your existing core banking system is predictable, transparent, and aligned with your risk and compliance standards.