Skip to content
KramviaTECHNOLOGIESTalk to us

ERP accounting & audit review

Operational records with a financial trail.

Accounting is part of Kramvia ERP. Its implemented core links supported business transactions and settlements to journal entries and party balances, with permissioned audit review and controlled corrections. Standalone Ledger is a separate choice for businesses keeping their current ERP.

FOLLOW THE WORKFLOW

See how the work fits together.

  1. Post a supported transaction
  2. Inspect its journal & balance
  3. Review recorded activity
  4. Request a controlled correction

FICTIONAL WORKFLOW EXAMPLE

Correct the record without hiding the original

A fictional team identifies an incorrect settlement. The supported correction workflow records a reason, checks the approver’s authority and prevents the requester from approving their own correction. A separate correcting entry retains the relationship to the original.

This supports investigation and review. It is not an automated audit opinion, fraud guarantee or statutory certification.

Link a transaction to its accounting effect

Supported operational postings and settlements create linked, balanced journal entries in the ERP core. This lets a reviewer connect the business document with its financial record rather than treating accounting as an unrelated export-only task.

  • Supported purchases, sales, returns and settlements retain source links.
  • Review open items and customer/supplier balances in the supported scope.
  • Agree the applicable workflow and acceptance checks for the pilot.

Keep corrections separate from the original

Posted journal records are append-only in the implemented core. Supported commercial adjustments and settlement corrections retain their own records rather than silently replacing an earlier entry.

  • Retain a documented reason for a correction.
  • Enforce relevant permissions and approval rules.
  • The requester cannot approve their own settlement correction.

Give authorised reviewers a record of activity

The audit explorer provides permissioned access to redacted activity records. Supported events and corrections can be investigated within their distributor/location scope. This helps review; it is not an automated audit opinion or certification.

  • Restrict audit access through enforced permissions.
  • Preserve supported activity records against ordinary update/delete operations.
  • Confirm event coverage, export and retention needs separately.

Distinguish the accounting core from the complete release

The implemented journal, settlement and audit slices do not mean every report or statutory workflow is finished. Broader accounting statements, GST returns and bank reconciliation integration remain development work, alongside production acceptance.

  • Confirm which reports are available for the agreed evaluation.
  • Do not assume direct GST filing or completed P&L functionality.
  • Use professional accounting review where the business requires it.

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.

Implemented scope

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.

Implemented scope

Pharmacy operations

Pilot-core purchasing, sales, batch and stock workflows. Exact document and operational scope must be agreed.

Implemented scope

Transaction accounting

Linked journals, settlements and party balances. This does not mean every accounting statement is complete.

Implemented scope

Audit review and corrections

Permissioned audit explorer and defined correction workflows. Full event coverage, exports and retention are separate requirements.

Validation remaining

Deployment and customer acceptance

Production hardening, LAN/TLS deployment, recovery evidence and customer acceptance remain release gates.

In development

Financial statements, GST returns and bank reconciliation integration

Broader financial reporting and statutory outputs are unfinished. No direct filing availability is implied.

View all product availability →

Questions about accounting and audit review

Are accounting entries and financial statements the same thing?

No. Entries record financial effects. Statements such as Profit & Loss need complete, correctly classified records and a validated reporting layer; broader statements remain unfinished.

Does audit review replace our accountant or auditor?

No. Activity records and correction history support professional review; they do not establish an independent audit opinion.

What to bring to the discussion

  • Transactions and settlements the team needs to review.
  • Correction scenarios and who can request or approve them.
  • Required statements, audit outputs and release dependencies.
Discuss your requirements