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.
API_OPLACCTGDOCITEMCUBE_SRV—A_OperationalAcctgDocItemCube, keyed on company code, fiscal year, accounting document and item: the open item, for customers (FinancialAccountType = D) and vendors (K) alikeAPI_BUSINESS_PARTNER— business partner, addresses, bank details, tax numbers, and the AR master data proper:A_Customer,A_CustomerCompany(company-code terms, reconciliation account, head office) andA_CustomerDunning(dunning procedure, level, last dunned on, block, recipient)API_SALES_ORDER_SRVandAPI_BILLING_DOCUMENT_SRV— only in the optional order scope, and only for the order and invoice numbers a delivered item actually names
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
Debtors (customer header): one per customer and company code — payment terms, dunning block, reconciliation account and accounting clerk are company-code facts, and the same customer in two company codes is commercially two things. The customer without the company code is the bracket over them. Head office, alternative payer and alternative dunning recipient travel as their own fields and are never silently resolved.
Journal entries (open items): one per accounting document item, keyed on company code, document, fiscal year and line. Document type and posting key map to the Bilendo document type; special G/L items (down payments, guarantees, noted items) are not receivables and are not delivered unless the customer names an exception.
Clearing: a cleared item is re-delivered with the clearing document, clearing date and the cleared flag; a reset clearing (
ClearingIsReversed) re-opens it. A partial payment usually produces a residual item with a new document number — the reference to its origin travels with it, so Bilendo does not end up with two unrelated receivables.Dunning history: level and last dunning date, from the customer record and from the item, taken over once at the initial load so an account on level 2 does not start again at 1.
Vendor items (optional): where customer and vendor are linked and both sides carry the clearing flag, the vendor’s open items arrive under the debtor, negative, with their own document type and a permanent dunning block — visible in the account, lowering the balance, never dunned.
Order context (optional): order number and date, the customer’s own purchase order number, sales organisation, partner functions and item texts — the facts a clarification call is actually about.
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
It never posts, pays or clears in SAP — the technical user is read-only.
It does not deliver special G/L items, statistical items or noted items; they are not receivables.
It does not load the vendor ledger. The optional scope is the clearable vendor behind a debtor, not Accounts Payable.
It does not read orders for their own sake: an order no open item names is never fetched.
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.