Architecture & Data Flow

Four zones, one control layer: SAP system, BTP (or Communication Arrangement), AWS data handler, Bilendo.

The four zones

ZoneWhat resides thereTask
SAP S/4HANAFI-AR, business partners with a customer view, optionally vendors and SD documentsSource. Only read from.
SAP BTP (On-Premise) or Communication Arrangement (Public Cloud)API management proxy per OData service, destination + Cloud ConnectorThe one door into the customer system. The Cloud Connector's tunnel ends in BTP; the facade makes it callable from outside (OAuth 2.0 Client Credentials). This is not needed in the Public Cloud.
AWS · Data handler per customer projectEventBridge schedule, Step Functions, Lambda (Collector, Transform, Deliver, Report), S3 raw data, DynamoDB watermarks, Secrets ManagerReads page by page, transforms according to the mapping from the IMS, delivers delta batches, reports every run.
BilendoLoader (API POST or SFTP), customers, journal entries, dunning runs per dunning areaTarget. Updates known items, dunns and clarifies.

The control layer

The Bilendo IMS describes the data handler (target state, schedule, company codes, objects, secret names) and sees its runs; it does not operate it and holds no access credentials, only the name under which the access credentials are stored in the customer's secret store. Roles, states, and the meaning of each column of the run table are documented once in Data Handler: Control & Runs — written there using the Utilities example, but equally valid here unchanged.

A run

  1. Read the target state and watermark, assign a run ID.

  2. Per object in a fixed order — Customers → Dunning data → Items → (Vendors) → (Orders and invoices) — read page by page with a delta filter; raw data goes unchanged to S3.

  3. Transform according to the variant's mapping into the columns of the Bilendo header template; apply clearing and open-item rules; batches of up to 5,000 rows each.

  4. Deliver customer batches, then journal batches; each part carries an idempotency key.

  5. Report the manifest to the IMS; advance the watermark only upon confirmed delivery.

The order is mandatory, not a matter of preference: an item needs its customer, and order data is read against numbers that only the items reference.

A failed run leaves the watermarks in place. The next run delivers the same window again — Bilendo updates, and no duplicate is created.

Frequency

One to three times daily. The last run of the day takes place before the Bilendo dunning run, so that a payment booked in SAP in the morning is not dunned in the afternoon.