Billing Connect

Have more questions? Submit a request

What is Billing Connect?

Billing Connect allows TBP to import and export timekeeping from a PMS that is not directly connected via integrations (e.g., Aderant, 3E). The service allows firms to upload their timekeeping data (client matters, etc.) and receive exports of released timekeeping data on a daily basis.

TBP-Billing_connect-model-01.png

  • Billing Connect imports timekeeping data (client matters, timekeepers, codes, etc.) on a daily basis using TBP’s import format through a SFTP service.
  • Billing Connect exports released time (timekeeper, hours, narratives etc.) on a daily basis in TBP’s export format for firms to upload into their PMS through an SFTP service.

Billing Connect Import

Importing timekeeping data (clients, matters, etc.) into TBP is done through upload of several files via SFTP. Timekeeping data will be made available to timekeepers in TBP within 60 minutes from successful upload.

  • All files must be put into a single ZIP file named TBPBillingConnectData.zip
  • Import files must be formatted to instructions below for successful upload and be in UTF-8  standard. 
  • Uploads will be completed in an upsert manner for updating existing or adding new data.
  • Authorized administrators will receive email notifications on billing data upload status.

Please work with your Customer Success Manager and Solutions Engineer to ensure the data your timekeepers need for keeping time with TBP is supported.

Data

File Name / Type

Supported Mappings

Notes

Clients

clients.csv

-

Required.

Matters

matters.csv

Clients

Required. 

Codes

codes.csv

Matters

Not Required. These are the codes used at a matter and attached to time entries.
Currently, TBP supports:
phase, task, location, action, activity, and currency types and should be listed as such. 

Code Types

code-types.csv

   

Code Sets

code-sets.csv

   

 

Data: Clients

  • Filename: clients.csv
  • Filetype: Comma separated values (CSV)

The clients file provides all information related to clients that need to be available in TBP to your timekeepers. The file must be formatted with the constraints outlined below.

Column Name

Data Type

Description 

code

string

Required The client code. 

id

string

Required: The client code identifier (sometimes set as externalId); if no id is provided, it will be set to code.

displayName

string

Required: The client name text that should display in TBP. 

 

Data: Matters

The matters file provides all information related to matters that need to be available in TBP to your timekeepers. The file must be formatted with the constraints outlined below.

  • Filename: matters.csv
  • Filetype: Comma separated values (CSV)

Note: We do not support restricted matters for the Billing Connect solution at this time.

Column Name

Data Type

Description 

code

string

Required: The matter code that should display in TBP.

displayName

string

Required: The matter name text that should display in TBP. 

billingIncrement

decimal

Required: The matter increment for billed time (ie. 0.1, 0.25, etc.).

clientId

string

Required: Set to the id mapping to client, found in clients.csv (or previously uploaded into TBP). 

billingType

string

Required: Please set to Billable, Nonbillable, Probono

currencyCode

string

Not Required: An optional string for currency type (ie. GBP).

id

string

Required: The matter code identifier (sometimes set as externalId); if no id is provided, it will be set to code.

 

Data: Work Codes

The codes and code-types file provides all information related to billing codes that need to be available to be set in TBP to your timekeepers. The file must be formatted with the constraints outlined below.

  • Filename: codes.csv
  • Filetype: Comma separated values (CSV)

Column Name

Data Type

Description 

type

string

Required: The type of code being uploaded. Currently, TBP supports: phase, task, location, action, activity, and currency types and should be listed as such. 

code

string

Required: The task or phase code that should display in TBP (ie. 

description

string

Required: The description of the code. 

id

string

Required: A unique identifier for this code, sometimes known as an externalId. If none is provided, the id will be set to the code and must be unique for a successful import. 

mappingId

string

Not Required: If the code has a mapping, such as a Task being mapped to a Phase, the value of the id should be placed here. 

 

Billing Connect Export

As timekeepers use TBP to track and release their time, released time data will be made available to firms on a daily basis via an export file SFTP. 

  • Export files will be formatted to TBP’s standard.
  • The export will occur daily after midnight local time for your firm (set in firm configuration).
  • Export files will contain all columns even if not used (with empty or default values).
  • Days without released time will not have an export file available.
  • Export files will be available for 14 days before being deleted.

Please work with your Customer Success Manager and Solutions Engineer to ensure you are able to access the export files. Firms will be required to translate export data for their upload into the billing system.

Export File

The export file provides all information related to released time from timekeepers using TBP. Each file is formatted as laid out below. While all fields (columns) are exported, not all values will be filled depending on the TBP setup.

  • Filename: export_.csv
  • Filetype: Comma separated values (CSV)

Column Name

Data Type

Description 

uniqueEventId

string

Required: A 32 char UUID for each time entry to assist in IT administrative efforts
(ex.: 5dd8849f-ebc7-47f2-b400-28f4bbb8fc41 ).

transactionDate

datetime

Required: The date that the time entry was generated (createdOn) in ISO 8601 format
(ex.: 2019-09-07T15:50+00Z ).

timeSource

string

Required: A text noting the source of the time entry (ex.: “TBP”).

timekeeperId

datetime

Required: Timekeeper identifier for which the time entry is assigned (ex.: 1234).

timekeeperSource

string

Required: Timekeeper identifier for the time entry releaser (ex.: 4321). Usually this value is the same as timekeeperId but may differ in situations where a timekeeper has delegated their timekeeping to another person.

workDate

datetime

Required: The date that the work for the time entry was completed in ISO 8601 format
(ex.: 2019-09-07T15:50+00Z ).

clientCode

string

Required: The identifier for the Client assigned to time entry (ex.: 13200).

matterCode

string

Required: The identifier for the Matter assigned to time entry (ex.: 02728-0002).

durationIncrements

decimal

Required: The number of work increments assigned to time entry (ex.: 0.3 or 0.25).

narrativeText

string

Required: The narrative assigned to time entry in text format with encoding considered
(ex.: “Correspondence with Cpt. Lucard regarding Space matter”).

phaseCode

string

Not Required: The phase code assigned to time entry, in non-description format if possible
(ex.: L400).

taskCode

string

Not Required: The phase code assigned to time entry, in non-description format if possible
(ex.: L450).

actionCode

string

Not Required: The action code assigned to time entry (ex.: A108).

activityCode

string

Not Required: The activity code assigned to time entry (ex.:).

currencyCode

string

Not Required: The currency code assigned to time entry (ex.: ).

locationCode

string

Not Required: The location code assigned to time entry (ex.: NYC1).

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
  • Training

    An interactive tutorial to learn TBP in no time