IFS Cloud | Master data · Independent IFS Cloud practice
One agreed record per business entity, with an owner for every field
A golden record in IFS Cloud is the single version of a business entity that every transaction uses: one supplier, one customer, one part, built from rules your company writes down. IFS Cloud gives you duplicate checks and migration-time cleansing. The rules and the owners still have to come from you.
Key takeaways
- A golden record rests on a written decision: for each attribute of a customer, supplier or part, you name the system that owns it and the person who approves changes to it.
- IFS Cloud has a Duplicate Check for leads, accounts and supplier requests, configured on the Duplicate Check Rule and Duplicate Check Action Setup pages.
- IFS Data Migration Manager lists inbuilt data cleansing and validation and automatic flagging of potential duplicated data, so the first clean-up belongs in the migration, before the first transaction.
- Survivorship rules (recency, trusted source, completeness, frequency) decide which value wins when two records describe the same entity. Write them per attribute, not per record.
- A duplicate found after go-live already carries orders and invoices, so it is closed for new use and its open business is moved, which costs far more than catching it at load time.
When the sales team knows a customer as "Acme Corp" in London, logistics ships to "Acme Corporation Ltd" in Manchester and finance invoices "Acme Intl" in New York, IFS Cloud holds three customers where the business has one. Each of them gets its own credit limit, its own order history and its own line in the spend or sales report. The golden record is the fix: one customer with one identifier, plus a written rule that says which address is correct and which credit limit applies. This article explains how to build that in IFS Cloud and which parts the system does for you.
1.What is a golden record in IFS Cloud?
A golden record is the authoritative version of a key business entity (customer, supplier, part or site) that all processes and reports use, assembled from every source that holds data about it. In an IFS Cloud implementation the golden record usually lives in IFS Cloud itself, because that is where orders and invoices are posted against it.
The record can be a composite. The phone number and contact person may come from a CRM, the credit limit from finance, the tax ID from a registry check, and the delivery address from the order desk. What makes it "golden" is that each of these attributes has one owning source and one rule for conflicts.
| Property | What it means in practice |
|---|---|
| Authoritative | When another system disagrees, the golden record wins and the other system is corrected. |
| Composite | Different attributes can come from different owning systems, each written down. |
| Persistent | The identifier stays stable through updates, re-imports and integration changes, so history stays attached to it. |
| Governed | Named data stewards approve new records and changes to owned attributes. |
If you run a separate master data tool in front of IFS Cloud, the same decisions apply. The tool then holds the match and survivorship rules and sends the result to IFS Cloud through an integration, and IFS Cloud becomes a subscriber instead of the place where the record is decided.
2.Where duplicate master data comes from
Duplicate master data in IFS Cloud enters through four routes, and each route needs its own control.
- Migration loads. Two legacy systems, or one legacy system with years of manual entry, deliver the same supplier under two names. If nobody matches them before the load, both go live.
- Manual entry at several sites or companies. A buyer at one site creates a supplier that another site already uses, because searching took longer than creating.
- Integrations. A CRM, e-commerce platform or supplier portal creates records through an interface that skips the checks a user would see on screen.
- Supplier onboarding. A supplier request is approved without anyone comparing its tax ID and bank details with existing suppliers.
Migration is the cheapest route to close, because nothing has been posted yet. The recurring migration failure patterns are covered in IFS Cloud Data Migration: Five Risks That Delay Go-Live.
3.What IFS Cloud gives you out of the box
IFS Cloud provides two standard tools that support a golden record: the Duplicate Check for new records, and the quality functions of IFS Data Migration Manager for loads.
Duplicate Check
The IFS Cloud documentation on Duplicate Check describes it as a check that prevents duplicate leads, accounts and supplier requests. It runs automatically when one of these records is created and can be triggered manually afterwards. Two pages configure it:
- Duplicate Check Rule: the rules used in the duplicate search. Some rules are delivered by default, and you can add or edit others.
- Duplicate Check Action Setup: the default action per object, with different actions possible for specific representatives.
The action decides how hard the check is. You can prevent the user from saving the new record, notify the user and show a list of potential duplicates (not available for account records), only notify the user, or take no action and store the duplicate information with the record.
Data Migration Manager
IFS Data Migration Manager is the migration tool for moving data between environments, and its technical documentation lists "Inbuilt data cleansing and validation" and "Automatic flagging of potential duplicated data" among its quality functions. The practical use of both, from legacy table to loaded record, is described in IFS Cloud Data Migration: FndMig & DMM Field Guide.
| Tool | When it acts | What it does not decide for you |
|---|---|---|
| Duplicate Check | At creation of a lead, account or supplier request, or on demand | Which of two matching records survives and which attributes it keeps |
| Data Migration Manager | During trial loads and the final load | The match rules and the owner who signs off each merge decision |
| Your data governance | From the first trial load onwards | Nothing: this is where survivorship rules and stewardship are written down |
4.How are records matched, and which value survives?
Building a golden record takes three steps on every incoming record: standardise it, match it against existing records, and merge the match according to survivorship rules.
Standardise before you match
Match rules compare values character by character, so inconsistent formats hide real duplicates. "St." and "Street", a phone number with and without the country prefix, or a country written as a name in one source and as a code in another will defeat any match rule. Agree on formats first: phone numbers in E.164, country codes as ISO values, legal-form suffixes such as "Ltd" or "GmbH" removed from the match key.
Deterministic and fuzzy matching
Deterministic matching treats records as the same entity when a unique identifier is equal: tax ID, VAT number, company registry number or a DUNS number. It is safe to automate. Fuzzy matching compares names and addresses and produces a likelihood score. Records above your upper threshold are treated as matches, records below the lower threshold as different entities, and everything between goes to a data steward.
Survivorship rules
Survivorship rules decide which value of each attribute is kept when matched records disagree. They are written per attribute, because the most trusted source for a credit limit is rarely the most trusted source for a phone number.
| Rule | How it decides | Example |
|---|---|---|
| Recency | The most recently updated value wins | The delivery address changed last month replaces the one from last year |
| Trusted source | A named system owns a named attribute | CRM owns phone numbers, finance owns credit limits |
| Completeness | The value from the record with more populated fields wins | Keep the address that includes the postal code |
| Frequency | The value that appears in most sources wins | Use the name spelled the same way in most source systems |
Start with trusted source and recency, because both are easy to explain to the business. Add completeness and frequency where the first two leave ties.
5.Data stewardship: who decides the grey cases
A data steward is the named person who decides matches the rules cannot settle and approves changes to the attributes their domain owns. In practice there is one steward per domain: purchasing for suppliers, sales or credit control for customers, engineering or planning for parts.
Stewardship has to be in place before go-live, because a wrong merge propagates. Two legacy records merged in error before the load, in the migration or in an external master data tool, arrive in IFS Cloud as one record carrying the open orders and history of both, and separating them afterwards means correcting transactions, not just master data. Once a duplicate has transactions against it, the usual route is to stop its use for new business, move open orders to the surviving record and keep the duplicate for history.
The same discipline applies to the attributes that drive automation. A supplier lead time, a reorder point or a planning parameter that nobody owns produces automated decisions nobody can explain, which is the pattern described in The Exception That Was Not an Exception in IFS Cloud. A broader view of ownership and data governance is in the consulting article Your Single Source of Truth.
6.How to build a golden record in an IFS Cloud project
A golden record is built in six steps, and the first four belong in the data migration workstream, before the first trial load.
- Profile the source data. Count duplicates, empty mandatory fields and inconsistent formats per source and per entity. The numbers tell you where stewardship effort will go.
- Name owners per attribute. The business functions agree which system owns which attribute and who approves changes to it.
- Write match and survivorship rules. Deterministic keys first, fuzzy thresholds second, survivorship per attribute. Keep them in the migration strategy document so they can be reviewed.
- Cleanse and match before the load. Run cleansing and duplicate flagging in the trial loads and clear the steward queue before the final load. Expect the first trial load to produce the largest queue.
- Configure Duplicate Check for live operation. Choose the rules and the action per object on the Duplicate Check pages, so new leads, accounts and supplier requests are checked when they are created. The documented scope does not name suppliers created directly (without a supplier request) or parts, so those need a steward review of new records.
- Keep it running. Integrations that create records get the same checks as users. Stewards review new records on a fixed rhythm, and the rules are revisited when a new source system is connected.
The governance checks that keep this disciplined through cutover are listed in The Data Migration Governance Checklist. Writing the rules down is where the Data Migration Strategy Template (IDK-14) helps: it gives the migration workstream one document covering scope by data object, ownership, cleansing approach, load cycles and reconciliation, and the match and survivorship rules fit into its ownership and cleansing sections instead of living in one consultant's head.
7.Frequently asked questions
What is the difference between a golden record and a data warehouse?
A golden record is operational master data that IFS Cloud transactions use, such as the one supplier record a purchase order is placed against. A data warehouse stores history for analysis and reporting. The golden record feeds the data warehouse, so a clean golden record is what makes spend and sales reports add up.
Does IFS Cloud check for duplicate customers and suppliers?
IFS Cloud has a Duplicate Check that, according to the IFS Cloud documentation, prevents duplicate leads, accounts and supplier requests. The documented scope does not name suppliers created directly without a supplier request, or parts. The check runs when such a record is created, uses rules maintained on the Duplicate Check Rule page, and its action (prevent saving, notify with a list, notify, or no action) is set per object on the Duplicate Check Action Setup page.
What happens if two records are merged by mistake before the IFS Cloud load?
Two legacy customer or supplier records merged in error before the load, in the migration or in an external master data tool, arrive in IFS Cloud as one record carrying the open orders and history of both, and the error spreads to every report and integration that reads it. Separating them later means correcting transactions, which is why grey-zone matches go to a named data steward instead of being merged automatically.
When should the golden record be built in an IFS Cloud implementation?
The golden record for an IFS Cloud implementation should be built during data migration, before the first trial load, because duplicates cost least to resolve before any transaction exists. Data profiling comes first, then attribute ownership, then the match rules, and the steward queue is cleared before the final load.
Who owns master data in an IFS Cloud company?
Master data in IFS Cloud is owned per domain and per attribute by named business people, not by IT. Purchasing typically owns supplier data, sales or credit control owns customer data, and engineering or planning owns part data. Each owner approves new records and changes to the attributes their domain is responsible for.
8.About the author
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
Master data decisions are made in the migration workstream of every implementation I work on: which source wins, who signs off a merge, and when the duplicate check is switched on.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Write the match and survivorship rules down before the first load
The Data Migration Strategy Template (IDK-14) gives your migration workstream one document for scope by data object, ownership, cleansing approach, load cycles and reconciliation, so the decisions behind the golden record are signed off before the first trial load.
See the Data Migration Strategy Template (IDK-14) Read: The Data Migration Governance Checklist

Deutsch (Deutschland)
Polski (PL)