Skip to content
KramviaTECHNOLOGIESTalk to us

Accounting teams

Keep the source close to the decision.

Kramvia supports two product directions for accounting teams: transaction-linked accounting and audit review inside ERP, or standalone Ledger for businesses keeping their existing ERP. Choose by where your records are created and whether the business wants to migrate.

FOLLOW THE WORKFLOW

See how the work fits together.

  1. Confirm source and period
  2. Review interpretation
  3. Match supported movements
  4. Investigate differences
  5. Retain review evidence

FICTIONAL WORKFLOW EXAMPLE

A payment difference that should remain visible

A fictional ledger shows ₹10,000 while a bank record shows ₹9,950. The team should investigate the ₹50 difference instead of silently treating both amounts as equal. A fee is one possible explanation, not an automatic conclusion.

In ERP, review supported transaction-linked accounting and audit records. With another ERP retained, use the Ledger discussion to assess export-based reconciliation.

Choose the source of your accounting records

When the business adopts Kramvia ERP, supported operational postings and settlements link to the ERP accounting core. When it retains another ERP, Ledger begins with reviewed financial exports. These are different entry routes, not a requirement to use both products.

  • ERP: review the accounting effect of supported business transactions.
  • Ledger: map exported records and reconcile bank statements.
  • Confirm the release scope of reporting, filing and integrations independently.

Agree the interpretation of source data

A reliable review begins with the period, ledger purpose and sign convention. Opening balances, subtotals and repeated headers should not silently become ordinary transactions.

  • Identify the ledger account and reporting period.
  • Validate field mappings against representative rows.
  • Compare record counts and totals with the source export.

Review allocation across accounts

A receipt may arrive in more than one bank account or remain partially settled. The accounting view must preserve the amount already allocated when another statement is selected.

  • Keep original and remaining amounts visible.
  • Investigate duplicate imports before matching.
  • Require an explicit review when a completed allocation is reversed.

Separate matching from accounting conclusions

A match explains a payment movement; it does not independently establish the correct ledger classification, tax treatment or complete financial result.

  • Keep unmatched differences available for follow-up.
  • Retain references to supporting documents.
  • Confirm reporting and GST availability before using the product for those tasks.

Questions about this workflow

Can a bank match prove the correct accounting treatment?

No. Matching explains a movement; classification, tax treatment and reporting completeness require their own review.

What to bring to the discussion

  • Your source ledger types and statement formats.
  • Your period-end review and correction process.
  • The roles responsible for preparation and final review.
Discuss your requirements