General Contractors and the owners can use the 'History' screen to review logs of all approved SOVs, including those submitted by subcontractors as well as those submitted directly by the GC. This screen provides access to the full details of any previously submitted SOV for comprehensive review and reference.
To view SOV logs
- Open the 'SOV' > 'History' screen of the project. To do so:
- Ensure that you are on the management console of the project
- Click the app launcher on the top-right and select 'Finance'
- Click 'SOV' on the top, then select 'History' from the options on the left
The list shows the SOVs generated so far with details:
- Billing Period - The SOV generation date, that is, the last date of that billing cycle. Click the date to view the list of SOVs submitted on that date.
- Total Amount - The total gross billable amount of that billing period less retainage. This includes the sum of total amounts for all contractors.
- Retainage - The amount retained from the total gross billable amount of that billing period as per the agreed SOV terms from all the contractors.
- Unused Material - The dollar value of the materials in stock on that billing date.
Search and filter options:
- Use the 'Search' box located at the top left to find a change order using any value from the table as search criteria
- Right-click the column header and customize the display and order of the columns as you wish
- The options at the top right allow you to filter the entries, create nested groups of entries, and manage personalized and customized views of the table. Use the links below to learn more about these:
- Click on a specific month to view the list of SOVs received for that billing period.
- The received SOVs from contractors will open as a list in the 'Current Month' screen for easy access.
- GC only - Select a contractor's name from the list to view the detailed SOV submitted by that contractor for the selected month.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article