SAP S/4HANA Utilities (FI-CA)

Pull integration from SAP S/4HANA Utilities via SAP BTP: open items, payments, dunning procedures, and budget billing plans from contract accounts receivable and payable (FI-CA) to Bilendo.

Audience: The customer's SAP Basis and FI-CA consultants (or those of its implementation partner), receivables management, Bilendo project management. As of: September 2026, S/4HANA ≥ 2302.

This guide describes how Bilendo takes over the receivables of an energy or water utility from SAP S/4HANA Utilities and runs dunning, while SAP remains the leading system for billing and payments. The direction is always SAP → Bilendo; the only return channel carries the dunning level, dunning date, and dunning area.

The key points in five sentences

1. A utility's open items are not in FI-AR but in the subledger FI-CA (Contract Accounts Receivable and Payable); the debtor is the pairing of business partner + contract account.

2. Bilendo reads six released OData services (business partner, contract account, FI-CA document, invoice view, payments, dunning history) plus one customer-specific CDS view for installment amounts.

3. The collector runs in AWS and reaches the SAP system only through a facade in SAP BTP (API Management), because the Cloud Connector opens into BTP, not to the internet.

4. Data is delivered in delta batches; an item that is delivered again is updated in Bilendo, and a clearing travels as a change row with the clearing document.

5. Each SAP dunning procedure becomes a Bilendo dunning area with its own strategy; the regulated disconnection process (§ 19 StromGVV/GasGVV) remains in IS-U and is triggered by the dunning level reported back.

Pages in this guide

• Architecture & Data Flow — the four zones and the control layer

• Prerequisites & Access — release, services, technical user, BTP facade

• OData Services & Data Model — the six services, their entities and keys

• Mapping: Debtor, Items, Clearing — which SAP field becomes which Bilendo column

• Dunning Procedure & Disconnection Process — division of labor between Bilendo and IS-U

• CDS View for Budget Billing Plan — copy template for installment amounts

• Dunning Level Return Channel — what goes back to SAP and where

• Checklist & Question Catalogs — what we need from the customer, and where they answer it