Skip to content

Product questions

Answers before you plan your next step.

These answers explain how Kramvia products fit together and what to confirm before sharing data or planning an evaluation.

Does ERP include accounting, or is Ledger required?

ERP includes its own transaction-linked accounting core and audit-review controls. Ledger is a standalone accounting product for teams that retain another ERP, not a required add-on for ERP accounting. Broader reporting and statutory outputs need separate release validation.

  • Choose ERP when switching the wider business workflow.
  • Choose Ledger when keeping the existing operational system.
  • No shared database, automatic integration or bundled licence is implied.

Can we keep our current software?

Ledger is being designed around imported records, so replacement of an operational ERP is not the intended requirement. Actual compatibility still depends on the exports your system provides. ERP evaluation involves a separate workflow and migration discussion.

  • List the report names and formats available today.
  • Check whether the needed fields are included in the export.
  • Do not assume automatic synchronisation between systems.

Will every format and bank be supported?

No universal compatibility claim is made. Different ledgers and statements need explicit mappings and validation. Uploading a statement is also different from connecting a live bank feed.

  • Identify the account, period and amount convention.
  • Check a representative sample before relying on an import.
  • Confirm availability of any external connection separately.

Can we use GST filing and accounting reports now?

Broader accounting, Profit & Loss and GST workflows remain in development. Reliable reporting needs complete and correctly classified records; direct filing additionally needs the required integrations and authorisation.

  • Use availability information to distinguish plans from current scope.
  • Discuss the records and review controls your team needs.
  • Do not use a prototype or fictional workspace for live filing.

Can every old ERP and all historical data be migrated?

Not currently. The implemented migration path is an EasySol CSV adapter for defined master records, opening stock and party opening balances. Every additional source or historical entity needs its own mapping, validation and acceptance evidence.

  • Confirm source software/version, export formats and entity scope.
  • Review duplicate and invalid rows before applying records.
  • Agree counts, stock totals, balances and exclusions before cutover.

What to bring to the discussion

  • A concrete workflow question rather than sensitive attachments.
  • Your current system and available export types.
  • The capability you need confirmed before an evaluation.
Discuss your requirements