Best practices: Importing non-transaction records

Bill.com offers the option to import non-transaction records and data.

Non-transaction records

  • Vendors
  • Customers
  • Chart of Accounts
  • Departments
  • Items
  • Classes
  • Locations
  • Jobs

How the import works

The import works by checking Key Fields in Bill.com for a record to update. On the import preview page, the Action column will display if the line item will be a Create or an Update. If no matching record is found, the Action column will display Create, indicating a new record has been created. If more than one field is listed for a record, the Action column will display Update and both fields must match the record in Bill.com before the import attempts to update the record.

The import creates and updates records by checking the following Key Fields:

Vendor

  • Vendor Name*

Customer

  • Customer Name*

Chart of Account

  • Name*
  • Account Number

Department

  • Name*

Item

  • Name*

Class

  • Name*

Location

  • Location Name*
  • Location ID*
  • Parent Location ID

Job

  • Job Name*
  • Job ID*
  • Parent Job ID

Class

  • Class ID*
  • Parent Class ID

Things to know

  • Import non-transaction records before importing transaction records
  • Fields denoted by an asterisk are required
  • Make sure all Key Fields in the import file are unique. Otherwise, an error will occur For example, attempting to import multiple Vendors with the same Vendor Name will result in an error. When a record type has more than one Key Field, the combination must be unique. For example, you may have Accounts with the same Account Name as long as they have different Account Numbers.
  • If a field in the import file matches more than one record in Bill.com when creating or updating during an import, it will result in an error
  • If you leave a column blank in the import, it will ignore that field when importing
  • If an import fails, click the View link in the Action column to get more information and to download a CSV Error Report