Blog
Why Are My Zoho Emails Going to Spam? Fix It With SPF, DKIM and DMARC
Find out why your Zoho emails go to spam and fix it fast by setting…
14 min read
Read article →
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.
To enable this requisition-to-PO flow, go to Setup > Accounting > Accounting Preferences and turn on Purchase Requisitions. Once enabled, a Requisition option appears under Transactions > Purchases. The requisition form captures the requested item, quantity, preferred vendor, and estimated amount, and approval routing is configured under Setup > Workflow, where you define who approves requisitions above a given threshold.
Once approved, the procurement team opens the requisition and clicks Create Purchase Order, and NetSuite pre-fills the PO with the requisition details. The buyer then adds the confirmed vendor terms, currency, and delivery address before sending the PO to the vendor.
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.
For import procurement, NetSuite handles foreign currency purchase orders 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. Customs duty and IGST on imports can be captured as landed cost elements and added to the item’s average cost in inventory.
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.
When goods arrive, the warehouse team creates an Item Receipt against the open PO, recording the quantities actually delivered. When the vendor sends its invoice, the accounts team creates a vendor bill linked to the same PO, and NetSuite automatically compares the billed quantity and rate against both the PO and the receipt.
Discrepancies are highlighted directly on the bill record. Common discrepancies in Indian procurement include price variance, where the vendor bills at a rate different from the PO; quantity variance, where fewer goods are received than invoiced; and tax discrepancy, where a different GST rate is applied. A designated approver must explicitly sign off before a bill with discrepancies can be posted to the accounts.
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 payments 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.
When a vendor is set up with a TDS section, such as 194C for contractors or 194J for professionals, NetSuite calculates and withholds TDS automatically on every bill from that vendor. The deducted amount sits in a liability account until the challan payment is made to the government and Form 26Q is filed for the quarter.
For a complete walkthrough of the full process, see our NetSuite ERP implementation guide.
Frequently Asked Questions
Can NetSuite handle blanket purchase orders?
Yes. Create a blanket PO with a total committed amount and release individual orders against it over time. NetSuite tracks the remaining balance on the blanket PO. This is common for annual supply agreements with key vendors.
Does NetSuite support vendor advance payments?
Yes. Record vendor advance payments and apply them against future vendor bills. The advance is tracked as a prepayment until the bill is received and the advance is consumed. This handles the common Indian practice of advance payments to vendors before delivery.
How does three-way matching work for services?
For services, matching is typically two-way (PO to bill) since there is no goods receipt. Configure the matching rule per item type: three-way for physical goods and two-way for services. NetSuite handles both in the same procurement workflow.
Can I process vendor payments in bulk?
Yes. Use the Payment Batch feature to select multiple approved vendor bills and process them as a single bank transfer batch. Generate the EFT file for upload to your bank. This reduces the time finance teams spend on weekly or fortnightly vendor payment runs.
Does NetSuite support vendor-managed inventory (VMI) arrangements?
NetSuite supports consignment inventory and drop-ship arrangements, which are related to VMI concepts. For true VMI where the vendor holds stock at your facility and invoices only when consumed, this typically requires a custom workflow in NetSuite. An implementation partner can configure this, but it is not a standard out-of-the-box feature.
Can NetSuite handle reverse charge mechanism (RCM) for GST on vendor payments?
Yes, with configuration. Transactions subject to RCM, for example import of services, goods transport agency payments, or purchases from unregistered suppliers in specific categories, can be flagged in NetSuite so that the GST is self-invoiced and the corresponding output and input entries are created. This requires the India tax localisation to be properly configured, which is best done during implementation with a partner familiar with Indian GST rules.
How does NetSuite handle recurring purchase orders for regular supplies?
NetSuite does not have a native recurring PO feature, but you can create a template PO and copy it each period. Some businesses use saved searches or SuiteScripts to generate monthly POs automatically from a template. Alternatively, blanket POs, a single PO for a total annual quantity drawn down over time with each delivery, are a commonly used approach in NetSuite for regular supply arrangements.
