How it fits together
S/4HANA stays exactly as it is. Budget Pulse reads from it, checks each purchase order against the rules your controller sets, and sends alerts to Teams and Outlook.
No custom code in S/4HANA
No modifications, no transports and nothing to retest at upgrade time. Clean core by design.
Read-only and warn-only
It shows and explains numbers. It can't post, change, approve or block anything in SAP.
Runs on SAP BTP
A side-by-side app with SAP BTP sign-in and roles. Built for S/4HANA Cloud and on-premise.
Easy to remove
Nothing is installed inside S/4HANA, so switching it off leaves your system exactly as it was.
What Budget Pulse reads, and why
Only what the budget check needs, through SAP's released, read-only APIs.
| Data | From S/4HANA | Why |
|---|---|---|
| Purchase orders | Purchase Order API | To check each new or changed PO against its budget |
| Budget plan | Financial Planning Entry Item (read) | To know each cost center's budget, unless you upload it from Excel |
| Actual costs | Journal entry items (read) | To know what each cost center has already spent |
| Cost centers and G/L accounts | Master data APIs (read) | To show names and owners in alerts and screens |
| Suppliers | Business Partner API (read) | To show the supplier name on an alert |
New purchase orders are picked up by checking for changes every few minutes. No SAP Event Mesh needed. If you already use SAP business events, Budget Pulse can listen to those instead.
Security and data handling
- Alerts in your Microsoft 365
- Teams cards go through a Workflows connection your team creates. Emails are sent from a mailbox you choose, after your Microsoft admin approves access once. An alert contains the PO number, supplier, amount, cost center and budget used.
- AI is optional and limited
- AI notes are off until you turn them on. When on, only totals and cost center names are sent, supplier names are masked, and people's names and emails are never sent. Every call is logged against hard daily and monthly limits.
- What Budget Pulse stores
- Your budget rules, uploaded budgets, the result of each PO check and the audit log of who was alerted and when. It does not keep a copy of your SAP ledger.
- Logs you can support
- Every check and alert has a reference id. Passwords, keys and email addresses are masked in logs, and a health check shows the status of every connection.
How a rollout works
Connect your test system
We connect Budget Pulse to your development or test system with a read-only technical user.
Load budgets and rules
Your controller sets warning levels and loads budgets from S/4HANA or Excel. We connect Teams and Outlook.
Move to production
The same package moves to production when you are ready. Nothing is transported into S/4HANA.
Questions IT teams ask
Do we need SAP Event Mesh or Integration Suite?
No. Budget Pulse checks for new purchase orders every few minutes on its own. If you already run SAP business events, it can use them for instant checks.
What access does the SAP technical user need?
Read access to the APIs listed above, and nothing else. It cannot create or change documents.
Which Microsoft permissions are needed?
Permission to send email from one mailbox you choose, plus a Teams Workflows connection for the channel that receives alerts. Your admin approves both.
Does it affect SAP performance?
It reads small amounts of data through standard APIs on a schedule. Each check reads one purchase order and the totals for one cost center.