Finacle Cross-System Integrations - Gaddiel Essuman-Acquah

Problem

GTBank’s Finacle core banking migration in 2024–2025 required deep integration across four critical systems that previously operated in isolation: Finacle CBA, Alfresco DMS for document management, ProcessMaker for workflow approvals, and SWIFT for interbank transactions. Each system had its own data model, authentication, and integration patterns. Without coordinated integrations, the migration would have created daily operational friction for 500+ users.

A second challenge: 4M+ customer and account records had to move from Oracle source systems into Finacle-ready datasets, organised by branch and currency, with full integrity controls.

Approach

Led the data workstream and built the integration layer across all four systems.

Oracle to Finacle ETL. Designed and ran the end-to-end extraction, transformation, and reconciliation pipeline. 4M+ records extracted from Oracle source systems, transformed into Finacle-ready structures, reconciled by branch and currency.
Finacle / Alfresco DMS. Integrated via CMIS and REST APIs. Workflow attachments stored in Alfresco are now retrievable directly from Finacle screens.
Finacle / ProcessMaker. REST API integration enabling workflow-driven access to core banking data for 500+ users. Approvals, compliance reviews, and operational workflows all now touch Finacle data without manual lookups.
Finacle / SWIFT. Automated bidirectional SWIFT message processing between Finacle and SWIFT servers via secure SSH (Bitvise). Real-time transaction sync, no manual reconciliation.
Data integrity controls throughout. Every ETL stage includes row counts, checksum validation, and a reconciliation report. Discrepancies surface immediately, not after cutover.

Data integrity has to be built INTO the pipeline, not bolted on after. Row counts and checksums at every stage caught issues that would have been invisible at cutover.

Architecture

Oracle source branch · currency

→

ETL pipeline checksum · reconcile

→

Finacle CBA core banking

→

Alfresco · PM · SWIFT downstream integrations

Four heterogeneous systems, four different integration philosophies. Alfresco speaks CMIS; ProcessMaker speaks REST; SWIFT speaks SWIFT messages over an SSH channel; Finacle is the spine. The right pattern for each is the one its system supports natively, not the one we’d standardise on for convenience.

What it shipped

4M+ records migrated with full data-integrity controls

4 systems connected into a coherent integration fabric

500+ users with workflow-driven access to core banking

The migration cutover executed without operational discontinuity. SWIFT reconciliation that had been daily and manual became real-time and audited. Workflow approvals that had been “look up the customer in Finacle, then approve in PM” became a single screen.

Reflections

Integrating across heterogeneous banking systems is a discipline. CMIS for Alfresco, REST for ProcessMaker, message-based SWIFT. The right pattern is the one each system supports natively, not the one you’d standardise on.
Build data-integrity controls into the pipeline, not on top of it. Row counts and checksums at every transform stage caught discrepancies during the run that would have been invisible at cutover. Adding them later would have meant rerunning the migration.
SSH-driven SWIFT integration sounds old-fashioned but works reliably and is easier to audit than message-broker alternatives in a regulated environment. The boring choice was the right one.
Coordinating four integration paths around one cutover date forced the discipline that open-ended work doesn’t. Hard dates clarify priorities.