Transactions Import Type

Transactions imports support the addition or update of data for some transaction subtypes. Processed lines for some transaction types contribute to the Monthly Transaction Lines metric that counts toward maximum limits for your NetSuite service tier. For more information, see Transaction Types Included in Monthly Transaction Lines Metric.

The Import Assistant supports the following transaction subtype imports:

• Advanced Intercompany Journal Entry Import

• Cash Sale Import

• Check Import

• Credit Card Charge Import

• Credit Card Refund Import

• Credit Memo Import

• Custom Transactions Import

• Customer Payment Import

• Estimate Import

• Inventory Details on an Inbound Shipment

• Inventory Adjustment Import

• Inventory Cost Revaluation Import

• Inventory Transfer Import

• Invoice Import

• Item Demand Plan Import

• Item Supply Plan Import

• Journal Entry Import and Intercompany Journal Entry Import

• Opportunity Import

• Order Reservation Import

• Paycheck Import

• Period End Journal Entry Import

• Purchase Order Import

• Return Authorization Import

• Sales Order Import

• Statistical Journal Entry Import

• Transfer Order Import

• Vendor Bill Import

• Vendor Credit Import

• Vendor Payment Import

• Vendor Prepayment Import

• Vendor Return Authorization Import

Be aware of the following:

• You can import transaction data in a single CSV file, or in multiple files, for example, with transaction header data in one file and item-level data in other files. For imports of new data, you should include external ID values to uniquely identify transactions. For updates, you can use internal IDs for this purpose. The unique ID should be included in every line of the CSV files. Note that the transaction ID is not unique.

• By default the Field Mapping page for a transactions import includes the NetSuite fields from your preferred form for the selected record type. Fields can be mapped for the import job if they are displayed (not hidden) and not disabled on your preferred form. These default mappable NetSuite fields may not match the fields that you need to import; you may want to include fields available on another record type form.

  To ensure that the appropriate fields are available for mapping, you can change the selection for Custom Form, in the Advanced Options area of the Import Assistant's Import Options page. For more information, see Set Advanced CSV Import Options.

• If auto-generated numbering is enabled, transaction numbers can still be set if the Allow Override option is enabled.

• To maintain performance, you should not submit transactions that contain more than 5000 lines through CSV import. (For journal entries, this limit is 10,000 lines per transaction.)

• To avoid errors related to imported transaction address data: for state fields, use short names rather than full names, and for country fields, use full names rather than codes. A dropdown list of country names is available from the edit icon on the Field Mapping page, to be set as default country field values. See State and Province Names for CSV Import and Country Names for CSV Import.

• To import a transaction with multiple line items, use the same transaction number field for each line item.

• You should import entities and items data before you import transactions data.

  • To reference entities such as customers in transaction CSV files, use the number if auto-generated numbering is enabled; otherwise, use the customer name.

  • Item references in transaction CSV files must match the spelling and case of the item names in your NetSuite account.

  • Account references in transaction CSV files should be account names rather than numbers.

  • For sub-customers, sub-items, and sub-accounts, use hierarchical parent : child references. For more information, see Delimiters for Hierarchical and Multi-Select Fields.

• Use entity account names and numbers when importing transactions, not the chart of accounts number.

• For Cash Sale, Estimate, Invoice, Purchase Order, Sales Order, and Vendor Bill imports, Items data is required for imports of new records, but not for imports that update existing records. Items data is not required for Opportunity imports. Items data is not relevant to Customer Payment and Vendor Payment imports. See Required Items Sublist Fields for Transactions Imports.

  • You can import values for custom transaction item options along with Items sublist data. The Item Options feature must be set up in your account, and transaction item options must first be set up at Customization > Lists, Records, & Fields > Transaction Item Options > New. For details, see Importing Transaction Item Options.

  • If you do not map the Price Level field for any imported transaction items, the base price from the item record is used as that line item's price. To use a different price, you must map the Price Level field in your import, and either include a Price Level column with values in the CSV file, or on the Field Mapping page, click the edit icon for the mapped Price Level field and select Custom as the default. (Note that this default is not guaranteed to be a valid level for all items.)

• Be aware of the following when you use the Import Assistant to update transaction records:

  • As of Version 2010 Release 1, the Use Conditional Defaults option is no longer available. Now, imports always populate dependent field values automatically when related field values are set, in the same manner that dependent field values are populated in the user interface. For updates, be sure to include all necessary values in CSV files, to avoid inadvertently changing existing field values to defaults.

  • Some transaction sublists are keyed and some are not. For non-keyed sublists, partial updates are not supported; CSV file sublist data either completely replaces existing sublist data or is appended, depending upon the setting for the Overwrite Sublists option. Also, for non-keyed sublists, you shouldn't update main transaction fields and sublist fields in the same import job. For a list of keyed and non-keyed transaction sublists supported for import, see Supported Sublist Imports.

  • The Import Assistant lets you update items data for the following types of transactions: Cash Sale, Estimate, Invoice, Opportunity, Purchase Order, Sales Order, and Vendor Bill. You can modify data for existing line items and/or add line items to existing transactions. The Items sublist for transactions uses either Line/Order Line or Item as a key field to determine how to update or add line items. For more information, see Line Item Updates on Transactions Imports.

  • Complete deletion of sublist data currently is not supported. Existing sublist data can only be overwritten with new CSV file sublist data, not with an absence of CSV file sublist data.

  • You can use transaction import capabilities to perform mass updates of supported transaction subtype data. Create a saved search, export saved search results and modify them in an external application, then use the Import Assistant, with an Update data handling option, to reimport modified data. You need to set certain criteria for your saved search to generate an exported file with appropriate data for reimporting. For information, see Creating Transaction Saved Searches for Reimport.

Additional Information

Importing CSV Files with the Import Assistant

Related Topics

Guidelines for CSV Import Files

Supported Record Types for CSV Import

Tips for Successful CSV Imports

General Notices