BQE Core Integrated Data

What this page covers: A complete reference mapping every BQE Core field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.


Integration type	Cloud (BQE Core API)
Setup complexity	Low
Configurable fields	Bill rate override, phase archiving, inactive phase status
Prerequisite	BQE Core Integration Setup

How Data Flows

BQE Core (BQE Core API) → Mosaic Sync Engine (field mapping) → Mosaic (11 synced data types)

Mosaic pulls data from BQE Core using the BQE Core API. Members, clients, projects, phases, activities, time entries, roles, and rate information are mapped into Mosaic's data model.

Integrated Data Types

The integration syncs 11 data categories from BQE Core into Mosaic:

Data Type	Description
Members	Member records with name, email, and active/archived status
Standard Roles	Role definitions derived from member titles
Member Roles	Default role assignment per member
Member Project Roles	Member-to-project role assignments from project staff classifications
Clients	Client records (name, description, status)
Projects	Project records (name, code, fee, dates, billable status, project status)
Phases	Phase breakdowns under projects (name, code, fee, dates, billable status, phase status)
Work Categories	BQE Core activity items synced to Mosaic for time categorization
Time Entries	Time records (hours, date, billability, rate, comments, approval status)
Member Bill Rates	Member-level billing rate entries with effective date ranges
Member Cost Rates	Member-level cost rate entries with effective date ranges

This list may expand as new features are added.

Not Synced

Data Type	Description
Office / Region	Geographic or office classifications on members or projects
Department	Member department assignments
Rate Groups	BQE Core rate tables are not synced as Mosaic rate groups
Project Manager	Project Manager assignment is not pulled from BQE Core

Reading the Field Mapping Tables

Symbol legend for technical tables

The Technical Reference tabs below use a shorthand notation for API sources. Read this legend before reviewing the mappings.

Symbol	Meaning	Example
`.`	API object field reference	`Employee.FirstName` = the FirstName field from the Employee object
`>`	Fallback priority — use the first available value	`Project.CompletedOn` then `Project.DueDate` = use CompletedOn; if null, use DueDate

Members

What Syncs to Mosaic	Where It Comes From in BQE Core
Member ID	The unique BQE Core employee identifier
First Name	The member's first name
Middle Name	The member's middle initial
Last Name	The member's last name
Email	The default email address from the member's address record
Is Active	Whether the member's status is Active
Is Archived	Members with any status other than Active are archived
Created Date	When the member record was created in BQE Core
Modified Date	When the member record was last updated in BQE Core

Standard Roles

What Syncs to Mosaic	Where It Comes From in BQE Core
Role ID	A unique identifier derived from the role title
Role Name	The member's title from BQE Core

Roles in Mosaic are sourced from BQE Core member titles. Each unique title becomes a Standard Role in Mosaic.

Member Roles

What Syncs to Mosaic	Where It Comes From in BQE Core
Member Role ID	The member's BQE Core employee identifier
Member	The member this role assignment belongs to
Role	The member's title from BQE Core
Override Member Roles	Whether this assignment overrides existing Mosaic roles (default: off)

Member Project Roles

What Syncs to Mosaic	Where It Comes From in BQE Core
Member Project Role ID	A composite of the member, project, phase, and classification
Project	The project the assignment is for
Phase	The phase the assignment is for (when the assignment targets a phase)
Member	The member assigned to the project or phase
Role	The classification (role) assigned to the member on the project staff list
Start Date	The start date of the project assignment
Created Date	When the assignment record was created in BQE Core
Modified Date	When the assignment record was last updated in BQE Core

Clients

What Syncs to Mosaic	Where It Comes From in BQE Core
Client ID	The unique BQE Core client identifier
Client Name	The client's display name
Client Description	The client memo/description
Is Archived	Clients with any status other than Active are archived
Created Date	When the client record was created in BQE Core
Modified Date	When the client record was last updated in BQE Core

Projects

What Syncs to Mosaic	Where It Comes From in BQE Core
Project ID	The unique BQE Core project identifier
Project Name	The project name
Project Number	The project code
Description	The project memo
Client	The client linked to the project
Billable Status	Determined by Contract Type — Marketing and Overhead are not billable; everything else is billable
Project Status	Mapped from BQE Core project status (configurable mapping — see Project Status Mapping)
Is Archived	Projects with status Canceled or Inactive are archived
Fee	The project's contract amount
Start Date	The project start date
End Date	The completed-on date if present, otherwise the due date
Created Date	When the project record was created in BQE Core
Modified Date	When the project record was last updated in BQE Core

Project Status Mapping

BQE Core project statuses map to Mosaic project statuses using the following defaults. The mapping is configurable in your integration settings.

BQE Core Status	Default Mosaic Project Status	Default Mosaic Phase Status
Active	Active	Active
Completed	Complete	Complete
Hold	Hold	Hold
Inactive	Hold	Not Started
Canceled	Hold	Not Started
Draft	Proposal	Not Started

Phases

