In-Bound Data Feeds

Chrome River accepts file feeds for many different types of data

Chrome River provides admin tools to manually enter company / organization data, such as:

  • People
  • Allocation (matters)
  • Entities (data lists)

However, most companies / organizations elect to automate the population and maintenance of data into Chrome River. One way of accomplishing this is via data feeds.  Data feeds are specifically formatted files that are transmitted to your Chrome River secure FTP site. Chrome River retrieves the files from the FTP site on a recurring basis and loads the data to the Chrome River database.

​There are specific file layouts for each type of data feed.  The Chrome River Data Feed Specifications document (below) provides details for creating all feeds accepted by Chrome River:

Chrome River Data Feed Specifications:

General Information about Feeds can be found below:

File Format Plain text encoded in UTF-8 or ISO_8859_1 format
File Name


File name is case sensitive—it must be capitalized as shown above.   QA references apply only if your organization is subscribed to UAT

Naming Variables

Environment: qa or prod
CustomerCode: Customer Code assigned by Chrome River
YYYY: Year
MM: Month
DD: Day 
HHMM: Time in hours/minutes in 24-hour format


Pipe-delimited file.

File Data Delimiter

- There should be a pipe character ('|') between all data fields and should include all optional fields whether they include data or not. Any column in RED is "REQUIRED" to have data. All other columns can be empty but still need delimiters for placeholders.

- The first row of each file should include a pipe-delimited list of the column names.

- Each new record should be on a separate row.

- The last column should have a pipe after it.

File Transfer

1) Log in to the Chrome River FTP site via SFTP at the appropriate address:
C1 Production/QA – s

C3 Production – s
C3 QA – s

C5 Production – s
C5 QA – s"
2) Change to the directory named "files"
3) Upload the data file to this directory via ASCII mode
4) After the file transfer is complete, upload an acknowledgement “trigger” file that has the same filename with an "ACK" extension. This can be an empty file.  (Note that the Matter Filters feed should NOT be sent with a .ACK file.)


File Contents Consult the individual feed spec to understand whether the feed is a Full Feed type or an Incremental type. If the feed spec mentions that "a full list" of values must be provided, this indicates that the feed is a full feed type and will do a complete replacement of the data type within Chrome River with the contents of the file.

For your convenience, we have provided template spreadsheets in the data feed spec for our most common data feeds and some other additional ones (below).

  • Person Feed - Populates company / organization employees (users of Chrome River and/or employees selectable as internal guests on expense line items)
  • Allocation (Matter) Feed - Populates a set of "cost objects" that line items can be charged to
  • Entity Feed - Populates various data "lists" defined in Chrome River
  • Paid Expense Feed -  Updates payment status of expense reports processed through the customer's financial system

To use the templates, simply type values into the spreadsheet columns and properly formatted records will be generated at the end of each row. You may include the generated records in your data feed:

 Person Feed Template

 Allocation (Matter) Feed Template

 Entity Feed Template

 Paid Expense Feed Template

 Invoice Vendor Feed Template

 Paid Invoice Feed Template

Share this