Vendor Payment Import
NetSuite Vendor Payment transactions record payment of vendor bills when they are due. These transactions post expenses to the general ledger, and affect both accounts payable and the bank account used for the payment.
To maintain performance, you should not submit transactions that contain more than 5000 lines through CSV import.
For more details about vendor payments in NetSuite, see Vendor Payments.
Usage Notes
Consider the following usage notes when importing vendor payment data.
-
You can import Vendor Payment transaction data in a single CSV file, or in multiple files.
-
You must map external ID or internal ID to serve as a unique ID per record. The unique ID should be included in every line of the CSV files. For imports of new data, use external ID.
-
Each imported Vendor Payment record should include a reference to a NetSuite Vendor record, mapped to the Vendor Payment's Payee field. This reference should match exactly the Vendor ID field value in the Vendor Record.
-
You must map a CSV file field to the NetSuite Account field to represent the accounts from which payments are made. You have the option of mapping to the A/P Account field to represent the accounts payable accounts impacted by payments. If the Use Account Numbers preference has been enabled at Setup > Accounting > Accounting Preferences, imported values for the Account and A/P Account fields should include both account number and name, for example: 11000 Accounts Payable. If this preference is not enabled, values should be account name only, for example: Accounts Payable.
-
All vendor payments must be applied to vendor bills in full. You cannot import unapplied amounts. You cannot import a total amount value for a payment; this amount is calculated by adding all of the values for the Payment field in the Bills sublist data.
If you are importing both vendor payments and vendor bills, and you want to apply imported payments to imported bills, you need to import bills first.
-
If the Multiple Currencies feature is enabled, you must map the Exchange Rate field. If your CSV file does not include values for this field, you can set it to a default value. Currency values are taken from referenced vendors. See Currency Management.
-
To import data for the In-Transit, Available Balance, Approval Status, and Next Approver fields, you must enable the following features and set the following preferences:
-
Enable the In-Transit Payments feature at Setup > Company > Setup Tasks > Enable Features, on the Accounting subtab.
-
Check Vendor Bills and Vendor Payments at Setup > Accounting > Preferences > Accounting Preferences, on the Approval Routing Subtab.
-
Select a Vendor In-Transit Payment Account at Setup > Accounting > Preferences > Accounting Preferences, on the General subtab, under Accounts Payable. Also check the Use In-Transit Vendor Payments by Default box.
-
For details about fields that can be mapped in the vendor payment record, see the SOAP Schema Browser’s vendor payment reference page. You can use the field definitions here as a basis for creating your own CSV import template file. For information about working with the SOAP Schema Browser, see SOAP Schema Browser.
Review the following guidelines for vendor payment imports:
Supported Vendor Payment Sublist Data Imports
The Vendor Payment import supports the import of Bills sublist data. Each line in this sublist represents a vendor bill to which the payment is applied. The sum of Payment field values for sublist records represents the total amount of the payment.
In this sublist, the required Bill key field holds the transaction IDs for vendor bills to which payments are applied. An additional, optional Line key field holds the line numbers for the vendor bill lines to which payments are applied.
If you use only the Bill key, the following error may be returned to indicate that a unique reference was not found, “Ambiguous sublist reference; multiple matches exist for key value <>”.
An import can add new vendor bills or vendor bill lines to which a payment is applied, change the amounts applied to existing vendor bills or vendor bill lines, or remove vendor bills or vendor bill lines.
When the Overwrite Sublists advanced option is not enabled (which is the default), CSV file sublist data selectively updates existing vendor bills data. When this option is enabled, CSV file sublist data completely replaces existing vendor bills data. For example:
-
- If the existing Vendor Payment Bills sublist data is:
- Vendor Bill A: $100
- Vendor Bill B: $200
-
- And CSV file sublist data is:
- Vendor Bill A: $120
- Vendor Bill C: $180
-
- When Overwrite Sublists=F, post update sublist data is:
- Vendor Bill A: $120
- Vendor Bill B: $200
- Vendor Bill C: $180
-
- When Overwrite Sublists=T, post update sublist data is:
- Vendor Bill A: $120
- Vendor Bill C: $180
The Vendor Payment Import also supports the import of Accounting Book Detail sublist data. Accounting Book Detail sublist data is available only when the Multi-Book Accounting feature is enabled, and only when more than one active accounting book exists. This sublist is selectively updateable based on the Accounting Book key field.
Complete deletion of sublist data currently is not supported. For more information, see Sublist Data Import.
Using Import Assistant for Vendor Payments Mass Update
You can perform a mass update of existing Vendor Payment main fields by creating a Transaction saved search with a filter of Type is Vendor Payment, changing data externally, then using the Import Assistant to import modified data. For more information, see Creating Transaction Saved Searches for Reimport.
The Import Assistant is available at Setup > Import/Export > Import Tasks > Import CSV Records. After you select the record type for import, you choose the import character encoding. For more information, see Select a Record Type for Import and Choose Import Character Encoding.