SAP S/4HANA FI-AR

Pull integration from classic SAP S/4HANA Accounts Receivable Accounting: open items, clearings, and dunning data to Bilendo — optionally including payables-side receivables and order data from SD.

Target audience: SAP Basis and FI consultants of the customer or its implementation partner, accounts receivable accounting and receivables management, Bilendo project management. Status: September 2026, S/4HANA ≥ 2302.

This guide describes how Bilendo pulls receivables from the FI-AR module of an SAP S/4HANA system and manages the dunning process, while SAP remains the leading system for invoicing, payments, and clearing. The direction is always SAP → Bilendo; the only back channel carries the dunning level, dunning date, and dunning area.

The essentials in five sentences

1. The FI-AR open item is a line of an accounting document and comes from one released API — API_OPLACCTGDOCITEMCUBE_SRV; the key is company code · document number · fiscal year · posting line.

2. The debtor is the pair customer + company code: payment terms, dunning block, reconciliation account, and clerk are tied to the company code.

3. No customer-specific CDS view is required — the dunning data is also available in the standard, at the customer (A_CustomerDunning) and on the item itself.

4. A partial payment usually creates a residual item with a new document number; its invoice reference is the chain back to the origin, and without it, Bilendo ends up with two disconnected receivables.

5. Two scopes are optional and attach to the same item line: payables-side receivables (FI-AP) and order data from SD.

Pages of this guide

• Architecture & data flow — the four zones and the control layer

• Prerequisites & access — release, services, technical user, the path from outside

• OData services & data model — the services, their entities, and delta capability

• Mapping: debtor, item, clearing — which SAP field becomes which Bilendo column

• Payables-side receivables (FI-AP) — optional scope: offsettable payables

• Order data from SD — optional scope: the order behind the receivable

• Dunning & back channel — dunning procedures, handover of dunning authority, path back to SAP

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

The data handler — the pull server in the customer project, its states, and the run table — is described once and applies to every source system: Data handler: control & runs.