Skip to main content

Procore and Spectrum Configuration Checklist

Below is a non-exhaustive list of configuration settings to consider during your Agave implementation. Work with your Agave representative to enable/change these settings.

Configuration Settings​

Budgets & Cost Codes​

Tiering​

Procore offers tiered Cost Code segments as an option for structuring your Cost Codes.

Agave can support up to 2 tiers, split in a format of your choosing. The character lengths of each tier must be consistent across projects. For more information, see Cost Codes.

Commitments​

Default Ledger Accounts​

Agave can set default GL accounts (one each for Purchase Orders and Subcontracts) that Agave will apply to commitment line items if no other GL account is found. See the Subcontracts reference for the priority with which GL defaults are applied.

Sync Procore POs as Subcontracts​

Some users prefer to sync Procore Purchase Orders to Spectrum as Subcontracts so that Spectrum will accept COs against them. They will still appear on the “Purchase Orders” screen in Agave, but will be synced to Spectrum as a Subcontract.

Numbering​

Spectrum only allows 10 characters on commitment numbers, whereas Procore numbers are often longer.

Agave Sync can automatically take the last N characters of the Procore commitment number to minimize errors. For example, if your commitment is SC-AG2501-001 and the setting is set to 10, the Spectrum commitment number will be AG2501-001.

If the Sync Procore POs as Subcontracts setting is enabled, this number must be 9 or less. The first letter will be P or S to notate which Procore commitment type it came from.

Change Orders​

Statuses​

Spectrum Change Request status options are user-defined and vary in functionality (see Spectrum's documentation). Agave allows setting default Spectrum statuses for each Change Order type (Commitment and Prime), and Change Requests will then be imported with those default statuses.

Commitment CO Numbering​

By default, Commitment Change Orders in Procore against different commitments can reuse the same number. To help avoid duplicate number errors and follow Spectrum’s character limit, Agave has a custom setting that will automatically use Spectrum-friendly numbering. See the Change Order reference for more information.

Billing Lines​

Agave has three options for how billing lines are synced into Spectrum from Prime Changes.

Invoicing​

Batch Code​

Agave Sync automatically sets a date-based batch number as part of invoice syncs. See the AR Invoice reference for how this is structured.