If a record is not syncing between BuildOps and Spectrum, the fastest way to resolve it is to review the failed record and any available sync error details in BuildOps, then correct the related data or Spectrum setting. If the error details are unclear or missing, contact BuildOps Support.
In most cases, sync failures are caused by one of these issues:
The customer, job, or project has not fully synced yet
The invoice or PO date falls outside an open accounting period in Spectrum
A field exceeds Spectrum’s character or format limits
A department in BuildOps does not match the related cost center in Spectrum
A Spectrum or AppXchange setting is preventing the export
Before making changes, first review the failed record in BuildOps and check any visible sync status or error details.
The error message usually points to the field or setting that needs to be corrected.
Common fixes
Customer, job, or project has not synced yet
If an invoice, PO, or related record fails because the customer or job has not synced first:
Open the customer, job, or project in BuildOps
Click Edit
Click Save
This re-triggers the export to Spectrum. After that finishes, try syncing the dependent record again.
Invoice date is outside the open accounting period
If the invoice fails with a G/L date or processing date error:
Open the invoice in BuildOps and review the Issue Date
In Spectrum, go to System Administration > Installation > Processing Dates
Review the current, minimum, and maximum dates for Accounts Receivable
Update the invoice date in BuildOps so it falls within an open period
Retry the sync
If your team uses strict G/L period controls, you may also need to review the Spectrum setting Invoice Date must be in G/L period.
Job or contract cost center does not match the BuildOps department
If the department in BuildOps does not align with the related cost center in Spectrum, invoice sync can fail.
To fix this:
Open the job in BuildOps and note the selected Department
In Spectrum, go to Job Cost > Maintenance > Jobs
Find the matching job and verify the Cost Center
Update the BuildOps department or the Spectrum setup so they match
Retry the sync
Tax classification error on a job
If the error says the tax class code is invalid:
If the error says the tax class code is invalid:
In Spectrum, go to System Administration > Installation > Job Cost.
Review whether Utilize Tax Classification is enabled.
Check with your accounting admin before changing this setting, since this configuration depends on how your Spectrum environment is set up.
If your accounting admin or BuildOps Support confirms that a change is needed, update the setting and save it in Spectrum.
In BuildOps, open the job, click Edit, then Save to re-trigger the sync.
Descriptions or values are too long
Spectrum enforces field-length and formatting limits. Syncs may fail if values are too long or do not fit Spectrum’s required format.
Common examples include:
Customer Name over 30 characters
Customer Address Line 1 over 30 characters
Property Address Line 1 over 30 characters
Phone Number over 14 characters
State Code not using a 2-character abbreviation
Schedule of Values description over 30 characters
If a record fails to sync, shorten the affected value and try again.
Project cost code does not fit the Spectrum phase mask
If a project or cost code sync fails:
In Spectrum, go to System Administration > Installation > Job Cost
Review the Phase Number Mask
In BuildOps, update the project cost code so it matches that mask
Save the record and retry the sync
Item, GL account, or cost type mismatch
If a PO or receipt fails, the issue may be that the item’s GL account and cost type mapping in BuildOps does not match Spectrum.
To review:
In BuildOps, open the item and review the assigned GL Expense Account
In Spectrum, go to General Ledger > Maintenance > Master File
Review the allowed cost type for that GL account
Update the BuildOps line item or item setup so the cost type matches
Retry the sync
If you are not sure which GL account or cost type should be used, check with your accounting admin before updating item setup.
Product or item code formatting issue
If the error points to an item or product code:
Review the product or item code in BuildOps
Remove any extra spaces or invalid formatting
Save the record
Retry the sync
To reduce future sync issues:
Make sure customer, property, and project fields stay within Spectrum field limits
Keep department and cost center mappings consistent
Confirm invoice and PO dates fall within open Spectrum processing periods
Review item, GL account, and cost type mappings before exporting transactions
Check the affected record’s sync status first, then review the Sync Log for additional details if needed. If the reason for the failure is still unclear, contact BuildOps Support.