SuiteProcurement: Multi-Vendor Requisitions, Partial Receipts, and Default Category Mapping

What changed

Multi-Vendor Requisitions

Order Requisitions in SuiteProcurement can now reference multiple vendors on a single document. Previously, each requisition was limited to a single vendor, forcing admins to split requests across multiple records when sourcing from different suppliers.

Partial Item Receipts

SuiteProcurement now supports generating partial item receipts. Before 2026.1, receiving against a PO was all-or-nothing — you had to receive every line item and create a complete item receipt in one action. You can now receive a subset of items and generate a corresponding partial receipt, which aligns the SuiteApp behavior with native NetSuite item receipt functionality.

Default Item and Expense Category Fallback

A new configuration option lets you define default item and expense categories that apply when a specific category mapping is not found. This reduces errors on requisition submission when category mappings are incomplete or when new items are introduced without explicit mappings.

PO Document: Item Description Included

The outbound Purchase Order document now includes the item description field. If you have integrations or vendor portals consuming the PO XML/PDF output, the description will now appear without any additional configuration.

Bug Fixes

• Doubled Total Amount — Fixed an issue where the Total Amount field on purchase orders and requisitions was erroneously doubled. If you built any workarounds (e.g., custom calculated fields or client scripts that halved the total), you should remove them after upgrading.
• Missing PO Details on Approval — Fixed an issue where purchase order details were not sent when a PO was approved and approval routing was disabled. This affected downstream integrations or notifications that relied on PO approval events to trigger detail transmission.

What to do

1. Update the SuiteProcurement SuiteApp — Verify you are running the 2026.1 bundle version. Navigate to Customization > SuiteBundler > Search & Install Bundles > List and check for available updates.
2. Review multi-vendor workflows — If you previously created multiple requisitions to handle multi-vendor sourcing, evaluate whether consolidating onto a single requisition simplifies your process. Update any saved searches or workflows that assume one vendor per requisition.
3. Test partial receipts — If you have SuiteScript customizations on the itemreceipt record (User Event or Client scripts), test them against partial receipts to ensure they handle partially fulfilled PO lines correctly.
4. Configure default categories — Set up default item and expense categories under the SuiteProcurement configuration to catch unmapped items. This is especially useful if you frequently onboard new inventory items.
5. Remove doubled-total workarounds — If you deployed any scripts or formulas compensating for the doubled Total Amount bug, remove them to avoid the total now being incorrectly halved.
6. Validate PO approval integrations — If you have integrations triggered by PO approval (e.g., SuiteScript afterSubmit on purchaseorder, or workflow actions), verify that PO details now flow correctly with approval routing disabled.