SAP master data,
managed across every system

Lleverage is an AI agent for master data management in SAP S/4HANA and ECC. It keeps business partners, materials and prices in SAP in step with your CRM, webshop and PIM, checks every change against your rules before it spreads, and sends bank details, credit limits and merges to the person who owns that field.

How does SAP master data management work with an AI agent?

In SAP S/4HANA a customer or a supplier is one business partner, with its customer and supplier data kept in step by customer/vendor integration, and an article is a material with basic data and plant data. The agent keeps those records true across every system that holds a copy, in 4 steps.

Read every copy of the record

The business partner’s general data (BUT000), its sales data per customer (KNVV) and its supplier data (LFA1), the material’s basic and plant data (MARA, MARC), and the same customer, supplier or article in your CRM, webshop and PIM.

Find where the copies disagree

A sweep every morning compares field by field: a VAT number with two digits swapped, an address changed in one system only, a material without a net weight, two business partners for one company. Your survivorship rules decide which value wins.

Check the change before it spreads

A VAT number is checked against the register, a mandatory field is filled, a new business partner is matched against the ones SAP already holds. Bank details, credit limits and merges never change on their own: they go to the person who owns that field.

Write it back to SAP and log it

The winning value is written to the business partner or material in SAP and to every other system that holds a copy. SAP keeps its own change history, and the agent adds where the value came from, who approved it and why.

Glass jars moving along a conveyor on a food production line

What changes for master data in SAP?

When the business partner in SAP and its copies in the CRM, the webshop and the PIM agree, sales orders stop failing on an old address and payments stop bouncing on stale bank details. Every agent downstream works from data you can trust.

Learn more

Example data

SAP S/4HANAMaster data health

Live

SAPCRMWebshopPIM

Customers

Suppliers

Articles

Prices

Contacts

AgreesDriftedNot held

99.6%of 14,208 records agree across 4 systems▲ 1.8 pts this month

Waiting on Finance · Supplier 2291 · bank details

SAP · changed todayNL20 •••• 4567

CRM · since 2023NL91 •••• 4300

Keep SAPKeep CRMBank details never change without the owner

One business partner, disagreeing between SAP and Salesforce.

The same customer is a business partner in SAP S/4HANA and an account in Salesforce, and the two records no longer agree. Somebody changed one of them and did not change the other.

Example data

Master data sweepEvery morning, 06:00

0records checked across six systems

23 disagreeand one of them is about to cost you three weeks of invoices

What that one field already touchedBrakveld Techniek · VAT ID

4Open orders carrying the wrong VATnot yet invoiced

2Invoices already issuedwill be rejected

1Credit check run on the bad recorddecision stands

Proposed to the data owner, with both records side by sideawaiting approval

Master data agent AI coworker · Lleverage

Online

You flagged 23 this morning. Which one is urgent?

This one. Brakveld Techniek’s VAT ID, and it has already been used.

Data sync check Salesforce · SAP

Working In sync

Salesforce Scanning

SAP S/4HANA Scanning

Brakveld Techniek 0 records compared

Salesforce

VAT ID

NL8123.45.678B01

SAP

VAT ID

                    NL8132.45.678B01
                    NL8123.45.678B01
                  

≠

Salesforce is right. SAP has been wrong since 14 May.

Approved. Brakveld Techniek’s business partner is corrected in SAP and the other five systems, and the change is logged. The other 22 are queued the same way.

Human in the loop

You decide which SAP master data fields need their owner

Every field on a business partner or material has an owner and a rule. Clear-cut fixes are written to SAP and every other system on their own, and anything that touches money, rights or a merge waits for the person who owns that field.

01Who owns which fieldFinance owns payment terms, sales owns contacts. You write it down once.

02Checked where the change happensVAT, duplicates and formats before the record spreads.

03Some fields never change on their ownBank details, credit limits and permissions always go to their owner.

Example data

Business partner 2291 · Noordkamp Lagers B.V.5 fields changed

AddressKeizersgracht 12, AmsterdamAgent · synced

Phone+31 20 555 0192Agent · synced

VAT numberNL8591 ••• B01Agent · checked

Bank detailsNL20 •••• 4567Person · Finance

Credit limitEUR 40,000 → 60,000Person · Credit control

The agent handles itGoes to a person

SAP Master Data Governance or Lleverage: which fits when?

SAP’s own answer is SAP Master Data Governance (MDG), which governs business partner, customer, supplier, material and financial master data with change requests, consolidation, mass processing and data quality rules. We read SAP Learning’s course on MDG on SAP S/4HANA and SAP’s product page on 11 October 2026, and every statement in the middle column comes from those pages.

	SAP Master Data Governance	Lleverage
