Skip to content

Kramvia Ledger

Keep your ERP. Give financial work its own workspace.

Kramvia Ledger is our standalone accounting product for pharma businesses that do not want to replace their current ERP. It is being developed around supported ledger exports, bank statements and side-by-side reconciliation, with broader accounting reports and GST workflows still under development.

FOLLOW THE WORKFLOW

See how the work fits together.

  1. Keep your existing ERP
  2. Export supported financial records
  3. Map & review the import
  4. Compare bank statements
  5. Investigate remaining differences

FICTIONAL WORKFLOW EXAMPLE

Two banks, one outstanding receipt

Illustrative workflow: a ₹12,000 receipt is settled as ₹7,000 into one account and ₹5,000 into another. After allocating the first payment, only ₹5,000 should remain available when the user switches accounts.

The intended reconciliation rule preserves allocations across accounts. Source compatibility and production readiness must still be validated.

An independent choice, not a required ERP add-on

Your existing ERP can remain the operating system for purchases, stock and billing. Ledger works from supported exported financial records. Separately, Kramvia ERP has its own accounting core and audit-review controls.

  • Confirm your export formats before planning an import.
  • Do not assume a live connector or automatic synchronisation.
  • Choose Ledger for financial workflow improvement without an ERP migration.

Prepare records before matching

Two files can contain the same financial meaning while using different headings or layouts. Import preparation must make the interpretation visible before a user relies on the records.

  • Identify the ledger type, accounting period and source system.
  • Map dates, references, parties and debit or credit amounts.
  • Review opening balances, totals and rejected rows rather than assuming every line is a transaction.

Reconcile across bank accounts

The intended workspace keeps the ledger alongside the selected bank statement. Switching the bank must not reset what has already been allocated from the ledger.

  • Review full and partial allocations with the remaining amount visible.
  • Investigate duplicate imports and overlapping statement periods.
  • Keep unmatched records available for follow-up instead of forcing agreement.

Build accounting on validated records

Reconciliation is one part of accounting. Profit & Loss reporting and GST workflows also require correct classifications, complete records and appropriate review. These broader capabilities remain under development.

  • Do not treat a bank match as proof of tax treatment or expense classification.
  • Keep supporting source records close to review decisions.
  • Confirm availability and the supported workflow before planning production use.

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.

In development

Standalone imports and reconciliation

Development workflows use ledger exports and bank statements. Production use and source compatibility still require validation.

In development

Broader accounting reports and GST filing

Reporting completeness, required integrations and authorisation must be established before availability is claimed.

View all product availability →

Questions about this workflow

Does Ledger need a live ERP connection?

The starting approach uses supported exports. A live connector or automatic ERP synchronisation is not implied.

Can we continue billing in our current ERP?

Yes, that is the intended product choice: keep operational work in your ERP and bring supported financial exports into Ledger. Confirm formats and available scope before use.

What to bring to the discussion

  • A description of your ledger exports and bank statement formats.
  • Examples of partial payments, fees and transfers your team encounters.
  • The reports and review controls your accounting team needs.
Discuss your requirements