Overview
Master data represents the core reference elements used across the Yarken platform. It forms the foundation for:
-
spend distribution
-
planning data (Budget, Forecast, and Workforce Planning)
-
cost pool, tower, consumers rules and mapping
-
reporting and analytics
All financial and consumption data relies on master data to ensure consistent classification and accurate cost allocation.
Master data is persistent across model periods, meaning any updates apply globally to past, current, and future data models.
What is included in master data
The following datasets are part of Master Data:
-
Accounts
-
Cost Centers
-
Vendors
-
Solution Offerings
-
Consumers (Business Units)
These datasets are interconnected and referenced throughout the Spend, Budget, and Forecast model.
Key considerations
-
Master data must be loaded before transactional data (such as spend or consumption).
-
Mandatory fields must be populated for successful uploads.
-
By default, only active records are visible in the application.
-
Changes to master data impact all dependent mappings and reports.
Master data types
Accounts
Accounts represent financial line items from the general ledger, such as expenses, revenue, or liabilities.
Usage in Designer
-
Mandatory during spend upload
-
Used in:
-
Cost Pool rules
-
Tower rules
-
filtering logic
-
Mandatory fields during configuring accounts:
-
Account Code
-
Account Name
-
Accounts must be configured before uploading actual spend
-
Spend records are mapped against accounts
Cost Centers
Cost Centers represent organizational units such as departments, teams, or business functions where costs are incurred.
Usage in Designer
-
Mandatory for spend uploads
-
Used in:
-
Cost Pool rules
-
Tower allocation
-
reporting dimensions
-
Mandatory fields during configuring Cost Centers:
-
Cost Center Code
-
Cost Center Name
-
Cost Centers must be configured before uploading actual spend
-
Spend records are mapped against Cost Centers
Vendors
Vendors represent external suppliers providing products or services.
Usage in Designer
-
Used in:
-
Cost Pool rules
-
Tower rules
-
Mandatory fields during configuring Vendors:
-
Vendor Code
-
Vendor Name
Vendor is optional during spend upload, however its recommended to load the vendor data for analyzing spend at vendor-level.
Solution Offerings
Solution Offerings represent the services delivered by IT, typically grouping multiple applications, platforms, or capabilities. It forms the service layer of the TBM model.
Usage in Designer
-
Used in:
-
Solution mapping
-
consumer allocation
-
Mandatory fields during configuring Solution Offerings:
-
Offering ID
-
Offering Name
-
Solution Name
Consumers
Consumers (Business Units) represent the internal or external entities that use IT services. The Consumer is the final allocation layer in the model and enables chargeback reporting. It provides visibility into who consumes IT spend.
Usage in Designer
-
Used in Solution-to-consumer mapping
Mandatory fields during configuring Consumers:
-
Consumer ID
-
Consumer Name
Next step
Related content