An unapproved supplier is a tax risk waiting to happen. A duplicate material is a repeat purchase. A customer with the wrong tax ID is a rejected invoice.
Data domains: where every error begins.
We organize every data domain in your company — supplier, customer, material, service, tax and reference data — into a single record, with rules, approval and evidence. Your team stops arguing over which system is right, purchases go through without rework and invoices go out without rejection.
160 clients trust us
The domains
Each domain has its own pain point and a dedicated solution.
Start with the domain that hurts most today. The platform is the same; what changes is the data model, the rules and who approves.
Supplier
Registration, qualification and approval with certificates, sanctions and automatic re-checking. No payment to anyone who is not compliant.
Supplier qualification →Customer
Onboarding with KYC and KYB, valid tax registration and normalized address before entering the ERP and the CRM. Sales released faster.
Customer onboarding →Material
Standardized description, taxonomy, mandatory attributes and deduplication. Idle stock and duplicate purchases show up before they cost you.
Material standardization (PDM) →Service
Service catalog with clear scope, unit of measure and tax linkage. Contracting and measurement no longer depend on interpretation.
Service standardization (PDS) →Tax and fiscal
Correct NCM, NBS, CST and cClassTrib in the master record, item by item. It is the master data that underpins Brazil's Tax Reform.
Reforma Tributária →Reference data
Lists, codes, units, plants and classifications that every domain consumes — kept in one place and checked against the official source.
Reference sources →What changes for you
Less rework, less risk, more speed.
Records come out right the first time
The rule enforces the required field at the moment of entry. No one opens a ticket later to fix what came in wrong.
The queue is no longer a black box
Every request has a deadline, an owner and a status. Procurement and sales stop emailing to ask where the record stands.
Tax risk goes down
Registration status, clearance certificates, tax registrations and tax classification are checked at the source and revalidated over time.
Reports add up again
With duplicates handled and descriptions standardized, spend by category, ABC curve and supplier view stop diverging across areas.
321+
master data projects delivered since 2019
60M
domain records managed on the platform
127k
users managing records day to day
6
countries served, with local and remote teams
“We started treating master data as a process, with an owner and a deadline. The argument over which database is right simply left the agenda.”
Start by measuring the size of the problem
The free diagnostic runs on a sample of your database and shows, by domain, how many records are duplicated, incomplete, or have irregular status in the public source. Nothing to install.
Concept
What MDM is, and why you need dedicated software.
Master Data Management (MDM) is the discipline that defines, maintains and distributes the single record for each business domain: supplier, customer, material, service and reference data. It is not a report or an integration: it is the master record itself, with an agreed definition, quality rules, an owner and history.
MDM software exists because this work has requirements that no general-purpose system meets: a data model per domain, attribute-by-attribute validation, deduplication with scoring, approval by authority level, lookup against official sources and publication to consuming systems — all with an audit trail.
Model per domain
Entities, attributes, value domains and hierarchies configured per domain, with no development.
Single record
Deduplication, matching and survivorship rules to reach a single record, and keep it that way.
Measured quality
Rules at entry and in base scans, with indicators per critical attribute and per domain.
Governed distribution
The approved record is published to ERP, CRM, WMS and the data lake, with versioning and change log.
Why what you already have in-house does not solve it
Almost every company first tries to adapt a tool it already has. Each one solves a piece and leaves out what matters most.
SRM and procurement portals
Built for the transaction, not for master data
They handle quotation, purchase order and contract, but treat the supplier as a partner in that process — not as master data shared by tax, finance and logistics.
They cover a single domain. Material, service, customer and reference data remain outside.
No deduplication, no survivorship rules and no periodic revalidation of certificates and registration status.
Helpdesk and workflow tools
They move the order, they do not know the data
The ticket circulates with attachments and free text. The tool does not know what a product classification code, a unit of measure or a tax registration is, so it validates nothing.
Approving means closing the ticket; data entry in the ERP is still manual, and that is where the error comes in.
The history stays in the ticket, not in the record. No one can say who changed that attribute, or why.
Legacy descriptive standardization
Good description, project that finishes
Legacy standardization software generates descriptions from templates and dictionaries, but stops there: no workflow, no approval levels, no lookup against official sources and no online integration.
The base is standardized once, during the project, and starts degrading again the day after go-live, because item creation remains out of control.
They only address material. Supplier, customer and tax data remain untreated.
What only MDM delivers
One master record per domain, with its own model, rules at entry, deduplication, approval by authority level, lookup against more than 600 official sources, publication to consuming systems and an audit trail — plus a governance model that keeps it alive after the project.
How it works under the hood
From domain model to ERP load.
The mechanics are the same in any domain: model, validate, deduplicate, approve and distribute. What changes are the attributes, the sources and the approval policy.
Domain modeling
Entities, mandatory and optional attributes, value domains, hierarchies and relationships between domains (vendor × material × plant).
Standardized taxonomy and nomenclature, with a description template per material or service class.
Low-code setup: field, type, mask, requirement and visibility per stage, with no development.
Quality rules
Syntactic, semantic and cross-field validation, applied at entry and in periodic scans of the active base.
Checks against official sources: Receita Federal, SEFAZ, Sintegra, certificates, sanctions lists and more than 600 sources.
Dimensions measured per domain: completeness, uniqueness, consistency, conformity, accuracy and timeliness.
Deduplication and golden record
Phonetic and similarity search prevents the duplicate at creation, not just in next month's report.
Batch matching with score, surviving record suggestion and attribute-by-attribute survivorship.
ADAM, the platform's AI, analyzes the description, suggests a classification and flags the similar record for the steward to decide.
Workflow and integration
Approval flow per stage, with authority levels by area, SLA, return with reason and a full trail of what changed.
Publishing to SAP ECC and S/4HANA, plus ERPs, CRM, WMS and data lake, via API, IDoc, BAPI or file.
Scheduled reprocessing and re-checks keep the record valid after go-live.
Management model
Domain governance: roles, policies and indicators.
A tool without an owner does not sustain quality. Each domain gets an operating model: who decides, who executes, what is written in the policy and what is measured every month.
MDM Engineering: who builds this model with you
Defining roles, responsibilities, processes, deadlines, KPIs and SLAs — implementing the MDM management model in your company — is delivered by our MDM Engineering, a service contracted separately from the platform.
Role
Data owner
Business executive responsible for the domain. Approves the data definition, the policy and the exceptions.
Role
Data steward
Manages the domain day to day: reviews requests, resolves duplicates, maintains taxonomy and answers for the indicators.
Policies and controls
Registration policy by domain: who requests, who approves, what is mandatory and what blocks.
Data dictionary with business definition, owner and rule for each attribute.
Segregation of duties, access profile by step and field, and change log with author, date and previous value.
Audit trail and evidence attached to the record, aligned with ISO/IEC 27001, LGPD and GDPR.
Indicators tracked
Completeness and compliance index by domain and by critical attribute.
Duplicate rate and volume of merged records in the period.
Average request handling time and SLA adherence by step.
Records with expired documentation, irregular status or open pending issues.
Maturity and evolution
From firefighting to mature governance.
No company jumps from chaos to control in a single quarter. The path runs domain by domain, in waves, with visible gains at each stage. The diagnostic shows where you stand on this scale.
Level 1
Reactive
Records kept in spreadsheets and email, with no owner. Correction happens only after the error has already stopped operations.
Level 2
Standardized
Domain model defined, base cleansed and a single request flow, with rules applied at the point of entry.
Level 3
Governed
Owner and steward appointed, policy published, indicators tracked and a complete audit trail.
Level 4
Optimized
Quality monitored in real time, AI supporting classification and decision-making, and the domain sustaining analytics and tax initiatives.
Which level is each domain of your company at today, and what is the next step with the best ratio between effort and return?
Talk to a specialistContact
Which domain do you want to organize first?
A specialist reviews your scenario, shows the current state of the chosen domain, and proposes the next step. No commitment.
Av. Queiroz Filho, 1700, Torre E, Conjuntos 715 a 718
Vila Leopoldina, São Paulo, SP, 05319-000
Perguntas frequentes