An advanced integration platform connecting your core banking, credit cards, and financial systems to Kollect through online and batch interfaces, powered by Kollect*ETL.
Every collection, every recovery action, every receivable workflow depends on data flowing in from somewhere else, core banking, card management systems, ERP, and host systems. Kollect*ETL is the connective tissue that makes Kollect work in heterogeneous, real-world environments.
Most Malaysian institutions run on a mix of legacy core banking, card management systems, and homegrown databases. Getting clean, timely, reconciled data into a downstream platform is rarely a solved problem; it is a continuous engineering tax.
Silverlake here, FlexCube there, a card system from a different vendor, an Islamic core, a legacy AS/400. Each has its own export format, schedule, and quirks. Building point-to-point connectors does not scale.
End-of-day file drops mean collectors and recovery teams operate on yesterday's truth. By the time a payment posts, the call has already been made.
Operations teams babysit SFTP transfers, rerun failed jobs, and email failure notices. Lights-out automation remains aspirational rather than operational.
Card authorisations, balance enquiries, payment postings, all of it needs an online channel. Without ISO 8583, Web Services, or message broker support, real-time integration is a custom build every time.
When the core banking system goes through a release cycle, every downstream interface tends to break. Without an abstraction layer, the integration team becomes the upgrade bottleneck.
Data that arrives partial, duplicated, or out of order has to be caught somewhere. If reconciliation lives in spreadsheets, errors compound and audit trails weaken.
Bank Negara Malaysia's Financial Sector Blueprint 2022-2026 sets a clear direction: financial institutions are expected to achieve at least 85% digital transaction volume, with corresponding upgrades to core systems for real-time processing, API integrations, and cybersecurity under the Risk Management in Technology framework.
The headline is digitalisation. The actual delivery is integration work, on the wire, in production, between heterogeneous host systems that were never designed to talk to each other in real time.
Source: Bank Negara Malaysia, Financial Sector Blueprint 2022-2026
Six quick questions. No data leaves your browser. At the end you'll see where your integration sits on the maturity curve, and which Kollect*ETL capabilities matter most for you.
Kollect*ETL (also known as Kollect*Integrator, ETTL) is a Data Extraction Platform with Transformation, Transportation (SFTP), and Loading modules, built to facilitate integration with a multitude of Core Banking, Credit Cards, and other Financial systems.
It pairs a faceless deployment engine that runs lights out in an automated environment with online real-time host interfaces supporting ISO 8583, Web Services, and Silverlake DSP. It also supports the IBM WebSphere Message Broker environment, and Web Services integration via SOAP, WSDL, and REST.
Whether you operate a single core banking environment or a heterogeneous estate across consumer, cards, Islamic, and corporate, Kollect*ETL gives you a single integration spine, the same backbone every other Kollect product (Kollect*Apps, Kollect*Valley, Kollect*eInvoicing) deploys against.
Kollect*ETL is the connective layer for organisations running heterogeneous core banking, card, ERP, and finance systems, both conventional and Islamic, across consumer, commercial, and corporate lines.
Each capability stands on its own and strengthens the others when combined. Click any tab to explore what it does and where it fits.
Banks running heterogeneous core estates where each product line, cards, loans, mortgages, trade finance, sits on a different host. If your integration team is building point-to-point extractors by hand for every new feed, this is your starting capability.
Talk to UsIntegration teams whose downstream platforms (collections, recovery, receivables, ERP) need consistent, validated data. Particularly valuable when source systems disagree on customer IDs, account number formats, or currency representations across products.
Talk to UsOperations teams managing dozens of inbound and outbound feeds across hosts, branches, and third parties. If your team currently logs into multiple servers to verify file drops or rerun failed transfers, this is the layer that makes that work disappear.
Talk to UsInstitutions running Kollect alongside legacy collections, recovery, or finance systems. Particularly relevant for migrations where source and target need to run in parallel for a period, and reconciliation between the two has to be airtight.
Talk to UsCard issuers, switch operators, and any institution where downstream systems need to query the host for live balances, authorisation status, or payment confirmations. Particularly relevant for collections and recovery teams who want to act on the latest data, not yesterday's batch.
Talk to UsOperations teams running 24/7 environments where someone is currently paid to babysit overnight batches. Also relevant to leaner integration teams that want to scale feed coverage without scaling headcount, the cost of operating a feed should not grow linearly with the number of feeds.
Talk to UsFive stages, one orchestration spine, built to run lights out across batch and online modes. Operators step in only when an exception demands attention.
Almost 3 decades of deep banking, government, receivables, cash flow, and treasury experience, engineered into a single AI-driven platform.
Advanced AI is woven throughout the platform, intelligently learning to advise on customer engagement, propensity to pay, and treatment strategy.
Decades of banking, government, receivables, cash flow, treasury, and payments knowledge, embedded in every module's design.
Dedication, innovation, and commitment as integral attributes, focused teams that deliver value, not just software.
Engage as SaaS or fully procure the platform. The choice depends on your budget, timeline, and operational requirements.
Book a session with our integration team. We'll review your current host estate, identify the capabilities that matter most, and show you what your data spine could look like.
Fields marked * are required.
