Combining the RSM cloud solution InTime with Bullhorn, via webservices, provides a seamless integrated and scalable solution that will streamline processes, automate key tasks and provide greater visibility and control across your entire operations. The below examples display InTime’s unique integration with front office provider Bullhorn.  

Overview

The integration allows an agency to automatically synchronise front end data from the Bullhorn system into InTime . No Data is passed from InTime back to Bullhorn but it is possible to view an InTime summary of the placement, client or worker including recent timesheets, expenses and invoices within Bullhorn using the InTime tab.

Please see attached client Integration guide:-

 Bullhorn InTime Client Integration Guide 2.0.pdf

Editable version (.word) - HERE

Bullhorn InTime Dashboard Screenshots

Candidate View

Image Removed 

Company View

 Image Removed

For further details please contact Support@in-time.co.uk 

Please note this Integration module carry's a chargeable set-up fee.for use in timesheets, expenses and invoicing. The following pages describes this capability and how to configure the systems. The interface operates using Bullhorn’s SOAP Web Service API.

In order to use this integration you must have an active license agreement with both Bullhorn and InTime and should check with Bullhorn to determine if web services integration is available in your contract. Configuration of both systems is required in order to activate the integration so both suppliers need to be informed in advance that the integration is required so it can be planned in.

The data required by InTime is similar in structure to that held in Bullhorn and the equivalent components are as follows:

How it works

Data is only transferred from Bullhorn to InTime, never from InTime to Bullhorn. When something is changed in Bullhorn it creates an “event”. The InTime system checks Bullhorn every minute to see if any new events exist. If there are new events, InTime reads in the updated information from Bullhorn.

Not all of the placements in Bullhorn will be imported into InTime – only the ones that are going to go live and need timesheets and invoices. It is the placement “Status” field that determines if the placement is imported and only the users, candidates, contacts and companies that are associated with a valid placement are imported.

There are certain fields for each placement which must be populated and correctly formatted for a successful import because they contain data that is mandatory for InTime. These fields are identified later in this document. Additional fields and data can also be imported if required. These are called customisations and have to be specifically configured on your system.

The InTime “Ref Code” for an item imported from Bullhorn will be in the format “BH-n“ where n is the Bullhorn ID Number. This is how InTime associates the item with the correct Bullhorn item and is therefore mandatory. You can use this to visually cross-reference items in the two systems. This also means Automatic Ref Code Generators can not be used for clients, placements, managers, consultants or workers in InTime. This should not be a problem unless you have been using them in InTIme prior to integrating with Bullhorn. InTime support can assist with this.

Although no data is passed from InTime back to Bullhorn it is possible to view an InTime summary of the Placement, Client or Worker including recent timesheets, expenses and invoices from within Bullhorn using Custom tabs. See the section on InTime Summary views below.

A selected InTime user will receive on-screen notifications of any problems that have occurred importing data from Bullhorn. There is also a screen to view all Bullhorn update events that InTime has received along with the status message. This is accessed from the Batch Operations -> Bullhorn Updates menu.

In normal conditions you should expect any Bullhorn updates to be reflected in InTime within a couple of minutes. If you have any kind of bulk import or update utility for Bullhorn it can result in a large number of updates in a short space of time, this means it can take longer for updates to be reflected in InTime.