If you are using the subcontractor progress claim and not using the ERP version of Job to Date Costs, you may notice that your budget's Job to Date Costs do not match your subcontractor progress claim amounts. To understand why, read below.
Procore's previous version of the subcontractor billing tool, called Progress Claims, did not have the ability to bill variations by line item. Variations included in a Progress Claim were shown and billed as a single line item lump sum amount. When Procore released the current subcontractor billing tool, Subcontractor Progress Claims, variations added to an progress claim were required to be billed for by line item (and therefore, by cost code). However, for variations that were previously added to Progress Claims prior to updating the project to using Subcontractor Progress Claims, these variations remained as a single line item lump sum amount.
In the Budget tool, all items must be broken down by cost code in order to appear in the Budget. This includes the default Job to Date Costs column, as well as the optional Progress Claims column. Because the variations previously added to Progress Claims remained as a single line item lump sum amount and are not billed for by line item (and therefore, cost code), these variations amounts cannot appear in the Budget in the Job to Date Costs or Progress Claim columns. There is no way for Procore to determine the variation amount billed per cost code since these variations were billed for a lump sum amount.
How do I know if my project is affected?
Your project is affected if any of the following apply:
- Your project started with the Progress Claims tool and had variations to the Progress Claims.
Your project is not affected if any of the following apply:
- Your project started with Progress Claims tool, but did not have Progress Claim variations prior to switching to the Commitment Progress Claims (now Subcontractor Progress Claims) tool.
- Your project started with the Commitment Progress Claims or Progress Claims tool.
What should I do?
For affected projects, it is recommended that you create a second budget view (see Set up a New Budget View), remove the Job to Date Costs (and Progress Claims) column and apply that view to those projects. The Commitment Summary view, Custom Reporting and Progress Claims to Date report are not affected since they do not report Progress Claim values per cost code.