Sign in

NetSuite Sync - Best Practices and Additional Information

Overview

This article provides more information about how the sync works, and outlines our best practices for syncing between Bill.com and NetSuite. 

For instructions on setting up the sync between Bill.com and NetSuite, visit our Setup Guide below: 

NetSuite Sync Setup Guide

 

Table of Contents

  1. Introduction
  2. Best Practices and Additional Information

 

1. Introduction

 

This section covers the high-level overview of the following:

  • List of objects that sync from Bill.com to NetSuite, and vice versa
  • Known limitations 

 

Record Types and Known Limitations

 

Record Type

NetSuite to Bill.com

Bill.com to NetSuite

Known Limitations

General

Vendors

Yes

Yes

- Bill.com does not support more than one subsidiary per vendor.

- Vendors with Access enabled in NetSuite cannot be updated by Bill.com

Customers

Yes

Yes

Customers with Access enabled in NetSuite cannot be updated by Bill.com

- Bill.com does not support more than one subsidiary per customer.

Chart of Accounts

Yes

Yes

- Summary accounts are not supported.

Departments

Yes

Yes

 

Locations

Yes

Yes

 

Classes

Yes

Yes

 

Items

Yes

Yes

- Items created in Bill.com and synced to NetSuite use the subtype: For Resale.

- Sales Tax Items are not supported.

Jobs

No

No

- Jobs do not sync to/from NetSuite

Custom Fields

No

No

- Custom fields do not sync from NetSuite to Bill.com.

- When creating custom fields in NetSuite, assign a default value to avoid any conflicts.

*Custom fields are ignored by the sync. They will not prevent the bills from syncing to Bill.com. Custom fields will be preserved in NetSuite but will not be visible in Bill.com.

Currency

USA only

USA only

- Multi-currency is not supported.

Payment Terms

No

No

- Payment Terms do not sync to/from NetSuite.

Attachments

Yes

No

- Attachments sync from NetSuite to Bill.com

- Attachments will not sync from Bill.com to NetSuite.

Partners

No

No 

- Partners do not sync to/from NetSuite.

Payables

Bills

Unpaid bills only *

Yes

- Partially- and fully-paid bills do not sync from NetSuite to Bill.com.


* You can disable import of unpaid bills from NetSuite to Bill.com.  See Sync your transactions for more details.

Vendor Credits

Unapplied vendor credits only **

Yes

- Partially- and fully-applied vendor credits do not sync from NetSuite to Bill.com.

- Vendor Credit applications (applying, un-applying, and reapplying) do not sync from NetSuite to Bill.com.

** You can disable import of unapplied vendor credits from NetSuite to Bill.com. See Sync your transactions for more details.

Approval Status

No

Limited***

*** You can opt to only sync bills/vendor credits approved in Bill.com into NetSuite. However, approval status is not kept in sync. See Best Practices and Additional Information for more details.   

Bill Payments

No

Yes

- Payments made in NetSuite do not sync to Bill.com.

- Payments synced from Bill.com to NetSuite will always use the same Department, Class, and/or Location, per subsidiary, as applicable. See Best Practices and Additional Information for more details.

Purchase Orders

Yes, once converted to unpaid bills

N/A

- You cannot view original Purchase Order in Bill.com.

- The Purchase Order number will appear on bills and vendor credits that originated from POs in NetSuite.

- Bills created from POs from NetSuite should not be edited in Bill.com. See Best Practices and Additional Information for more details.

AP Funds Transfers

No

Yes

- Funds Transfers synced from Bill.com to NetSuite will always use the same Department, Class, and/or Location, per subsidiary, as applicable. See Best Practices and Additional Information for more details.

Commissions

No

No

- Commissions do not sync to/from NetSuite

Receivables

Transactions

No

No

- AR transactions (Invoices, Credit Memos, Sales Orders, Invoice Payments, AR Funds Transfers)  are not supported.

 IMPORTANT: With bundles prior to 3.0.3.c, for list objects (Customers, Chart of Accounts, Departments, Locations, Classes, Items), certain hierarchies are not supported. Please refer to NetSuite Sync: Hierarchies Best Practices for more details. 

 

 2. Best Practices and Additional Information

 

