NetSuite Procurement and Purchase-to-Pay for India

NetSuite procurement covers the full purchase-to-pay cycle: purchase requisitions, vendor selection, purchase orders, NetSuite inventory management receipt, vendor bills, and payment. For Indian companies managing 50 to 500 vendors across multiple locations, this structured procurement workflow prevents unauthorised spending and ensures three-way matching.

Purchase Requisitions

Employees create purchase requisitions for items they need. The requisition goes through an approval chain based on amount and department. Once approved, the purchasing team converts the requisition into a purchase order. This prevents direct vendor contact by non-purchasing staff and creates an audit trail of who requested what.

Vendor Management

Each vendor in NetSuite has a comprehensive record: contact details, GSTIN, PAN, payment terms, default TDS section, bank details, and performance history. Rate vendors on delivery reliability and quality. Use vendor ratings when selecting between multiple suppliers for the same item.

Three-Way Matching

NetSuite’s three-way matching compares: (1) the purchase order, (2) the goods receipt, and (3) the vendor bill. All three must align on quantity, rate, and total before the bill is approved for payment. Discrepancies are flagged for review. This is fundamental procurement discipline that prevents paying for goods not ordered or not received.

Approval Workflows

Configure multi-level approval workflows based on PO amount, department, or item category. Common Indian setup: POs under Rs. 50,000 approved by department head, Rs. 50,000 to Rs. 5 lakh by procurement manager, above Rs. 5 lakh by CFO or director. All approvals are logged with timestamps.

Vendor Payments and TDS

When a vendor bill is approved, it enters the accounts payable automations queue. Process payments via EFT/NEFT batch, printing cheques, or manual bank transfer. NetSuite deducts TDS at the configured rate for each vendor and tracks the liability for quarterly filing.

For a complete walkthrough of the full process, see our NetSuite ERP implementation guide.

The Purchase Requisition to Purchase Order Workflow

In NetSuite, the procure-to-pay process starts with a Purchase Requisition. A team member submits a requisition (a request to buy something), a manager approves it, and the procurement team converts the approved requisition into a Purchase Order sent to the vendor. This approval layer prevents unauthorised spending and creates an audit trail that Indian finance teams need for internal controls.

To enable the PR-to-PO flow, go to Setup > Accounting > Accounting Preferences and enable Purchase Requisitions. Once enabled, users see a Requisition option under Transactions > Purchases. The requisition form captures the requested item, quantity, preferred vendor, and estimated amount. Approval routing is configured under Setup > Workflow, where you define who approves requisitions above a certain threshold.

Once approved, the procurement team opens the requisition and clicks Create Purchase Order. NetSuite pre-fills the PO with the requisition details. The buyer adds the confirmed vendor terms, currency, and delivery address before sending the PO to the vendor.

Three-Way Matching and Item Receipt

NetSuite’s three-way matching connects the Purchase Order, Item Receipt (goods receipt note), and Vendor Bill. When goods arrive, the warehouse team creates an Item Receipt against the open PO. The receipt records the actual quantities delivered. When the vendor sends their invoice, the accounts team creates a Vendor Bill linked to the PO. NetSuite automatically compares the billed quantity and rate against the PO and the receipt.

Discrepancies between the PO, receipt, and bill are highlighted in the bill record. Common discrepancies in Indian procurement include price variance (vendor billed at a rate different from the PO), quantity variance (fewer goods received than invoiced), and tax discrepancy (different GST rate applied). NetSuite requires explicit approval from a designated approver before a bill with discrepancies can be posted to the accounts.

Vendor Management and Indian Tax Compliance

NetSuite maintains a Vendor master record with fields for GSTIN, PAN, bank account details for NEFT/RTGS payments, and TDS section mapping. When a vendor is set up with a TDS section (194C for contractors, 194J for professionals), NetSuite automatically calculates and withholds TDS on every bill from that vendor. The deducted TDS is tracked in a liability account until you make the challan payment to the government and file Form 26Q.

For import procurement, NetSuite handles foreign currency POs and bills. The exchange rate at the time of the PO is recorded, and any rate difference at the time of payment creates an exchange gain or loss entry automatically. Custom duty and IGST on imports can be captured as landed cost elements and added to the item’s average cost in inventory.

Frequently Asked Questions