ERP · EasySol CSV migration
Defined masters, opening stock and party balances, with mapping and review. Other ERP adapters and full historical migration are not established as supported.
Product availability
Know what the next step actually includes.
Kramvia products are being introduced through development and scoped evaluation. This page distinguishes an enquiry, a controlled pilot discussion and future capabilities so you can plan with accurate expectations.
CURRENT PRODUCT SCOPE
What is implemented. What still needs work.
Reviewed 22 September 2026. “Implemented scope” describes specific development work; it is not unrestricted production availability.
ERP · Pharmacy operations
Pilot-core purchasing, sales, batch and stock workflows. Exact document and operational scope must be agreed.
ERP · Transaction accounting
Linked journals, settlements and party balances. This does not mean every accounting statement is complete.
ERP · Audit review and corrections
Permissioned audit explorer and defined correction workflows. Full event coverage, exports and retention are separate requirements.
ERP · Deployment and customer acceptance
Production hardening, LAN/TLS deployment, recovery evidence and customer acceptance remain release gates.
ERP · Financial statements, GST returns and bank reconciliation integration
Broader financial reporting and statutory outputs are unfinished. No direct filing availability is implied.
Ledger · Standalone imports and reconciliation
Development workflows use ledger exports and bank statements. Production use and source compatibility still require validation.
Ledger · Broader accounting reports and GST filing
Reporting completeness, required integrations and authorisation must be established before availability is claimed.
Kramvia ERP: controlled pilot enquiries
The ERP has implemented pilot-core operations, transaction-linked accounting, an audit explorer and a controlled EasySol CSV import path. Production deployment and customer acceptance gates remain. Broader accounting statements, GST returns and bank reconciliation integration are unfinished.
- Agree the exact migration entities and supported source format.
- Evaluate operational, accounting and audit-review workflows together.
- Do not treat code implementation as unrestricted production readiness.
Kramvia Ledger: development and validation
Ledger is being developed around financial imports and reconciliation. Accounting reports and GST workflows require further validated functionality and, where applicable, external integrations and authorisation.
- Confirm export compatibility using representative samples.
- Evaluate reconciliation rules before relying on results.
- Treat direct GST filing and broader reporting as development scope.
Connections and scope must be confirmed
There is no automatic ERP–Ledger integration currently available. Bank connections, external services and new file formats require their own implementation and validation work.
- Do not assume an existing bank-feed connection.
- Confirm supported source formats and operating requirements.
- Agree any future integration separately when it becomes available.
What to bring to the discussion
- The product and workflow you want to evaluate.
- The dependencies you would need for real business use.
- The checks needed before expanding a pilot.