General Best Practices

 

Keeping the Bill.com Bundle Up-to-Date

  • The NetSuite bundle now updates automatically! Nothing manual from you needed--we'll handle it. 

 

Preferred Forms and Required Fields

  • When syncing records from Bill.com to NetSuite, the sync will use the preferred form for that record type.  
  • Fields that do not sync with Bill.com cannot be set as required fields on the preferred form for a given record type.

 

Locked and Closed Periods

  • The sync cannot use periods that are closed.  If a period is closed, the sync will use the most recent open period.
  • The sync will be able to write to periods that have been locked.  If this is an issue, we recommend that you completely close periods you would not like the sync to be able to change.

 

Amortization Schedules

  • When an amortization schedule is in use, the Bill.com sync will not change line items for bills and vendor credits covering sublists, expenses, and items.
    • Any changes to line items for bills/vendor credits should be made in NetSuite. 

 

Best Practices for Each Record Type

 

Vendors

General

From NetSuite to Bill.com

From Bill.com to NetSuite

  • Bill.com only supports one subsidiary per vendor.  If a single vendor spans across multiple subsidiaries, you must make one instance of the vendor for each subsidiary.
  • Enabling access for a vendor will cause sync errors when that vendor is updated in Bill.com.
  • Vendors with access enabled need to be managed in NetSuite.
  • The NetSuite character limit for Vendor IDs is 83 characters. The sync with Bill.com recognizes the full Vendor ID length.
  • When Vendor Auto-Numbering is On in both NetSuite and Bill.com, the vendor ID generated in NetSuite will sync to Bill.com.
  • Vendor as a Tax Agency will sync to Bill.com when it is first created. Any subsequent changes will not sync. 
  • For vendors of type: Company, Company Name is required to sync to NetSuite.
  • For vendors of type: Individual, First Name and Last Name are required to sync to NetSuite.
    • If the first and last name fields are left blank, then we will split vendor name with " " and use the first part of the name as NetSuite’s first Name and the remaining part as NetSuite’s last Name.
    • If we can’t split the name, we will repeat the vendor name for first name and last name.



 

Customers

General

From NetSuite to Bill.com

From Bill.com to NetSuite

  • Child customer will sync even if subsidiary does not have access to the parent. See Hierarchy Best Practice for more details.
  • Enabling access for a customer will cause sync errors when that customer is updated in Bill.com.
    • Vendors with access enabled need to be managed in NetSuite.
  • The NetSuite character limit for Character IDs is 83 characters. The sync with Bill.com recognizes the full Character ID length.
  • For OneWorld users: 
    • The Bill.com sync has no limit on Customer hierarchy. 
  • For non-OneWorld users:
    • The Bill.com sync limits Customer hierarchy to 3 levels deep.
  • When Customer Auto-Numbering is On in both NetSuite and Bill.com, the customer ID generated in NetSuite will sync to Bill.com.
  • For customers of type: Company, Company Name is required to sync to NetSuite.
  • For customers of type: Individual, First Name and Last Name are required to sync to NetSuite.
    • If the first and last name fields are left blank, then we will split customer name with " " and use the first part of the name as NetSuite’s first Name and the remaining part as NetSuite’s last Name.
    • If we can’t split the name, we will repeat the customer name for first name and last name.



 

Chart of Accounts

General

From Bill.com to NetSuite

  • Bill.com does not support Summary accounts. 
  • Child account will sync even if the subsidiary does not have access to the parent. See Hierarchy Best Practice for more details.
  • Account Numbers are required for syncing an account from Bill.com to NetSuite



 

Departments

General

  • Child department will sync even if the subsidiary does not have access to the parent. See Hierarchy Best Practice for more details.



 

Locations

General

  • All parent locations in a given hierarchy must be accessible by a given subsidiary in order to sync child locations.  See Hierarchy Best Practice for more details.



 

Classes

General

  • Child classes will sync even if the subsidiary does not have access to the parent. See Hierarchy Best Practice for more details.



 

Items

General

