Posted by Paul Giese ● Dec 30, 2019 2:36:11 PM

Best practices for converting vendor records to NetSuite

Early in the NetSuite implementation process, organizations will need to import their vendor records into NetSuite. This blog post shares some best practices and common struggles I've seen in the conversion process.

  • Consolidate vendors across subsidiaries - for a multi-entity, multi-ERP organization, each operating entity will have its own vendor list. With a NetSuite OneWorld account, legal entities can share vendors. When preparing the vendor import template, make sure that duplicate vendors between entities are removed. Keep in mind that, across entities, a user may have entered a vendor as 'ABC Corporation' vs. 'ABC, Inc', etc. If the changes are made in the legacy ERP, the vendor mapping process will be easier when importing financial transactions and/or historical data. Users also need to decide which vendors can be used by which entity. If you aren't sure, I'd share the vendor across all entities. You can easily change this later down the road if needed.
Case Study - read about how intheBlk helped Oncorus with their historical financial data import process.
  • Consolidate vendors across functional currencies - many basic ERP systems will not allow users to post transactions in multiple currencies to a single vendor. Organizations work around this by adding the same vendor multiple times for each currency the vendor operates in. NetSuite allows users to post transactions in multiple currencies to the same vendor. You also can set a preferred currency. As part of the import process, consolidate vendors that have been entered multiple times, identify which currency(ies) the vendor can operate in, and set the vendor's preferred currency.
  • All non-employee vendors that won't be imported to NetSuite should be made inactive - the 'Vendor Contact List' report is the baseline report I'd recommend for exporting vendor data out of QBO. This report excludes inactive and deleted vendors.
  • Distinguish employee records on the vendor list with an (EE) or equivalent, and DON'T import into NetSuite as vendors - many basic ERP systems, like QBO, do not separate lists for employees and vendors. Organizations add employees as a vendor to enter expense reports. In NetSuite, 'Employees' and 'Vendors' are two distinct lists. As such, organizations no longer need to track employees as a 'Vendor' in NetSuite. Remove employees from the import file.
  • Get the Country code right on the import file - in NetSuite, a country is required for any vendor that has an address. To find the list of country names in NetSuite, navigate to Setup -> Company -> Countries. Use a VLOOKUP to map between the legacy system and the NetSuite country code.
  • Remember, you can always re-import data later - NetSuite allows users to made updates via a CSV template. If you find yourself running out of time or you forget to import a key field, you can always add this later.

Converting data from a legacy system, like QBO, to NetSuite can be a daunting task. intheBlk has experience helping clients move off of QuickBooks Online, QuickBooks Desktop, Sage 50, and Microsoft AX. We can help your organization successfully migrate to NetSuite. Contact us today!

Topics: Financial Reporting, Systems, ERP, Technology, NetSuite

How can we help you?