Skip to main content

Job Costs

Agave Sync allows you to export ServiceTitan Labor, Material, and Equipment Job Costs to Vista JC Cost Adjustments.

Syncing Job Costs from ServiceTitan to Vista gives you a more complete picture of each Vista Job’s profitability.

note

Agave Sync exports Job Costs to Vista in a Posted status by default. If you would like to not post Job Costs, let your Agave Account Manager know.

Visual Mapping​

Equipment and Material Job Costs​

ServiceTitan and Vista Visual Mapping

Video Tutorial​

Equipment and Material Job Costs​

Common Errors and FAQs​

Are there any pre-requisites to syncing Job Costs?​

Yes:

  1. The Job associated with the Job Cost must be synced,
  2. A default Cost Code (Phase Code) must be applied,
  3. A default Cost Type (Cost Type) must be applied, and
  4. A default Offset GL Account must be applied.

Let your Agave Account Manager know which defaults you would like to apply for 2-4.

note

Your Agave Account Manager can set different default Cost Codes or Cost Types based on whether the Job Cost type is ‘Labor’ or ‘Equipment and Material.

Do I need to sync all types of Job Costs?​

No. You can choose to sync (1) Labor Job Costs and/or (2) Equipment and Material Job Costs.

You may choose to sync only Labor Job Costs if all Equipment and Material costs are already captured through Purchase Orders and AP Invoices synced from ServiceTitan to Vista.

Conversely, you may choose to sync only Equipment and Material Job Costs if you are already syncing Timecards from ServiceTitan to Vista.

Do I have to post Job Costs?​

No. Agave Sync exports Job Costs to Vista in a Posted status by default. If you would like to not post Job Costs, let your Agave Account Manager know.

If you opt to not post Job Costs, all Job Costs synced from ServiceTitan to Vista within a day will be added to the same Vista batch number.

Error 0070: Associated Job or Project is not Synced​

In the Errors tab, you might see an error message related to a Job or Project, typically shown as:

error
  • Associated Project is not synced: 25-12345

Causes​

This error occurs when the related Project hasn't been synced between systems. Common reasons include: the Project was never pushed or linked, or the destination system doesn't recognize or support the format of the Project.

How to fix it​

To fix this problem, follow these steps:

  1. Identify the record(s) you're trying to sync and note the associated Project.
  2. In Agave, navigate to the Project (or Job) module via the side panel.
  3. Search for the relevant Project or Jobs(s), then select and push them to your ERP.
    • If the Project or Jobs(s) already exist in your ERP, you may have the option to autolink them.
  4. Once the Project or Jobs(s) are pushed or autolinked, retry the sync.

Still having trouble?​

Contact Agave Support for help.