SAP BTP Utilities
Connectors · General
What this integration does
Pulls receivables data from SAP S/4HANA Utilities into Bilendo through SAP BTP, so that Bilendo runs dunning and clarification for a utilities company while SAP remains the system of record for billing and payments. The direction is always SAP → Bilendo; the single write-back is the dunning level and the last dunning date.
Where the data lives in SAP
Utilities receivables are not customer line items of FI-AR. They are business-partner items of the Contract Accounting sub-ledger (FI-CA), and the debtor is the pair business partner + contract account. The integration therefore reads six released OData APIs:
API_BUSINESS_PARTNER— business partner, addresses, bank details, tax numbersCONTRACTACCOUNT_0001— contract account, payment method, SEPA mandate, dunning procedure, locksCADOCUMENTMANAGE_0001— the FI-CA document and its business-partner items: the open itemAPI_CABUSPARTINVOICE_0002— invoice view with the current open amount per itemAPI_CABUSPARTPAYMENT_0002— payments and the invoice items they clearedCADUNNING_0001— dunning history, read once at the initial load to hand the dunning level over
Future budget-billing instalments have no released API; they come from a customer CDS view exposed as OData (see the architecture "SAP S/4HANA Utilities (FI-CA)").
What arrives in Bilendo
Debtors (customer header): one per contract account, the business partner as parent. Name, address, contact, tax id, payment term, dunning lock, and as custom fields the SAP payment method, SEPA mandate and dunning procedure.
Journal entries (open items): one per FI-CA business-partner item, keyed on contract, document number, company code and line. Due date honours deferrals; amount and open amount travel separately; document type and main/sub transaction map to the Bilendo document type.
Clearing: a hard clearing arrives as the same item re-delivered with the clearing document, clearing date and the fully-cleared flag; a soft clearing (payment on account, partial payment) arrives as a payment item sharing the assignment number of the receivable.
Budget-billing instalments: future rates as items of their own document type, withdrawn when the rate is posted in FI-CA and arrives as a real item.
How it runs
A data handler per customer project (AWS Lambda behind an EventBridge schedule) reads through the BTP destination one to three times a day, master data first, then movement data, and delivers delta batches to the Bilendo loader via API or SFTP. New items are found by posting date, clearings by clearing date; a watermark per object advances only after Bilendo has accepted the batch, with an overlap so a missed run heals itself. Bilendo updates a re-delivered item, so a delivered row is always the current state of that item.
Dunning procedures — who runs which step
A utilities company does not run one dunning process in FI-CA but several dunning procedures (or BRF+ collection strategies), one per customer segment: households in basic supply under § 19 StromGVV/GasGVV, special-contract households, district heating (§ 33 AVBFernwärmeV), water, business customers, grid partners. Each procedure has levels, and a level carries activities: letter, dunning charge, default interest, disconnection threat, disconnection order to the grid operator, hand-over to collections.
The integration maps each SAP dunning procedure to a Bilendo dunning area (Mahnbereich), carried as a mapped custom field "Mahnverfahren" on the debtor — the way other SAP customers already import their dunning procedure — so every segment gets its own Bilendo dunning strategy. The SAP dunning notice group (which items share one letter) becomes the Bilendo dunning group (Mahngruppe); the two are different questions and stay different fields. Bilendo then runs the communicative levels — reminders, dunning letters, charges and interest, collections hand-over where the segment allows it. The regulated disconnection chain stays in IS-U: threshold check (two monthly instalments, at least €100), four-week threat period, the mandatory offer of an interest-free instalment agreement, eight-working-day announcement, disconnection order via market communication and reconnection. The dunning level Bilendo reports back is what triggers that chain in SAP, which is why the write-back carries the level, its date and the dunning area. Dunning locks, deferrals and instalment plans remain SAP facts that Bilendo follows; the FI-CA dunning history is taken over once at the initial load.
What it does not do
It never writes postings, payments or clearings into SAP — the technical user is read-only.
It does not send dunning letters from SAP: at the cut-over date the FI-CA dunning procedures of the covered contract accounts lose their letter, charge and interest activities, while the disconnection levels stay and are reached through the level Bilendo reports back (export or webhook).
It does not deliver statistical items or down-payment requests; they are not receivables.
Onboarding
Four question catalogues are attached to this integration and instantiated on the customer's account when the integration is created: System & Zugang (SAP basis), Fachliche Festlegungen (receivables department), Mahnverfahren & Sperrprozess (receivables management and legal) and Rückkanal Mahnstufe (the write-back receiver). Their answers are the specification the SAP partner builds against.