One record, every hub
Change a name, a unit or a category once and sales, purchasing, stock, receivables and payables all follow.
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.
Change a name, a unit or a category once and sales, purchasing, stock, receivables and payables all follow.
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.
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.
Merges and the field groups you choose go through a change request that a different person approves; the assistant drafts and never decides.
Each record shows who changed which field, from what to what, when, from where and through which approval.
Search or filter. Planned items are labelled; everything else is available now.
One record per product or service, shared by every hub.
4 featuresOne record per customer, supplier or partner, with a tab for each role and each licensed hub.
4 featuresRules, approvals and history for the masters.
4 featuresData quality reports and the public API.
2 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Master Data.
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.
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
Dashboards
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
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.
The lists and the record pages follow the phone frame; the decisions on merges and change requests are available on a phone.
gl: the category accounts post to the chart of accounts
ap: bill lines name the item, accounts and tax class follow its category
ar: customer view with terms, credit and dunning
wms: stock profile and costing of the item
cpq: sales view, price books and bundles
procurement: purchasing view and supplier items
crm: the account that shares the partner
clm: contracts that reference an item or a partner
workflow: second-person approval of merges and change requests
analytics: data quality datasets and dashboard
Yes. One business partner can hold both roles; each role has its own tab with the terms of that hub.
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.
You decide. A field group can be changed directly or only through a change request that a different person approves.
No. It finds likely duplicates and can propose a merge; a different person decides it, and a merge can be undone for 30 days.
No. Items and partners are archived and can be restored; every hub keeps its history.