Intro: Integrating Bullhorn and Sage Intacct 

First published on: 05/09/2025/2:56 pm

 

The Basics

Vision33’s The Saltbox Platform is a cloud-native, low-code integration platform as-a-service (iPaaS) solution that empowers small and midsized companies to integrate disconnected systems like ERP, CRM, and eCommerce. 

 

Technology modules called connectors work with The Saltbox Platform to facilitate the integration.

 

This connector enables users to:

  1. Integrate Bullhorn and Sage Intacct
  2. Automate common transactions between applications (using ExpressConnect workflows)

 

These ExpressConnect workflows accelerate integration projects by getting data flowing between systems quickly. Workflows can then be customized to address business-specific processes and requirements. 

 

Bullhorn One - Sage Intacct ExpressConnect Workflows 

 

Update Sage Intacct

Changes in Bullhorn One are pushed to Sage Intacct

 

 

Finalizing and setting an Accounts Receivable Invoice to “Export” in Bullhorn One will:

  • Create or update the customer contact in Sage Intacct.
  • Create or update the customer in Sage Intacct.
  • Create an Accounts Receivable Invoice in Sage Intacct.

 

Update Bullhorn One

Changes in Sage Intacct are pushed to Bullhorn One

 

 

Create a payment for each paid Sage Intacct invoice in Bullhorn One when an AR payment for previously imported Bullhorn invoices is created in Sage Intacct 

 

 

 

 

 

 

 

 

 

 

Click here for workflow details.

 

 

Don't see what you're looking for?

These workflows can be customized or new workflows can be created to address your unique requirements.

 

Contact us to start the discussion.

 

How Long Does It Take To Build an Integration? 

It takes approximately 16 weeks from project kickoff to completion to build a standard integration (with limited customizations).

 

This timeline could be extended if:

  • Requirements aren't well defined or change mid-project
  • Client availability or subject matter knowledge is limited
  • The project isn’t prioritized
  • The applications being integrated aren't live
  • Data quality is poor

 

If we avoid these pitfalls, the project could be completed early.

 

What Does a Typical Integration Project Look Like? 

A typical Saltbox integration project follows this process:

 

  • Vision33 sets up (provisions) your instance of Saltbox, your account, and the workflow(s) you purchased.
  • Vision33 leads a collaborative mapping session to review the purchased workflows and how the affected data will map between the integrated applications. A templated document, aka a blueprint, is updated to document the workflow settings and revised mappings. 
    • Vision33’s implementation team uses this document to instruct the implementation.
  • The blueprint is sent to you for signature.
  • You assess and prepare third-party and/or Sage Intacct data quality to ensure it’s ready for integration.
  • You perform user acceptance testing (UAT) with support from your Vision33 delivery team.
  • Together, we do a final project review and user acceptance testing sign-off.
  • Vision33 migrates the project to the production environment, and it goes live!
  • The completed project enters Hypercare, a two-week monitoring period to catch issues.
  • The Vision33 implementation team performs a soft transfer to the TOTAL Care customer support team, who will support you should issues arise.

 

The Integration Project Team 

Vision33

Client
  • A Delivery Manager will be your point person. They'll manage the project and guide you through the rollout from start to finish.
  • Saltbox Implementation Consultant(s) will create your Saltbox project, configure the workflows, provide training, and assist with testing and Hypercare.

Your project team should include:

  • A Sage Intacct Administrator or someone who is technical and familiar with your Sage Intacct setup.
  • An Administrator for your third-party solution or someone who is technical and familiar with your third-party solution's setup.
  • Someone with an intimate understanding of business operations, how your systems are structured, how your company uses those systems, and how they want to use them after the integration.

 

 

Licensing and Technology Requirements

Sage Intacct

Sage Intacct integration projects require:

  • A Sage Intacct Application account 

  • A Sage Intacct Web Services account 

  • Authorization for Vision33 Sage Intacct sender ID ‘Vision33MPP’ to make web services API requests to the Sage Intacct company

  • Giving Vision33 access to the sandbox and production sites for Sage Intacct

 

(Vision33 can support these requirements for an additional fee.)

 

Bullhorn One

To enable the integration, the client must provide Vision33 with access credentials for both the sandbox and production environments of Bullhorn One’s API. The following credentials are required:

  • client_id
  • client_secret
  • username
  • password

 

Additionally, the client is responsible for requesting the addition of the Saltbox Redirect URI in both environments. This request should be made directly with Bullhorn Support and can be submitted alongside the request for the credentials listed above.

 

The API user associated with the provided credentials must have appropriate entitlements, including but not limited to:

 

  • Read access to Invoices and all related entities such as:
    • Bill Master Transactions
    • Billable Charges
    • Placements
    • Companies
    • Contacts

 

  • Write access to:
    • Create invoice payments
    • Apply credits to invoices

 

Proper entitlement configuration is essential to ensure successful interaction with the Bullhorn One API.

 

Version Support

Vision33’s ExpressConnect workflows support any Bullhorn One version providing a REST API.

 

Vendor API Changes

This section outlines how we handle vendor API changes and customer responsibilities:

  • Vision33 uses APIs to exchange data between third-party applications and The Saltbox Platform.
  • Occasionally, third-party vendors release API changes with little to no warning, which can lead to failed integration(s).
    • Vision33 is not responsible for changes third-party vendors make to their software or APIs or the impact of those changes on your business. Should an unplanned change occur, we will do our best to minimize the effect on your business.
  • We regularly monitor API release notes for planned changes and, when announced, assess and communicate their impact to all customers with active integrations. 
  • If work must be completed to eliminate disruption to your integration(s), Vision33 will provide a scope of work, next steps, and cost estimate.
    • Work will not begin without your explicit consent, and timing will be coordinated in advance with you.
  • Additional costs could apply to both planned and unplanned vendor API changes. 
  • Any work and related costs must be approved in writing before work can begin.

 

Required Skill Set for Self-Implementation of Starter Workflows

Self-implementation requires a working knowledge of:

  • XML
  • The ERP system (queries, custom/user-defined fields, etc.)
  • The third-party application
  • Data types
  • Data transformation
 - this needs to be redone to include Saltbox Success Assurance program

 

 

 

 

 

 

Next

  

Last modified: 05/14/2025/5:56 pm

On this page

-