What Syncs to Mosaic	Where It Comes From in BQE Core
Phase ID	The unique BQE Core phase identifier
Phase Name	The phase name
Phase Number	The phase code
Parent	The parent project or parent phase
Project	The root project the phase belongs to
Client	The client linked to the phase's project
Order	The phase order within its parent
Billable Status	Determined by Contract Type — Marketing and Overhead are not billable; everything else is billable
Phase Status	Mapped from BQE Core project status (see Project Status Mapping). Inactive phase status is configurable.
Is Archived	Configurable — phases with status Canceled and/or Inactive can be archived (see settings)
Fee	The phase's contract amount
Start Date	The phase start date
End Date	The completed-on date if present, otherwise the due date
Created Date	When the phase record was created in BQE Core
Modified Date	When the phase record was last updated in BQE Core

Phase Archive Settings

Two configurable options control which phase statuses are archived in Mosaic:

Archive canceled phases — phases with status Canceled are archived

Archive inactive phases — phases with status Inactive are archived

Both options can be enabled, disabled, or combined.

Work Categories

What Syncs to Mosaic	Where It Comes From in BQE Core
Activity ID	The BQE Core activity item identifier
Activity Code	The activity item code
Activity Name / Title	The activity item description
Is Billable	Whether the activity is marked billable in BQE Core
Created Date	When the activity item was created in BQE Core
Modified Date	When the activity item was last updated in BQE Core

Time Entries

What Syncs to Mosaic	Where It Comes From in BQE Core
Time Entry ID	The unique BQE Core time entry identifier
Date	The date of the time entry
Member	The member who logged the time
Project	The project the time was logged against
Phase	The phase the time was logged against (when the entry targets a phase)
Work Category	The activity item used for the time entry
Hours	The actual hours logged
Description	The time entry description
Billable	Whether the time entry is marked billable
Hourly Rate	The bill rate on the time entry
Status	Approval status — Not Submitted, Submitted, Approved, or Rejected
Created Date	When the time entry was created in BQE Core
Modified Date	When the time entry was last updated in BQE Core

Approval Status

Mosaic uses the most recent workflow event on the time entry to determine status: Submitted maps to Submitted, Approved to Approved, Rejected to Rejected, and Unsubmitted/Unapproved to Not Submitted. If no workflow events exist, the status is Not Submitted.

Member Bill Rates

What Syncs to Mosaic	Where It Comes From in BQE Core
Bill Rate ID	A composite of the member identifier and the rate's start date
Member	The member the bill rate applies to
Rate Amount	The bill rate amount
Rate Description	Auto-generated as `<First Name> <Last Name>'s Bill Rate - <Start Date>`
Start Date	The effective start date of the bill rate
End Date	The effective end date of the bill rate
Override Bill Rates	Whether this bill rate overrides existing rates in Mosaic (configurable)

Override Bill Rates Setting

By default, BQE Core bill rates are added without overriding existing Mosaic rates. The isOverridingBillRates setting can be enabled to overwrite existing Mosaic bill rates during sync.

Member Cost Rates

What Syncs to Mosaic	Where It Comes From in BQE Core
Cost Rate ID	A composite of the member identifier and the rate's start date
Member	The member the cost rate applies to
Hourly Rate	The cost rate amount
Rate Type	Always Hourly
Description	Auto-generated as `<First Name> <Last Name>'s Cost Rate - <Start Date>`
Start Date	The effective start date of the cost rate
End Date	The effective end date of the cost rate

Configurable Fields at a Glance

The following fields can be configured during integration setup. Refer to your integration settings to see which option is active.

Entity	Field	Available Options
Project / Phase	Status Mapping	Configurable mapping from each BQE Core status to a Mosaic status
Phase	Inactive Phase Status	When BQE Core status is Inactive or Canceled, override the Mosaic phase status
Phase	Archive Behavior	Archive canceled phases, archive inactive phases, or both
Member Bill Rate	Override Existing Rates	Whether incoming bill rates overwrite existing Mosaic rates (default: off)

Troubleshooting & FAQ

Why isn't a member's role showing up in Mosaic?

Roles in Mosaic come from the BQE Core member's title. If a member has no title set in BQE Core, no role will be created. Review the member's record in BQE Core and ensure a title is set, then run a sync.

Why is a project showing as "Not Billable" in Mosaic?

Projects and phases marked as Marketing or Overhead in BQE Core are synced as Not Billable in Mosaic. All other contract types are synced as Billable. To change a project's billable status, update its Contract Type in BQE Core.

Why isn't a canceled or inactive phase archived in Mosaic?

Phase archiving is controlled by the Archive canceled phases and Archive inactive phases settings. If neither is enabled, those phases will sync as active in Mosaic. Contact your Mosaic Solutions team to update these settings.

Why is a member's email blank in Mosaic?

Mosaic uses the email from the member's default address record in BQE Core. If the default address has no email communication, the member will sync without an email. Ensure the default address has an Email entry.

I need a data source or field that isn't listed here.

Any integration not listed in this documentation is considered a customization and is charged at an hourly rate. For more information, see Integration Requests.

BQE Core Documentation Links

A consolidated reference of all BQE Core documentation referenced in this guide:

Topic	Link
API Explorer	BQE Core API Explorer
BQE Core Help	BQE Core Support