Executive / leadership
Management visibility, finance, project commercial control
See leakage and exceptions across projects before month-end spreadsheets.
“What requires a decision today across active sites?”
Platform
One platform across the project lifecycle
Six capability areas, fifteen modules, one set of masters and one approval engine. Every transaction stays connected to the project, the user, the approval path and the financial impact.
Shasvatm Control Tower
Nine operational domains. One set of masters, one approval engine.
Project & Planning
Setup · BOQ / Job · Planning · Budget · Progress
Procurement
Indent · Enquiry · Comparison · PO · Rate contract
Stores & Inventory
GRN · Issue · Transfer · Stock · Gate
Subcontract
Work order · Work done · Subcontract bill
Client Billing
RA billing · BOQ billing · WIP
Plant & Machinery
Hire · Logs · Working / idle / breakdown
Finance
GL · AP / AR · Project finance · Reporting
Quality & Safety
Quality workflows · Safety workflows
Admin & Control
Users · Roles · Approvals · Masters · Audit
Every transaction remains connected to the project, user, approval path and financial impact.
Capability areas
Six areas. Pick the one that is costing you money.
Each area opens with the question a buyer is actually asking, and each page behind it is something you can operate — a cycle to walk, an engine to route a transaction through, a number to trace back to its source.
The question it settles
“Can we stop a commitment before it becomes a cost?”
Indent, enquiry, comparison, purchase order, gate-in and GRN, then vendor bill and payment — with budget, approval, vendor and project context on every hop. Stores still issue and transfer after receipt; the money thread does not stop at the store.
- Central procurement with project visibility, or project-specific buying
- Rate contracts, vendor comparison and configurable approvals
- Gate-in, GRN with quantity and quality validation, then issue and transfer
- Vendor bill against the PO and GRN — GST and e-invoice on B1 / Enterprise
- Payment and project accounting on the same operational backbone
- Classification, budget-linked controls and a full audit trail throughout
Budget, approval, vendor and project context sit on every hop — so the control happens at the indent, not at the invoice.
Waiting on that page: A clickable six-hop cycle, indent to payment
Walk the P2P cycle →Module map
Fifteen modules, and what your edition includes
Switch the edition to see what is in scope. Select any module for what it covers. Nothing here is a bolt-on — the modules share the same masters, approvals and audit trail.
Show me:
Procurement
In B1Indent, enquiry, vendor comparison, purchase order and rate contract — with project, approval and budget context before the commitment.
Modules outside the selected edition stay visible on purpose. Most organisations start with the cycle that hurts most and grow into the rest — the backbone does not change when they do.
Roles on the backbone
Navigation in the product is role-aware. These are the jobs the Control Tower is built to support — mapped to modules in the 2026 profile.
Project manager
Planning, procurement status, subcontract progress, site issues
Keep plan, indents, work-done and billing on one project spine.
“Which activities need attention across this project?”
Procurement / commercial
Indent, enquiry, comparison, PO, rate contract, approvals
Commit only with project, vendor and budget context already on the transaction.
“Which requirements and orders are pending, and where is approval stuck?”
Stores / logistics
Gate, GRN, stock, issue, transfer, returns
Keep site stock tied to the project — not a parallel register.
“Where is material, and what is moving between projects?”
Commercial / billing
BOQ, RA / client billing, subcontract bills, retention, WIP
Bill from execution and quantities, not from a disconnected workbook.
“Where do subcontract bills, client RA bills and WIP stand?”
Finance / accounts
GL, AP/AR, project accounting, GST, e-invoice, e-way bill
Post the financial impact of the operational transaction on the same backbone.
“What is the project-level financial position from live transactions?”
Site / mobile user
Approvals, indent, GRN, issue, transfer, gate in/out
Transact from the site on the same workflow and audit trail as head office.
“Can this be raised or approved without waiting for a desktop?”
IT / admin
Users, roles, masters, approval engine, audit trail
Encode organisational authority in the system so people do not route around it.
“Does approval in the ERP match how the company actually signs?”
Next step
You have seen the mechanism. The useful part is seeing it against your data.
A walkthrough is worth more than a brochure because your indents, your approval levels and your billing terms are the things that decide whether this fits. Here is exactly what happens if you ask.
- 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
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
A written recap
Scope, edition fit and what a sensible first phase would cover — in writing, so you can circulate it internally.
Start where it hurts
Tell us which cycle is leaking and we will lead with that one.
Request a walkthroughNo obligation and no procurement process to start a conversation. If the fit is wrong we will say so on the first call.