Migrate from Oracle

Oracle Fusion ERP Cloud provides reconciliation through Cash Management, Intercompany, and the broader General Ledger/Receivables/Payables modules. While Oracle's reconciliation tools are tightly integrated with the ERP, they have several operational limitations that FVI addresses.

Why migrate from Oracle reconciliation

Frequent pain points reported by Oracle reconciliation users include:

1. Cash Management limitations — Oracle Cash Management handles bank reconciliation but lacks modern AI matching and exception triage.
2. Intercompany complexity — Oracle Intercompany Hub requires extensive configuration and manual settlement tracking.
3. Limited external reconciliation — Oracle's reconciliation against external counterparties (banks, custodians, partners) is batch-based and slow.
4. Audit trail gaps — Oracle's audit trail is fragmented across multiple tables (GL_JE_LINES, AR_PAYMENT_SCHEDULES, AP_INVOICES, etc.).
5. Slow change velocity — Oracle change requests require IT involvement with multi-week lead times.
6. Limited customization — Oracle's match logic is configurable but cannot easily combine multiple matching strategies.

FVI addresses each of these with a modern, AI-native reconciliation platform that integrates with Oracle Fusion ERP Cloud via standard REST APIs and BI Publisher reports.

Migration approach

FVI's migration approach is staged over 6-12 weeks:

Phase 1: Discovery (2 weeks)

• Document current Oracle reconciliation landscape (Cash Management rules, Intercompany hubs, custom reports)
• Identify reconciliation volumes, exception rates, and SLA breaches
• Map Oracle master data (GL accounts, suppliers, customers) to FVI's data model
• Identify all downstream consumers of Oracle reconciliation output

Phase 2: Shadow run (2-4 weeks)

• Deploy FVI in the customer's environment
• Configure FVI to ingest the same transaction streams as Oracle (REST API, BI Publisher, OTBI)
• Run FVI reconciliation in shadow mode (parallel to Oracle, no downstream impact)
• Compare FVI output to Oracle output, identify and resolve discrepancies

Phase 3: Parallel run (2-4 weeks)

• Configure FVI to write reconciliation results back to Oracle (via REST API or Fusion connector)
• Run both Oracle and FVI in parallel for the reconciliation cycle
• Operations team uses FVI for review and exception handling
• Daily reconciliation between Oracle and FVI outputs

Phase 4: Cutover (1 week)

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

Phase 5: Decommission (1 week)

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

Pre-built Oracle connectors

FVI ships with pre-built connectors for:

1. Oracle Fusion ERP Cloud — REST API for transaction read, BI Publisher for reports
2. Oracle E-Business Suite (EBS) — SQL connector for direct DB read, REST adapter for events
3. Oracle NetSuite — SuiteTalk REST API (see NetSuite integration)
4. Oracle Banking — Oracle Banking Cloud REST API
5. Oracle Cash Management — REST API for bank statement and cash positioning

Data model mapping

FVI's data model maps to Oracle's standard tables:

FVI	Oracle	Notes
Account	GL_CODE_COMBINATIONS	GL account combination
Counterparty	HZ_PARTIES	Trading partner master
Transaction	GL_JE_LINES / AR_PAYMENT_SCHEDULES / AP_INVOICES	Accounting / receivables / payables
Bank statement	CE_STATEMENT_LINES	Bank statement line
Reconciliation run	Custom table	FVI creates and tracks runs
Exception	Custom table	FVI stores exceptions with full lineage
Audit trail	GL_JE_LINES.AUDIT_*	FVI stores immutable audit trail

Step-by-step: configuring FVI for Oracle reconciliation

1. Install the Oracle connector. In FVI, navigate to Integrations → Oracle and install the Oracle connector. Configure the Oracle connection parameters (REST endpoint, OAuth client credentials) and test the connection.

2. Map master data. Run the master data mapping wizard to map Oracle GL combinations, parties, and bank accounts to FVI's data model.

3. Configure transaction streams. Configure the transaction stream for each Oracle module (GL, AP, AR, Cash Management). FVI ingests via REST APIs or BI Publisher reports.

4. Create reconciliation rules. Use FVI's rule template for Oracle reconciliation. The template includes pre-built field mappings for Cash Management, Intercompany, and AP/AR reconciliation.

5. Run shadow reconciliation. Trigger a shadow reconciliation run and compare the output to Oracle. 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 Oracle exceptions.

7. Enable writeback. Enable the Oracle writeback to update Oracle reconciliation status fields. FVI writes the reconciliation status back via REST 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 Oracle shadow reconciliation
const run = await fvi.integrations.oracle.shadowReconciliation({
  source: 'FUSION-CLOUD',
  modules: ['GL', 'AP', 'AR', 'CM'],
  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.oracle.shadow_reconciliation(
  source="FUSION-CLOUD",
  modules=["GL", "AP", "AR", "CM"],
  from_date="2026-08-01",
  to_date="2026-08-22",
)
print(f"Shadow run {run.id}: {run.matched_count} matched, {run.exception_count} exceptions")

Related articles

• Migrate from SAP
• Migrate from FIS
• Migrate from BlackLine
• Oracle integration

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