How a change starts	A business user opens a change request. The data is maintained in a staging area, validated by business rules and approved by domain experts before it is activated and replicated.	Wherever the change is made: in SAP, the CRM, the webshop or the PIM. A sweep every morning finds the records that drifted without anyone asking.
Which master data	Customer, supplier and business partner, material, and financial data such as profit and cost centres. Retail and enterprise asset management data come as add-ons with their own licence.	Customers, suppliers, articles, prices and contacts: the records the other agents on our platform work from.
Systems outside SAP	Approved data is replicated to SAP and non-SAP systems with the Data Replication Framework, on ALE/IDoc and Enterprise Services, with key and value mapping and a replication status per target system.	Reads and writes the systems you already run, including on-prem databases and portals with no API, and keeps each copy in step with the one that should win.
Duplicates	Duplicate checks run early in the change request, and consolidation matches loaded records against each other and against existing ones, with a best record review.	A new business partner is matched against the ones SAP holds before it is created. A merge always goes to a person.
Bulk changes	SAP’s strength. Mass processing changes many business partner, customer, supplier and product records at once, from a table or a CSV or Excel upload, validated before activation and run in the background.	Corrections are proposed one record at a time, each with its owner and its trail. For a planned bulk change inside SAP, we think MDG mass processing is the stronger tool.
Data quality rules	A central repository of validation rules, built in BRFplus, used for quality evaluations and to check change requests, consolidation and mass processing. Rules can be simulated before approval.	Rules per field, written down once with your data owners: who owns which field, which checks it needs, which fields never change on their own.
Audit trail	Change documents show who changed which attribute, when, and from what value to what value. Workflow logs show who approved which change.	Lineage on every field: which system the value came from, who changed it, when, and on whose authority, readable by a person.
Versions and price	Runs on SAP S/4HANA on-premise or Cloud Private Edition, as a hub or co-deployed. A public cloud edition covers business partner and product. The Private Edition offering is sold in blocks of 5,000 objects, price on request.	SAP S/4HANA and SAP ECC, on your own servers included. One monthly price per agent, with integration included.
Fits best when	Every new customer, supplier or material must pass a formal request and approval, and an SAP team configures the data models, workflows and rules.	Records drift between SAP and the systems around it, and your people spend the day finding the differences and fixing them by hand.

We think SAP Master Data Governance is the right tool when every create and change in SAP has to pass a formal request with approvals, and you have the SAP team to configure it. We think Lleverage fits when the work you want gone is finding what drifted between SAP and the systems around it, and fixing it with the owner in the loop. More on AI agents next to MDM software.

Our engineers set it up with you.
It takes on more of the data work as it learns.

Forward deployed engineers clean the first domain with your data owners and connect it to SAP, S/4HANA or ECC, so the corrections come off the desk in the first weeks rather than at the end of a project. From there it automates gradually: every decision teaches it which system owns which field, and fewer business partners and materials need a person to look.

A busy operations office with people working at their desks

The FDE model Forward deployed engineers, with you for the first domain and for every one after.

They work inside your operation. They map every system that holds a copy with your data owners, set the confidence line together, and stay on as systems are added. Not a licence and a manual. A team that knows your records.

If you preferSame agents Self-served Your own data team builds it in Lleverage.

The system connections, the ownership rules, the validations and the log are yours to configure. Our documentation and support sit behind your team, and an engineer is a call away whenever you want one.

Talk to us about either ↗

Frequently asked questions

What is SAP master data management?

It is keeping the records every SAP process runs on correct: business partners for customers and suppliers, materials, prices and finance objects. In SAP S/4HANA a customer and a supplier share one business partner, and SAP offers Master Data Governance to control changes. The agent keeps those records in step with the systems around SAP.

Do we still need SAP Master Data Governance?

Not to start, and it does not get in the way if you have it. MDG governs how a record is requested and approved inside SAP. We think the agent earns its place on the work around that: finding records that drifted between SAP, the CRM and the webshop, checking them and fixing them with their owner.

Does it work with SAP ECC?

Yes. On ECC the agent compares and corrects the customer, supplier and material records your release holds, as it does business partners on S/4HANA, with a data steward’s access, on your own servers too. We think ECC is a good place to start: records cleaned now are fewer to fix in a move to S/4HANA. See integrations.

Which SAP master data does the agent change on its own?

Only the fields you allow. Clear-cut fixes, such as an address or a phone number that one system holds wrong, are written to SAP and the other systems on their own. Bank details, credit limits, permissions and any merge of two business partners always wait for the person who owns that field.

How long until the first records are cleaned?

One domain comes first, often customer business partners, and it typically runs supervised within a few weeks. Our forward deployed engineers sit with the people who own each field, list every system that keeps a copy and write down which value wins. Until the numbers show otherwise, every proposed fix waits for a person to approve it before SAP changes.

Where is our master data hosted?

In the EU by default, and on-prem if you need it, under GDPR. Your business partners and materials stay in SAP, which remains the record. Contacts, addresses and bank details are read to compare copies, and each field the agent touches keeps its lineage: the source system, who changed it, when and on whose authority. See control and audit trails.