
AI collections for SAP S/4HANA
Every overdue account, worked.Every outcome, in SAP.
CashPulse reads open items live from S/4HANA, works each overdue account from a friendly reminder to a formal warning to a final-notice AI voice call, and writes the promise, dispute or payment back to SAP. The long tail of your receivables book gets the same attention as the top ten.
Built on
- SAP BTP
- SAP CAP
- SAP Fiori
- S/4HANA OData
- XSUAA
Live · 00:00· Northwind Traders
AI disclosure delivered at 00:03 · call is recorded
Transcript
Agent actions this call
- AI disclosure spoken00:03 · done
- Dispute flagged on invoice01:48 · done
- Callback scheduled: Thu 10:0002:24 · done
- Payment link queued by email02:38 · pending
The collections ladder
- 01Friendly reminder
- 02Formal warning
- 03Final notice by AI call
- 04Outcome captured
- 05Written to S/4HANA
The capacity ceiling
The long tail is where cash leaks
Collectors rationally work the largest balances first. The mid-size overdue accounts get contacted late, inconsistently or never, and the attempts that are made rarely reach the ERP.
Coverage runs out
A team has a fixed number of hours. Past a certain portfolio size, some accounts simply do not get a call this month.
Dunning stops at email
Most automation sends a reminder and stops. It never has the conversation that actually uncovers the dispute or the promise.
No evidence in SAP
Calls and outcomes live in notebooks and inboxes. When DSO drifts, nobody can show where the follow-up broke down.
What CashPulse does
One ladder, run for every account
From the open item in S/4HANA to the posting that clears it, each step is recorded with its reason.
- 01
Reads live from S/4HANA
Open items, payers and contact data through SAP connectivity services. No credentials in the app, no data warehouse in between.
- 02
Stages and prioritises every account
Days past due sets the collection stage, from Stage 0 to Stage 3, and a priority from 1 (most urgent) to 4. Accounts on dispute hold are left out of outreach.
- 03
Reminds, then warns, by email
Stage 1 is a friendly reminder and Stage 2 a formal warning, each with a secure self-service payment link. You review drafts, or an administrator schedules sending.
- 04
Delivers the final notice by AI voice call
At Stage 3 the agent calls. It knows the invoices, the balance, prior outreach and its earlier conversations with this payer.
- 05
Captures the outcome
Promise to pay, dispute, callback or refusal is taken from the conversation and shown in the post-call analysis. Partial payments keep the invoice open for the exact remaining balance.
- 06
Writes everything back to SAP
Outreach history, transcripts, follow-ups and the decision log go back to S/4HANA. Received payments are reconciled and the FI posting clears the item.
Built for the long tail
The 1–30 day band is where timely contact changes the outcome
A handful of very old, very large items get human attention anywhere. The youngest overdue band, largest by value and by count, is exactly the one a stretched team deprioritises.
Figures from the synthetic reference dataset shipped with the product.
Responsible AI
A voice agent with hard limits
These are product decisions, and each one can be checked in the demo.
It says it is an AI, first
The AI disclosure and recording notice come before anything else on the call. It is on by default; turning it off takes an explicit administrator setting and is logged on every call.
Its authority is its tool set
It can schedule a callback, send a payment link, transfer to a person and end the call. It cannot grant a discount, waive interest or agree a write-off.
Disputes go to people
A dispute suspends automation on the account and routes it to a collector.
Every decision has a reason
Each autonomous decision is logged with its reason, in S/4HANA as well as locally.
Guardrails on both paths
Prompt-injection guardrails apply to the live call and to the post-call analysis.
Collectors can take over
The transcript streams live to the collector, who can listen in or take the call at any moment.
Capabilities
What ships today
- Live S/4HANA integration, reading and writing back
- Collection stages 0 to 3 with priority 1 to 4
- AI-drafted reminder and warning emails, reviewed or scheduled
- Real-time conversational AI voice calls for final notices
- Live call transcript streamed to the collector, with take-over
- Post-call analysis: outcome, sentiment, promise-to-pay extraction
- Partial payments tracked to the exact remaining balance
- Payment reconciliation and FI posting that clears the open item
- Late-payment interest terms, with accrual on the outstanding balance
- Secure self-service payment portal, full or partial payment
- Decision engine with a written reason for every decision
- In-app Help Centre: walkthroughs, FAQs and troubleshooting
Who it is for
Built for high-volume receivables books
A strong fit
- Mid-market and enterprise organisations on SAP S/4HANA
- Receivables books with a long tail of mid-size overdue accounts
- AR, credit and collections teams and shared service centres
- DSO drifting upward, or an audit finding on contact evidence
Not a fit
- A handful of very large customers, each with a dedicated collector. There is no capacity problem to solve
How it works
Inside the collections ladder
How CashPulse decides what to do next, how the voice agent is bounded, and how it fits your SAP landscape.
- 01Friendly reminder
- 02Formal warning
- 03Final notice by AI call
- 04Outcome captured
- 05Written to S/4HANA
Stages and escalation
Stage 1
Friendly reminder
A courteous email with the open items and a secure payment link.
Stage 2
Formal warning
A firmer email that references the earlier reminder and any agreed late-payment terms.
Stage 3
Final notice by AI call
A real conversation with the payer's AP contact, with the account's history in context.
Outcome
Promise, dispute or callback
Captured from the call and shown in the post-call analysis. A dispute puts the account on hold.
Follow-up
Follow-up and clearing
Follow-ups are scheduled, payments are reconciled, and the FI posting clears the item in S/4HANA.
Stages follow days past due, and the thresholds are configurable. Outreach you trigger is never sent until you send it; scheduled outreach runs only where an administrator enables it. Accounts on dispute hold are excluded.
Your landscape
How it fits your landscape
CashPulse runs on SAP BTP, reads and writes S/4HANA through SAP connectivity services, and reaches payers by email, voice and a secure payment portal.
SAP S/4HANA
Open items, payers, FI postings
CashPulse on SAP BTP
Stages, decisions, AI drafting, call analysis
Your customer
Outcomes, payments and the decision log go back to S/4HANA
What it is built on
Runtime
SAP BTP, Cloud Foundry environment
Application
SAP Cloud Application Programming Model
User interface
SAP Fiori, launchpad-ready
Access
Role-based access through your SAP BTP identity setup
ERP connectivity
SAP Destination and Connectivity services with SAP Cloud Connector
AI
Real-time voice and language models, with prompt-injection guardrails
Deployment and operations
- Deploys inside your SAP BTP landscape as a dedicated instance, not a shared tenant
- Connects to S/4HANA through SAP Cloud Connector, with no credentials in the application
- SAP-side objects delivered as a transport for your S/4HANA system
- Health and readiness endpoints for your own monitoring
- Versioned releases with published release notes
ROI calculator
Model what CashPulse could change in your receivables book
The model behind this calculator comes from the CashPulse solution brief. Starting values are placeholders, not customer results. Replace each one with your own portfolio figures.
Amounts are in US dollars. Switching currency converts every amount at the reference rate. Reference rate of 16 nov. 2026 from ExchangeRate-API.
Your overdue portfolio
Your collections team today
Your estimate with CashPulse
Working capital (optional)
Investment
FAQ
Questions buyers ask us
What is CashPulse?
AI-driven accounts receivable collections on SAP BTP. It reads open items live from S/4HANA, runs a staged email ladder with secure payment links, escalates to a real-time AI voice call, captures the outcome and writes everything back to S/4HANA, including the FI posting that clears the item.
How does it connect to S/4HANA?
Through the SAP Destination and Connectivity services and SAP Cloud Connector. The SAP-side objects are delivered as a transport for your S/4HANA system. There are no SAP credentials inside the application.
Does the AI tell the payer it is an AI?
Yes. The agent says it is an AI and that the call is recorded before anything else. This is on by default. Turning it off takes an explicit administrator setting and is logged on every call, so it can be audited.
What can the voice agent agree to?
Only what its tools allow: schedule a callback, send a payment link, transfer to a human collector and end the call. It cannot grant a discount, waive interest, agree a plan outside policy or commit a write-off.
What happens when a payer disputes an invoice?
The dispute is captured from the conversation, the account goes on dispute hold, and automated outreach stops for it until a collector resolves it.
Will CashPulse contact customers without us?
Only if you set it up that way. Outreach you trigger is never sent until you send it. Scheduled outreach runs only where an administrator has enabled it, and accounts on dispute hold are always excluded.
What happens when a customer pays only part of an invoice?
The invoice stays open for the exact remaining balance and appears under partial payments. The account is not treated as settled until every invoice is cleared.
Can a collector step in during a call?
Yes. The transcript streams live to the collector, who can listen in or take over at any moment.
Which AI and telephony providers are used?
A real-time speech-to-speech model for the call and a language model for post-call analysis and email drafting, behind prompt-injection guardrails. Calls run over standard telephony. SAP AI Core and Generative AI Hub support is on the roadmap.
Where does CashPulse run?
It deploys inside your SAP BTP landscape as a dedicated instance on the Cloud Foundry runtime, not as a shared multi-tenant service.
Is CashPulse SAP-certified?
Not yet, and we say so before a proof of concept, not after. The integration uses custom ABAP OData services rather than SAP released APIs, which is the blocker for SAP Certified Integration; moving the read path to released CDS-based services is on the roadmap.
How is CashPulse priced?
Pricing is on request and scoped to your portfolio. Talk to us about a proof of concept on your own receivables.
Have a question that is not here?
Ask the CashPulse team

