Skip to main content

NetSuite - Configuring the Purchase Order (Export)

Micah A. Parker avatar
Written by Micah A. Parker
Updated over a week ago

Product: NetSuite


A Purchase Order Export is used to create Sales Orders for a NetSuite Customer by exporting out an Inbound Purchase Order (850) from your Trading Partner.

The Purchase Order Export Framework Settings allows you to adjust various aspects of that Export, such as whether to use Pricing from your EDI Purchase Order or your NetSuite Pricing Levels. These can be configured at the Company Level which will affect all Trading Partners listed under that company, or the Trading Partner Level which will only affect that specific Trading Partner.


Company Level Settings


The Company Level Settings allow settings across all Transactions to be configured and applied across all Trading Partners allowing for an easy way to configure a default setup across any Trading Partner within Transaction Manager.

Navigate: Business System → (Company Name) → Company Configuration → Integration Options

Company Level Settings display all Transaction Settings - be sure to check how each setting may affect your Business Process


Trading Partner Specific Settings


The Trading Partner Settings allow for a Trading Partner to override the Company Level Settings and be configured independently for a specific Transaction while still allowing other Transactions to inherit the Company Level Settings.

Navigate: Trading Partners → (Partner) → Preferences → Integrations

Integration Type: Purchase Order (Export)

Check: Use Partner Level Settings

Enabling Use Partner Level Settings will overwrite ALL settings at the Company Level - be sure to mimic any settings to at the Partner Level that you wish to keep the same as the Company


Purchase Order (Export) Settings


Each setting listed below will affect the Purchase Order Export. If modified at the Company Level will apply to all Trading Partners, if modified at the Trading Partner Level will only apply to that specific Trading Partner - overriding any Company Level Settings if there is a conflict.

Setting

Description

Error on Duplicate PO

Prevents the Sales Order creation, produces Error within Transaction Manager

Price Verification

Compares the Inbound Purchase Order (850) price against the NetSuite Item Price

  • Assign the NetSuite Unit Price

    • Ignores EDI Price, uses NetSuite. Provides no warning

  • Assign the EDI Unit Price (Warning)

    • Allows creation of the Sales Order using the value sent on the Purchase Order (850) - provides Warning if does not match NetSuite (or Tolerance %).

  • Validate EDI/NetSuite Price (Error if Different)

    • Prevents creation of the Sales Order, and produces an error.

Price Verification Tolerance %

If greater than 0 - will allow for a tolerance across differing prices between the Purchase Order (850) and NetSuite while still allowing the Sales Order to be created.

Used when Price Verification is set to Validate EDI/NetSuite Price

Enable Customer Creation on Export

When enabled, will determine if NetSuite should create a new Customer Card based off of the Customer Criteria setting.

If disabled - will error if a match is not found in NetSuite to a Customer Card.

Customer Criteria

The Criteria to determine if a new Customer Card should be Created.

  • First Name, Last Name, Email

  • First Name, Last Name, Phone

  • Last Name, Email

  • First Name, Last Name

  • Customer Name

  • Company Name, Parent

Next Document Number

Will assign the Sales Order # sequentially using the Prefix and Number

  • Empty - Checking will disable feature - allowing NetSuite to auto-generate Sales Order #s

  • Prefix - Checking will insert the same string entered into the settings input box to every Sales Order

  • Number - The number to begin sequencing from (Setting Auto-Increments each Export to show what next number is)

Additional Resources


rev 9/23/2025

Did this answer your question?