Nakisa Cloud Connector Delivers Native Integration Across SAP ECC and S/4HANA

Nakisa positions its Cloud Connector as the entry point that lets outside finance systems and records, including SAP S/4HANA, reach the Nakisa Cloud Platform. It runs on secure, open REST APIs vetted by ERP technology providers and appears in both the SAP and Oracle partner marketplaces. Nakisa says it built its Lease Accounting solution in collaboration with SAP from the first development iteration, and the resulting connector supports up to 45 concurrent, bidirectional ERP integrations.

Inside the Cloud Connector: Bridging SAP ECC and S/4HANA

The Nakisa Cloud Connector provides native, bidirectional integration with both SAP ECC and SAP S/4HANA, using SAP’s Java Connector over TCP/IP. Master data transfers happen in real time between the ERP environment and Nakisa Lease Accounting, and journal entries post directly to GL accounts. The platform can also sync with reconciliation tools such as BlackLine.

Nakisa Lease Administration and Nakisa Real Estate integrate through the same connector, letting customers manage lease and real estate processes inside their ERP environment regardless of which SAP generation they run. Nakisa leverages BAPIs to enable two-way data exchange between SAP ERPs and its own solutions.

Nakisa recommends secure, open REST APIs validated by SAP as a baseline standard for third-party integrations, communicating over a two-way encrypted channel that uses TLS over TCP. ABAP, the programming language native to the SAP environment, underlies the RFCs, BAPIs, and ZBAPIs that make up the core of bidirectional integration work in these deployments.

Many finance organizations today run a mixed SAP landscape, with some entities still on ECC and others already migrated to S/4HANA, as multiyear migration timelines play out. SAP’s continuing push toward validated APIs in S/4HANA environments has also raised the bar for how outside software connects into finance systems, favoring documented, provider-validated methods over custom code changes.

Multi-ERP Integration at Scale: The Nestlé Deployment

Nestlé began working with Nakisa in 2016 to become an early adopter of the IFRS 16 lease accounting standard. The company went live on the Nakisa cloud in 2020, in a migration that included 40,000 lease contracts, 70,000 monthly journal entry postings, and 360 company codes spanning multiple ERP systems.

A single Nakisa instance integrated with multiple SAP ERP instances at Nestlé, operating at both the main ledger and sub-ledger level. The main ledger and sub-ledger integration provided direct postings of journal entries to SAP and master data synchronization. Danilo Cacciagrano, IT Financial Operations Senior Product Manager at Nestlé, described the effect this way: “Because it doesn’t only integrate on the main ledger level, but it also integrates on the sub-ledger level as well, which provides a granular view in the existing system. As we have a standardized global system which is used across the company worldwide by most of the businesses, a strong integration is fundamental.”

Nakisa used a lift-and-shift strategy to migrate Nestlé’s existing data to the cloud. The rollout included an automated quality assurance process with more than 60 test cases built from real business scenarios, plus volume and stress testing. A Nestlé team member identified only as Dana summarized the result: “The upgrade was done by the Nakisa team without any major issues. It was smoother than we could have anticipated considering the volume of historical data.” IFRS 16 compliance work of this kind has historically required subledger-level integration with ERP general ledgers to keep lease accounting entries auditable at scale, a pattern the Nestlé deployment reflects.

What This Means for SAPinsiders

• One connector spans two SAP generations. Finance teams running mixed ECC and S/4HANA landscapes can maintain a single integration approach rather than rebuilding connections mid-migration. The shared connector reduces the operational overhead of running parallel integration projects during a transition window.
• Marketplace validation gives buyers a reference point. Teams evaluating lease accounting or real estate software can weigh ERP-validated REST APIs and BAPI-level integration against custom-built alternatives using documented marketplace listings. Provider validation shifts due diligence away from unverified vendor claims toward confirmed integration standards.
• Enterprise-scale integration has a documented benchmark. Nestlé’s deployment across 360 company codes and multiple SAP instances gives governance teams a reference case for sizing integration architecture under real organizational complexity. Teams planning similar consolidations can calibrate testing and quality assurance expectations against that documented scale.