Requisition, quote comparison, and purchase orders — connected to specific BOQ line items, so every rupee spent traces back to what it was budgeted for.
A purchasing process disconnected from the BOQ makes it easy to lose track of whether spending on a given material or work category is still within budget until a much larger overrun surfaces. Rebota's procurement flow — requisition, RFQ/quote comparison, and purchase order — ties every PO back to a specific BOQ line, so budget-vs-actual for that line is visible as spending happens, not reconstructed later.
Vendor bank account numbers and IFSC codes are encrypted at the application layer (AES-256-GCM), the same standard applied to other sensitive financial fields in the platform. Access to manage vendor records follows a deliberate authority model: a plain project co-member gets no rights over another account's vendor data by default, but an owner can explicitly delegate management rights to a company-level admin or PM.
Contractors currently raising purchase orders without a structured link back to BOQ budget, making it hard to catch overspending on a specific line item until later.
A business with very low procurement volume or a single small project may not need structured RFQ/comparison workflows yet.
Large-scale procurement platforms with deep supplier-network marketplaces or advanced e-sourcing/auction functionality serve a different, higher-volume procurement need than most individual construction projects require.
Very low purchase-order volume can be tracked manually a while longer.
For connecting procurement spend directly to BOQ budget line by line, this closes a gap that a standalone or disconnected purchasing process typically leaves open.
Raise every purchase order against its BOQ line item at the time of purchase, not retroactively — the budget-vs-actual visibility this module provides depends on that discipline.
