[ SAP S/4HANA / Accounts receivable ]

SAP S/4HANA collections, followed up daily

engini reads your customers’ open items from SAP S/4HANA every morning, and an AI agent sends each customer the reminder that fits the stage, reads the replies, and records promises to pay and disputes where your team works. Sales sees the overdue balance in Salesforce or HubSpot before calling.

SAP S/4HANAOutlook or GmailSlackSalesforceHubSpot
Read the SAP S/4HANA guide →
A morning collections run
  1. Every weekday at 7:00schedule trigger
  2. SAP S/4HANA logo
    Read open customer itemsOData: open items and business partners
  3. Agent writes remindersstage, amount, items, last contact
  4. Reply read"line 2 is disputed, wrong quantity"
  5. Slack logo
    Dispute to the owner#collections with the item and the reason
Illustration of the flow on this page, not a product screen.
What it does
Daily reminders from SAP open items, replies read, disputes routed
Systems
SAP S/4HANA (OData), Outlook or Gmail, Slack or Teams, Salesforce or HubSpot
Built with
A scheduled workflow with an AI agent step
Your control
Read-only SAP access is enough; wording and stages are yours
[ 01 / The problem ]

Dunning letters go out. The follow-up does not.

SAP S/4HANA can run dunning and has receivables management built in. The everyday work around it is still manual: reading the customer’s reply to a dunning letter, recording that they promised to pay on the 15th, routing a disputed line to the person who can fix it, and telling the account manager before they call. SAP Press describes how much of receivables still depends on items that do not clear on their own.

Meanwhile sales works from the CRM and has no idea which customers are 60 days late.

What collectors spend their day on

  • Pulling open items and deciding who to contact.
  • Writing reminders that mention the right documents and amounts.
  • Reading replies and keeping notes in a spreadsheet.
  • Passing disputes to sales, logistics or billing by email.

What the agent does, and what it does not

engini reads customer open items and the business partner behind them through SAP’s OData services. An AI agent ranks accounts, writes each reminder with the right documents and tone, reads the replies, and records the outcome in your tracking sheet or monday.com board and in Slack or Teams. If you use Salesforce or HubSpot, it writes the overdue balance to the account.

This flow reads SAP; it does not clear items or post payments in SAP. That keeps the SAP access read only, which is the simplest thing to approve. Payments are posted in SAP the way you post them today.

[ 02 / How it works ]

Read SAP, reach the customer, route the answer

01 / Read

Open items every morning

A scheduled workflow reads overdue customer items and their business partners from SAP S/4HANA, each service on its own connection.

02 / Remind

One email per customer

An AI agent step writes each reminder with the document numbers, amounts and tone for the stage, and sends it from Outlook or Gmail.

03 / Listen

Replies become actions

The agent reads replies, records promises to pay and disputes in your tracking sheet or monday.com board, and alerts the owner in Slack or Teams.

04 / Share

Sales sees it too

The overdue balance and last note can be written to the Salesforce account or HubSpot company.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
SAP S/4HANACustomer open items; business partnersRead
Outlook or GmailReminder emails and repliesSendRead
Google Sheets, Excel or monday.comCollections log: promises, disputes, next stepWrite
Slack or TeamsDisputes to the ownerWrite
Salesforce or HubSpotOverdue balance on the account (optional)Update
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the SAP logo, the engini mark and a frosted tile joined by a thin line, labeled open items: overdue, reminder, dispute routed

Editorial image: a daily collections route.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: every weekday at 7:00, read overdue customer open items from SAP S/4HANA, group them by customer, send each customer one reminder from Outlook listing the documents and amounts, and add a row per customer to the "Collections log" Google Sheet. Post a summary to #collections in Slack.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect SAP S/4HANA, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can an AI agent read open receivables from SAP S/4HANA?

Yes. engini reads customer open items and business partners through SAP’s OData services, on a connection and SAP user your administrator sets up. Read access is enough for this flow.

Can it send and track reminders outside SAP’s dunning run?

Yes. The agent sends reminders from Outlook or Gmail and records each outcome in a sheet, a monday.com board and Slack or Teams. Many teams keep the formal dunning run in SAP and use the agent for the follow-up.

Does it clear items or post payments in SAP?

No. This flow only reads SAP. Payments are posted in SAP the way you post them today.

How often does it refresh without SAP triggers?

engini has no SAP triggers, so it reads open items on a schedule you choose, typically once each morning, or more often during month end.

Can sales see overdue balances in Salesforce or HubSpot?

Yes. The same workflow writes the overdue balance and the last collections note to the Salesforce account or HubSpot company.

Which OData services do we need?

The customer open item service and the business partner service, each on its own engini connection. Your SAP administrator activates them and sets up the user or OAuth client.