Skip to main content

Migrate from SAP

Many enterprises run reconciliation inside their SAP ERP using a combination of GRIR (Goods Received / Invoice Received) clearing accounts, bank statement reconciliation (BSR), and the SAP Application Interface Framework (AIF). While SAP's reconciliation tools are deeply integrated with the rest of the ERP, they present several operational challenges that FVI is purpose-built to address.

Why migrate from SAP reconciliation​

Frequent pain points reported by SAP reconciliation users include:

  1. Limited match logic — SAP's match logic is rule-based but cannot easily combine multiple matching strategies (exact + fuzzy + ML).
  2. Manual exception handling — SAP exceptions are routed through transaction codes (FBL1N, FBL5N, etc.) and require manual effort to triage.
  3. Poor audit trail — while SAP has CDPOS change documents, the user-facing audit trail is fragmented across multiple tables.
  4. Brittle integrations — bank statement ingestion relies on the EBS (Electronic Bank Statement) format or third-party MT940 parsers, both of which require ongoing maintenance.
  5. Slow change velocity — SAP change requests require IT involvement with multi-week lead times.
  6. Limited AI — SAP's AI features (in S/4HANA Cloud) are limited and cannot be customized.

FVI addresses each of these with a modern, AI-native reconciliation platform that integrates cleanly with SAP via standard APIs and pre-built connectors.

Migration approach​

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

Phase 1: Discovery (2 weeks)​

  • Document current SAP reconciliation landscape (GRIR accounts, BSR variants, custom reports)
  • Identify reconciliation volumes, exception rates, and SLA breaches
  • Map SAP master data (GL accounts, vendors, customers) to FVI's data model
  • Identify all downstream consumers of SAP 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 SAP (IDoc, BAPI, OData)
  • Run FVI reconciliation in shadow mode (parallel to SAP, no downstream impact)
  • Compare FVI output to SAP output, identify and resolve discrepancies

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

  • Configure FVI to write reconciliation results back to SAP (via IDoc, BAPI, or direct DB write)
  • Run both SAP and FVI in parallel for the reconciliation cycle
  • Operations team uses FVI for review and exception handling
  • Daily reconciliation between SAP and FVI outputs

Phase 4: Cutover (1 week)​

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

Phase 5: Decommission (1 week)​

  • Archive SAP reconciliation configuration and data
  • Update operational runbooks
  • Remove SAP reconciliation roles and authorizations
  • Document lessons learned

Pre-built SAP connectors​

FVI ships with pre-built connectors for:

  1. SAP S/4HANA Cloud — OData API for transaction read, IDoc for event streaming
  2. SAP S/4HANA on-premise — BAPI/RFC for transaction read, IDoc for event streaming
  3. SAP ECC 6.0 — BAPI/RFC for transaction read, ALE/IDoc for event streaming
  4. SAP Ariba — Open API for invoice and PO reconciliation
  5. SAP Concur — REST API for expense reconciliation
  6. SAP Fieldglass — REST API for contingent worker reconciliation

Data model mapping​

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

FVISAPNotes
AccountSKA1 / SKB1GL account master
CounterpartyLFA1 / KNA1Vendor / customer master
TransactionBSEG / BKPFAccounting document
Reconciliation runCustom tableFVI creates and tracks runs
ExceptionCustom tableFVI stores exceptions with full lineage
Audit trailCDPOS / CDHDRFVI stores immutable audit trail

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

  1. Install the SAP connector. In FVI, navigate to Integrations → SAP and install the SAP connector. Configure the SAP connection parameters (host, client, user, password) and test the connection.

  2. Map master data. Run the master data mapping wizard to map SAP GL accounts, vendors, and customers to FVI's data model. The wizard handles the field-level mapping and the cross-reference resolution.

  3. Configure transaction streams. Configure the transaction stream for each SAP module (FI, AP, AR, GRIR). FVI ingests IDocs, BAPIs, or OData feeds based on the SAP version.

  4. Create reconciliation rules. Use FVI's rule template for SAP reconciliation. The template includes pre-built field mappings for GRIR, BSR, and intercompany reconciliation.

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

  7. Enable writeback. Enable the SAP writeback to update SAP reconciliation status fields. FVI writes the reconciliation status back to the original SAP document.

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 SAP shadow reconciliation
const run = await fvi.integrations.sap.shadowReconciliation({
  source: 'S4HANA-CLOUD',
  modules: ['FI', 'AP', 'AR', 'GRIR'],
  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.sap.shadow_reconciliation(
  source="S4HANA-CLOUD",
  modules=["FI", "AP", "AR", "GRIR"],
  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/sap/.