Business management · Master Data (MDM)

One person, one CPF, everything the company holds on them in a single profile

The same person is a graduate, the financial guarantor of another graduate, a freelancer and a CRM customer, in records that do not talk to each other. Type the CPF and see where they appear in more than 30 records across the platform, the consolidated record with the source of each field, what they owe and how many tickets they have. Record quality points out invalid CPFs, records without a CPF and names that do not match, and the data subject report answers the LGPD request, with a record of who looked it up.

The problem and the fix

The problems Master Data (MDM) solves every day

If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.

The problem

To find out what a person has with the company, someone opens module after module and builds the answer by hand.

With Partiu Formatura

The CPF profile searches every record at once and shows each link with the module, the role and a shortcut to the record.

The problem

The graduate's name is spelled one way in the contract, another in the app and a third way in finance.

With Partiu Formatura

The consolidated record shows the values from each source, flags the mismatch and lets the steward pin the correct value with a reason, with a history of who decided.

The problem

Nobody knows how many records have no CPF or an invalid one.

With Partiu Formatura

Record quality shows, source by source, how many records have a CPF, how many do not and how many are invalid, with spreadsheet export.

The problem

The committee sent a spreadsheet with 300 CPFs and the question is who is already in the database.

With Partiu Formatura

The batch check takes up to 500 pasted CPFs and returns a CPF by module matrix, with invalid and not found flagged.

The problem

An LGPD data access request arrived and nobody knows where to start.

With Partiu Formatura

The data subject report gathers everything the company holds on that CPF, with the issue date, ready to export and print.

The problem

There is no way to say who looked at a person's data.

With Partiu Formatura

Every profile opened, report issued and list checked goes into the access log, with who and when, and the log can be filtered by CPF.

In practice

Real examples of Master Data (MDM) working for you

Everyday situations at graduation companies, from the problem to the result, using the modules on this page.

01

The mother who was also a freelancer

The scenario

A graduate's mother called to complain about a charge, and the support team did not know she also worked as a freelancer at the events.

With the system

Her CPF opened the profile with her links as financial guarantor, freelancer and app user, plus a summary of the open installments.

The result

Support solved the charge knowing who they were talking to, without opening three modules.

02

The name that did not match the contract

The scenario

A graduate appeared with an abbreviated surname in the pre-registration and the full one in the signed contract.

With the system

The profile showed the mismatch and picked the name from the contract, the most trusted source. The steward confirmed the value with a reason.

The result

The consolidated record started showing the correct name, and the team fixed the source pre-registration through the profile shortcut.

03

The data subject request answered the same day

The scenario

A former graduate asked, under the LGPD, for a list of everything the company held on him.

With the system

The profile was opened by CPF and the data subject report was issued with the issue date.

The result

The answer went out the same day, and the access log kept who issued the report.

How it works

How information flows through Master Data (MDM)

Every step is a real module, and what comes out of one goes into the next without anyone typing it again.

  1. 1The CPF is typed inWith or without punctuation, or a search by name and email returns masked CPFs. The CPF never goes into the page address.
  2. 2The records are read liveMore than 30 sources are queried in parallel, and installments, tickets, contracts and orders come in through the app users linked to the CPF.
  3. 3The record is consolidatedFor each field, the steward's choice wins, then the most trusted source and, on a tie, the most recent record. The source of each value stays visible.
  4. 4The steward decidesWhen sources disagree, whoever has permission pins the correct value with a reason, and the choice goes into the history.
  5. 5Quality is measuredThe quality screen points out invalid CPFs, records without a CPF and mismatches by source, so the fix happens in the source module.
  6. 6The LGPD request is answeredThe data subject report comes from the profile, and the access log records every lookup, report and list checked.

Module by module

Everything included in Master Data (MDM)

6 modules and 28 features on this page, all running on the same class, graduate and event records.

Person Profile by CPF

Where the CPF appears, in which role and what it has with the company.

  • Search by CPF with or without punctuation, or by name and email, with candidate CPFs always masked
  • More than 30 sources: graduate, guardians, app and admin users, CRM, employee, freelancer, supplier, contract, legal, ticket, store and others
  • Each link with the module, the person's role and a shortcut to open the source record
  • Open and overdue installments, tickets, contracts and orders through the app users linked to the CPF
  • A CPF with a wrong check digit is still searched, with a warning that it is invalid
  • The CPF never goes into the page address or the browser history
  • Nothing is copied: the profile is read live from each module's records

Consolidated Record with Source

The value that counts for each field, and where it came from.

  • Name, email, phone and date of birth consolidated from every source
  • Survivorship rule: the steward's choice wins; without it, the most trusted source; on a tie, the most recent record
  • Each candidate value shows the source, the date and whether it was chosen
  • Differences only in accents, case, spacing or phone prefix do not count as a mismatch
  • Only the person's own data counts: the graduate's name on the guardian's row does not get mixed in

Stewardship with a Reason

When sources disagree, someone decides, and the decision is recorded.

  • Pin the correct value of a field with a required reason
  • Stewardship history with when, field, value, reason and who
  • Undoing the choice returns the field to the automatic rule
  • Stewardship does not change the source record, which is still corrected in its own module

Record Quality

Where the wrong, missing or conflicting CPFs are.

  • By source: records, with CPF, without CPF, invalid CPF and distinct people, with spreadsheet export
  • Invalid CPF by length, repeated digits or check digit
  • Same CPF with a different name and a different date of birth across modules
  • People who appear in the most modules, as a starting point for review
  • Result cached for 10 minutes and a button to recalculate on the spot

Batch List Check

Paste the spreadsheet and find out who already exists in the company.

  • Up to 500 CPFs pasted at once: the committee spreadsheet, the caterer's list, the guest list
  • CPF by module matrix, with invalid and not found flagged
  • Result as a spreadsheet and a shortcut to each person's profile

LGPD: Data Subject Report and Access Log

The data subject request answered, and every lookup recorded.

  • Data subject report with everything the company holds on the CPF and the issue date, as a spreadsheet and for printing
  • Log of every profile opened, report issued and list checked, with who and when
  • Log filter by CPF to find out who looked up a person
  • Separate permissions to view, pin values and export

Find the right plan for Master Data (MDM)

Compare the modules and choose the setup that fits your operation.