Shasvatm

Module catalogue

Fifteen modules. One transaction backbone.

Coverage grows from Community through B1 to Enterprise on the same platform — you do not rebuild your ERP to add finance, workflow or budget control.

Filter by edition, or by the part of the business you are fixing

Every module carries the same masters, approval engine and audit trail, so the question is never whether two of them will talk to each other. It is only which ones you switch on first.

Edition

B1 includes 12 of 15 modules. The rest stay visible so the growth path is honest.

Admin & Control

Available in Community, B1, Enterprise.

Users, roles, masters, approval rules and a full audit trail across the organisation.

Procurement

Available in Community, B1, Enterprise.

Indent, enquiry, vendor comparison, purchase order and rate contract — with project, approval and budget context before the commitment.

Stores & Inventory

Available in Community, B1, Enterprise.

Gate in, GRN with quantity and quality validation, issue, internal transfer, returns and multi-location stock tied to the project.

Client Billing

Available in Community, B1, Enterprise.

BOQ-based claim and RA-style billing: claim bill, certification, proforma, tax invoice and receipt tied to the project and contract.

Subcontract

Available in Community, B1, Enterprise.

Work order, work-done certification, retention and subcontractor billing on one workflow.

Finance

Available in B1, Enterprise.

GL, payables, receivables, project accounting, GST, e-invoice and e-way bill on the operational backbone.

Mobile Operations

Available in B1, Enterprise.

Approvals, indent, GRN, issue, transfer and gate in/out from a phone — same workflow as head office.

Budget & Budgetary Control

Available in Enterprise.

Project budgets by cost head and BOQ, commitment checks, variance and overrun governance.

Editions differ in more than module count — companies, workflow, attachments, users and hosting change too. Compare editions in detail →

How organisations actually start

Nobody switches on fifteen modules on day one

A phased start is the norm, and the backbone is what makes it safe: the second phase inherits the masters, approval rules and history created by the first.

Phase one

The cycle that is leaking

Usually procurement and stores — indent, order, gate in, GRN and issue. It is where uncontrolled commitment turns into cost, and it produces data everything else needs.

Phase two

The money side

Client billing and subcontract, then finance. Certified value, invoices and payables sit on transactions that are already trustworthy because phase one created them.

Phase three

Control and coverage

Budget control, plant, quality, safety, planning and payroll — added when the organisation is ready to be measured against them, not before.

See how an implementation runs →

Next step

Tell us how you buy, store, bill and approve today.

Module lists do not decide anything on their own. What decides it is whether your indent limits, approval levels and billing terms fit — so we map coverage to Community, B1 or Enterprise against your processes, not a checklist.

  1. 1

    You send a note

    Two lines on your projects and where control leaks today. No form marathon — the optional fields exist only to make the first call sharper.

  2. 2

    A 20–40 minute walkthrough

    We narrate the Procurement to Pay cycle against how you actually work. It is your process on the screen, not a feature tour.

  3. 3

    A written recap

    Scope, edition fit and what a sensible first phase would cover — in writing, so you can circulate it internally.

Get a coverage map

We will come back with which modules you need in phase one and which can wait.

Request a walkthrough

No obligation and no procurement process to start a conversation. If the fit is wrong we will say so on the first call.