Kramvia ERP
Kramvia ERP brings pharmacy operations, a transaction-linked accounting core and audit review into one product. A reviewed migration path helps distributors and wholesalers establish a checked opening position before starting work in Kramvia. Current use remains subject to an agreed pilot scope.
FOLLOW THE WORKFLOW
FICTIONAL WORKFLOW EXAMPLE
A fictional distributor receives a batch of stock. The supported purchase workflow records the operational document and its linked accounting entry. A later commercial correction is reviewed through its own record, so the original transaction remains traceable.
The useful connection is document → accounting effect → review history. Exact pilot scope determines which documents and corrections are included.
The current EasySol CSV adapter stages manufacturers, products, parties, opening stock and party opening balances for review. Other systems and historical documents need separate support confirmation before a migration is planned.
A receipt needs more than a product name and quantity. The operational record must preserve the supplier, batch, expiry and commercial context used by the team later in the day. Existing master data and unit conventions need review before migration.
Billing and inventory decisions belong in the same operational conversation. A team should be able to understand which stock a transaction refers to, rather than reconstructing the movement from separate files.
Supported operational documents and settlements create linked accounting entries. The ERP also includes a permissioned audit explorer and controlled correction workflows. Standalone Ledger is not required to obtain this accounting core.
A pilot should test a defined workflow with a responsible reviewer and an agreed way to compare results. It is not an unrestricted production launch or a promise that every existing system can be migrated automatically.
CURRENT PRODUCT SCOPE
Reviewed 22 September 2026. “Implemented scope” describes specific development work; it is not unrestricted production availability.
Defined masters, opening stock and party balances, with mapping and review. Other ERP adapters and full historical migration are not established as supported.
Pilot-core purchasing, sales, batch and stock workflows. Exact document and operational scope must be agreed.
Linked journals, settlements and party balances. This does not mean every accounting statement is complete.
Permissioned audit explorer and defined correction workflows. Full event coverage, exports and retention are separate requirements.
Production hardening, LAN/TLS deployment, recovery evidence and customer acceptance remain release gates.
Broader financial reporting and statutory outputs are unfinished. No direct filing availability is implied.
No. ERP has its own transaction-linked accounting core. Ledger is a separate product for businesses that want to keep another ERP.
No. Defined development slices are implemented, but deployment, recovery and customer acceptance gates remain. Broader statements and statutory outputs also need completion.
