Sign in Start free trial
Platform

Master Data

One item master and one business partner record, shared by every hub you license, with the quality rules and approvals a data steward needs.

Every product, service, customer and supplier is one record, not a copy in each hub. The item master holds the basic facts and the item category that decides which accounts an item posts to; the business partner holds names, tax ids, addresses, contacts and relationships, and can be a customer and a supplier at once. Each licensed hub adds its own view of the same record: sales prices, supplier terms, stock profiles, credit limits, bank details. You decide which fields are required, which changes need a second person, and you can see who changed what, when and why.

14 features available 4 capability areas
Highlights

What stands out

One record, every hub

Change a name, a unit or a category once and sales, purchasing, stock, receivables and payables all follow.

The category decides the accounts

Revenue, cost of sales, inventory, expense, goods received not invoiced and price variance post to the accounts of the item category, per legal entity, from a date.

Duplicates found at any size

Partners are matched on normalised tax id, email, phone and name, never every pair against every other, so the review stays fast with hundreds of thousands of partners.

A second person for what matters

Merges and the field groups you choose go through a change request that a different person approves; the assistant drafts and never decides.

Every change on record

Each record shows who changed which field, from what to what, when, from where and through which approval.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Item master

One record per product or service, shared by every hub.

4 features
  • Item workspaceBasic data, kind, base unit and other units, category, attributes, status and external ids, with a tab for each licensed hub's view.
  • Create, copy, import, archiveCreate from a form, by copying an item, from a file with a preview of the rows it would refuse, or by asking the assistant; archive and restore, never delete.
  • Item categories and accountsA category has a valuation class, a tax class and a parent; for each role it names the account, per legal entity and from a date. Warehouse, Receivables and Payables resolve the item, then the category, then the entity default.
  • Items on bill linesA payables bill line can name its item; the expense, goods received not invoiced and price variance accounts and the tax class follow it.

Business partners

One record per customer, supplier or partner, with a tab for each role and each licensed hub.

4 features
  • Partner workspaceNames, tax ids, typed addresses, contact people, the parent company and bill-to and ship-to relationships, with the customer, supplier and CRM views of the hubs you license.
  • Protected sectionsCredit limits and bank details are sent only to people who hold the right; bank details change only through the bank-change controls.
  • Duplicates at scaleCandidates come from normalised tax id, email, phone and name keys with indexes, never all pairs, and a scan is paged.
  • Four-eyes mergeAnyone who may edit partners, or the assistant, proposes a merge; a different person approves it; it can be undone for 30 days.

Data quality and governance

Rules, approvals and history for the masters.

4 features
  • Mandatory fields per roleRequired, recommended or not asked, for each partner role and item kind, as company settings with safe defaults.
  • Change requestsMark a field group as needing approval: the change becomes a draft that is submitted and approved by a different person, who applies it.
  • Change historyEvery change of every item and partner, with who, when, from where, the approval it came through, and from and to of each field.
  • Where usedQuotes, orders, stock, invoices, bills, subscriptions and contracts that rely on a record, with the contracts linked to an item.

Reports and API

Data quality reports and the public API.

2 features
  • Data quality reportsDuplicates, incomplete partners and items, items and categories without accounts, partners by role and the merge queue, with a dashboard.
  • Public API and eventsItems, categories, account rules, addresses, relationships and contacts with idempotent writes and webhook events.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Create an item, copy it, archive it or change its category
  • Find duplicate partners and propose a merge for a second person to approve
  • Add an address, a relationship or a role to a business partner
  • Ask what is missing on a partner or an item against your quality rules
  • Ask for a change that needs approval and see who has to approve it
  • Show the full history of a partner or an item
  • Link an item to a contract and list the contracts that use it
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Master Data.

Workflow

A merge of two partners and any change to a field group you mark as needing approval is decided by a different person than the one who asked, enforced in the database. The requester submits, the approver applies.

  • A merge of two partners needs a second person
  • A change of a partner's legal name waits for a finance lead
  • A new item category for an item needs approval

Reporting and analytics

Ready-made data quality reports and a Master data quality dashboard: duplicates, partners and items missing required or recommended fields, items without accounts, categories without accounts, partners by role and the merge queue.

Datasets

ItemsItem categoriesBusiness partnersPartner rolesMerges

Dashboards

Master data quality

Integration

Items, item categories, the account rules of a category, partner addresses, relationships and contact people are API resources with list, get, create, update and archive, idempotent writes, and events that webhooks deliver. Setting a category account and deciding a merge stay with a person.

/v1 items, item categories, item category accounts, parties, party addresses, party relationships, party contacts

Events

Item created, updated, archivedItem category changedPartner address or relationship changedMerge approvedChange requested and applied

Migration

Items and partners that a migration pack lands appear here like any other record, with their source ids kept, and the quality reports show what the load left incomplete.

Mobile

On the phone

The lists and the record pages follow the phone frame; the decisions on merges and change requests are available on a phone.

Who uses it

Data stewardFinance leadProcurement leadSales operations

Industries

  • Industry starter packs bring sample items, categories and partners
Questions

Frequently asked

Is a customer and a supplier the same record?

Yes. One business partner can hold both roles; each role has its own tab with the terms of that hub.

Can we make some fields mandatory?

Yes. For each role of a partner, or kind of item, you choose which fields are required, recommended or not asked. A required field refuses a save that leaves it empty and says what to add.

Who can change a partner's legal name?

You decide. A field group can be changed directly or only through a change request that a different person approves.

Does the assistant merge duplicates?

No. It finds likely duplicates and can propose a merge; a different person decides it, and a merge can be undone for 30 days.

Do you delete items?

No. Items and partners are archived and can be restored; every hub keeps its history.

See Master Data on  AI

Talk to us