Map cost types to one grid
The agent reads the non-staff cost accounts of all four hospitals and assigns them to a common product group. Accounts it cannot assign are listed individually.
61 cost types mapped to 12 product groups, 4 openCompares several hospitals per bed day, systematically rather than anecdotally.
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
Each hospital books its non-staff costs to its own cost types, one under medical supplies, another under consumables. For a comparison, someone has to sort the accounts, put the bed days alongside and align both to the same period. It takes so long that it rarely gets beyond an anecdote in the management meeting.
The gap of 9.40 euros per bed day becomes negotiable once the 61 cost types have the same names in all four hospitals, and non-staff costs fall by 40%.
The 40% reduction in non-staff costs is this agent's headline figure. The number of hospitals, the cost types and the range per bed day reflect a typical group comparison; they are not measured values.
The agent reads the non-staff cost accounts of all four hospitals and assigns them to a common product group. Accounts it cannot assign are listed individually.
61 cost types mapped to 12 product groups, 4 openThe agent puts the bed days from the hospital information system alongside and calculates each product group per bed day. The period is the same for every hospital.
Comparison Q2/2026, 4 hospitals, 12 product groups per bed dayThe agent puts the product groups with the largest gap at the top and names the hospital, account number and amount. Purchasing and controlling can see where to ask questions.
sachkosten_benchmark_Q2-2026.xlsx, 5 outliers with account numbersIt shows the gap between the hospitals with account and amount. Purchasing handles the talks with the supplier.
Why hospital C uses more disposables is not in any account. The clinical department provides the explanation.
Anything billed on a collective invoice without a product group is missing from the comparison and has to be added by hand.
Connected systems
Operations
A pilot typically runs on your own data within 4 to 6 weeks. The agent connects to your existing systems rather than running as a separate, parallel environment.
EU cloud, private cloud or on-premises. Processing is GDPR-compliant and models are never trained on your data. Details in the Trust Center.
It is based on experience from comparable projects and process benchmarks, not a commitment. We work out the realistic effect for your organisation during the assessment before the pilot.