SAP S/4HANA FI-AR

Connectors · General

What this integration does

Pulls receivables from the classic Accounts Receivable ledger of SAP S/4HANA into Bilendo, so that Bilendo runs dunning and clarification while SAP remains the system of record for invoicing, payments and clearing. The direction is always SAP → Bilendo; the single write-back is the dunning level and its date.

Where the data lives in SAP

The open item of FI-AR is a line of an accounting document, and it is served by one released API. That single entity also carries the clearing facts, the dunning facts and the references into Sales & Distribution — which is why the two optional scopes of this integration are cheap: they hang off the same row.

No customer-built CDS view is required. Unlike the utilities strecke, where future budget-billing instalments have no released API, everything this integration needs is a released standard service. There is no released FI-AR dunning API either — but the dunning facts sit on A_CustomerDunning and on the item itself, so nothing has to be built for them.

What arrives in Bilendo

How it runs

A data handler per customer project (AWS Lambda behind an EventBridge schedule) reads one to three times a day — master data first, then items, then the optional scopes — and delivers delta batches to the Bilendo loader by API or SFTP. FI-AR is better placed for deltas than FI-CA: the item carries LastChangeDate, so new items are found by posting date, changes by the change stamp and 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. A re-delivered item updates.

An on-premise system is reached through a facade in SAP BTP (API Management), because the Cloud Connector opens into BTP and not into the internet. A system in the public cloud is reached directly through a communication arrangement.

Dunning: who runs which step

Each SAP dunning procedure becomes a Bilendo dunning area with its own strategy, carried as a mapped custom field on the debtor; the SAP dunning area becomes the Bilendo dunning group. The two answer different questions — how is dunned and which items share a letter — and stay different fields. Bilendo then runs reminders, dunning letters, charges and interest. Dunning blocks, payment blocks, instalment plans and the legal dunning date stay SAP facts that Bilendo follows.

The write-back carries the level, its date and the dunning area. Whether it can be written through the standard Business Partner API (A_CustomerDunning) or needs a receiver built by the customer is the first thing tested in the QA system — it is a candidate, not a promise.

What it does not do

Onboarding

Five 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 (the receivables department), Mahnwesen & Rückkanal (receivables management), and for the optional scopes Kreditorische Debitoren and Auftragsdaten aus SD. Their answers are the specification the SAP partner builds against.