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.
This page gives an overview of the integration. Please see the associated child pages for further information:
Overview
The integration allows an agency to automatically synchronise front end data from the Bullhorn system into InTime for use in timesheets, expenses and invoicing.
...
The data required by InTime is similar in structure to that held in Bullhorn and the equivalent components are as follows:
Bullhorn | InTime |
Placement | Placement |
Candidate | Worker |
Company | Client |
Contact | Manager |
User | Consultant |
Job / Vacancy | Additional Placement data |
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.
...
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 for more information.
A selected InTime user will receive on-screen notifications of any problems that have occurred importing data from Bullhorn. There is also a screen for Admins 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. If there has been a problem importing a placement there is a link to try importing again.
...
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.