Automated purchase order processing means the purchase order, the goods receipt note (GRN), the supplier's bill and the payment are linked by software, so nobody has to retype a document or hunt for the one it belongs to. In Indian practice that chain usually lives in Tally or an ERP: a Purchase Order voucher, a Receipt Note when goods arrive, a Purchase voucher when the bill is booked, and a Payment voucher when the supplier is paid. Automation helps most at the two points where people lose time: getting the supplier's bill into the books, and checking it against what was ordered and received.
This guide walks through each stage with a worked example, shows how TallyPrime links the documents, and is clear about which parts TaskAutomate handles today and which it does not.
The four documents in an Indian PO cycle
| Stage | Document | Who creates it | In TallyPrime |
|---|---|---|---|
| 1. Order | Purchase order (PO) | Buyer's purchase team | Purchase Order voucher (an order voucher) |
| 2. Receipt | Goods receipt note (GRN) | Buyer's stores or site | Receipt Note voucher (an inventory voucher) |
| 3. Billing | Supplier's tax invoice | Supplier | Purchase voucher (F9) |
| 4. Payment | Payment advice or bank transfer | Buyer's accounts team | Payment voucher (F5), often with TDS |
Most of the waste in a manual PO process is not in any single document. It is in the gaps between them: the bill that arrives on WhatsApp and sits in someone's phone, the GRN that was written on paper at the site and never entered, the PO number nobody wrote on the invoice.
How TallyPrime links PO, receipt and purchase
Tally has had order processing for a long time, and it is worth using before you buy anything else. According to TallyHelp's purchase order guide, you record a PO from Alt+G (Go To), Create Voucher, F10 (Other Vouchers), Purchase Order, entering the supplier, an Order No., the stock items, quantities and due dates. When you later book the purchase, setting Provide Order Details to Yes (F12 Configure) lets you pick the open PO, so quantities and rates carry across.
The receipt side runs on tracking numbers. Once Use tracking numbers is turned on under F11 Features, a Receipt Note carries a tracking number, and a Purchase voucher entered with the same tracking number is matched to it. TallyHelp's Purchase Bills Pending report then sorts everything into three buckets:
- Goods Received but Bills Not Received: a Receipt Note exists, the supplier's bill has not been booked.
- Bills Received but Goods Not Received: the bill is booked, the Receipt Note is missing.
- Cleared Purchase Bills: both exist and match.
A worked example
A Bengaluru manufacturer (GSTIN starting 29, Karnataka) orders components from a supplier in Pune (GSTIN starting 27, Maharashtra). The supply is inter-state, so the bill should carry IGST, not CGST and SGST. All figures below are illustrative.
| Quantity | Rate (₹) | Taxable (₹) | IGST 18% (₹) | Total (₹) | |
|---|---|---|---|---|---|
| Purchase order PO-0412 | 1,000 | 120 | 1,20,000 | 21,600 | 1,41,600 |
| Receipt note (GRN) | 950 received, 50 short | ||||
| Supplier's invoice as sent | 1,000 | 122 | 1,22,000 | 21,960 | 1,43,960 |
| What should be paid | 950 | 120 | 1,14,000 | 20,520 | 1,34,520 |
The fix is a conversation with the supplier, usually ending in a credit note or a revised invoice, and only then booking the Purchase voucher for the corrected amount and paying it with a Payment voucher (F5). If the payment attracts TDS, that is deducted at the payment or booking stage as your CA advises.
For the detailed rules on tolerances, partial deliveries and what to do with each type of mismatch, see our guide to 3-way matching of PO, GRN and invoice. This post stays on the overall flow.
Which steps can actually be automated
PO process automation is a set of separate jobs, and different tools do different ones. Splitting them makes buying decisions easier.
- Raising the PO. Tally, an ERP or a procurement tool can create POs from a template, route them for approval and send them to the supplier. If you raise POs in Excel today, moving them into Tally's Purchase Order voucher is the cheapest first step.
- Recording the GRN. The stores team enters a Receipt Note against the PO when goods arrive. This is mostly discipline, not software: the GRN has to be entered the day goods come in, or the matching downstream has nothing to match against.
- Capturing the supplier's bill. Bills arrive as PDFs, photos, scans and WhatsApp forwards. Reading the supplier, GSTIN, invoice number, line items, quantities, rates and tax split off each one is the most repetitive step in the cycle, and it is where AI bill reading saves the most hours.
- Checking GST on the bill. Is the buyer GSTIN yours? Is it IGST for an inter-state supplier and CGST plus SGST for a same-state one? Do the line totals and tax add up to the grand total? These checks are mechanical and should never depend on someone remembering to do them.
- Matching the bill to the PO and GRN. Compare quantity and rate on the bill with the PO and the Receipt Note, and hold anything outside tolerance.
- Approving and booking. A person approves, and the Purchase voucher is posted to the books.
- Paying. Due dates are tracked and Payment vouchers are raised, often in a weekly payment run.
A practical PO matching routine without new software
If you are not ready for a dedicated PO matching tool, this routine catches most errors:
- Ask suppliers to print your PO number on every invoice. Put it in the PO terms.
- Enter Receipt Notes the same day goods arrive, with the PO number and a tracking number.
- Book Purchase vouchers only against an existing tracking number. A bill with no Receipt Note goes into a hold folder.
- Run Purchase Bills Pending every week. Chase every line in Goods Received but Bills Not Received (bills you are missing, and ITC you cannot yet claim) and every line in Bills Received but Goods Not Received (possible over-billing).
- Run Purchase Orders (Due Only) monthly and pre-close POs that will never be delivered, so stale orders do not hide real ones.
Where TaskAutomate fits today
TaskAutomate does not link invoices to purchase orders or match them yet. It does not read your POs or Receipt Notes from Tally, and it will not flag the ₹9,440 difference in the example above on its own. That matching stays in Tally, your ERP or a person's review.
What it handles is the bill side of the cycle, steps 3, 4 and 6 above:
- Suppliers' bills come in on WhatsApp or by upload, and the AI reads the vendor, GSTINs, invoice number, every line item with quantity and rate, the CGST, SGST or IGST split and the totals. If you add a PO number field to a template, it is read off every bill too, so the PO reference sits on the record for whoever reviews it.
- Seven GST checks run on each bill, including whether the buyer GSTIN is yours, whether IGST or CGST plus SGST is right for the supplier's state, and whether subtotal plus tax equals the total.
- A person reviews each entry beside the original bill and approves it. Nothing posts without that approval.
- The Tally Bridge posts the approved voucher into TallyPrime or Tally ERP 9, or you export to Excel or CSV for matching in your ERP.