SAP-native collection automation — no ABAP, no risk
SAP Gateway OData connection
AgentCollect connects to SAP S/4HANA via SAP Gateway using standard OData APIs. For SAP Business One, we use the Service Layer REST API. Your Basis team configures the communication user in SM59 — no transports, no custom code, no system modifications.
FI-AR entity and dunning mapping
Map AgentCollect to your open AR items via the BSID table (customer open items). Configure collection triggers by dunning area, credit control area, or company code. Set minimum balance thresholds and exclude strategic accounts.
AI agents collect under your brand
AI agents contact customers by phone, email, and SMS. AgentCollect syncs with your accounting system several times a day and stops contacting a customer about any invoice your books show as paid, so customers who already paid are not chased.
What syncs between SAP and AgentCollect
| Direction | Data | Frequency | SAP Object |
|---|---|---|---|
| SAP → AC | Open AR items | Every 2 hours | BSID / CustomerOpenItems OData |
| SAP → AC | Customer master data | On sync | Customer OData / BusinessPartner |
| SAP → AC | Company code / credit control area | On sync | CompanyCode / CreditControlArea |
Tech stack: SAP Gateway ODataService Layer RESTOAuth 2.0No ABAP requiredMulti-company code
Built for SAP finance teams
Zero ABAP, zero modifications
AgentCollect uses only standard SAP OData APIs published via SAP Gateway. No custom ABAP development, no transport requests, no risk to your SAP system stability or support agreement.
Dunning level sync
AgentCollect writes the dunning level back to the CustomerDunning entity in SAP. This prevents conflicting dunning notices from SAP's standard dunning run and AgentCollect's AI agents operating simultaneously.
SAP integration FAQ
Ready to automate your SAP collections?
No ABAP. No SAP modifications. AgentCollect pricing.
Start a free pilot →