Skip to main content

Migrate from FIS

FIS (Fidelity National Information Services) provides reconciliation and treasury management through several products, including FIS Integrity (cash and treasury), FIS Profile (banking platform), FIS AvantGard (treasury and reconciliation), and FIS Treasury and Risk Manager. These products have deep legacy in mid-to-large banks but present several operational challenges that FVI addresses.

Why migrate from FIS​

Frequent pain points reported by FIS reconciliation users include:

  1. High total cost of ownership — FIS products require ongoing license fees, plus dedicated infrastructure and support.
  2. Limited AI/ML — FIS products are rule-based and lack modern AI/ML matching and exception triage.
  3. Slow change velocity — FIS product changes require vendor involvement with multi-month lead times.
  4. Aging user interface — FIS products use older terminal-style or thick-client interfaces that don't match modern UX expectations.
  5. Limited cloud support — FIS products are largely on-premise, with limited cloud-native capabilities.
  6. Vendor lock-in — FIS data formats and APIs are proprietary, making it expensive to migrate or add integrations.

FVI addresses each of these with a modern, AI-native, cloud-native reconciliation platform that integrates cleanly with FIS via standard file formats and APIs.

Migration approach​

FVI's migration approach is staged over 8-16 weeks (longer than SAP/Oracle migrations due to FIS data complexity):

Phase 1: Discovery (3 weeks)​

  • Document current FIS reconciliation landscape (Integrity modules, AvantGard accounts, Profile accounts)
  • Identify reconciliation volumes, exception rates, and SLA breaches
  • Map FIS master data (accounts, counterparties, rules) to FVI's data model
  • Identify all downstream consumers of FIS reconciliation output

Phase 2: Data extraction (2 weeks)​

  • Extract FIS reconciliation history, rules, and audit trail
  • Convert FIS data formats to FVI's import format
  • Validate the conversion with sample data
  • Resolve data quality issues

Phase 3: Shadow run (3-4 weeks)​

  • Deploy FVI in the customer's environment
  • Configure FVI to ingest the same transaction streams as FIS (file drop, API, MQ)
  • Run FVI reconciliation in shadow mode (parallel to FIS, no downstream impact)
  • Compare FVI output to FIS output, identify and resolve discrepancies

Phase 4: Parallel run (3-4 weeks)​

  • Configure FVI to write reconciliation results back to FIS (via file drop, API, or MQ)
  • Run both FIS and FVI in parallel for the reconciliation cycle
  • Operations team uses FVI for review and exception handling
  • Daily reconciliation between FIS and FVI outputs

Phase 5: Cutover (1 week)​

  • Switch the primary reconciliation engine to FVI
  • Maintain FIS as a fallback for 60 days
  • Update downstream consumers to read from FVI
  • Decommission FIS reconciliation after 60 days

Phase 6: Decommission (1 week)​

  • Archive FIS reconciliation configuration and data
  • Update operational runbooks
  • Document lessons learned

Pre-built FIS connectors​

FVI ships with pre-built connectors for:

  1. FIS Integrity — file drop connector (XML, CSV, fixed-width), MQ, and SOAP API
  2. FIS Profile — file drop connector (XML, CSV), JDBC for direct DB read
  3. FIS AvantGard — file drop connector, MQ, and REST API
  4. FIS Treasury and Risk Manager — file drop connector (XML), MQ
  5. FIS TradeFlow — file drop connector (FpML), REST API

Data model mapping​

FVI's data model maps to FIS's standard schemas:

FVIFISNotes
AccountAccount masterFIS account master
CounterpartyCounterparty masterFIS counterparty master
TransactionTrade / positionFIS trade / position record
Reconciliation runReconciliation batchFIS batch record
ExceptionException recordFIS exception record
Audit trailFIS audit logFVI stores immutable audit trail

Step-by-step: configuring FVI for FIS reconciliation​

  1. Install the FIS connector. In FVI, navigate to Integrations → FIS and install the FIS connector. Configure the FIS connection parameters (file drop location, MQ queue, or API endpoint) and test the connection.

  2. Map master data. Run the master data mapping wizard to map FIS accounts, counterparties, and rules to FVI's data model.

  3. Configure transaction streams. Configure the transaction stream for each FIS module. FVI ingests via file drop, MQ, or API based on the FIS product.

  4. Create reconciliation rules. Use FVI's rule template for FIS reconciliation. The template includes pre-built field mappings for cash, treasury, and trade reconciliation.

  5. Run shadow reconciliation. Trigger a shadow reconciliation run and compare the output to FIS. Iterate on the field mapping until the output matches.

  6. Configure exception routing. Set up the exception routing rules to send exceptions to the same operations teams that handle FIS exceptions.

  7. Enable writeback. Enable the FIS writeback to update FIS reconciliation status fields. FVI writes the reconciliation status back via file drop, MQ, or API.

Code samples​

TypeScript​

import { FVI } from '@falconveritas/sdk';

const fvi = new FVI({
  baseUrl: 'https://api.falconveritas.com',
  bearer: process.env.FVI_JWT!,
  tenantId: process.env.FVI_TENANT_ID!,
});

// Trigger FIS shadow reconciliation
const run = await fvi.integrations.fis.shadowReconciliation({
  source: 'INTEGRITY',
  modules: ['cash', 'treasury', 'trade'],
  fromDate: '2026-08-01',
  toDate: '2026-08-22',
});

console.log(`Shadow run ${run.id}: ${run.matched_count} matched, ${run.exception_count} exceptions`);

Python​

from falconveritas import FVI

client = FVI(
  bearer=os.environ["FVI_JWT"],
  tenant_id=os.environ["FVI_TENANT_ID"],
)

run = client.integrations.fis.shadow_reconciliation(
  source="INTEGRITY",
  modules=["cash", "treasury", "trade"],
  from_date="2026-08-01",
  to_date="2026-08-22",
)
print(f"Shadow run {run.id}: {run.matched_count} matched, {run.exception_count} exceptions")

Last updated: 2026-08-22 · Page owner: Documentation · Source: src/lib/migrations/fis/.