From Bill.com to NetSuite

  • Sales Tax items are not supported.
  • Child items will sync even if the subsidiary does not have access to the parent. See Hierarchy Best Practice for more details.
  • Items created in Bill.com will sync to NetSuite with the subtype: For Resale.
    • If an item needs to have a different subtype, it must be created in NetSuite.

 

 

 

Custom Fields

General

  • Custom fields do not sync from NetSuite to Bill.com.
    • Custom fields are ignored by the sync. They will not prevent the bills from syncing to Bill.com.
    • Custom fields will be preserved in NetSuite but will not be visible in Bill.com.
  • When creating custom fields in NetSuite, assign a default value to avoid any conflicts.

 

 

 

Currency

From NetSuite to Bill.com

From Bill.com to NetSuite

  • Transactions in NetSuite that are not in US dollars will be ignored by the sync.
  • Transactions in Bill.com will always sync to NetSuite using the US dollar currency.



 

Attachments

 

From NetSuite to Bill.com

From Bill.com to NetSuite

  • Upload and handle your documents in NetSuite. Attachments will sync from NetSuite to Bill.com.
  • Attachments will not sync from Bill.com to NetSuite.



 

Bills

General 

From NetSuite to Bill.com

From Bill.com to NetSuite

  • All users, regardless of their assigned role, have access to the View in Bill.com button in NetSuite
  • Customers coded in the bill line items can be prevented from syncing to/from NetSuite
  • If a bill is created from a PO, it will sync to Bill.com
    • Do not edit the line items of these bills in Bill.com; doing so will unlink the bill from its PO in NetSuite.  The Description field for the line item in Bill.com will indicate if the bill is connected to a PO in NetSuite.
  • If a bill is partially or fully paid in NetSuite, it will not sync from NetSuite to Bill.com
  • If the currency for a bill is not US dollars, it will not sync from NetSuite to Bill.com
  • Documents/files attached to bills in NetSuite will sync to Bill.com
  • Bills in NetSuite can be classified both in the general section of the bill, as well as the line items of the bill.  Bill.com only supports classifications in the line items of a bill.
    • When bills sync from Bill.com to NetSuite, the general section of the bill will use whatever is set as the Default Payables classification in the Bill.com Preferences record.
    • To make it easier to reclassify these records (as needed), you can create a department, location, and/or class called “Unclassified”, or “Uncoded”, or similar, and set that as your Default Payables classification.  This will allow you to run a report to isolate the bills that need to be reclassified.
  • If “Only Sync Approved Bills/Credits from Bill.com" is selected, bills will not sync from Bill.com to NetSuite unless their Approval Status is Approved.
    • When bills sync to NetSuite, their status will automatically be set as:
      • “Approved” in NetSuite, if NetSuite approvals are turned off
      • "Pending Approval" if NetSuite approvals are turned on
    • Once a bill is approved in Bill.com and syncs to NetSuite, changes to the approval status will not sync.
  • If Bill.com’s “Sync only approved Bills/ Vendor Credits” preference is selected, bills will not sync to NetSuite unless their Approval Status is Approved in Bill.com.
    • When bills sync to NetSuite with this enabled, their NetSuite approval status will not be changed.
    • Once a bill is approved in Bill.com and syncs to NetSuite, changes to the approval status will not sync.



 

Vendor Credits

General 

From NetSuite to Bill.com

