Control every rupee of spend, from request to payment.
A complete purchase-to-payment platform. Requests follow your real approval hierarchy, budgets are committed the moment a request is raised, and no invoice is paid until it matches both the order and what was actually delivered.
- Coverage
- Request → Payment
- Approvals
- Unlimited levels
- Matching
- Three-way
- Access
- Role & permission based
The process
Every stage, in one system
Nothing moves forward until the stage before it is genuinely complete.
Requests that route themselves
Staff raise a request against a department, category and cost type. It then follows the approval chain you defined, with limits applied per role, so nothing depends on someone remembering who signs off.
- Multi-level approval hierarchies with per-role spending limits
- Line-by-line quantities, discounts and tax
- Capital and operating expenditure classified per line
- Required fields, justification and supporting attachments
- Reject with reason, recall, and resubmit — all recorded
- Full approval timeline visible on every request
Budgets that commit, not just report
Most systems tell you that you overspent. This one prevents it. The moment a request is submitted, its value is committed against the budget and removed from what remains available — then converted to actual spend when the invoice arrives.
- Available = allocated − committed − spent, calculated live
- Commitment released automatically on rejection or recall
- Budget periods: monthly, quarterly, half-yearly or annual
- Separate capital and operating budgets per department
- Utilisation alerts at a threshold you set
- Requests checked against the budget before they can proceed
Competitive quotes, compared side by side
Turn an approved request into a quotation round, invite the suppliers you choose, and collect their bids in one place. Award the winner and the purchase order is created for you — priced to the bid, with the losing bids recorded for audit.
- Create a quotation request directly from an approved requisition
- Invite selected suppliers — only invitees can see or bid
- Submission deadlines enforced automatically
- Bids compared side by side, lowest highlighted
- Award converts straight to a purchase order at the awarded value
- Unsuccessful bids retained as evidence of a fair process
What you ordered is what you check in
Purchase orders carry your terms, delivery address and expected date. When goods arrive, receipt is recorded against the order line by line — and the system will not let you receive more than you ordered.
- Purchase orders with terms, delivery address and expected dates
- Suppliers can accept or decline, with a reason recorded
- Partial deliveries received against the same order
- Over-receipt blocked, not merely flagged
- Outstanding quantities visible on every order
- Branded order documents ready to send
Three-way matching, with a tolerance you set
Every supplier invoice is checked against the purchase order and the goods actually received. Small differences within your tolerance are flagged for review; anything beyond it is held as a discrepancy until someone resolves it.
- Invoice matched against both order and receipt
- Tolerance percentage configurable per organisation
- Within tolerance flagged for review, not silently accepted
- Duplicate invoice numbers rejected on entry
- Budget moves from committed to actual spend on match
- Payables ageing calculated on the outstanding balance
Your suppliers, off email
Invite a supplier and they get their own secure area. They set their own access code — you never see it, and never hold it. From there they quote, respond to orders and track what they are owed, without a single attachment going back and forth.
- Invitation-based access; suppliers set their own credentials
- Quotation requests visible only to invited suppliers
- Bid submission and revision before the deadline
- Accept or decline purchase orders with a note
- Invoice and payment status visible to the supplier
- Access revoked instantly, ending every active session
Also included
Everything around the process
The parts that make it usable day to day, and defensible at year end.
Payments
Record full or partial payments against an invoice. Overpayment is blocked, and status reflects reality — partly paid stays partly paid.
Multi-location
Run several properties or branches under one organisation. Users see only the locations they are assigned to, and budgets are held per location.
Roles & permissions
A reporting hierarchy for approvals, plus a permission matrix controlling exactly what each role may view, create, edit or delete.
Branded documents
Design your own order, quotation and payment documents — paper size, fonts, colours, columns, terms and logo — and set a default per document type.
Dashboards & reporting
Spend summaries, commitment against budget, payables ageing and cycle times — scoped so each role sees what is relevant to them.
Integration
Sync suppliers, items and bills with Zoho Books, and trigger your own systems on events such as approval, order or payment.
Common questions
Before you ask
Can it match our existing approval structure?
Yes. Approvals follow a reporting hierarchy you define, with a spending limit per role. A request escalates until it reaches someone whose limit covers it, so a 50,000 request and a 5,000,000 request take different paths automatically.
What happens if someone tries to spend beyond budget?
The request is checked against the remaining budget for that department and period before it can proceed. Committed amounts from requests already in flight are included, so two people cannot each consume the last of a budget at the same time.
Do our suppliers need to buy anything?
No. Supplier access is included. You invite them, they set their own access code, and they use it at no cost to either side.
Can we run more than one company or location?
Yes. Multiple locations are supported under one organisation, with users assigned to the locations they work in and budgets held separately per location.
How is our data kept separate from other clients?
Every record belongs to one organisation, and access is derived from the signed-in user's verified membership — not from anything the browser sends. There is no shared view across clients.
How long does implementation take?
It depends on how much of your process is already documented. Configuration is usually measured in days rather than months, followed by a pilot with a small group before wider rollout. We will give you a realistic estimate after the first conversation.
See it running on your own process.
We will walk through a live requisition, an approval, a quotation round and a matched invoice — using categories and limits that resemble yours, not a generic demo.