Purchase requisitions raised by any team, approved by the rules you configure, converted to purchase orders against registered vendors, and received against delivery — so spending is decided before the money leaves, not explained after.
Why it exists
Procurement software gives buying a paper trail before the money leaves, not after. In Kuzhu a need becomes a requisition — what, how many, why, for which cost centre — that routes through approval before anyone talks to a vendor. Approved requisitions become purchase orders against vendors you maintain, with agreed prices and delivery expectations, and receipts record what actually arrived against what was ordered.
The approval is the point. Maker–checker on spending is the control every auditor asks about first, and here it is the same workflow engine the rest of the platform uses: chains by amount, by category, by cost centre — a ₹5,000 stationery order and a ₹5 lakh equipment purchase take appropriately different paths without anyone remembering to escalate.
Because procurement lives beside assets and finance, the loop closes: goods received can become tracked assets with warranties and assignment; vendor invoices reconcile against POs and receipts — the classic three-way match — before payment is recommended. The spend report by category, vendor and cost centre is a query, not a quarterly archaeology project.
The outcome
“Every purchase has an approval that happened before the purchase.”
Feature by feature
Start
01
Requisitions with budgets and justification, routed by amount
02
Vendor registry with terms and history
03
Purchase orders generated from approved requisitions
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
Vendors with GSTINs, contacts, categories and payment terms — one list, with the history of what each has supplied.
What is needed, for which cost centre, with justification. Requesters see status instead of asking purchasing.
Chains route by amount and category. The ₹5,000 order and the ₹5 lakh one take different paths automatically.
Approved requisitions become POs; receipts record quantities and condition against them — shortfalls visible immediately.
Vendor invoices match against PO and receipt; received equipment can flow straight into asset tracking.
Worth a closer look
Buyer questions
2 answers
The answer
The invoice that arrives is compared with the order that was placed and the goods that arrived — quantity and rate. Matches proceed; mismatches are flagged with the specific line that disagrees. This one habit is where procurement fraud goes to die, and it costs a click here rather than a reconciliation afternoon.
The answer
Every requisition and order carries a cost centre from your structure, so departmental spend is attributed at the moment of commitment, not allocated by argument at quarter end. Budget owners see their committed and received spend in the report, which changes the tone of the next budget meeting.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Yes — chains route by amount bands, category and cost centre, so bigger spends automatically climb higher.
Yes. Receipts record what arrived; a PO can receive in parts and shows the open balance until fulfilled or closed.
The vendor invoice is matched against the PO and the receipts — the three-way match — with mismatched lines flagged for a human decision.
Yes — equipment from a receipt can flow directly into asset management with vendor, cost and warranty carried over.
Spend by vendor, category, cost centre and period; open orders; and the exception list of mismatches and overdue deliveries.
Works best beside
Other money modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
WhatsApp us
WhatsApp us