---
title: "SAP S/4HANA — intercompany reconciliation"
description: "OData GL extract from S/4HANA into Ninon: company-code mapping, OAuth or bearer, and the connector runbook."
locale: en
canonical: https://www.ninonai.com/en/integrations/sap-s4hana
last_updated: "2026-09-01"
---

# SAP S/4HANA intercompany reconciliation

S/4HANA company codes often sit next to non-SAP entities. Ninon reads a published OData GL service and reconciles those lines against the rest of the group in one session.

## The intercompany problem on S/4

SAP intercompany and group reporting stay in the SAP landscape. Entities outside S/4 still produce breaks that finance clears in files.

## What Ninon ingests

Published OData root plus a pasted bearer or OAuth client credentials. erpLinks.sap_s4hana is the company code. Optional entity-set and date-field overrides are documented for operators.

## Limits

We consume the GL API you publish; we do not implement SAP Intercompany Governance or post documents back. Custom OData shapes may need the runbook. Connector use is gated when billing is enabled.

## FAQ

**Q.** Is this SAP Intercompany Governance by BlackLine?
**R.** No. That is a different product. Ninon is an independent GL reconciliation workspace.

**Q.** Where is the operator runbook?
**R.** /guides/erp-connectors-runbook.

**Q.** Can we start from a SAP extract file?
**R.** Yes — governed CSV/Excel is the Pilot default when the OData path is not ready.

## Sitemap

See the full [sitemap](/en/sitemap.md) for all pages.