TL;DR
The Procurify SuiteApp is the connector that powers the Procurify NetSuite Integration for purchase orders (POs), item receipts, vendors, and catalog items. The Procurify SuiteApp replaces the legacy Procurify SuiteBundle, which loses NetSuite support in the second half (H2) of 2026. A SuiteApp installs from the NetSuite SuiteApp Marketplace, while a SuiteBundle uses NetSuite's older bundle install method.
All new fixes and features for the Procurify NetSuite Integration ship to the Procurify SuiteApp only.
Key Benefits
Compliance: Vendors and catalog items deactivated in NetSuite are also deactivated in Procurify, so both systems stay aligned.
Speed: Requesters, approvers, and buyers keep the same Procurify workflow, and Procurify runs the migration at no cost.
Visibility: Vendor address, vendor phone, preferred vendor, and item cost sync correctly again after the NetSuite 2026.1 release.
How does the Procurify SuiteApp work?
The Procurify SuiteApp keeps every core sync from the Procurify SuiteBundle and adds fixes and features that are only available on the Procurify SuiteApp. Procurify maintains the Procurify SuiteApp and keeps it compatible with future NetSuite releases.
What stays the same when I move to the Procurify SuiteApp?
POs approved in Procurify are created in NetSuite. The sync runs every 15 minutes.
Item receipts recorded in Procurify are created against the matching NetSuite PO.
Vendors sync from NetSuite to Procurify.
Account Codes sync from NetSuite for accounts flagged for Procurify.
Catalog and inventory items sync from NetSuite.
Payment terms sync from NetSuite.
Custom field mappings carry over. If your organization has custom field mappings, Procurify provides upgraded mapping files during the migration.
How does vendor and item deactivation work in the Procurify SuiteApp?
Vendor and catalog item status in Procurify now follows the status in NetSuite.
Action in NetSuite | Result in Procurify |
Deactivate a vendor | The vendor is deactivated in Procurify |
Reactivate a vendor | The same vendor record is reactivated in Procurify. No duplicate is created. |
Deactivate a catalog item | The catalog item is deactivated in Procurify |
Reactivate a catalog item | The same catalog item record is reactivated in Procurify. No duplicate is created. The item is not added back to its catalog bundles automatically. |
After reactivating a catalog item, re-add the catalog item to any catalog bundles it belonged to. Vendor and item deactivation is rolling out now, so your Procurify contact can confirm when the feature is enabled for your account.
What is the NetSuite 2026.1 sync fix?
After the NetSuite 2026.1 release, some Procurify SuiteBundle syncs report success but leave out data. The missing fields are vendor address, vendor phone, preferred vendor, and item cost. The Procurify SuiteApp fixes the NetSuite 2026.1 issue, and the fix is not available on the Procurify SuiteBundle.
How does the Procurify SuiteApp compare to the Procurify SuiteBundle?
Capability | Procurify SuiteBundle (legacy) | Procurify SuiteApp |
PO and item receipt sync | Yes | Yes |
Vendor, Account Code, item, and payment term sync | Yes | Yes |
Custom field mappings | Yes | Yes |
Vendor address, phone, preferred vendor, and item cost after NetSuite 2026.1 | Affected by the 2026.1 issue | Fixed |
Vendor and item deactivation and reactivation | No | Yes (rolling out) |
Install method | Bundle install | NetSuite SuiteApp Marketplace |
NetSuite support | Ends H2 2026 | Ongoing |
New fixes and features | None | All future releases |
What happens during the migration to the Procurify SuiteApp?
Procurify runs the migration on behalf of your team using temporary Administrator access to your NetSuite environment. Plan for 2 to 3 hours of integration downtime.
Before the migration, your NetSuite Administrator completes these steps:
Provide Procurify with temporary Administrator access that includes access to the NetSuite SuiteApp Marketplace.
Enable Allow Non-GL Changes in NetSuite for the migration window.
Confirm a migration date and time with Procurify.
During and after the migration:
The Procurify SuiteApp replaces the Procurify SuiteBundle.
Existing POs and item receipts stay linked to their NetSuite records.
POs approved in Procurify during the downtime sync automatically once the Procurify SuiteApp is live.
Procurify confirms test syncs with your team before closing the migration.
Do I need to change how my team works in Procurify?
No. Requesters, approvers, and buyers use Procurify exactly as before.
Will I lose my PO history when I move to the Procurify SuiteApp?
No. Existing POs and item receipts stay linked to their NetSuite records.
Is there a cost to move to the Procurify SuiteApp?
No. The migration to the Procurify SuiteApp is free.
What happens if my organization stays on the Procurify SuiteBundle?
The Procurify SuiteBundle receives no new fixes and loses NetSuite support in H2 2026. Issues like the NetSuite 2026.1 vendor address issue are fixed on the Procurify SuiteApp only. Future NetSuite releases may also change functions the Procurify SuiteBundle relies on, and Procurify will not update the Procurify SuiteBundle to address those changes.
Who do I contact to move to the Procurify SuiteApp?
Reach out to your Procurify Customer Success Manager (CSM) or Procurify Support.
Keywords: NetSuite, SuiteApp, SuiteBundle, Migration, NetSuite Integration, Purchase Order, Item Receipt, Vendor Sync, Catalog Items, Deactivation, Reactivation, NetSuite 2026.1, Custom Field Mappings, Account Code