Data validation before an ERP update
See what will change before it reaches the ERP. Check company details, contacts and addresses in the same review process.
What does human validation mean here?
Manual data validation lets a user inspect and correct the draft or compare a bulk proposal with the current source value. Approval applies to the displayed changes and selected connection.
What to verify before approval
Review information in context
Check the legal entity, customer or supplier type and tax details alongside the contact information.
Share the review experience
Addresses can be billing, shipping or both. Review those roles before provider-specific mapping.
Keep authorization separate
Follow the result after submission. A failed request and an uncertain source write need different follow-up.
How it works
- 1
Open the proposal
Open the draft or proposed changes.
- 2
Check company and contacts
Compare critical values with your source records.
- 3
Inspect the exact changes
Correct the data and confirm the intended scope.
- 4
Approve deliberately
Submit and check the reported outcome.
Example: Human validation
A website lists the head office, but purchasing needs a branch delivery address. Change the shipping address while keeping the correct billing address.
Human approval does not make website data legally verified. Source automation may run after an approved update.
Frequently asked questions
What does this process do?
Which systems and data are covered?
What access or approval is needed?
What usage conditions apply?
Have a record or connection in mind?
Set up your company workspace, or describe the ERP and master data problem through Contact.