Excel / CSV import
Customers, base volume, on- and off-invoice transactions. Turkish number and date formats are supported; ambiguous formats (1.234, 3/4/26) are rejected, never guessed.
CollMind TPM · Foundation
Data, integration and security: TPM is only as good as its data
Product hierarchy, customers, prices, costs and sales are treated as ERP data; CollMind TPM reads them and never overwrites them. Today data enters via Excel/CSV and is validated, and every operation runs through a REST API. Tenants are separated at database level, access is limited by role and scope, and financial records cannot be deleted.
The challenge
Data in spreadsheets, access open to all
Product codes, customer groups and price/cost data circulate in different files and versions. Anyone who opens a spreadsheet can see and change everything, and nobody can tell who changed a financial record, or why.
- No single source of truth for master data.
- Ambiguous number and date formats are silently misread.
- Who can see and change what is not defined.
How it works
- Step 1
Set up master data
Product hierarchy, customers and customer groups, channels, and the tactic and mechanic catalogue are defined on admin screens.
- Step 2
Import files
Customers, base volume and on/off-invoice transactions come in through upload → validate → confirm.
- Step 3
Define access
Users are given a role and a customer-group × category scope.
- Step 4
Keep the trail
Administrator actions, approval history and the ledger are kept as immutable records.
Key capabilities
REST API
Every operation runs through a REST API, documented with Swagger.
Multi-tenant isolation
Every record carries a tenant ID; database-level row security (RLS) and separate application, migration and operator database roles. Out-of-scope records return a uniform “not found”.
Roles and scopes
Role checks on every endpoint, deny by default, segregation of duties; scope is customer group × category.
Audit trail
Administrator actions, approval history and the ledger cannot be deleted.
Session and password security
JWT sessions; the application will not start if the signing key is missing, weak or a known default. Passwords are stored with bcrypt.
Who it is for
IT and data teams
Set up data flows through files and the API.
Information security
Assess tenant isolation, the access model and the audit trail.
System administrators
Manage master data, users, roles and scopes.
Screenshots use demo data; brand, customer and user names are illustrative. The product UI is shown in Turkish.
Roadmap
Coming next
The items below are not yet available; they are in development or planned.
- In development
Sales actuals upload
Backend and data contract ready; the upload screen is on its way.
- Planned
ERP and SFA integrations (e.g. SAP, Repzone) · data warehouse / BI connection
- Planned
Public, versioned API · Excel export
- Planned
Multi-currency and multi-language · e-invoice and e-reconciliation
- Planned
An audit vocabulary covering all event types, with retention automation
Let’s start with your data
We will show how your product and customer structure is brought into CollMind TPM using your own files.