All modules
Module · Purchase Orders

Order it. Approve it. Match the bill.

Raise a PO on a vendor with line items and GST, approve it, then link the vendor bills that fulfil it — so you always know what's been ordered versus billed.

ProcurementProject managersAccounts payableOwners approving spend
buildersitenow.com/purchase-orders
What's inside

Everything the purchase orders module ships with.

Line items with GST

Build the order with HSN and a per-line GST rate; the order total and tax are computed for you.

Approval lifecycle

Draft → approved → partial → closed (or cancelled). Approvals leave an audit trail.

Bill-against-PO

Link vendor bills to the PO; billed-vs-ordered updates automatically so nothing is over-billed.

Per-site orders

Tag a PO to a site so committed spend rolls into that project view.

Vendor-aware

Place of supply and GST split (CGST/SGST vs IGST) follow the vendor's state automatically.

Clean audit

Every create, edit, approve and cancel lands in the tenant audit log.

Where it earns its keep

What this looks like on a real site.

01

The vendor bills you for more steel than you ordered

Link the incoming bill to the purchase order and billed-versus-ordered updates on the spot. Over-billing stops being something you notice three months later while reconciling and becomes something the system flags while the bill is still in front of you. The order stays open at partial until it is genuinely fulfilled, then closes.

02

A supervisor commits ₹4 lakh of spend nobody approved

Orders move through draft to approved before they go out, and the approval is recorded against a person and a timestamp in the tenant audit log. For firms where the owner wants to see anything above a threshold before it is committed, this is the gate. Cancelled orders keep their history rather than disappearing.

03

You want to know what a site owes before the bills arrive

Tag orders to a site and committed spend rolls into that project view alongside actual billed cost. That is the difference between knowing what you have paid and knowing what you are already on the hook for — which is the number that matters when you are deciding whether a project still has room in its budget.

Common questions

Purchase Orders, answered.

Do I have to raise a PO for every purchase?

No. Purchase orders are optional and bills can be entered directly without one. Most builders use POs for the large, planned procurement — steel, cement, tiles, fittings — and enter small site purchases straight as bills. Both paths end up in the same vendor aging and the same project cost.

How is GST handled on an order?

Line items carry HSN and a per-line GST rate, and the order total and tax are computed for you. The split into CGST/SGST or IGST follows the vendor's place of supply automatically, so an order to an out-of-state supplier is taxed correctly without anyone remembering to change a setting.

What if a vendor delivers in several parts?

That is what the partial status is for. Link each bill as it arrives; the order tracks cumulative billed quantity against ordered quantity and stays partial until fulfilled. You can see at a glance which orders are still open and how much is outstanding on each.

Is there a record of who changed an order?

Every create, edit, approve and cancel lands in the tenant audit log with the user and the time. Purchase orders are where money gets committed, so the trail is not optional — it is the thing you go back to when a supplier and a supervisor remember the same conversation differently.

Pairs well with

Modules that connect to Purchase.

See Purchase Orders in action.

A 30-minute walkthrough with one of your sites loaded in.

Book a demo