Sub Jobs (Project Tasks) and Cost Codes

Visual Mapping

Sub Jobs (Project Tasks)

The Tasks on the Project in Acumatica correspond to the Sub Jobs created within the project in Procore. See Default Project-Level Task for why Task "0000" is not included in this example.

Cost Codes

Project-Level Cost Codes

The full Acumatica Cost Code list is synced to the project in Procore.

Sub Job-Level Cost Codes

The full Acumatica Cost Code List is also synced to each Sub Job so it can be used for building Sub Job budgets.

Configuration Options

Default Project-Level Task

Since Acumatica requires Tasks on the Cost/Revenue Budgets and Procore does not, you can designate a Default Project-Level Task that Agave will treat as project-level rather than sub-job specific in Procore.

Example

In this sample project, Task "0000" is set as the Default Project-Level Task in Agave. Thus, it is not synced as a Sub Job:

When this project's Budget Line Items are synced between Procore and Acumatica (in either direction), the Sub Job is not included for Task "0000" on the Procore side, but is present in Acumatica:

Note the difference between a Budget Line Item for Task "0000" (blue) vs "Concrete" (red) in Procore. The Default Task is applied automatically when syncing Budget Line Items and other data types into Acumatica.

Setup

Consult your Agave rep to enable this setting. You can set one task code as the Default Project-Level Task across all projects in Agave. In the above example, you would use "0000" as the Default Project-Level Task across all Acumatica projects.

Tiering

Agave offers flexible settings for taking advantage of Procore's Cost Code tiering feature.

When this is enabled, Agave can break your Acumatica Cost Codes into tiers in Procore:

Consult your Agave rep to enable this setting; Agave can support up to 3 tiers.