From Bill.com to NetSuite

  • Customers coded in the Vendor Credit line items can be prevented from syncing to/from NetSuite.
  • If a vendor credit is partially applied or fully applied in NetSuite, it will not sync from NetSuite to Bill.com
  • If the currency for a vendor credit is not US dollars, it will not sync from NetSuite to Bill.com
  • Vendor credits in NetSuite can be classified both in the general section of the vendor credit, as well as the line items of the vendor credit.  Bill.com only supports classifications in the line items of a vendor credit.
    • When vendor credits sync from Bill.com to NetSuite, the general section of the vendor credit will use whatever is set as the Default Payables classification in the Bill.com Preferences record.
    • To make it easier to reclassify these records (as needed), you can create a department, location, and/or class called “Unclassified”, or “Uncoded”, or something similar, and set that as your Default Payables classification.  This will allow you to run a report to isolate the vendor credits that need to be reclassified.
    • Vendor credit application syncs along with the bill to which it has been applied.
  • If “Only Sync Approved Bills/Credits from Bill.com" is selected, vendor credits will not sync from Bill.com to NetSuite unless their Approval Status is Approved.
    • When vendor credits sync to NetSuite their status will automatically be set as:
      • “Approved” in NetSuite, if NetSuite approvals are turned off
      • "Pending Approval" if NetSuite approvals are turned on
    • Once a vendor credit is approved in Bill.com and syncs to NetSuite, changes to the approval status will not sync.
  • If Bill.com’s “Sync only approved Bills/ Vendor Credits” preference is selected, vendor credits will not sync to NetSuite unless their Approval Status is Approved in Bill.com.
    • When vendor credits sync to NetSuite with this enabled, their NetSuite approval status will not be changed.
    • Once a vendor credit is approved in Bill.com and syncs to NetSuite, changes to the approval status will not sync.



 

Bill Payments

General

From NetSuite to Bill.com

From Bill.com to NetSuite

  • If a bill is paid outside of Bill.com, you should mark it as paid in Bill.com and allow that payment record to sync into NetSuite.
    • Recording the payment in NetSuite first will cause sync errors.
  • Payments made in Bill.com can be edited in NetSuite.
  • All users, regardless of their assigned role, have access to the View in Bill.com button in NetSuite
  • Bill Payments do not sync from NetSuite into Bill.com.
  • Bill.com does not support departments, locations, and/or classes on bill payments.
    • When bill payments sync from Bill.com to NetSuite, they will use whatever is set as the Default Payables classification in the Bill.com Preferences record.
    • To make it easier to reclassify these records (as needed), you can create a department, location, and/or class called “Unclassified”, or “Uncoded”, or something similar, and set that as your Default Payables classification.  This will allow you to run a report to isolate the bill payments that need to be reclassified.
    • A payment made in Bill.com can ONLY be voided in Bill.com
      • When a payment is voided in Bill.com, the void will sync to NetSuite.
    • Supported Payment Methods: 
      • Bank Account
      • PayPal
      • Checks
      • Vendor Credits




 

Purchase Orders

General

  • The purchase order record does not exist in Bill.com, and therefore cannot be viewed there.
    • When you create a bill from a purchase order in NetSuite, that bill will sync into Bill.com, with the Purchase Order number as a read-only field.  You can then pay that bill in Bill.com.
    • Do not edit the line items for these bills in Bill.com; doing so will unlink the bill from its purchase order in NetSuite. The Description field for the line item in Bill.com will indicate if the bill is connected to a purchase order in NetSuite.
  • The field PO Number on bills in Bill.com will populate with the bill's NetSuite Purchase Order number. Once a bill is connected via PO number, the bill should ONLY be edited in NetSuite, or errors will occur. 
    • This information is also available on a line item basis. 
      • Ex: Description: Linked to NetSuite Record - do not change account, item, or classifications.



 

AP Funds Transfers

From Bill.com to NetSuite

  • AP funds transfers sync to NetSuite as journal entries.
  • Bill.com does not support departments, locations, and/or classes on AP funds transfers.
    • When AP funds transfers sync from Bill.com to NetSuite, they will use whatever is set as the Default Payables classification in the Bill.com Preferences record.
    • To make it easier to reclassify these records (as needed), you can create a department, location, and/or class called “Unclassified”, or “Uncoded”, or something similar, and set that as your Default Payables classification.  This will allow you to run a report to isolate the AP funds transfers that need to be reclassified.



 

 

 

Version 2.0 October/2015

 

This document is supplied as and intended to be a reference document for users of Bill.com. The document is periodically updated and may contain data that does not apply to user’s specific product or that is obsolete. If questions exist regarding the applicability of the data relative to your product, contact Bill.com Customer Support.

Copyright © 2007-2016 Bill.com, Inc. All Rights Reserved.

No part of this document may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Bill.com, Inc.

Bill.com is a registered trademark of Bill.com, Inc.

All other trademarks, service marks, or registered trademarks appearing in this guide are the trademarks or service marks of their respective owners.

Have more questions? Submit a request
Powered by Zendesk