Platform

Model the business, not the limitations of the software.

Kiwid lets you define the entities, fields, relationships, hierarchies, and terminology your operation needs, so new products, markets, and industry requirements can be introduced without rebuilding the platform.

View Documentation
Core capabilities

Extensible Data Model

Configure the core once, then apply it consistently across the products, workflows, and teams that depend on it.

Entities & Fields

Define the business objects and attributes Kiwid needs to represent your operation.

Applied in practice

  • Add new business entities

    Model concepts such as service accounts, meters, contracts, claims, policies, merchant locations, or partner records without rebuilding the platform.

  • Extend existing records

    Add fields to customers, products, invoices, subscriptions, settlements, or other records as new requirements emerge.

  • Support market-specific data

    Capture additional attributes required by a country, business unit, product line, or operating model.

  • Model industry-specific operations

    Extend the common Kiwid foundation with the records required for telecom, financial services, SaaS, utilities, and other industries.

Relationships & Hierarchies

Connect records in the way your organisation, products, and financial relationships actually work.

Applied in practice

  • Model complex customer structures

    Connect organisations, accounts, billing accounts, services, subscriptions, and contacts across parent-child hierarchies.

  • Connect products to operations

    Link products, plans, services, usage, agreements, charges, and billing outcomes.

  • Trace financial relationships

    Connect invoices, receivables, payments, settlements, payables, adjustments, and accounting records.

  • Model partner ecosystems

    Represent merchants, agents, suppliers, distributors, and other counterparties with the appropriate commercial relationships.

Layouts & Terminology

Adapt how records are presented to match the language and operating context of each team.

Applied in practice

  • Use business-specific terminology

    Rename labels and concepts to reflect how your organisation refers to customers, accounts, services, contracts, or cases.

  • Configure role-specific views

    Show operations, finance, collections, or support teams the information most relevant to their work.

  • Adapt by market or business unit

    Present different layouts and information based on country, product line, or operating model.

  • Simplify complex records

    Organise fields and related information so teams can work with rich data models without clutter.

Industry & Domain Extensions

Extend the common platform with domain-specific records and relationships.

Applied in practice

  • Add telecom structures

    Model services, numbers, devices, network products, usage records, and service hierarchies.

  • Support financial services

    Add facilities, repayment arrangements, fees, financial products, or institution-specific records.

  • Model utility services

    Represent meters, premises, service points, consumption records, and tariff structures.

  • Support new business models

    Introduce the entities needed for a new product or industry without creating a separate platform.

Record Lifecycle & Status Models

Define how business records move through their operational lifecycle.

Applied in practice

  • Model agreement lifecycles

    Track agreements through draft, active, amended, suspended, renewed, and terminated states.

  • Control financial record states

    Manage invoices, settlements, payables, disputes, or adjustments through defined processing stages.

  • Support operational cases

    Define statuses and transitions for collections, exceptions, disputes, investigations, or service processes.

  • Standardize lifecycle behavior

    Apply consistent statuses and transitions across teams while preserving domain-specific processes.

Reference Data & Classifications

Maintain the controlled business definitions used across the platform.

Applied in practice

  • Standardize business classifications

    Manage product categories, transaction types, customer segments, reason codes, and other shared definitions.

  • Support market variations

    Maintain currencies, tax classifications, locations, channels, and market-specific reference values.

  • Drive rules and reporting

    Use classifications consistently in policy decisions, workflows, pricing, segmentation, and analytics.

  • Reduce inconsistent data

    Replace free-form values with governed reference structures where consistency matters.

Modernize your data model