Tokuva is a Toku Technology product toku.com.tr

+90 532 488 94 66
TR EN
Customer Portal
tokuva
Request a demo
Product
Modules
Finance and Accounting Manufacturing Procurement Sales Inventory and Warehouse Human Resources Payroll Quality Management View all (24)
Solutions
Manufacturers Textile and Apparel Food Production Machinery and Metal Construction and Contracting Distribution and Wholesale
Resources
Blog Tools Resources Compare Pricing Newsletter
Company
Who we are Toku Technology Customers Careers Contact
Request a demo
Customer Portal

Enterprise resource planning

One data model from the shop floor to the ledger

Tokuva is a twenty-four module enterprise resource planning (ERP) system that brings the shop floor, finance and statutory reporting into one data model. A kiosk confirmation issues components, receives the finished item and writes the cost to the journal. Nothing is carried between them by hand.

Request a demo with your data Explore the modules
  • 24 modules, one data model
  • Local regulation in the core
  • Four-level tenant, company, branch and site structure
  • One vendor, one accountability
24
modules
In one data model
4
structural levels
Tenant, company, branch, site
9
cost dimensions
On a single journal line
2
languages
Interface and data

Architecture decisions

Four decisions no feature list shows

How an ERP behaves day to day is decided by choices like these, not by a comparison matrix.

Modules never post directly

Every event produces a balanced posting proposal first. A wrong mapping lands in a draft, not in the ledger.

A released work order is frozen

Later engineering changes cannot disturb an order in progress, so what was built matches what the system recorded.

Three-way matching is a gate

Not a report. An invoice outside tolerance cannot be approved without a reason, and the reason stays on the document.

The default is closed

A new user sees no company's data until access is granted explicitly.

End to end

Two core flows, one chain

Order-to-cash and procure-to-pay do not stop at module boundaries.

Scope

Modules

Each module is a face of the same data model, not a separate product.

FIN
Finance and Accounting
Turkish chart of accounts, multi-dimensional costing, auditable ledger
MFG
Manufacturing
Bills of material, routings, work orders, shop-floor kiosk and live OEE
PRC
Procurement
Requisition to payment with real three-way matching
SLS
Sales
From price list to electronic invoice in one chain
INV
Inventory and Warehouse
FIFO cost layers, lot and serial traceability, dual units of measure
HRM
Human Resources
Employee records, leave, time and attendance, thirteen ready documents
PAY
Payroll
Attendance to journal, behind a four-eyes approval
QMS
Quality Management
Control plans, audits, corrective actions and certificate tracking
EBL
Electronic Documents
e-Invoice, e-Archive, e-Despatch and e-Ledger in one cockpit
MNT
Maintenance
From breakdown report to a posted maintenance cost
AST
Fixed Assets
Tax, IFRS and inflation books running in parallel
CRM
Customer Relationship Management
Lead to opportunity, quotation to order, one funnel
All modules

Shop floor

The kiosk is where the floor meets the ledger

An operator scans their badge, picks the order and reports. A stop cannot be saved without a reason, because that is exactly where the availability term of OEE comes from.

  • Machine and operator resolved by QR
  • Setup, run and downtime counted separately
  • Good quantity and scrap reported apart
  • Backflush, receipt and posting proposal on confirmation
Saha kiosku ekranı %86,7

Frequently asked

What size of business is Tokuva for?
It is designed for organisations with more than one legal entity, a production operation and typically more than fifty employees. For a single-company business that does not manufacture, the discipline of an enterprise ERP produces friction rather than value, and we would not recommend the move.
How long does implementation take?
Data determines the timeline, not code. Setting up definitions and migrating master data usually takes two to four months, including screen-by-screen testing. Go-live is staged company by company rather than all at once.
Is Turkish electronic invoicing supported?
Yes. Outgoing e-invoices, e-archive invoices, e-despatch notes and incoming invoices are tracked in one cockpit. Until an integrator account is defined and its connection test succeeds, the system stays deliberately in mock mode and submits nothing officially.
Can we migrate our existing data?
Master data is loaded through CSV import, validated by the same application rules as manual entry, with a row-level success and error report. Opening balances come in as open items or an opening journal. We usually advise against migrating full transaction history; the old system is kept as a read-only archive.
Where is our data held?
On your own server or a cloud provider you choose. The database is SQL Server and it is yours; you reach it with standard backup and export tooling. Data ownership is stated explicitly in the contract.

Run the demo on your own data

Share three of your items, one of your structures and one of your customers; a single end-to-end flow then runs on your own data. Wherever it snags is where it would snag in production.

Request a demo See pricing