Purchase management software with GST & ITC
Run procurement end to end — purchase orders, goods receipt, GST purchase bills, supplier ledgers and ITC — with reorder suggestions, all offline.
Live product UI — sample data.
PO to bill
Raise POs, receive goods, and convert to GST purchase bills without re-entry.
Suppliers & ITC
Supplier-wise ledgers and outstanding, with GST input credit and GSTR-2B reconciliation.
Buy smarter
Reorder suggestions from stock and demand, with preferred-supplier hints.
What this actually means in practice
Buying is a cycle, not a document. Someone asks for something and says why; the request is approved against a budget; an order goes out; goods arrive and are counted at the gate; and only then does a supplier's bill get paid. Most small firms skip the first step, which is precisely where control lives — without a requisition, nobody can answer later who asked for the item or on whose authority.
The three-way match is the discipline at the end. LekhaPro compares each line across the order, the goods receipt and the supplier's invoice: quantity billed against quantity received, rate billed against rate ordered, each within a tolerance you set in basis points. Any line outside tolerance makes the whole match an exception, and an exception routes for approval rather than posting itself — which is the entire point of the control.
Goods received without a bill are still a liability, so the gap between receipt and invoice is held in a goods-received/invoice-received clearing account until the bill lands and clears it. Input credit is a separate test again: a matched, posted bill still has to appear in your GSTR-2B before the credit is safe, which is why reconciliation flags credit at risk rather than assuming the supplier has filed.
| Where the three documents disagree | What it usually means | What should happen next |
|---|---|---|
| Received more than ordered | Over-supply, or a part shipment counted twice | Accept within tolerance or return; never bill the excess |
| Billed more than received | Short supply invoiced in full, or a receipt not yet entered | Hold the bill until the receipt is posted or a credit note arrives |
| Rate billed above the ordered rate | A price revision never amended onto the order | Route for approval; amend the order or seek a credit note |
| Received, never billed | Supplier's invoice pending — a liability missing from your books | Leave it in GR/IR clearing and chase the bill before period close |
| Billed, never ordered | Off-process buying, or the wrong entity billed | Reject, or regularise with a retrospective order |
| Matched, but absent from GSTR-2B | Supplier has not filed, or used a wrong GSTIN | Flag as credit at risk and take it up with the supplier |
What’s included
- Purchase orders & GRN
- GST purchase bills
- Supplier ledgers & outstanding
- ITC & GSTR-2B reconciliation
- Reorder suggestions
- Landed-cost & schemes
- Offline-first
What it does not do
- · A variance is raised for a human to decide: LekhaPro will not auto-approve an exception, auto-write-off a shortfall, or post a mismatched bill.
- · Suppliers do not log in and submit invoices themselves — the vendor portal today is a staff-side preview of what a supplier would see; EDI, GeM and reverse-auction connectors are not built.
- · No payroll module, and there is no automated Tally import — Tally XML export is available, but transaction history does not come in.
Frequently asked
Does it reconcile purchases with GSTR-2B?
Yes — GSTR-2B reconciliation and ITC-at-risk are built in, all offline.
Can I convert a PO to a bill?
Yes — receive goods against a PO and convert to a GST purchase bill in one step.
Is it offline?
Yes — procurement, stock and GST run offline.
What does a three-way match actually compare?
Three sources, line by line: the purchase order, the goods receipt note and the supplier's invoice. Quantity billed is tested against quantity received, and the invoiced rate against the ordered rate, each within a tolerance expressed in basis points. If any line breaches its tolerance the whole match becomes an exception and routes for approval instead of posting.
Why is a requisition worth raising if I already issue purchase orders?
Because the order records what was bought, and the requisition records who asked and why. Without it, budget ownership, approval authority and the business reason for a spend all live in somebody's inbox. With it, the chain runs requisition to order to receipt to bill, and every stage can be answered from the books rather than reconstructed after a query.
What exactly is included in Purchase · procurement?
purchase orders & GRN, GST purchase bills, supplier ledgers & outstanding, ITC & GSTR-2B reconciliation, reorder suggestions and landed-cost & schemes, and 1 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is purchase · procurement handled differently here?
It rests on PO to bill, suppliers & ITC and buy smarter. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does Purchase · procurement post to the real books?
Yes, and that is the whole reason it lives in this product rather than beside it. What PO to bill records lands in the same posted double-entry ledger the Trial Balance, P&L and GST returns are built from — so there is no second set of purchase · procurement numbers to reconcile against the first.
Does Purchase · procurement cost extra?
No. Purchase · procurement is part of the accounting core rather than a paid add-on, so suppliers & ITC is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try Purchase · procurement before committing?
Yes — 14 days, no card. Test purchase · procurement against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.