Base
Master data every module inherits — warehouses, clients, groups, products, units, currencies, cost centres, tax classes, chart of accounts, and the small reference tables that tie everything together.
What lives
.
A line-by-line inventory of what ships. None of it is hypothetical — these are the menu items, reports, and workflows in production.
- Warehouses, clients, groups, regions
- Persons, expense types
- Cities, countries, products, units, categories
- Groups, taxes, product locations
- Municipalities, taxpayer types
- Accounts for assets and cost centres
- Currencies, banks, cards
- Religions, gender, nationalities, education
- Regional units, annual parameters
- Contribution rates, annual operations
A module,
.
Base Data is not a separate app. It uses the same customers, the same products, the same cost centres, and the same currencies as every other Venikom ERP module. Postings land in the same accounting. The audit trail is one line, not eighteen.
Adding another module later means turning it on — not re-entering a single customer, product, or account.
- Your customers one list, shared across everything
- Your accounting numbers flow in automatically
- Your archive every document, searchable
- Your permissions who sees what, set once
- Your reports one format, everywhere
Shipped, running, .
This module is in production at paying customers. It runs under the same SLA as the rest of the platform. It follows the same release rhythm — monthly minor updates, quarterly reviews, emergency patches when a regulator publishes new requirements.
- Domain
- Platform & administration
- Slug
- base-data
- Tagline
- Shared master data across modules
- Capabilities
- 10 documented
- Isolation
- your data stays yours
- Audit
- full trail · archived
- Status
- production
Twenty minutes is enough if it fits.
We open a sandbox loaded with a scenario from your industry and walk through Base Data with your team watching.