Platform
Twenty-four modules on one data model
How an ERP behaves day to day is decided not by module count but by how modules connect, how many times data is keyed, and when the system refuses a transaction. Tokuva's architecture rests on the answers to those three questions.
Platform foundations
Four organisational levels
Tenant, company, branch and site, with departments modelled as a matrix of reporting parent and physical location.
Posting proposal engine
The only door between modules and the ledger. Balanced drafts released by approval.
Nine-dimensional costing
One journal line carries company, site, department, cost centre, project, product group, channel, activity and a free dimension.
Localisation in the core
Turkish primary, English fallback, Unicode throughout, culture-aware date, number and currency formats.
API first
Anything a screen can do, a service can do. Integration is not a later layer.
Audit trail everywhere
Creator, modifier and deleter on every row. Deletion is logical; hand-made backup tables are forbidden.
24 modules
All sharing one data model.
See the architecture on your own flow
A live flow runs on your own data instead of a slide deck.