25.9.2 Release Notes

• Improved functionality for creating contract schedule of values claims – You can now convert a schedule of values payment claim with a 0.00 value to a contract schedule of values claim. This provides more flexibility by allowing you to select zero-value certified schedule items before converting to a contract claim.

• Document generation collection table can support 300 rows in a single table – The document generation process has been optimized to now support more than 300 rows in a collection table, ensuring more efficient document creation for users.

• Import truncates description field to allowable character limit instead of blocking import with errors – The Schedule of Value import now properly truncates descriptions that exceed the character limit, allowing the import to proceed smoothly.

25.9 Release Notes

General release is available starting 27-OCT-2025

• Configure placeholder documents in Supporting documents – You can now specify placeholder documents in the Supporting documents configuration by document type and subtype. To support this enhancement and to provide additional flexibility when configuring supporting documents, the Supporting documents set up has been moved to the Contract type configuration set up page (organization Settings > Configurations > Contract type configuration setup). The previous Supporting documents configuration has been removed from the Configurations list. Any settings from previous releases have been migrated to the new configuration. Read more

  The Define Supporting documents requirements section has been added to the Contract type configuration page. The new section consolidates configurations by document type or subtype, so you do not have to set up default locations and requirements for publishing and approval status for each event.

  

  For each contract type, you can click Manage Documents to select the document types and subtypes you want to require.

  

  In the Define supporting documents requirements grid, you can specify default locations, such as a contract, vendor change order, or payment form for each document type or subtype.

  When you create one of the named items, the Supporting documents page automatically shows blank lines for each of the selected document types and subtypes as placeholders. A yellow warning triangle shows as a visual reminder that the document is a default document type.

  

  You can then add and then edit the document or click the link in the hover text to add document information and the file or link.

  

  The Define Supporting documents requirements section also lets you specify whether a document is required for workflow or publishing and if the document approval is required. Document type placeholders that are required for workflow or publishing cannot be removed from the Supporting documents page.

  The Edit supporting document dialog box has been updated so that you can add documents from your computer, the Supporting document list, or from InEight Document.

  For more information about placeholder configuration, see Contract type configuration setup. For information about adding a document to a placeholder, see Supporting documents.

• Schedule of values Valid from and Valid through dates – The Valid from and Valid through fields have been added to the schedule item details, so you can restrict use of the schedule item based on chosen dates. Read more

  

  When you associate a schedule of values item to a line item, the schedule item's valid from and valid through dates automatically default to the line item's valid from and valid through dates. You can edit the dates as needed, but the schedule of value item dates must be within the associated line item valid from and valid through dates.

  Any claims or payment claims using the schedule item must post within the schedule item's valid from and valid through dates.

  Valid from and Valid through columns have also been added to the Schedule of values register.

  The Valid from and Valid through dates have been added to the import template for all schedule of values imports.

  For more information about the Valid from and Valid through fields, see Schedule of values tab. For more information about contract claims, see Claim schedule items from Contract.

• Schedule of values import calculation history – The import calculation has been added to the Schedule of values import History tab, so you can quickly see the calculations used in previous imports. Read more

  

• Schedule of values date restriction – You can no longer use dates prior to 01 January 2000 in the Schedule of values module.

• New diversity participation tags – Tags for the fields in the Diversity participation section of the contract header have been added to the general tags and collection table tags lists. A collection table has been added for the Category, Percent, and Comments fields.

• Associate unassigned change items to a change order – The Unassigned Change items dialog box that shows when you click the Unassigned changed item total now includes the option to associate unassigned changed orders to a new, existing, or executed vendor change order. Read more

  A new check box and the Associate button have been added to the Unassigned Change items dialog box. To associate a change item, select the check box for the item, and then click Associate.

  

  The Associate change item dialog box opens where you can associate the change item to a new or existing unpublished vendor change order.

  

  If you have the permission Edit executed vendor change order details (Permissions > Contract > Contracts > Edit contracts), you can select Executed to view a list of executed vendor change orders. Using the Executed option can be helpful when a change order was executed without the change items, and you want to come back later to reduce the value of the unassigned change items and assign any items that were missed.

  Also, if you have the Edit executed vendor change orders details permission, you can assign unassigned items or change other information on the Details page of the executed vendor change order. Previously, the Vendor change order type was the only field that could be changed after execution.

  For more information about unassigned Change items, see Vendor change orders.

General release is available starting 25-AUG-2025

• Vendor payment claims – Vendors can now submit payment claims directly into Contract from the Vendor contract summary page. Read more

  The Payment claims section has been added to the Vendor contract summary page. This section lets vendors add payment claims to Contract. Vendors also use this section to view comments on existing payment claims.

  

  For information about the Vendor contract summary page, see Vendor contract summary page.

  The vendor clicks the Add icon to add a new payment claim. The vendor's Payment claim details page opens, where they enter the payment claim description, the dates of the work completed, the date of the payment claim, and comments. The Payment claim ID is set to New and is not editable.

  

  After the vendor saves the payment claim, they can enter new or existing schedule of value items on the Schedule of values tab. Existing schedule items are pulled from the parent contract. The vendor can see the submission in their Schedule of values register and can edit values in the Vendor submission section.

  

  Any schedule item added by a vendor is automatically hidden in InEight Plan and InEight Progress. The Contract user can edit the schedule item to make it visible in Plan or Progress if applicable.

  The invoices tab lets vendors add and edit invoices. Vendors can submit invoices from the invoices tab or when they submit the payment claim.

   

  

  When the vendor user is ready to submit their payment claim to Contract, they can click the Submit button. Any invoices that are in the Draft state are automatically submitted, and the invoice status is set to Pending. The vendor can recall the submission if they find they have made a mistake if the Contract user has not received the payment claim or sent it back to the vendor.

  For the Contract user, the project Payment claims and Invoices tabs show a badge noting the number of new items when there are submitted invoices or payment claims that require attention.

  

  The Send to vendor and Received buttons have been added to the Payment claims page. If the new Payment claim is satisfactory, click the Received button to let the vendor know it has been received. If the payment claim needs some attention from the vendor, click the Send to vendor button. The claim is sent back to the vendor, where they can make changes and resubmit it.

  After the claim has been accepted, the claim is given a numeric ID instead of the New ID.

  When you certify the payment claim, the schedule of values is no longer editable by both the Contract user and the vendor. The vendor can still add invoices.

  The Vendor claim status has been added to the Payment claims register. The Payment claim status can be Pending, Recalled, Received, Returned, or Certified.

  The Date History section has been added to the Payment claim details for both Contract and the vendor, so you can see each exchange between you and the vendor. This information can be exported to a Microsoft Excel spreadsheet.

  For more information about vendor payment claims functions, see Payment claims functions. For information about working with vendor-submitted payment claims, see Working with vendor-submitted payment claims.

• Schedule of values enhanced single grid view – The Schedule of values page has been updated to have the same look and feel as the Line item page, including color coded column sections. The new page layout also improves performance when loading or scrolling the Schedule of values register. Read more

  The page includes the Schedule of values single grid toggle that lets you switch between the new layout and the layout from previous releases.

  

  Color coding is consistent with the color coding on the line items tab. For more information about managing the register, see Schedule of values column management.

• Schedule of values section updates – The Change orders section of the Schedule of values page has been renamed Changes to be consistent with the Line items page. Also, the Manual adjustments column has been added to the Changes section, so you can quickly see the total of all value changes made without a vendor change order after the contract is published. In the Schedule of values items section, the new Original value column shows the value of the item when the contract was published. Read more

  Prior to publishing the contract, the Original value column shows the current value. Publishing captures the current values as the original value. If you add a new schedule item after the contract is published, the new item will have the Original value column set to 0, and the Manual adjustment column set to the amount of the new schedule item.

  For more information, see Schedule of values register.

• Add invoices to a certified payment claim – If you miss adding an invoice to a payment claim before it was certified, you can now add it after certification. You can also edit invoices after certification if they are not on a submitted payment form or if the payment form is approved or in any approval workflow. For more information, see the Payment claims and Certification topics.

• Maximum Schedule value change without a change order setting – You can now specify the percent at which a schedule of values item can be updated before a change order is required. The new setting Maximum Schedule value change without a change order has been added to organization Settings > Configurations > Contract type configuration setup. Read more

  The setting shows only when the Use schedule of values for this contract type field is set to Yes.

  

  The setting validates both increases and decreases made to the schedule item. When you set a percentage and you make a change that exceeds the threshold, an error shows, and you cannot save the schedule of values until you are within the threshold.

  If you want all changes to require a change order, enter 0 in the field. If you want to allow all changes without a change order, select the Unlimited check box.

  For more information, see Contract type configuration setup.

• Export data from Line items Progress, Payment forms and Changes drill-down views – You can now export data from the Progress, Payment forms, and Changes views of the Line items tab to a Microsoft Excel spreadsheet to give you easier access to data. Read more

  The Excel format makes it easy to scroll through the data if you are looking for discrepancies.

  The Export icon has been added to the toolbars on the Progress, Payment forms, and Changes drill-down pages.

  

  To export, select an item from the drill-down view and then click the Export icon. The data is exported to an Excel spreadsheet.

  

  If there are multiple grids in the drill-down view, for example, the Progress drill-down view has grids for invoice receipts and goods receipts, the Excel spreadsheet shows the data on separate tabs.

  For information about exproting from drill-down views, see the Line items register topic.

• Vendor change order effective date defaults to current date – When you add a vendor change order, the effective date field now defaults to the current date. You can change the date as needed.

• Payment claim Contract line item ID – The Contract line item ID column has been added to the Payment claims Schedule of values register, so you can quickly see the line item associated with the Schedule of values item.

• Import and export template drop-down lists – Drop-down lists for the Schedule item ID and Contract line item ID fields have been added to templates for line item and schedule of values imports, so you can quickly select an ID instead of entering it manually. Read more

  The Schedule item ID drop-down list has been added to the VCO import and the imports for Schedule of values payment forms and payment claims.

  The Contract line item ID field was added to the following import templates:

  • Contract Schedule of values

  • Vendor change order Line item

  • Vendor change order Schedule of values

  • Payment form Line item

  • Payment claim Schedule of values

• Contract register Schedule of values columns – The Schedule value column on the main Contract register has been renamed Current schedule value. The Original schedule value column has been added to show the original value of the Schedule of values at the time the contract was published.

• Line items page standard view removed – The Line items page now shows in the enhanced single grid view only. The old standard grid is no longer available, and the Line item single grid toggle has been removed from the Line items page. For information about managing the line items page, see the Line items column management topic.

Contract 25.7.2 Release Notes

• Custom labels show in line item import template – The Line item import template was updated to show the custom labels for fields that have custom labels associated and turned on for project-level use. Showing custom labels makes it easier for you to identify the columns and enter the applicable data.

• Improved functionality for creating contract schedule of values claims – You can now convert a Schedule of values payment claim with a 0.00 value to a Contract schedule of value claim. This provides more flexibility by letting you select zero value certified schedule items before converting them to a Contract claim.

General release is available starting 23-JUN-2025

Updated 18-JUL-2025

• Copy contract level schedule of values – You can now copy schedule of values items on the contract Schedule of values page. Read more

  The Copy icon has been added to the Schedule of values page. You can select a schedule of values item, and then click the Copy icon to copy it. The copied item is added to the register. The values in the Schedule of values section are copied to the new schedule of values item. Data in the Quantity claimed and Value claimed sections is not copied.

  

  For more information, see Copy a schedule of values item.

• Allow accrued amount to exceed the line item value – You can now specify whether accrual amounts can exceed the line item value. Read more

  The Allow accrued amount toggle has been added to the Contract type configuration setup (organization Settings > Configurations > Contract type configuration setup). When you set the toggle to No, the accrual cannot exceed the line item value. When you set the toggle to Yes, you can set the maximum overage allowed per item. You can enter a percentage over the value of the line item, or you can select the Unlimited check box to allow any amount over the line item value. The default is to allow unlimited overages.

  

  For more information, see Contract type configuration setup.

• Payment claim Add existing Schedule item dialog box enhancements – The Line item ID, WBS code, Summary progress quantity, and Summary progress value columns have been added to the Add schedule item dialog box shown when adding an existing schedule of values item to a payment claim. The new columns give you additional information about the schedule of values item you are adding. Date filters have also been added so you can filter based on summary value posting date.Read more

  

  Date fields to allow you to filter the Schedule item and Summary progress columns in the dialog box to show the values of a specific date range. After the schedule item is added to the payment claim, the values in the Summary progress section reflect all progress to date. If you change the date range on the Payment claim Schedule of values tab, the Summary progress section is updated.

  For more information, see Schedule of values for payment claims.

• View unassigned change items in the Vendor change order log – You can now click the Unassigned Change items total at the top of the Vendor change order log to view a list of the Unassigned change items that contribute to the total. Read more

  

  Items in the Unassigned Change items list have at least one pricing item assigned to this vendor contract. You can click a change item in the list to view details of the change item in InEight Change.

  For more information, see Vendor change orders.

• Store and save values at the time of execution, submission, or certification – When you execute a vendor change order, submit a payment form, or certify a payment claim, a snapshot of the Schedule of values and Line items tabs are now taken, so that those values are stored. The saved and stored values let you see the values at the time of execution to make it easier to track progress. For information about executing a vendor change order, see Vendor change orders. For more information about submitting a payment form, see Payment form submittal. For more information about certifying a payment claim, see Certification.

• Prevent invoices that have been submitted from being deleted – After an invoice has been posted, you can no longer delete it from the payment form, and you cannot delete the payment form. For more information, see Invoice attachments.

• Note added when a payment form is deleted – When you delete a payment a form, a note is automatically added to the Administrative notes tab of the Notes slide-out panel on the Payment forms register. The notes help you keep track of which payment forms have been deleted. For more information, see Delete a payment form.

• Logic for the Maximum contract value change allowed without a change order setting – The setting Maximum contract overage allowed without a change order (%) (organization Settings > Contract > Configurations > Contract type configuration setup) has been renamed Maximum contract value change allowed without a change order (%) and now validates deleted lines and both increases and decreases made to the contract without a change order. For more information, see Contract type configuration setup.

• Payment claim new columns – The % Complete and Current total columns have been added to the Previous certification and Remaining sections of the Payment claims Schedule of values register to be consistent with other sections.

• Payment claim ID configuration – The Position column in the Payment claims configuration at both the organization and project levels (Settings > Configurations > Payment claims configuration) has been renamed ID to be consistent with other configurations. For information about the Payment claim ID configuration in organization settings, see the organization Payment claims configurationtopic. For information about the Payment claim ID configuration in project settings, see the project Payment claims configuration topic.

Contract 25.5.2 Release Notes

• WBS no longer automatically populates with the first CBS item – When the line item WBS field was left empty, the blank was matched with the first item in the Control CBS structure that had an empty WBS phase code. The logic was updated to not match the line item blank WBS with any empty phase code. Contract leaves this field blank, and you must select a WBS phase code, if required.

• The Post back dialog box now opens when clicking Add from InEight Document – When adding a document from Document’s Documents module to Contract, the Post back dialog box did not open. The Post back dialog box now opens correctly.

VIDEO | 25.3 Release Overview

General release is available starting 21-APR-2025.

Updated 22-APR-2025

• Value-only schedule of values items – You can now add schedule of value items that have value, including negative and zero value, but have zero quantity. Value-only schedule items give you the flexibility to track and claim value without having to enter a quantity. Also, because schedule of value items are now valid, you can now copy limit line items. Read more

  The Value only check box has been added to the Add schedule item slide-out panel. When the check box is selected, the Schedule quantity and Unit price fields are disabled, and the Hide in plan and progress field is set to YES and disabled. You can then enter any value, including zero and negative values.

  

  The Value only column has been added to the Schedule of value items section of the Schedule of Values register, so you can quickly see that a schedule item is value only.

  

  When you copy a limit line item to the schedule of values, the Value only check box is automatically checked and disabled. The unit of measure defaults to a value of PLS.

  For more information about value-only schedule of value items, see the Schedule of values tab topic under Contract setup. For information about adding a value-only schedule of value item to a vendor change order, see the Schedule of values tab topic under Vendor Change Orders. For information about adding a value-only schedule of value item to a payment form, see the Schedule of values tab topic under Payment Forms.

  When you make a claim against a value only schedule of value item, you can only claim value. The ability to claim quantity is disabled.

  When you add a value-only schedule item to a vendor change order or payment claim, only the Value field is editable. If you convert a certified payment claim that contains a value-only schedule item, you can only claim against the value.

  For information about claiming a value-only schedule item, see Claim schedule items from Contract. For information about converting a value-only schedule itemto an accrual or receipt, see Convert a schedule item to an accrual or receipt.

• Import value-only schedule of value items – The Value only column has been added to all Schedule of values import templates, so you can import value-only schedule items. When the value in the Schedule value only column is set to Yes, only the value is imported. For more information about how to use the template, refer to the Instructions tab of the Microsoft Excel template.

• Import line items at the payment form level – Import and export functions have been added to the Payment form Line items page, so you can quickly add or update line items. Read more

  You can use the import template to add existing items and enter the This submission column values. For more information about importing line items, see Line items tab. For more information about how to use the template, refer to the Instructions tab of the Microsoft Excel template.

• Calculating Change order adjustment values when copying a vendor change order line item into a schedule of values – The calculations for the Quantity, Unit Price, and Value columns in the Change order adjustment section of the Schedule of values page have been updated to more accurately reflect the adjustment. Read more

  Calculations have been refined for the following scenarios:

  • When the line item has a positive net price, a quantity, and a unit price in the Change order adjustments section, the copied schedule item uses the line item change order adjustments quantity and unit price.

  • When the line item has a positive net price and a quantity in the Change order adjustments section but no unit price change, the copied schedule item uses the line item change order adjustment quantity and calculates the unit price as the adjusted net price divided by the adjusted quantity.

  • When the line item has a positive net price and a unit price in the Change order adjustment section but no quantity change, the copied schedule item uses the change order adjustment net price divided by the change order adjustment unit price to calculate the quantity.

  • When the line item has a negative net price in the Change order adjustment section the copied schedule item will be value only.

  For more information, see Vendor change orders.

• Invoice net amount and invoice tax amount totals form Payment progress – Totals have been added for the Invoice net amount and Invoice tax amount columns on the Payment progress tab. For more information, see Payment Progress.

• Delete schedule of value items from a contract via a vendor change order – You can now delete a schedule of values item from a contract from the Vendor change order Schedule of values tab, to give you more flexibility when managing change orders. Read more

  From the Vendor change order Schedule of values tab, you can select an existing schedule of values item, and then click the Delete icon.

  

  The item shows with a strikethrough in the vendor change order, and the Schedule quantity and Unit price values are moved into the Change order adjustments section as negative values. When you execute and publish the vendor change order, the schedule item is deleted with a strikethrough in the parent contract.

  For more information, see Schedule of values tab.

• ERP Integration toggle restrictions removed – If you have the Edit contract configuration permission, you can switch the ERP integration toggle in the organization settings (Contracts > Contract configurations > Contract integrations) as needed. Previously, the toggle was locked after a contract had been created. For more information about ERP integration, see InEight Contract Overview .

• Manual adjustments in Line items register – The Manual adjustments column has been added to the Changes section of the Line item register, so you can quickly see the total of all value changes. The values in the column are linked to the Manual adjustments drill-down section of the Changes view.

• Tax ID document type – A new document type of Tax ID form is now available in supporting documents. The document type has a mandatory field for capturing the vendor’s unique tax ID. Previously, you had to create a custom document type or use the Other category to show the vendor tax ID. For information about adding a supporting document to a bid package, see Supporting Documents Tab . For information about adding a supporting document to a contract, see Supporting documents.

• Diversity participation percentage goal – The Percent field has been added to the Diversity participation section of the contract header, so you can enter the goal percentage. A Comments field has also been added. Read more

  You can have multiple diversity participation categories on a single contract. Each category can have its own percentage. The sum of the percentages does not have to equal 100%. The field is used for tracking and reporting purposes only. It is not validated against the Line items Diversity participation fields.

  

  For more information, see Diversity participation.

• Logic for the Maximum contract value allowed without a change order setting – The setting Maximum contract overage allowed without a change order (%) (organization Settings > Contract > Configurations > Contract type configuration setup) has been renamed Maximum contract value allowed without a change order (%) and now validates both increases and decreases made to the contract without a change order. For more information, see Contract type configuration setup.

• eSignature sender enhancement – The last step of the eSign status on the Supporting documents tab now shows the sender of the envelope with the annotation Receives a copy. Previously, the sender received a copy of the document, but it was not shown in the eSign status hover text. Read more

  

  For information about sending a document for eSignature, see Send contract documents for eSignature via DocuSign.

General release is available starting 17-FEB-2025.

Updated 17-FEB-2025

• View details of manual adjustments – You can now see the details of the Manual adjustments value shown in the Contract totals slide-out panel. The details provide visibility into the make-up of the manual adjustments. Read more

  The Manual adjustments value in the Contract totals shows changes to the contract without a vendor change order. When you click the new Manual adjustments link, the Changes drill-down view for the first line item in the contract opens.

  

  The Manual adjustments table in the view shows each line item that was changed manually along with quantity, unit price, value adjustment, and per details before and after the change. The name of the person who made the adjustment and the date is also included.

  The Changes section of the Line items tab and the drill-down view had previously been named Change orders.

  For more information, see Contracts toolbar.

• Import schedule of values items at the vendor change order level – Import and export functions have been added to the Vendor change order Schedule of values page, so you can quickly add or update items. Read more

  You can use the import template to add new schedule items or edit existing items. For more information about how to use the template, refer to the Instructions tab of the Microsoft Excel template. For more information about importing and exporting vendor schedule of values items, see Schedule of values tab.

• Import schedule of values items at the payment forms level – Import and export functions have been added to the Payment form Schedule of values page, so you can quickly add or update items. Read more

  You can use the import template to add or edit existing schedule items only. You cannot use the template to import new schedule items. For information about using the template, see the Instructions tab of the Microsoft Excel template. For information about importing and exporting payment form schedule of values items, see Schedule of values tab.

• Contract vendor updates in InEight Plan – When the Hide in plan and progress check box for a schedule of values item is not selected, and you update the vendor in the contract details, the vendor is now automatically updated in Plan. For information about updating vendor information, see Contract details.

VIDEO | 24.11 Release Overview

General release is available starting 09-DEC-2024.

Updated 21-NOV-2024

• Add invoices for retention release – You can now create invoices for retention release in the Payment forms module, so you can easily manage your retention release activities. Read more

  The Add retention release invoice option has been added to the Add invoice function on the project-level Invoices register and the Payment forms > Invoice attachments tab. The Add retention release invoice dialog box is like the Add new invoice dialog box; however, the Add retention release invoice dialog box only shows the taxes marked Net amount in the organization and project configurations.

  

  To add the invoice, enter values for the required fields. The value in the Retention release amount field cannot exceed the total of the retention withheld on the contract. Click Add to add the invoice.

  Payment form Line items tab

  To allocate the retention release invoices, Retention release columns have been added to the Payment forms Line Items tab in all sections except the Details section.

  • This submission section – The Retention release column lets you enter the amount of retention you want to release for this line.

  • Pending submission section – The Retention release column shows the sum of This submission retention release on pending payment forms on the current contract.

  • Previous submission section – The Retention release column shows sum of This submission retention release on submitted payment forms on the current contract.

  • Current total section – The Retention Release column shows the sum of This submission retention release and the Previous submission retention release.

  • Remaining section – The Retention release column shows the remainder of the current retention minus This submission retention release, Pending submission retention release, and Previous submission retention release.

  The tax for the net amount is calculated on the retention to be released. When you add a value to the Retention release column in the This submission section, on the payment forms Line items tab, the tax is calculated and displayed in the tax column.

  New and changed columns and fields

  On the Payments form page, the Remaining to Allocate field on the Payments form header has been renamed Invoice pre-tax remaining. It is the total of all non-retention invoices not yet allocated. The Retention release remaining field has also been added to the Payment forms header.

  

  The following register columns and detail page fields have been added or updated:

  

  For more information about retention release invoices, see Invoice attachments.

• Retention release permissions – The Edit retention release permission has been added. You must have this permission to have create, edit, convert, or delete a retention release invoice. For more information about permissions, see Permissions.

• Payment form auto submission for retention release – The Payment form auto submission now fails when the retention released on a line item across payment forms is more than the total retention withheld. For more information about payment form submittal, see Payment form submittal.

• Remove or delete schedule of values – The schedule of values now has separate functions for removing or deleting items. When you remove a schedule of values item, it is permanently removed from the contract, and subsequent schedule of value items are renumbered. When you delete an item, the item shows with a strikethrough, and it cannot be edited. The remaining schedule items are not renumbered, so you can maintain the schedule of values ID order. Read more

  To remove a schedule item, select it, and then click the Remove schedule of value icon (a circle with a minus sign).

  

  To delete a schedule item, select it, and then click the Delete schedule of value icon (a circle with an X). The item is deleted and shows a strikethrough. The Hide in plan and progress check box is automatically set to Yes and disabled.

  

  You can remove a schedule item if it has never been associated to a vendor change order, payment claim, or payment form. You can delete a schedule item with a strikethrough if the vendor change order, payment form, or payment claim have a net value of 0. If a schedule item is claimed in InEight Plan, InEight Progress, or Contract, it cannot be deleted or removed. For more information about removing or deleting schedule items see Schedule of values tab.

• Undo deletion of schedule of values item via a VCO – You can now re-add schedule of value items that were deleted from the parent Schedule of values page via a vendor change order. Read more

  To re-add the schedule item, you can click the Undo schedule of value removal icon in the Contract schedule of values register or the vendor change order Schedule of values tab.

  

  The strikethrough is removed from the schedule item, and the change order adjustment is updated. For more information, see Schedule of values tab.

• Disable Schedule of values Push to or Pull from buttons – To help prevent losing all line items when you push line items from the Schedule of values page to the Line items page, or pull line items from the Schedule of values page, the Push and Pull buttons are now disabled when a line item ID is blank for all schedule items. Read more

  On the Schedule of values pages for Payment forms and Vendor change orders, the Push to line items button is now disabled when the Contract line item ID is blank for all items. On the Line items pages, the Pull from schedule items button is now disabled when the line item ID is blank on all schedule of value items. The buttons are still enabled if any of the schedule items have a Contract line item ID.

  For information about pushing or pulling schedule items to the Line items tab see Vendor change orders and Payment Forms.

• Reuse deleted vendor change order IDs in the numbering scheme – When the toggle Generate vendor change order ID's sequentially (project Settings > Contract > Configurations > ID customization) is set to Yes, the last deleted vendor ID numbers can be reused in the numbering scheme. The reused vendor ID numbers reduce the number of gaps when you must delete vendor change orders created in error. Read more

  Deleting the last active vendor change order lets the vendor change order ID be reused for the next new vendor change order.

  For example, if vendor IDs 001, 002, and 003 were in use, and you deleted 003, the next vendor change order added would use the ID 003.

  For more information, see ID Customization.

• Workflow completion email for the person who started the workflow – Contract now sends the person who initiated a workflow an email when the workflow is complete. Previously, only users who created items or who completed the last step were sent completion emails.

• Line items page total additions – New totals have been added to the totals row of the Line items page. Read more

  Totals are now calculated for the following columns.

  Change orders section:

  • Potential change net amount

  • Executed net amount

  Progress section:

  • Goods receipt

  • Invoice receipt

  • Invoice receipt

  • Proposed accrual

  • Retention withheld

  Payment forms section:

  • Submitted net amount

  • Submitted retention amount

  • Submitted retention amount

  • Draft net amount

  • Draft retention amount

  Accruals/Receipts section:

  • Submitted accrual amount

  • Draft accrual amount

  • Submitted receipt amount

  • Draft receipt amount

• Project master agreements considered in Home page tile – Project master agreements are now included in the statuses listed in the Contracts tile on the project Home page. Previously only contracts were included.

VIDEO | 24.9 Release Overview

General release is available starting 07-OCT-2024.

Updated 23-OCT-2024

• Copy VCO line items – You can now copy line items in a VCO to the VCO schedule of values. The schedule of values items are automatically associated to the line items. Previously, when you added new line items to the VCO, you would have to manually add them to the schedule of values and associate them. You can also copy line items to the Line items page. Read more

  The Copy icon has been added to the VCO Line items page. When you click the icon, you can then select whether to copy to a line item or to the schedule of values.

  

  When copying to the schedule of values, a new schedule of values item is created, and the Contract line item ID, the description, UOM, quantity, and unit price fields are copied to the new item. The Hide in plan and progress field defaults to Yes. The line items are automatically associated to the schedule of values.

  Limit lines cannot be copied to a schedule of values.

  When you copy to the Line items page, a dialog box lets you select the sections of the line items you want to copy.

  

  For more information about copying VCO line items, see Vendor change orders.

• Start workflow when only one role per step has a valid user assigned – Now only one role in each step must have a valid user assigned to start a workflow. This enhancement lets you start a workflow when the organization-level setup includes a role that does not have a person assigned to your project. Read more

  Previously, when a workflow step had multiple roles, all roles were required to have at least one user assigned before starting the workflow.

  Now, when the Projects must select specific users … check box in the organization workflow approval setup is not selected, and there are multiple roles assigned in a single step, you can assign one user to any step before workflow can begin. When the check box is selected, you must assign specific users to each step.

  For more information, see Workflow Assignments .

• Master data libraries status for general ledger accounts, payment terms, and Incoterms – When the status of a general ledger account, payment term, or Incoterm is set to Unavailable in the Master data libraries, that account, payment term, or Incoterm no longer shows in drop-down lists for contract and VCO fields. Read more

  The import templates for the Contract header, Contract line items, and VCO line items now show only accounts and terms that are available in the template drop-down lists. If the Master data library item was updated to Unavailable before the file is imported, the field is imported as a blank.

  For more information about setting master data statuses, refer to the InEight Platform 24.9 Release Notes. For information about general ledger accounts, payment terms, and Incoterms, see Header Tab.

• Organization-level Contracts settings moved to Configurations – The Accrual/Receipts settings, Diversity participation, and Supporting documents configurations are now located in the Organization > Configurations list to improve performance. Previously, they were tabs under the Organization > Contracts settings. For more information, see Accrual/Receipt settings, Diversity participation, and Supporting documents.

General release is available starting 05-AUG-2024.

Updated 23-OCT-2024

• Line items tab improved performance and new look – The contract Line items tab now has improved loading times and performance. The Line items tab has also been updated to color coordinate the sections with the drill-down viewsets. Read more

  

  The toggle for the line item single grid view has been added to the top of the Line items page. This toggle lets you revert to the previous version of the line items view while transitioning to the new page. The toggle defaults to On. When this toggle is set to On, the new grid and performance benefits are enabled. When the toggle is set to Off, the previous Line items grid is used. The toggle will be removed in a future release after full regression of the new page.

  For information about the Line items tab, see Line items column management.

• Create a contract claim from a certified payment claim – You can now quickly convert a certified payment claim into a contract claim from the Payment claim Schedule of values page. Converting the contract claim from the payment claim lets a single entry of values apply across all locations. This option is only available after a claim has been certified. Read more

  The Convert to contract claim option has been added to the options for Convert schedule of values icon on the payment claim Schedule of values page.

  

  When you select the Convert to contract claim option, the Update contract claim for below schedule of value items dialog box opens where you can select the schedule of values to claim.

   

  

  Certified values from this payment claim automatically fill the Claimed quantity and Claimed values fields. After you click Claim, the contract claim values on the main schedule of values page are updated with the claim information. These values also drive progress in InEight Control if using the Update % complete setting in Contract.

  For more information about creating a contract claim from a payment claim, see Schedule of values.

• Generated document name on Supporting documents register – When you generate a document from a template, and the Save in supporting documents toggle in the Generate contract wizard is set to Yes, the value in the Name of document file now shows in the Title column of the Supporting documents tab. Previously, the name of the template showed in the column. Read more

  Now, if you enter a document name, the title and the name of the file or link are the same. If you do not enter a document name, Contract uses the template name. For more information about generating supporting documents, see Contract Writer.

• New template tags – New tags were added for the new fields in the Vendor details of the Master data libraries. Tags were also added for new fields added in recent releases. Read more

  The following tags have been added for vendor master data:

  <<Vendor remit to: Country/Region>> <<Vendor remit to: Address 1>> <<Vendor remit to: Address 2>> <<Vendor remit to: City>> <<Vendor remit to: State>> <<Vendor remit to: Postal code>> <<Vendor remit to: Phone>> <<Vendor remit to: Fax number>>

  The following tags were added for new fields:

  Contract summary: <<Remaining to be paid>> Contract Schedule of values: <<Remaining to be claimed>> Payment claim: <<Remaining to be certified>> Payment claim: <<Payment claim requested retention>> Payment claim: <<Payment claim certified retention>> Payment claim: <<Payment claim certified to-date gross>>

  For more information, refer to the tags list in Settings > Contract > Contract Templates > Template types.

• Increased decimal places in the organization level configuration settings – Percentage and amount fields in the organization-level Contract type configuration setup, Organization master agreement type configuration setup, and Tax settings now allow up to five decimal places to be compatible with decimal precision settings. Read more

  The following fields in the Contract type configuration fields have been updated to accept up to five decimal places:

  • Maximum contract overage allowed without a change order

  • Maximum over payment allowed per line item

  In the Master agreement type configuration setup, the Maximum contract overage allowed without a change order field has been updated to accept up to five decimal places. The Default % column in the Tax settings has been updated to accept five decimal places. For more informaiton about Contract type configuration, see Contract type configuration setup.

• Payment claims schedule of values register summary progress – The Summary progress section has been added to the Payment claims Schedule of values register, so you can track the contract and progress claims on existing Schedule of values items. Read more

  The Summary progress section includes the Quantity claimed and Value claimed columns. The Quantity claimed is the contract quantity claimed plus the component progress quantity claimed. The Value claimed is the contract value claimed plus the component progress value claimed. When you add a schedule of values from the Payment claims Schedule of values page, these fields are zero.

  

  For more information, see Schedule of values.

• DocuSign settings moved to Configurations – The DocuSign settings have been moved from the Contract templates to the project Configuration settings (project > Settings > Change > Configurations > eSign setup). You no longer need to have the Edit templates permission to set up or edit the eSign settings. Now, only the Edit contracts settings permission is needed to edit the eSign settings. For more information about eSign settings, see eSign setup.

• New totals on Schedule of values register – The Vendor value, Certified value, and Certified delta totals have been added to the Totals row in the Payment claims section. Read more

  The Pending value total also has been added to the Payment forms section.

  

  For more information about the Schedule of values register, see Schedule of values tab.

• Vendor change order log Clear all filters – The Clear all filters button has been added to the Vendor change order log. For information about the Vendor change order log, see Vendor change orders.

General release is available starting 03-JUN-2024.

Updated 21-JUN-2024

• Payment claims schedule of value % Complete to date – Contract now supports % Complete claiming in Payment Claims. The % Complete to date columns have been added to the Payment claims Schedule of values register. Contract calculates the claimed value and quantity when a user enters the percent complete. Read more

  The % Complete to Date columns have been added to the Vendor Submission and Certification sections. You can edit the two new columns from the register. Edits to the Quantity and Value columns cause the % Complete to date column to recalculate.

  Columns were also added to the import template for the payment claims schedule of values. The option to calculate inputs based on quantity, value, or percent complete to date were also added to the import data from template dialog box.

  The % Complete field is updated if any quantity or value changes are made to the SOV via the Contract Schedule of Values tab or as part of a Vendor Change order. Period Quantity and Value are used as the source of truth if changes occur.

  The calculation for the Vendor submission % Complete to date is as follows:

  ( (Vendor submission value ÷ Scheduled value) + (Previous certification value ÷ Scheduled value) ) × 100

  The calculation for the Certification % Complete to date is as follows:

  ( (Previous certification value + Certification value) ÷ Scheduled value) × 100

  A pending uncertified claim warning has been added to the Schedule of values page for the payment claim because totals calculations change when the pending payment claims are certified. The icon shows so that you can be aware that totals for the schedule of values item will change.

  

  For more information about % complete claiming, see Schedule of values.

• Estimated payment posting date – The Estimated posting date column has been added to the Payment form Invoice attachments register. When you use a proxy ERP, you can use this column to define your own posting date instead of using the submitted date. If you are relying on the integration with InEight Control for actuals, using the estimated posting date with your proxy ERP can prevent incorrect actuals in Control. Read more

  You must have permission edit payment form to update the Estimated posting date column.

  When you use an ERP system, the ERP system provides the posting date regardless of the value of this field.

  

  The Document year in the Payment progress tab is driven from the estimated posting date for proxy ERP customers. It is not automatically updated when you update the Posting date value. You can manually update the Document year as needed.

  For information about the estimated posting date, see Payment Forms.

• Contract register Current value and Schedule value hyperlinks – Values in the Current value column of the Contract register are now links to the Line items tab. Values in the Schedule value column are now links to the Schedule of values tab. The links let you quickly see line item or schedule item details. For more information about line items, see Line Items Tab. For more information about the Schedule of values, see Schedule of values tab.

• DocuSign Advanced Options – Contract now supports DocuSign Advanced options for branding, reminders, expiration, and comments. The advanced options show in DocuSign when you are in the Sender view. Read more

  From the Sender view in DocuSign, you can now go to the advanced options (Actions > Advanced Options) to access options for branding, reminders, expiration, and comments. You can see the advanced options based on your organization's DocuSign settings.

  

  • Branding options let you select a logo and brand colors, that were set up by the DocuSign administrator, for the envelope.

  • Reminders options let you specify whether DocuSign sends reminders to signees, when to start sending them, and how often to send them.

  • Expiration options let you set the number of days until the envelope expires and how often to send alerts. After the envelope is expired, recipients can no longer view or sign the documents in the envelope.

  • Comments options let you allow senders and recipients to enter comments on documents in the envelope.

  Options for recipient privileges, are also available. Refer to your DocuSign documentation for more information about advanced options.

  For more information about InEight DocuSign configuration, see Project Settings. For information about sending a document to DocuSign, see Send contract documents for eSignature via DocuSign.

• Payment forms and VCO nonzero remaining to allocate values – You can now start workflow, submit, publish, or execute a payment form or VCO when the remaining to allocate value is within +/- 0.0099 to account for differences in decimal precision. Previously, the value had to be zero. For more information about the Remaining to allocate field in a payment form, see Payment Forms. For information about the Remaining amount to to allocate field in a VCO, see Vendor change orders.

• Contract schedule of values date validation – An error icon now shows when you claim a contract schedule item and the item's posting date is not within the Valid from and Valid through dates. Read more

  You cannot claim the schedule items if they are not within the valid from and valid through dates. If there are no valid from and valid through dates, all posting dates are acceptable. For more information about claiming schedule items, see Claim schedule items from Contract.

• Payment claim register Requested value and Certified value columns and retention columns – Columns for the requested value and the certified value have been renamed to be consistent with other column names. The Retention column has been split into the Requested retention and Certified retention. Read more

  The Payment claim value column has been renamed to Requested value. This column is the vendor submission from the payment claim. The Amount certified column has been renamed Certified value.

  The Requested retention is the retention from the vendor submission. The Certified retention column is the retention from certified claims.

• All invoices selected by default when converting a payment claim to a payment form – When you convert a certified payment claim that has invoices associated to it, all invoices are now automatically selected in the Convert to Payment Form wizard to reduce problems after conversion. For more information about converting a payment claim into a payment form, see Convert to a payment form.

• Adding a schedule item with a negative quantity – Schedule of value quantities must now be greater than zero. A negative unit price can be used to add an item with negative value. This change was made to be consistent with line item functionality. For information about adding schedule items, see Schedule of values tab.

• Payment form schedule of values current total calculation – The current total in the payment form schedule of value is now calculated as the sum of the values of the This submission and the Previous submission columns. Previously, pending submission values were included. This calculation is now consistent with line item calculations. For more information about the Payment form schedule of values, see Payment Forms.

• Quantity and unit price in Add line item dialog box for payment forms and VCOs – The Quantity and Unit price columns have been added to the Add line item dialog box for payment forms and VCOs, so you can see more details when selecting line items.

• Schedule of values collection table tag updates – The <<Payform SoV: Vendor claimed to date>> tag was added to the Payment form Schedule of Values collection table. New collection tags have been added for fields in the VCO schedule of values to replace the tags from the previous releases. Read more

  The value from the new vendor claimed to date tag is the sum of the vendor submission value claimed against the current SOV item in all certified claims.

  The following new VCO tags have been added:

  <<VCO SoV: Current schedule line value component quantity>> <<VCO SoV: Change order adjustments quantity>> <<VCO SoV: Change order adjustments unit price>> <<VCO SoV: Change order adjustments value>> <<VCO SoV: Total revised value quantity>> <<VCO SoV: Total revised value unit price>> <<VCO SoV: Total revised value value>>

  For more information, refer to the Collection table tags list in Settings > Contract > Contract Templates > Template types.

• Remove canceled workflows from Action items tab – Contract now removes workflows that are not completed in 90 days and have been canceled from the Action items tab. For more information about bid package workflow, see Workflow Assignments tab. For information about contract workflow, see Workflow Assignments .

• Removal of Harmonized schedule fields – All fields relating to Harmonized schedule have been removed from Contract in this release.

General release is available starting 08-APR-2024.

Updated 08-APR-2024

• Copy line item to schedule of values – You can now copy line items from the Line items register in contracts and master agreements directly to the Schedule of values register. Copying line items gives you a starting point for building your Schedule of values and an easy way to make values match. Read more

  When the schedule of values is enabled for the contract, the option To schedule of values shows when you click the Copy icon in the Line items register. When you select To schedule of values, the selected line items are copied and associated to the schedule of values.

  

  Deleted line items and closed line items are copied, but the line item is blank in the schedule of values. Because Limit line item types are values without quantities and units of measure, they cannot be copied to the schedule of values.

  For more information about adding items to the schedule of values, see Schedule of values tab.

• Move line item columns from the Detail section of the grid to the locked section – You can now use the Column manager on the Line Items page to move columns from the Details section to the first section. Moving detail columns into the locked section gives you more options when customizing the view on the Line items page. You can also move the Material ID, Description, and Type fields from the locked section into the Details section. For information about managing Line items register columns, see Line items column management.

• Workflow recall – The user that recalled a workflow is now shown on the project Workflows page as part of the workflow details. Read more

  

  For more information about workflow, see Workflow Assignments .

• Roles without assigned users in workflow steps – You can no longer start an approval workflow when a role assigned to a step has no users assigned. A warning indicating that there is no applicable user for the step is shown. For more information about assigning roles in workflows, see Workflow Assignments .

• Payment term and Incoterm codes included with descriptions – The payment term and incoterm codes are now shown along with their descriptions in drop-down menus, registers, and exports.

• Accruals sent to InEight Control upon submission – Contract now sends accruals to Control only after they have been submitted. Previously, accruals were sent to Control when they were in Draft status. For information about submitting accruals, see Accruals/Receipts.

• New lines in published external purchase order contracts – The external API no longer allows additional lines to be added to published external purchase order contracts.

• Supporting document expiration notification toggle – When the toggle Expiration notification enabled is set to Yes for a supporting document, the toggle remains enabled and no longer changes 180 days after the expiration date has passed. Read more

  Previously, Contract reset the toggle to No after 180 days to stop email notifications. Now, the toggle remains set to Yes, and you can assume notifications were sent. Contract stops sending notifications 180 days after the expiration date.

  

  For more information about expiration notifications, see Supporting documents.

Due to lack of use, Harmonized Systems / Schedules functionality will be deprecated in the 24.5 release. This will include the settings, contract header field, line item fields, and any associated tags. Please contact customer support with any questions or concerns.

Updated 09-FEB-2024

• Restrict overpayment of line items – You can now configure whether overpayment of line items is allowed. The new Allow overpayment on line items toggle in the organization-level Contract type configuration (organization > Settings> Contract> Configurations > Contract type configuration setup) lets you indicate whether you can pay more than the line item current value. Read more Watch video

  Setup

  

  When the Allow overpayment on line items toggle is set to Yes, you can specify the maximum over payment percentage allowed per line item. You can also select the Unlimited check box.

  By default, you will continue to receive a warning if you attempt to overpay line items, but you are not stopped from overpaying unless the setting is turned off.

  For information about the overpayment settings, see Contract type configuration setup.

  Payment form overpayment tolerance

  When the Allow overpayment online items toggle is set to Yes, and you have entered a percentage instead of checking the Unlimited check box, Contract validates that the total of all approved payment forms does not exceed the overpayment percentage before submitting the form. A red warning icon is shown on the Line items tab of the payment form. If the project is set up for auto submission, the payment form is not submitted.

  When multiple payment forms are submitted on a line item, and one of the payment forms changes the overpayment calculation to exceed the overpayment tolerance, the auto submission of the form now fails, even if it had been approved. Contract sends an email to let you know the submission failed due to the overpayment tolerance.

  Also, when the project is set up for auto submission of approved payment forms and during the approval process, the Allowed per item setting is changed to a lower value, the submission of the approved payment form fails. You must recall the approval.

  The overpayment tolerance is based on the setting by the contract type.

  For more information about payment form overpayment tolerance, see Overpayment tolerance.

• Copy vendor-submitted values in a payment claim – You can now quickly copy the information from the Vendor submission column of the Payment claims > Schedule of values register to the Certification section. Copying the vendor submission information can reduce the chance of input errors and save time. Read more

  

  Click the Copy vendor submissions button in the Certification section heading of the Payment claims Schedule of values register to copy and paste the information.

  For information about using the Payment claims Schedule of values register, see Schedule of values.

• Payment claims schedule of values import template updates – You can now import vendor submission values using Microsoft Excel. The fields in the Vendor submission section of the template are now optional. Previously, these fields were ignored when importing. For information about using the Payment claims Schedule of values register, see Schedule of values. For information about importing, see .Imports and exports

• Payment claim document templates – You can now generate Payment claim documents from templates. A Payment claim template type has been added to the Contract documents templates. General tags and collection table tags for payment claims for all payment claims fields have also been added. For more information about document templates, see Template types subtab.

• Schedule of values tabs enhancements – The Payment claims section of the Contract > Schedule of values tab now includes the Pending quantity, Pending value, and Pending delta columns that function as placeholders for uncertified claims. The columns let you easily see the certified and pending claims for the schedule item. For more information aobut the Schedule of values tab, see Schedule of values tab.

• Edit dates in a payment claim – You can now indicate whether users can edit dates in a payment claim. The Allow users to edit dates in a payment claim toggle was added to the Payment claim configuration at the project level (project > Settings > Contract > Configurations > Payment claim configuration). Read more

  

  When the toggle is set to Yes, you can add dates or remove the default dates. When the toggle is set to No, you cannot add new dates or remove the default dates.

  For more information about payment claim dates, see Payment claim details.

• Payment claims project-level import – You can now import payment claims at the project level. For more information about importing payment claims, see Payment claims register.

• Line items column management improvements – The Line items tab has been updated to show only the columns for Details and Budget and commitment sections by default to improve register loading time. This is applicable for new views or if you reset to the default. Read more

  You can now add other sections and columns as needed. After you have added sections or columns, they remain in the view until they are removed, or you reset the defaults in the Column Selector Builder.

  For more information about line items column management, see Line items column management.

• Contract totals slide-out panel update – A line for Manual adjustments has been added to the Contract totals slide-out panel, so you can quickly see if any manual adjustments were made outside of a vendor change order. Read more

  

  Previously, you had to run the procurement summary or buyout review report to see that there were manual updates. For more information about the Contract totals slide-out panel, see Contract Creation.

• Schedule of values tab update – The Change orders section has been added to the Schedule of values register, so you can quickly see the executed quantity and amounts for the schedule item and the associated vendor change order. Read more

  The import template for the Schedule of values register has also been updated to include the Change orders, Payment claims, and Payment forms sections.

  For more information about the Schedule of values register, see Schedule of values tab.

• Master agreements Progress section enhancement – The Associated quantity and Associated values column have been added to the Progress section of the Master agreements Line items register. Read more

  The Associated quantity is the sum of all associated quantities for the line item. The Associated value is the sum of all associated values for the line item.

• Contract writer update – When you generate a contract document, the option to create individual documents is now the default for the Generate document as field in the Generate contract wizard. The Generate file type as field now defaults to Download as template file type. For more information about Contract writer, see Contract Writer.

• Enhanced Approval date collection table tags – Collection table tags for approver dates, including Contract approvers: Date, VCO approver: date, Payform approver: date, and Claim approver: date, now generate the time stamp along with the date of the approval. Previously, only the date was included.

• Back charges register update – You can now export the Back Charges to a Microsoft Excel spreadsheet like other registers. For more information about exporting, see Imports and exports.

• Payment form Line items tab update – The total has been added to the Tax column of the This submission section of the Payment forms Line items register, so you can identify the total tax without having to open the Details tab. Read more

  

• Owner legal name general tag – The owner legal name contract writer tag has been added to match the new field added to the project details page.

Due to lack of use, Harmonized Systems / Schedules functionality will be deprecated in the 24.5 release. This will include the settings, contract header field, line item fields, and any associated tags. Please contact customer support with any questions or concerns.

• Delete payment records sent in error – Your integration team can now delete records from the Payment progress tab without having to send a negative amount to cancel records sent in error by the ERP system. Read more

  The IsActive field has been added to the payment integration. When an item has been sent in error, your integration team can send the value with the IsActive flag set to False, which removes the entry from the Payment progress tab. Refer to integration documentation for more information.

Updated 27-SEP-2023

• Payment claims – You can now manage payment claims in Contract, so you no longer need to maintain additional spreadsheets and documentation. The payment claims function can be used when you are required to certify a vendor's claim of work in advance of receiving an invoice or before the payment form is created. Payment claims track items based on the schedule of values items. Read more Watch video

  Permissions

  The following permissions were added for payment claims:

  • Add payment claim

  • Edit payment claim

  • Delete payment claim

  Users must also have the Approve/Reject payment form permissions to send a payment claim through workflow.

  For more information about permissions, see Permissions.

  Set up

  Payment claims has been added to the organization and project Configurations settings. To use the payment claims feature, the Enable Payment claims toggle in the organization level configuration settings must be set to Yes, or else payment claims is turned off for the entire organization.

  

  To allow payment claims the Use payment claims for this contract type toggle in the Contract type configuration set up must be set to Yes. When set to No, the Payment claims tab is not visible for the contract type. Because a schedule of values is required for payment claims, the Use payment claims toggle is disabled when the Use schedule of values for this contract type toggle is set to No.

  For more information about payment claims configuration at the organization level see Payment claims configuration. For more information about payment claims configuration at the project level, see Payment claims configuration.

  

  The Push updates to existing projects toggle lets the payment claim due date and the schedule date names get automatically pushed to all projects. If set to No, the changes are valid for new projects only.

  The Allow projects to add/edit payment claim settings check box lets you indicate whether the organization-level settings can be edited at the project level.

  The Payment claim due date is the day of the month the payment claim is due. It is used to calculate the scheduled dates. You can then use the grid in the lower half of the page to set up a timetable based on the payment claim due date. You can enter positive or negative values. Schedule dates that are marked as Active can also be set to Default. If set to Default, the schedule date is automatically shown on the Payment claims detail page.

  If you want the payment claim to go through approval before it is certified, you can set up a workflow from the Payment claim approval setup tab in the organization and project settings.

  For information about configuring payment claims in the contract type configuration setup, see Contract type configuration setup.

  Payment claims tab

  The Payment claims tab has been added at the project and contract levels. Each payment claim has Details, Schedule of values, Invoices, and Supporting documents subtabs.

  Create a payment claim

  You can create a payment claim from either the project- or contract-level Payment claims register. To create a claim, click the Add payment claim icon. The Details tab opens. You can then enter detail information and use the Payment Claim Dates section as a timeline to track your communication with the vendor.

  

  For information about the payment claim dates and adding a payment claim, see Payment claim details.

  After saving you can then add schedule of values items. You can add a new or existing schedule item.

  

  You can use the columns in the Vendor submission section to enter the quantities and values to track information from the vendors. Use the columns in the Certification section to enter the values that you want to certify. If workflow is not enabled, you can change the Payment claim status to Certified.

  If your environment is configured for payment claims workflow, you can click the Save and approve button on the Details page to send the claim through approval workflow. After final approval, the Certified status is enabled, and you can update the payment claim status to Certified.

  For more information about the Schedule of values page in payment claims, see Schedule of values. For more information about certification, see Certification.

  After you have certified the claim you can go to the Schedule of values page, and then convert the schedule item to a payment form. If you added a new item, you cannot create a payment form if the value in the Certification section of the Schedule of values is not 0.

• Schedule of values claimed value and claimed quantity calculation - You now have the option to have Contract not recalculate the claimed value based on claimed quantity and vice versa. Previously, the claimed value was forced to be the quantity multiplied by the unit price. The option to recalculate lets you match the calculation to your business needs. Read more

  This calculation is available when you edit a contract claim and when you import schedule items from a template.

  When you edit the Claimed quantity field, a dialog box asks if you want to recalculate the value based on the entered quantity. If you edit the Changed value field, the dialog box asks if you want to recalculate the quantity based on the entered value. If you choose not to recalculate the value or quantity, you can still save the schedule item, but the values will no longer match mathematically. This allows you to enter values that are rounded without adjusting the quantity if the business process dictates.

  When you import from a template, you can set the Claim Option field in the Import data from template dialog box to Quantity, Value, or Quantity and Value. If you select Quantity, the Value claimed is recalculated regardless of what was entered and vice versa. If you select Quantity and Value, both columns are read regardless of whether they match. You are responsible for maintaining those fields.

  

  Additionally, the Claimed unit price column and the Scheduled unit price column have been added to the Contract claim history tab for a schedule item, so you can have visibility into pricing. The claimed unit price is the claimed value divided by the claimed quantity. The Scheduled unit price is the unit price of the schedule of values at the time the claim is made.

  For more information, see Claim schedule items from Contract.

• Bid package supporting document types – The Add supporting document dialog box in Bid packages now uses the defined list of document types that are available in Contract instead of using free text. To support this change, The Added on, Subtype, and Expiration notification enabled columns have been added to the Bid package Supporting documents register. Legacy document types have been replaced with Other and documented with a note. For more information, see Supporting Documents Tab .

• Integration UOMName field changes – The field used to receive UoM items from an ERP system in Contract has been changed to allow use of UOMName or SKFUOM for the Purchase order response, Accrual request, and Goods receipt request integrations. Customers must check their integrations to make sure these changed field names do not cause issues. Refer to the integration documentation for more details.

• Format large text boxes in Microsoft Word templates – You can now use Word's merge fields to format text boxes with multiple lines, such as the Scope of contract, in a Word template instead of using a tag. Using a merge field ensures the text in the generated document is formatted as it is in the text field. Read more

  The merge field also lets you format the font as needed. The generated document uses the font specified in the template. Other formatting is taken from the text field. Refer to the instructions in the General tags export list for more information about using merge fields.

  To use the merge fields in existing templates, you must delete the tag and then insert the merge field. You can then save the template as a new version. For information see Template types subtab.

• Component quantity in schedule of values – The Component Quantity column in the Schedule of values register has been added at both the contract and vendor change order. This column gives you visibility into changes made to the quantity in InEight Plan. Read more

  The Hide in plan and progress field in the schedule item must be set to No.

  The component quantity value is pulled from the Component quantity in Plan. If the value is modified in Plan by splitting the contract component, a blue dot shows next to the quantity to indicate the component quantity does not match the schedule quantity. For information, see Schedule of values tab.

• Line item updates in vendor change orders and payment forms – A Revised line item icon now shows in the VCO and Payment form Line items pages when a line item has been changed but not published. The icon lets you quickly see that changes have been made to the line item, and you can decide if you want to proceed with the VCO or payment form.

• Vendor change order tab new columns – The Issue ID, PCO ID, and CCO ID columns have been added to the Vendor change order log at the project and contract levels. These columns let you easily see any associated issues, potential change orders, or client change orders related to the vendor change order.

• Schedule of values import history improvements – The Schedule of values Import history page now includes totals and the number of errors at the bottom left, so you can see how many items are selected and find errors quickly. Read more

  

• Saving a payment form – You no longer need a payment term or a progress estimate to save a payment form when they are required for the payment form. The fields are required only for submittal and workflow. When the status of the payment form is New, a yellow warning icon shows next to the Progress estimate number and Progress estimate billing period fields to remind you that the fields are required for approval and submission. For more information, see Payment Forms.

• Back charges in Payment form details – When the Use back charges toggle in the contract type configuration is set to No, the Back charges section no longer shows on the Payment form Details page.

• eSignature correction permission – A new permission, Correct eSignature, has been added. You must have the Correct eSignature permission to correct DocuSign documents. For more information, see Permissions.

• Global approach to dates – The Payment form Approved, Payment form Rejected, and Supporting Document Expiration emails now use the global date format YYYY-MM-DD.

Updated 18-JUL-2023

• Contract Line items tab enhancements – The Line items tab has been redesigned with collapsible sections to make it easier to use and to be consistent with the enhancements to the Vendor change order line items tab and the Payments form line items tab. Read more

  Page layout

  The Line items grid is now divided into sections, so you can easily see related columns concurrently. The sections replace the views on the previous Line items page.

  The Line items sections include Details, Budget and Commitment, Change Orders, Progress, Payment Forms, and Accruals/receipts. If the Change orders, Payment forms, or Schedule of values features are not enabled in the Contract type configuration in the organization settings (Settings > Contract > Configurations > Contract type configuration setup), the corresponding sections are not shown on the Line items tab.

  You can click the arrow in the column header to collapse or expand the section. Multiple sections can be collapsed. The first section, which includes the Line item ID, Description, and WBS cannot be collapsed. You can click the double arrow in the first section to collapse the rest of the sections. You can widen the fields in the first section to take up half of the page. After you have reached the maximum expansion, the scroll bar shows at the bottom of the section. Each section also has a Collapse icon. The Collapse icon for each section is floating, so it is always visible as you scroll. You can manually size columns, so you can see the information you want.

  

  The column management feature lets you rearrange grid sections and add or remove columns within the sections. Click the Manage columns icon in the toolbar to open the Column Selector Builder dialog box.

  

  Drill-down actions

  You can click a link in a cell to access detailed information for an item. The link opens the drill-down page for the section.

  

  Add and edit line items

  When you add or edit a line item, a slide-out panel opens with a condensed view of the details page. This view lets you see more fields with less scrolling. Previously, when you added or edited a line item, the Line item details page opened.

  

  If you want to see the full Line items detail page, click View full page in the bottom left of the slide-out panel.

  When the Add or Edit slide-out panel is open, you cannot click on any buttons behind the panel to prevent adding conflicting data in the grid. If a slide-out panel opens from a slide-out panel, for example the Advanced material search panel sliding over the Edit line item panel, the original slide-out panel is disabled until the newly opened panel is closed.

  When the slide-out panel is closed certain fields can be edited from the grid. Editable fields are outlined in blue when you hover over them.

  Import template

  The Line items import template has been updated to include the sections and fields available in the Details section.

  Multiselect

  The Line items tab lets you select multiple items when you hold down the Shift key.

• Decimal precision – You can now set the number of digits that trail the decimal point in values, quantities, percentages, and unit prices shown in Contract. Read more

  The Decimal precision settings have been added to the project-level settings (Settings > Contract > Configurations > Decimal precision). You can choose a separate value for Values, Quantities, Percentages, and Unit price. If you do not enter a value, the setting defaults to a value of 2 for Values, Percentages, and Unit price and 3 for Quantities. You can choose values 0-5.

  

  Value, quantity, unit price, and percentage fields throughout Contract have been updated to support decimal precision, including imports and exports. All exports and imports can support five digits after the decimal regardless of the setting. The fields are stored in the database with five digits after the decimal but are shown on the UI according to the settings.

  Contract writer tag output continues to use two decimal places.

• Vendor invoice submission – Vendors can now submit invoices in InEight Contract. Invoices created by vendors show immediately in the Invoices register. Vendor-submitted invoices help the contractor save time and reduce the chance of errors. Read more

  Vendor roles and permissions

  Vendor users must be assigned to a role that includes the View Contract vendor page permission (Suite Administration > Roles and permissions > Suite administration > Vendor > View Contract vendor page). This permission automatically includes the Documents permissions under Suite Administration > Roles and permissions > Organization and project > Documents.

  

  When you create a vendor permission, set the administrator level to base level 0. The Vendor landing page view must be assigned in the View assignments section.

  User management

  The vendor user must have a vendor assigned in the Vendor field of the User details. You can assign a vendor user to a specific project on the project home page or assign the user at the organization level.

  After you add the vendor user, they receive an InEight notification with a link and sign-in information.

  Vendor home page

  When a vendor user signs in to the InEight cloud platform, they see the Vendor (Default) view of the home page. The Contracts tile widget lists the contracts the vendor has for the project or the organization, depending on whether the user is associated with a project.

  

  The vendor user clicks a contract ID -Description entry to go to the Vendor contract summary page.

  Vendor contract summary page

  Vendor users add and edit invoices using the Vendor contract summary page. The Vendor contract summary page also shows contract totals, contract details, and all invoices created by the vendor.

  

  The vendor user can click the Add invoice icon to add an invoice. They then use the Add invoice dialog box to add information and submit the invoice. The invoice is added to the Invoices grid with a status of Pending, and the number of items and invoice total at the bottom of the grid are updated. The invoice cannot be edited after it has been added unless it is recalled by the vendor user first.

  If the invoice is declined by the contractor, the record status of the invoice changes to Declined. The vendor user can then recall the invoice by clicking on the Invoice number and then clicking the Recall button in the Edit invoice dialog box. The record status changes to Recalled, and the vendor user can edit the invoice and submit it again.

  When the contractor accepts the invoice by clicking their Received button, the status on the Vendor contract summary page is updated to Received. After an invoice is received, the vendor user can no longer edit or recall the invoice.

  To add a comment to the invoice, the vendor user can select an invoice and then click the Notes/feed icon. The Notes/feed slide-out panel opens. The vendor user can then add notes. Any comments entered when adding the invoice are automatically applied.

  

  After the vendor user adds notes and then clicks Add, the note is added with a time stamp. The contractor can also add notes to an invoice. These are shown with a blue bar on the left side of the note.

  

  After the contractor applies the invoice to a payment form and the payment form is submitted, the value in the Paid amount column is updated with the amount paid.

  Contract Invoices page

  The Invoices register has been updated to support the vendor status, so you can quickly see which invoices were submitted by vendors. The Vendor status column has been added to the register. It is not shown by default, but you can add it from the column chooser.

  After a vendor submits an invoice, the invoice is shown on the Invoices register with a vendor status of Pending. Other statuses for vendor-added invoices include Received and Declined. Invoices created by Contract users have a status of Not applicable.

  Working with vendor-submitted invoices

  When you select a pending invoice, the Decline and Received buttons become enabled. Click Received to accept the invoice or Decline to reject the invoice and send it back to the vendor. These buttons are disabled when you select multiple invoices or an invoice created in the project by the contractor.

  When you click the Decline button, the Reject invoice dialog box opens. You can write a note telling why the invoice was rejected and then click Save to save the rejection and send it to the vendor. The invoice remains in the register with a status of Declined until the vendor users recalls it. After it is recalled by the vendor, the invoice is no longer shown in the register.

  When you click the Received button, the Receive invoice dialog box opens. After you add an approval note and click Save, the Vendor status column shows the Received status, and the invoice can be added to a payment form like an invoice that was created in the project.

  The Invoice tab of the Notes/Feed slide-out panel has been updated to show notes from the vendor for vendor-submitted invoices. These notes show with a blue bar on the left side of the note. The Send note to vendor check box was also added to the Notes/Feed slide-out panel. When the check box is unselected, the note is only visible to the project team and is not sent to the vendor. When the check box is selected, the note is sent to the vendor. The check box is enabled only for vendor-submitted invoices.

  

• Line item long description – The Long description has been added to the Line item type configuration setup page in the organization settings. Read more

  The Long description field lets you specify whether the line item Long description field is enabled on the Line Items page and whether it is required for workflow, locked after workflow, required for a purchase order, or locked after a purchase order.

  The Long description field can be configured for each line item type.

  

  If your organization uses a material master that has material attributes, the Long description field in the Line item details is disabled, and you must click the Assign material attributes icon to add a long description, regardless of the setting for the Long description field.

• Supporting documents permissions – You can now restrict users from adding, editing, or deleting supporting documents for bid packages and contracts. Read more

  The Add supporting documents, Edit supporting documents, and Delete supporting documents permissions have been added to the Edit bid packages and Edit contracts permissions in Suite Administration. Existing roles have been updated to have all three options selected if the Edit bid backages or Edit contracts permission is selected.

  The check box for the Delete supporting documents permission is enabled only when the Edit supporting documents permission is selected.

  

• DocuSign certificate of completion and time stamp – After signing is completed, the certificate of completion is now available when you hover over the ellipsis in the DocuSign status field in Supporting documents. Also, the Modified on column has been added to the DocuSign status information. Read more

  The View certificate of completion link becomes available after a document is completed. The certificate of completion is stored in Supporting documents, but it does not take up a separate entry in the Supporting documents register. The certificate does not expire in Contract.

  

  When you click View certificate of completion, a preview of the certificate from DocuSign opens in a new tab. You have the option to download the file if you want to store it separately.

  The Modified on date and time stamp is updated each time the DocuSign status changes.

• Invoice attachments preview – When you click the entry in the File/Link column to open an invoice attachment from the Invoice attachments or Invoices register, the document now opens a preview in a new tab, so you can view the pages instead of automatically downloading. The preview lets you view all pages of the document by clicking the Previous and Next buttons. If you want to download the document, click the Download file button in the preview.

• Advanced vendor search for Add contract – The advanced vendor search has been added to the Add contract dialog box, so you can easily select vendors when creating a contract. Read more

  To use the advanced search, type the first characters of the vendor search criteria in the Vendor field of the Add contract dialog box. The Advanced vendor search icon shows at the bottom of the Vendor drop-down list.

  

  Click the icon to see the Select vendor dialog box that shows more vendor details and has its own search function.

• Vendor contact enhancement – You can now enter any name in the Primary contact field in the Vendor contact section if the contract header. This lets users who might not have access enter vendor contacts in InEight Platform to add a primary contact name. As you type a name, the field shows names that have already been configured that might match. If you want to add a different name, you can continue typing.

• Vendors change order log totals row – A Totals row has been added to the bottom of the vendor change order log, so you can see the total of all vendor change orders for a contract. Read more

  The total amount of vendor change orders is calculated and shown at the bottom of the Vendor CO amount column.

  

• Negative goods receipt – You can now enter a negative quantity in a goods receipt up to the amount that has already been received. The negative quantity lets you back out quantities that may have been entered in error instead of canceling the receipt and starting over. Read more

  For example, if you submitted a goods receipt for a line item with a quantity of 100 and it needs to be adjusted to a quantity of 10, you can create a goods receipt for a quantity of -90. After the goods receipt is submitted, Contract automatically calculates the submitted receipt amount accordingly.

  A goods receipt must already be submitted before you can create a goods receipt for a negative quantity. When you create the negative goods receipt, you can enter a negative quantity up to the quantity that was previously received.

Updated 28-JUN-2023

• eSign enhancements – You can now correct documents in the original eSign envelope to avoid the expense of additional envelopes. Read more

  A new Correct button has been added to the DocuSign status that shows when you hover over the ellipsis for a document with the status of Sent.

  

  When you click Correct, DocuSign opens with the view of the original envelope instead of recalling the envelope and sending out a new one. If the document has not been signed, you can edit it, change the order of recipients, and change whether they are to sign or receive a copy.

  A new permission, Correct eSignature, has been added. You must have the Correct eSignature permission to correct DocuSign documents.

• Supporting documents preview – When you click to open a supporting document, the document now opens a preview in a new tab, so you can view the pages instead of automatically downloading. This feature is available on all Supporting documents pages. Read more

  The preview lets you view all pages of the document by clicking the Previous and Next buttons. If you want to download the document, click the Download file button.

  

• Contract register update – The Schedule value and Claimed value columns have been added to the Contract register. When a contract is associated with a schedule of values, the Schedule value column shows the sum of all scheduled values, and the Claimed value column shows the sum of values that have been claimed to date.

• Bid package milestone Default setting – The Required column toggle in the bid package milestone grid in both the organization and project settings (Settings > Contract > Bid packages > Bid package milestones) has been renamed to Default. Read more

  The setting indicates whether the milestone is required. Milestones set to Default cannot be removed from the bid package.

  

• Diversity participation sort order – The Diversity participation grid in the organization settings can now be reordered. Up and down arrows have been added to the Diversity participation grid (organization Settings > Contract > Contracts > Diversity Participation) to let you manage the order of diversity categories in the Diversity participation drop-down list in the contract header. Read more

  Managing the order of the list items can place the most used diversity categories to a more prominent position in the drop-down list.

  

• Vendor change order Schedule of values register update – The Unit Price column has been added to the Total revised value section of the Vendor change order Schedule of values register. As you make changes to a schedule item through a vendor change order, the unit price reflects the value after the change order is executed.

• Supporting documents time stamps – A time stamp has been added to the Added on and Modified on columns on all Supporting documents registers to provide more visibility into when a document was added or modified. Previously the fields only showed a date. Read more

  

  The time stamp does not show when you use a tag for Added on and Modified fields in a generated document.

• Invoice notes – You can now add notes specific to an invoice. Read more

  The Notes/feed icon has been added to the Invoices register. To add a note to an invoice, select the invoice, and then click the Notes/feed icon. You can then add notes to the Invoice tab of the Notes/Feed slide-out panel.

  

  Notes added to the Invoice tab show for the invoice only. You can add a note for the contract on the Contracts tab of the slide-out panel.

• Product flag for supporting documents – The types of supporting documents that you can create in Contract are now configured in organization settings (settings > General > Document types). Only document types that have been enabled in the settings can be created in Contract. You can make document types unavailable in Contract only if they have not been used.

• Schedule of values validation check – When you try to delete a schedule of values item that is associated with a draft vendor change order or payment form, a warning shows stating the item cannot be deleted.

• Line item import template – The line item import template has been updated to match new line item formatting and include additional fields.

• Advanced template settings – You can now specify the event at which a watermark is no longer required when generating a contract document. You can also define template settings based on template type. Read more

  The organization-level template settings tab (Settings > Contract > Contract templates > Template settings) has been redesigned so that you can set the template configurations toggles for each template type. Previously, the configurations applied to all template types.

  

  The End watermark requirement event field has been added for each template type. The field is enabled when the Require watermark stamp upon document generation toggle for a template type is set to Yes. You can then select the event that must occur before the watermark stamp is no longer required or to always require a watermark stamp. For example, if you set the End watermark event field to Contract approval, the watermark is no longer required after the contract is approved.

  

  When you generate the contract document after the end watermark event, the Select watermark stamp field in the contract templates details is shown, but a value is no longer required.

• Role-based workflow – Users added to a role after workflow has begun can now approve or reject items. Also, all roles are now available at the organization level to be assigned to workflows. Previously roles that had a base level permission of 0 could not be assigned at the organization level. Read more

  If you are added to a role that is associated with an active workflow, you can see the workflow item on your Action items tab. You can open the items from the Action items tab or from the applicable register, and the Approve and Reject buttons are shown. You do not receive an email notification.

• VCO schedule of values push/pull validation – The VCO schedule of values Push to line items and Pull from line items actions now validate that the line item associated to the schedule item has a nonzero unit price. Read more

  A dialog box warns that the line item has a zero unit price, and the adjustment quantity and unit price for the vendor cannot be calculated. You can click Yes to proceed or No to stop the push or pull action. If you proceed with the push or pull, no values are calculated for the Change order adjustments section of the VCO. You must add them manually.

  

• Approval status in contract query – The Approval status column has been added to the Contract query, so you can search for a contract by approval status.

• Schedule of values Associate schedule item – The Convert icon on the Schedule of values page has been relabeled as Associate schedule item to be consistent with the labeling on the Line items page. The functionality remains the same.

• Two-way match – The Use invoice plan for this contract type toggle in the Contract type configuration setup (organization Settings > Configurations > Contract type configuration setup) has been renamed to Use two-way match for this contract type. The Invoice plan toggle on the contract Header page has also been renamed to Two-way match. Read more

  

  The functionality of the toggles has not changed. When the toggle in the header is set to Yes, all lines are ineligible for goods receipts, and depending on your ERP system mapping, the ERP may create an invoice plan.

  

• External requisition and contract import – The Purchase Order Request and Response APIs have been updated to let you import contract data from an external system. Read more

  The Purchase Order Response (using the PurchaseOrder_Import API) now lets external systems create a new contract header and enter associated line item details. After the header and line item details are imported, you can then confirm the contract details and create the purchase order in Contract. Additional fields have been added to both APIs to match other import methods.

  Also, Requisition ID and Requesition Value fields have been added to the contract header to support external contract requisition requests using the updated APIs.

  

• Contract currency enhancements – Contract has improved how it handles differences between project and contract currencies. The InEight Control budget sent in the base currency is now converted to the contract currency for the budget and commission data block and for workflow. The contributed value of associated change items in a vendor change order are now converted to contract currency. Previously they had been in the project currency. Read more

  Contract now considers currency exchange rates when reviewing budget values and initiating workflow.

  If a contract or bid package currency exchange rate has not been configured in the project details, a yellow warning banner shows at the top of the contract Header page.

  

  When a workflow or budget check is started, Contract converts workflow values from the project currency to the contract currency to see if you have crossed a threshold or exceeded budget. In the case of a workflow, if the conversion shows that the value is greater than or equal to the threshold, the workflow begins.

  For the budget and commitment values, if the contract currency is different from the project base currency and a conversion rate is configured in the project details, Contract shows values in the contract currency.

  If there is no conversion rate listed in the project details, the conversion rate is assumed to be 1:1.

• Vendor change order Line items tab enhancements – The Vendor change order Line items tab has been redesigned with collapsible sections to make it easier to use. Read more

  The Vendor change order Line items grid is now divided into sections, so you can easily see related columns. Information that populated views in the previous releases are now in their own sections.

  

  You can click the arrow in the column header to collapse or expand the section. Multiple sections can be collapsed. The first section, which includes the Line item ID, Description, and UoM cannot be collapsed. You can click the double arrow in the first section to collapse the rest of the sections.

  The column management feature lets you rearrange grid sections and add or remove columns within the sections. Click the Manage columns icon in the toolbar to open the Column Selector Builder dialog box.

  

  The Available columns section shows all columns that are available for each section. To add a selection or column, select it, and then click the arrow to move it to the Selected Columns section. To remove a section or column, select it, and then move it to the Available columns section. Click Save to apply the changes. You can also rearrange sections from the Column Selector Builder dialog box. To move a section, select it, and then use the arrows to move the section up or down. You cannot add columns to the first section in the grid. You cannot move columns between sections.

  You can search for specific available or selected columns. For example, you could search for value Price, and the search results show all columns with Price in the column name in all sections.

• Schedule of values register enhancement – The total items and selected count have been added to the Schedule of values register. The total items and selected count have also been added to the vendor change order and payment form schedule of values registers. Read more

  The bottom of the grid now shows the total number of items and the total number of selected items.

  

  Filters also have been added to the bottom of the grid, so you can see selected items without having to scroll through all pages. Click View selected to only see the items you have selected. Click Clear selection to deselect all items.

  The Go to Schedule ID link has been added to the upper left toolbar to help you quickly find Schedule items that are not visible on the page.

• Schedule of values Convert options – The options for the Convert icon on the Schedule of values tab now varies based on permissions. The options for Convert to accrual/receipt show only when you have accrual/receipt permissions. The Convert to payment form option shows only when the Use payment forms toggle in the Contract type configuration setup in the organization settings is set to Yes and you have payment form permissions. If you don't have permissions to accrual/receipts and payment forms, the Options icon is disabled.

• Contract writer prior VCO tags – New tags have been added to show the sum value of prior pending and executed VCOs. These tags add the values of VCOs created before the currently selected VCO.

• Contract number and ERP doc type character limits – The contract number is now limited to 10 digits, and the ERP document type is now limited to 50 digits.

• Associate a bid package link in Contract details – The Associate a bid package link on the Contract details tab is now automatically hidden when the contract type has not been included in the bid package configuration. Previously the link was always shown.

• Schedule of values tab enhancements – The Schedule of values tab has been redesigned to make it easier to use. Enhancements include the ability to claim schedule items directly from the Schedule of values tab. Read more

  Improvements include new sections with headers, the ability to make claims, and access to claim history. Column management and search features have also been enhanced.

  Grid sections

  The Schedule of values grid is now divided into sections, so you can easily see related columns. Sections include Schedule of value items, Contract, Component progress, and Summary progress. You can click the arrow in the column header to collapse or expand the section. Multiple sections can be collapsed. The first section, which includes the Schedule line item ID, Contract line item ID, and Description cannot be collapsed. You can click the double arrow in the first section to collapse the rest of the sections.

  

  The Schedule of value items section shows details for the schedule of values item.

  • The Contract section shows claims that were made in Contract.

  • The Component progress section shows claims that were made in InEight Plan and InEight Progress. Previously, these claims were shown in the Component progress viewset.

  • The Summary progress section shows the total of claims made in Contract and in Plan and Progress.

  The calendar has moved to the toolbar. You can use the calendar dates in the toolbar to filter schedule items for a specific period.

  Column management and search features

  The column management feature lets you rearrange grid sections and add or remove columns within the sections. Click Manage columns in the toolbar to open the Column Selector Builder dialog box.

  

  The Available columns section shows all columns that are available for each section. To add a selection or column, select it, and then move it to the Selected Columns section. To remove a section or column, select it, and then move it to the Available columns section. Click Save to apply the changes. You can also rearrange sections from the Column Selector Builder dialog box. To move a section, select it, and then use the arrows to move the section up or down. You cannot add columns to the first section in the grid. You cannot move columns between sections.

  You can search for specific available or selected columns. For example, you could search for value Claimed, and the search results show all columns called Value Claimed in all sections.

  Contract claims

  You can now claim schedule items from Contract. Previously, you could only claim items in Plan and Progress but now when the Hide in Plan and Progress check box is selected, you can claim a schedule line item from the Contract Claim tab of the Edit schedule item slide-out panel.

  

  You can enter a claimed quantity, and the claimed value is automatically updated, or you can enter a claimed value and the claimed quantity is automatically updated. You must enter a claimed date. If you want to claim additional quantities, click the Add claim icon on the Contract Claim tab. Click Add to add the claims.

  You can also double-click the value of the Claimed quantity or Claim value field to claim items from the register. The Add claims dialog box opens, and you can then enter the claim information. All claims become visible in the Contract Claim section and the contract claim history.

  Claim history

  The Contract Claim History tab on the Edit schedule item slide-out panel shows all claims made in Contract against the schedule item.

  

  Claim multiple items

  You can claim multiple items at one time from the Schedule of values register. To claim multiple items, select one or more items, and then click the Claim multiple schedule items icon. The Claim multiple schedule items dialog box opens.

  

  You can then enter the claimed quantity or value for each item. To add additional schedule items, click Add schedule item. The Add schedule items box opens, and you can then select schedule items from the list.

  

  Click Add to apply your changes. After all items are entered in the Claim multiple schedule items dialog box, click Claim. The claims are added to the schedule of values.

  Claim schedule items from a spreadsheet

  When you have many schedule items to claim at one time, you can use the import function to claim these items. To claim items, click the Export icon on the Schedule of values tab, and then select With data. An Excel spreadsheet with the schedule items is downloaded. Open the template, and then claim items in the Quantity claimed or Value claimed columns. Save the file, and then import the file as you would in other modules.

  Claiming templates

  If you have many schedule items or if you have a group of claims that you use on a regular basis, such as at the end of the week or each time concrete is poured, you can create a claim template. The template can help you quickly find the schedule items you need each time the event occurs.

  To create a claims template, select one or more items as you would for claiming multiple items. Click the Claim multiple schedule items icon. The Claim multiple items dialog box opens. Add the schedule items for the event.

  

  After all items are entered, click Save as template. The Save template dialog box opens. Enter the name of the template, and then click Save.

  To use a claiming template, click Load template in the Claim multiple schedule items dialog box. The load template dialog box opens where you can select the claiming template to use. Click Load.

  

  The template opens in the Claim multiple schedule items dialog box. You can add or remove items. You can then claim items as you do when you are claiming multiple items.

  Convert a schedule of values to a payment form

  You can quickly convert schedule of value items to a payment form from the Schedule of values register. The new payment form is automatically populated with values from the schedule of value items for the date range selected.

  Any schedule item can be converted to a payment form. To convert schedule of value items to a payment form, select a date range, and then select one or more claimed schedule items. Click the Convert icon, and then click Convert to payment form. The Add payment form dialog box opens.

  

  You can add the payment form information, and then click Add. The payment form is added. The Payment form details page opens, so you can continue adding payment form information. The schedule items you selected show in the Payment forms schedule of values.

• Payment forms schedule of values – A Schedule of values tab has been added to payment forms. This feature at the payment form level lets you build the payment form from a schedule of values instead of using only line items. Read more

  Using a schedule of values to populate a payment form gives you the flexibility to create a payment form based on the values claimed in a specific period. For example, you could use the schedule of values to track the values used in a month. You can then push the values to the Payment form Line Items tab, so you pay against the line items.

  To add schedule items to the Payment form Schedule of values, click the Add icon.

  

  The Add schedule item dialog box opens with a list of schedule of value items from the Contract schedule of values, including the value remaining and the percent complete.

  

  Select one or more items, and then click Add. The items are added to the schedule. You can then update the Quantity or Value columns in the This submission section. When you update the Quantity column, the value in the Value column is automatically adjusted, and vice versa.

  To push schedule items to the Line Items tab, so they can be included in the payment form, select them, and then click Push to line items.

  

  A warning message indicates that the push updates the Line Items tab with values from the schedule items. Any value or line item that was added to the Line Items tab is removed. Contract then pushes only the line items that are associated to the Contract schedule of values and calculates the line item values. On the Line items page, the total values are shown in the Net price column in the This submission section. If there are multiple schedule items tied to the line item, Contract adds them together to populate the Net price column.

  The payment forms Schedule of values page has a structure like the enhanced Contract Schedule of values page. The Payment form page has the following columns to show the progress of a schedule item in payment forms:

  • This submission - The values used in this payment form.

  • Pending submission - The values used in previous payment forms that are not in Submitted status.

  • Previous submissions - The values used in previous submissions that have been submitted.

  • Current total - The sum of values in This submission, Pending submission, and Previous submissions.

  • Remaining - The Schedule quantity column in the Schedule of Values items section minus the current total.

  From the Payment forms Line Items tab, you can pull from schedule items. When you update the quantities in the This submission section of the Schedule of values tab, you can click Pull from schedule items to update the line items tab.

  

  When you click Pull from schedule items, a warning message indicates that values in the line items will be overwritten. When you click Yes, the values from the Schedule of values page overwrite the values on the Line items page. If there are no values on the Schedule of values page, Contract sets the quantity and net price to 0.00. Any value or line item that is not associated to schedule items is removed.

• Create an InEight Document form or mail – If a project is associated with Document, you can create a form or mail item from a contract, bid package, VCO or payment form. Read more

  To create a form or mail, expand the Actions menu on the Details page, select Create document, and then select Form or Mail. If you are not signed in to Document, you can sign in using single sign-on. The Create Document Mail or Create Document Form dialog box opens in Document, where you can enter the mail or form information. You can then add your attachments.

  When you create mail and if you have selected documents, they are automatically included in step 2 of the Create Document Mail dialog box. If you did not select documents, you can add them from the dialog box. After you have completed the fields in Document, you are returned to Contract. You can select the document type, and then attach it to the bid package.

• Enhanced Line Items registers – The Line Items registers have been enhanced to support contracts with up to 3000 lines. Sorting and error identification features have been added to help you quickly find the line items you need. Read more

  An error column has been added so you can quickly see if there is an error in the line that must be fixed before you can publish the contract. A yellow warning icon in the column lets you know that the line has errors (that is, the line is missing required fields). If you try to publish without fixing the errors, a red warning icon is shown.

  

  The bottom of the grid now shows the total number of selected items and errors. The total includes items on all pages, not just the current page. Click Clear selection to deselect all items.

  Filters also have been added to the bottom of the grid, so you can see selected items or items with errors without having to scroll through all pages. Click View selected to only see the items you have selected. Click n Items to see only the items with errors.

• DocuSign enhancements – The person who sends the document to DocuSign now receives an email notification when the document signatures have been completed. Also, you can now send a courtesy copy to recipients on documents sent for eSignature. The Action field has been added to the DocuSign recipient page of the Send for signature dialog box. You can then select Needs to sign or Receives a copy. Read more

  When the action is Needs to sign, the recipient receives a document that is ready to sign. When the action is Receives a copy, the recipient receives a snapshot of the document in the signing order. For example, if the recipient marked Receives a copy is second in the signing order, they receive the document after those first in signing order, even though they are not signing.

  

• Option to show or suppress supported document details in generated document - You can now specify whether a supporting document details are shown in a generated document. Read more

  Previously, when you used a supporting documents collection table tag in a template, all the documents in the register showed in the table in the generated document, even if they were not needed for the document.

  A new toggle on the Supporting documents register, Show in generated document, lets you indicate whether the document is shown in a collection table based on the collection table type. When you have a supporting document that you do not want to show in a collection table in a generated document, set the toggle to No. When a document is generated, only the documents that were set to Yes are shown.

  

  A document that is available at more than one level, such as a contract-level document available on the contract and VCO Supporting documents pages, can have a different setting at different levels. For example, you might set the toggle at the contract level to Yes to show in a generated document. You could set the toggle at the VCO level for the same document to No to not show in a VCO document. Contract uses the setting that corresponds to the level of the collection table tags in the template. Using the previous example, Contract shows the supporting document in a collection table as follows:

  • When you generate a document for a contract, the document is shown because the only collection table type in a contract document is a contract table.

  • When you generate a document for a VCO that has a contract-level collection table, the document is shown because it is part of a contract-level collection table.

  • When you generate a document for a VCO that has a VCO-level collection table, the document is not shown, because the document is suppressed at the VCO collection table level.

• DocuSign tag additions – You can now add DocuSign Text, Checkbox, Dropdown, and Radio button tags to your document templates. The tags let you to set up placeholders for those field types in your template. You can then add values in the DocuSign Sender view. Read more

  The DocuSign tags have been added to the DocuSign template tags for eSign 1-10, and for each project contact. When you add the tags in the template, you ensure that the corresponding item is consistently placed. For text and drop-down lists, you only place one tag in the template. For check boxes, you place one tag for each option. For radio buttons, a single tag places two buttons in the document. You can add more radio button tags for additional buttons.

  When a document with these tags is opened in the DocuSign Sender view, the tags are present, but they do not have values. You can add the values from the Sender view. For example, if the template has three check box tags, when the document is opened in DocuSign, three empty check boxes are shown. You then add the value for each check box in DocuSign.

• Custom labels in DocuSign – When custom labels are used for contacts in InEight Platform project details, Contract now uses the labels in the DocuSign section of the Contract, VCO, and Bid Package Details pages and in the Send for signature dialog box.

• Closed contract line items enhancement – Contract line items are now automatically closed when they are deleted. Read more

  You can only delete a line if there are no goods receipts or invoice receipts against it. Previously, when you deleted a line, it was deleted, but not marked as closed, and then a deletion indicator was sent to the ERP system. Now, when the item is marked as closed, the deletion, no further delivery, and no further invoice indicators are sent to the ERP system.

• Supporting documents edits – When a supporting document is in Approved status, you can now edit only the title, notes, and expiration notification.

• Supported document types – Contract now supports all document types, including custom document types, from InEight Platform. The document types are used when adding a new supporting document.

• Tax descriptions used in tax information – The Tax description configured in project settings is now used in the Total tax information icon to make the description more user friendly. Previously, the tax information came from the description in the purchase order or payment form response. Now, if the tax code in the response matches a tax code in the project settings, Contract uses the description in the project settings instead of the description in the response.

• Unavailable vendors in Platform – Platform Vendor details now support an Unavailable status for vendors. When a vendor is marked as Unavailable, and you have a contract for that vendor, the contract shows a warning icon. Any vendor that is unavailable is not shown in drop-down lists for new contracts and bid packages.

• Assigning vendors to Platform – When you publish a contract or payment form, Contract now automatically sends the vendor to Platform and assigns it to the project.

• Schedule of values line item viewset – A new data block has been added to the Line items page that lets you see the schedule of values items associated to each line item. This view provides a comparison between the line items and the schedule of value items. Read more

  The Schedule of values view is available in the View menu on the Line items page. The data block shows the scheduled value, value claimed, percent complete, and value remaining.

  

  When you click the scheduled value, you can see a detailed view. Each column can be sorted or filtered.

  

• Bid package register enhancements – You can now create and save custom views on the Bid package register, and edit specific fields in bulk. The Total estimate column has also been added to the register. Read more

  Create and save custom views

  To create a custom view, use the column chooser to add or delete columns from the current view, and then select Save view as from the View menu.

  

  The Save view name dialog box opens. Enter a unique name for the view, and then click Save. After saving, the Rename view, Delete view, and Share view options are enabled.

  To share custom views with other users, select Share view from the View menu , and then enter the names of the users you want to share the view with. The users must have the View permission for the project that you are sharing the viewset. Click Share. The users receive a notification in their Notifications list that they can access by clicking the Notifications icon in the upper right toolbar.

  To use and save a view created by another person, click the link in the notification. A dialog box opens prompting you to save the view. You can then enter a unique name for the view.

  Edit fields in bulk

  Columns that can be edited in bulk include those with free text or a drop-down list. When you need to make the same change to multiple bids, you can select them, and then click the Edit icon. The Bulk edit dialog box opens where you can select the field and the value. You can select up to five fields. Click Save to update the bid packages.

  

  Bid packages that have not been approved or converted to a contract cannot be edited.

• Bid package register editable fields enhancements – Editable fields in the Bid package register are now highlighted when you hover over them. This lets you quickly see which fields are editable. You also can now edit the budget columns from the Bid packages register. Read more

  A blue frame is shown around editable cells.

  

  The budget fields include the following:

  • Original base value
  • Contingency in estimate
  • Un-awarded adjustment
  • Escalation in estimate
  • Owner change amount
  • Actual completion date

  When you make a change to any of the editable fields, a blue dot shows to indicate a change that has not been saved.

  

• Include bid packages in primary reporting section – You can now set the default value at the organization level for the Include bid packages in primary reporting section. Read more

  The Include bid packages in primary reporting section toggle has been added to the bid package type configuration (organization > Settings > Contract > Configurations > Bid package type configuration setup).

  

  For each bid package type, you can specify the default for the Include this bid package in primary reporting section field (Bid package details > Additional Details > Reporting). The field value can be changed.

• Template writer versioning – You can now create a new version of an existing Contract writer template. This is helpful when you update templates with additional information. You can now update the version rather than inactivating the template, and then creating a new one. Read more

  The Create New Version button has been added to the Template details page. The button is enabled after you select a template from the register, and then click the Edit icon.

  

  When you create a new version, the version numbering starts after the previous version. The new template version starts in the draft state. You can edit any of the fields except the template type and language. You can then attach the new file.

  Only one version of a template can be active at the same time. After you add a new version, the previous version becomes inactive and is removed from the Templates register.

  The Version column has been added to the Templates register, so you can see the version. When you click the version number, the template version history is shown. The template names are linked to the Template details page, so you can quickly view the detail information.

  

  The Version history subtab has been added in the template with links to previous versions. The version history shows all versions in descending order, including inactive versions.

  

  Versions of organization-level templates are available for use at the project level, but you can only create a new version of those templates at the organization level.

• Contract writer template enhancements – Purchase order has been added as a template type at the project level. Previously, the purchase order template type was only available at the organization level. You can also copy a template and edit a template. Read more

  You can now edit details for published documents. You can edit the template name, description, markets, and set as default field. Changes to these fields do not create a new version.

  At the project level, you can now copy an organization-level template to the project level, so you can make changes specific to a project without affecting the organization-level template. The new project-level template is version 1. The template details are editable. After the project-level template is published, changes at the organization level do not affect the project-level template.

• New template tags – General tags have been added to break out vendor addresses. Previously, one tag held the entire address. Now, each part of the address has its own tag. New tags have been added for the VCO pricing item description and the tax descriptions and tax types.

• DocuSign updates – The Send for eSignature permission has been added. Previously, any user who had edit contract permission could send for signature. Also, when you send a document for eSignature, the name of the user who sent the document shows when you hover over the DocuSign status.

• Vendor change order line items tab updates – The Price column has been renamed to Unit price to be consistent with the naming convention across Contract.

• Restrict updates to existing lines in a vendor change order – A new organization-level setting lets you specify if lines can be updated in a vendor change order (VCO). Read more

  The Allow changes to existing lines toggle has been added to each contract type in the contract type configuration setup (organization > Settings> Contract > Configurations > Contract type configuration setup). When set to No, the Add existing line items option on the VCO line items tab is disabled, and then all lines added to the VCO are Add new line item only. When set to Yes, line items can be edited or deleted from the VCO. This prevents users from adjusting existing lines and aligns with the functionality of their ERP system.

  The setting is available only when the Use change orders for this contract type toggle is set to Yes.

  

  When updates are restricted, you can only add new lines to the VCO. You cannot add existing lines. Existing lines are not editable and cannot be deleted. If the contract is associated to a master agreement, you can add a line from the master agreement.

  It is recommended that when you set the toggle to No, you also set the Maximum contract overage allowed without a change order to be 0% to ensure that the line item cannot be changed. With this configuration, every change must be a VCO and must be a new line.

• Export file naming conventions – The file naming conventions for exports have been updated to [type of export]_[project display ID]_[YYYY-Month-DD].

• Master agreement enhancements – The Download purchase order icon has been added to the master agreement Associations tab.

• Automatic closing of line items – After a contract line item has passed its valid through date, the line item is now automatically set to Closed. This enhancement aligns with how many ERP systems close line items. Read more

  The valid through date is 11:59 p.m. on the date specified in the Valid through field in the Line item details.

  If you do not want the line item status to be Closed, you can manually change the status. When the contract is already published and the line item closes, the Line Item ID field shows the Revised line item icon.

  

• Payment form tab enhancements – The payment form is now editable from the Payment forms register, so support staff can make changes to the payment to keep Contract in sync with an ERP system. Read more

  The Edit icon has been added to the Payment forms register.

  

  To edit a payment form, select the form, and then click the Edit icon. The Edit payment form slide-put panel opens, where you can make changes to the Payment form status, Record ID, Record status, and Notes fields. You can edit up to 10 payment forms at one time. When you edit the Payment progress tab, no APIs are triggered, so duplicate items are not created and submitted to the ERP system.

  Changes made on the Payment forms tab affect the Payment forms tab only. They do not affect the Payment progress tab.

  The Administrative notes tab has been added to the Notes slide-out panel. This tab contains changes made to the payment form from the Payments form tab or the Payment progress tab. The notes are automatically generated when changes are made.

• Payment progress tab enhancements – New fields for Record status, Payment form ID, and Payment form request code have been added to the Payment progress register. The Record status field is editable from the register as are the Record ID, Paid amount, Method, Check number, Date cashed, and Retention released fields. Users with the permission EditPaymentProgress can edit the payment progress to keep Contract in sync with an ERP system. Read more

  Changes made to the payment form from the Payment progress register are shown in the Notes tab on the Payment forms register.

  Changes made on the Payment progress tab affect the payment progress tab only. They do not affect the Payment forms tab.

• Custom lists at the project level – Contract and line item custom lists are now available at the project level. The existing organization list is applied to the project level and defaults to Active. Ordering of custom lists is now handled at the project level, and if you do not want to use an item on a project, you can disable it at the project level. The Custom list page has been added to the Configurations settings (Project home > Settings > Contract > Configurations > Custom list).

• Bid package register enhancements – Viewsets have been added to the Bid package register. Also, the Contract number column has been changed to Contract ID. Columns for Contract ID, Custom lists 1 and 2, and Custom fields 1-10 have been added. Read more

  By default, all bid packages are shown in the Bid packages register. You can change the view to show only the bid packages in one of the following sets:

  • Awarded

  • Unawarded

  • In approval

  • Rejected

  

  The new custom fields have also been added to the import template. Custom labels that have been configured in project settings are retained in the register.

• Bid package milestone updates – You can now edit a scheduled completion date or the duration. Contract automatically updates the duration (if you changed the date) or date (if you changed the duration) of the scheduled item and the subsequent milestone dates. The Completed flag for a milestone is now automatically set when you enter the actual completion date. Previously, you had to enter the date and set the flag separately. Read more

  In this example, if you change the scheduled Request for proposal duration from three days to four, all the milestone dates after that are automatically changed.

  

  The previous completion dates are not affected.

  The flag icon in the Complete column of the Milestones section is filled in when you enter a value in the Actual completion date field.

  

  If you delete the date, the flag no longer shows as filled in.

• Editable bid package register fields– You can now edit custom fields, custom lists, date, duration, and float fields from the Bid package register. Read more

  The following fields are editable in the register:

  • Custom lists 1 and 2

  • Custom fields 1-10

  • Kickoff date

  • Project delivery date

  • Milestone float, date, and duration fields

  When you make a change to any of the editable fields, a blue dot shows to indicate a change that has not been saved.

  

  The Save changes button has been added to the toolbar. When you click Save changes, the edits are saved, and the blue dot is removed.

• Bid package import based on date or duration – You can now choose whether to base milestones in bid package imports on dates or durations. Choosing either dates or durations prevents errors when dates and durations entered in the import template are out of sync. Read more

  Bid package import now provides the ability to update dates or durations via import. A new field, Update milestones based on, has been added to the Import data from template dialog box. Before you import, you must select whether date or duration is the driver used to calculate fields.

  

  If there are discrepancies between a date or a duration, Contract uses your selection to calculate correct values. For example, if you choose to use dates, and the difference between the milestone scheduled date and the milestone forecasted date is five days, but the duration shows 10 days, Contract calculates a new duration of five days instead of using the duration from the template.

• Bid package budget check – You can now compare the bid package budget to the InEight Control cost item budget as part of the approval process. Also, a new organization-level setting lets you specify whether to allow the bid package workflow when the bid package is over budget. This prevents you from committing to a vendor and converting to a contract when you do not have the budget to support it. Read more Watch video

  A new step in the bid package workflow, Budget check, compares the original base value against the current budget before you start the approval process.

  

  Organizations can control whether workflow can be initiated based on budget. The Allow workflow when over budget toggle has been added to the bid package type configuration setup at the organization level (Organization home > Settings > Contract > Configurations > Bid package type setup). The toggle is set for each bid package type.

  

  When the toggle is set to No and the original base value exceeds the WBS current budget, an error shows when you try to start the approval process. You should then check the original base value or reach out to the project controller.

  

  When the toggle is set to Yes and the original base value exceeds the WBS current budget, a yellow warning banner shows at the top of the Budget check tab if there is a loss. You can still start the workflow if the bid package exceeds the current budget.

  

  The budget information has also been added to the workflow email notification, so that the approvers can see the budget before they approve the bid package.

• Budget commitment data block – A new line item data block provides cost item information from InEight Control and contract commitments on the line item has been added. The data block gives a more accurate comparison between the CB total cost and the line item cost. Read more

  The data block shows the following fields:

  • WBS
  • OB total cost
  • CB total cost
  • CE total cost
  • Line item commitment
  • Pending line item commitment

  

  The CB total cost column in the Budget and committed cost data block is equal to the sum of each unique WBS for each line item in the contract. That is, each WBS is counted only once if the same WBS is used in multiple lines.

• Contract commitment check – You can now compare the contract value to the Control cost item budget as part of the approval process. Also, a new organization-level settings lets you specify whether to allow the contract workflow when the contract is over budget. Read moreWatch video

  A new step in the contract workflow, Commitment check, compares the current value against the current budget before you start the approval process.

  

  Organizations can control whether workflow can be initiated based on budget. The Allow workflow when over budget toggle has been added to the contract type configuration setup at the organization level (Organization home > Settings > Contract > Configurations > Contract type configuration setup). The toggle is set for each contract type.

  When the toggle is set to No and the current value exceeds the WBS current budget, an error shows when you try to start the approval process. You should then check the current value or reach out to the project controller.

  

  When the toggle is set to Yes and the current value exceeds the WBS current budget, a yellow warning banner shows at the top of the Commitment check tab if there is a loss. You can still start the workflow if the contract exceeds the current budget.

  

  The contract commitment information has also been added to the workflow email notification, so that the approvers can see the contract commitment before they approve the contract.

• Single sign-on to InEight Document – The sign-on to Document from Contract now enables single sign-on. When you use Contract to Document features, such as adding a document from Document, you are taken directly to the Document sign-on page, where you can enter your Document credentials. This creates a sign-on token that lets you remain signed in until the session ends. The first time you sign into Document, a secondary window and the Document Home window are shown. After you close these windows, they do not show again, and single sign-on is activated.

• Contract document template instructions – The instructions page of the contract document template has been updated to describe how to use the template tags.

• Download purchase order from master agreement – You can now download a purchase order from the Master agreements register. Read more

  The Download purchase order icon has been added to the Master agreements register toolbar.

  

• Master agreement inactive vendors – When you copy a contract with an inactive vendor, the Agreement ID field of the contract details still has the master agreement ID, but the contract is not associated. If you activate the vendor, you must manually associate the master agreement to the contract.

• Vendor change order associated change items – The Description column has been added to the Associated change items section of the VCO Details page. The Description provides additional information about a pricing item associated to the VCO. Read more

  The Description column has been added to the Associated change items section. This field allows pricing item descriptions to be added in Contract.

  

  When a pricing item is added, the icon is enabled and you can click it to add a description. After a description is added and saved, the column shows a View icon. You can click the icon to see the description of the pricing item. This field is also added to the collection table tags for contract writer generation.

• Automatic approval for the first step of a workflow – When you start the approval process and you are the first approver in the approval workflow, the first step of the workflow is automatically approved, and continues with the next step, if applicable. Read more

  When starting the approval process for a contract, supporting document, bid package, VCO, or payment form, and you are the first-step approver in the approval workflow, either as a user or a member of a role or group, Contract automatically approves the first step upon creation.

  An email is generated saying that the first step has been approved.

  If you hover over the Approval status value in the applicable register, step 1 shows that it was approved and is in step 2 if there is a step 2. If you are the only step in the approval, you receive a second email confirming the new issue has been approved.

  

• User date preference in import templates – Import templates now support the date format defined in your user preferences. Previously import templates only supported the MM/DD/YYYY format. Read more

  When you download the template, the date columns show dates in the format defined in your user preferences, so you can enter dates in your preferred format. When you import the template, the dates are read correctly.

  Contract validates the dates based on the person who imports the data. If the dates do not match the preferences of that person, Contract generates an error in the import history and removes the date.

• Tax settings enhancements – A Tax Description field has been added to the Tax configuration in organization and project settings (Settings > Contract > Configurations > Tax settings), to make the tax more recognizable. When a tax is referenced, the tax description is shown in the InEight cloud platform, which matches the tax type or ERP code used in APIs.

• Payment form default template – You can now specify which contract types use the payment form template as the default. Read more

  The Template Details page in the organization settings (Organization home > Settings > Contract > Contract templates > Template types) has been updated so that when the Template type field is set to Payment form, you have the option to set the form as the default.

  

  When the Set as default field is set to Yes, it becomes the default template when you download payment forms for the specified contract type.

• Generate contract document improvements – You can now generate a contract document from the master agreement Details page. A submenu has been added to the Generate contract document action on the contract Details page and the master agreement details page. Read more

  The submenu lets you filter by contact type, such as Contract, Payment form, VCO, Purchase order, or Other.

  

• Vendor name column – The Vendor name column has been added to the Contract and Supporting documents registers, so you can see more vendor information from the register.

• Contract line items improvements – You can no longer add or delete line items in a contract while it is in approval. Once the workflow is started, the Add and Delete buttons on the Line items tab are disabled.

• Payment form register – The Progress estimate billing period and the Progress estimate number columns have been added to the Payment forms register.

• Import template naming conventions – The naming conventions for import templates now have more information for easy identification. The format for the import template name is ImportTemplate-project display ID-template type.

Updated 24-FEB-2022

• Tax setting configurations – Tax configurations have been added to provide the ability to estimate contract taxes before publishing a contract and specify whether the payment form taxes should be calculated based on Gross price or Net price. You also can define whether those taxes should be included in committed costs to InEight Control. Read more

  Previously, the only way to estimate taxes on a contract before publishing was to set up a third-party tax integration. Now, this new tax configuration allows taxes to be estimated on a contract prior to publishing, without a third-party integration.

  When the integrate tax calculation toggle in the organization Contract configurations (organization settings > Contracts > Contract integrations > Integrate tax calculation before publishing contract) is set to Yes, estimated taxes are calculated using the endpoint listed in Application integration > Other > Contract: Tax Request. (Refer to the APIM documentation for set-up information.)

  If you integrate with an ERP system, upon publishing the Contract, the tax information is updated based on the Purchase order response from the ERP system.

  If integrate tax calculation toggle is set to No, taxes are automatically estimated using the taxes and default percent from the project settings.

  For proxy ERP customers, upon publishing the Contract tax information is based on project settings default percentage and tax types unless it is overwritten by manual upload of the LogicApps file import.

  Organization configuration

  The Tax configuration settings are on the Configurations tab (organization Settings > Configurations > Tax settings).

  Taxes set up at the organization level flow down to project settings when the tax type country code matches the project country listed in the project details.

  The organization can define the following:

  • Tax type

  • ERP code (If you are an ERP customer, you must match ERP codes)

  • Default percent

  • Country code

  • Calculate payment form tax

  • Include in committed cost

  • Active

  

  The position indicates the order that the taxes are displayed. To change the position of a tax, drag and drop the line to the new position, and then click Save. The changed position is applicable on all projects.

  The ERP code corresponds to the tax provided from the ERP. You can set a country code so the tax is only applicable to projects in a specific country. You can also indicate whether to calculate the tax on the payment form the net amount after retention is withheld or the gross amount before retention is withheld.

  Project configuration

  The Tax configuration settings are on the Configurations tab (project Settings > Configurations > Tax settings).

  Organization level taxes show based on the project’s country and tax type country code and have an information icon. Projects cannot reorder the taxes, rename the tax type, update the ERP name or country code, or delete an organization-level tax type. Projects can inactivate the organization tax, edit the Default percentage, change when to calculate the tax in a payment form based on the net amount or the gross amount, and whether to include the tax in the committed cost.

  Additional taxes can be set up at the project level. Taxes entered at the project level are listed before those configured at the organization level. Project level taxes cannot be deleted if the tax has already been used. If any tax is no longer applicable, you can deactivate it for future contracts. Marking a tax as inactive removes the tax type for future contracts estimated taxes, but the tax column remains in any register where it was listed if any contract on the project was created before the tax type as deactivated.

  Contract tax calculation

  In a contract, the Calculate tax link has been changed to Estimate tax. Prior to publishing a contract, when you click Estimate tax, taxes are calculated based on the taxes and their default percent listed in project settings.

  When the contract is published, tax information is updated from the Purchase order response.

  Any new lines added to a contract will follow the same behavior until the purchase order is updated.

  If the organization has been configured to Allow edits to Is taxable field (organization Settings > Contract > Configurations > Line item type configuration), the user is shown an Is taxable check box in the line item details above the pricing summary for the line item. This check box defaults to selected. The taxes for the line are estimated either from project settings or from a third-party integration. When the Is taxable box is unselected, no taxes are estimated from project settings. Any tax information that is provided in the Tax request response, purchase order response, or manually uploaded via LogicApps file are shown regardless of the “is taxable” check box and are considered when calculating taxes on payment form line item.

  

  Payment form tax calculation

  In a payment form, the active project tax types show in columns on the Payment form register. When you add an invoice, all active tax types are shown in the Add Invoice dialog box and in the invoice attachment register. Within the line items, the tax column calculates a proportional estimate of the line item taxes based on the taxes received in the purchase order response or manually uploaded via a LogicApps file and whether the tax type should calculate on net price or gross amount. These taxes are shown as a total and hovering over the information icon shows the individual taxes.

  Committed cost

  Each tax type established in Organization or project settings defaults to include in committed cost. This configuration includes the taxes in the committed cost values in Control. See the Control Release notes for new project setting Drive committed cost values from Contract.

• Bid package type configuration – Bid package configuration settings have been added for each bid package type. Organizations can set these fields as disabled, optional, or required based on workflow or conversion to a contract. Read more Watch video

  Bid Package type configuration setup has been added to the organization settings (organization Settings > Configurations > Bid package type configuration setup).

  

  All fields have Yes as the default for the Enable settings, but you can disable any field except the Currency field. When a field is disabled, it shows on the Bid package header tab, but it is dimmed, and you cannot enter a value.

  When enabled, you can indicate whether the field is required for workflow, locked after workflow, required for converting to a contract, and locked after converting to a contract.

  The Currency field is required workflow and converting the bid package to a contract. These settings cannot be changed.

  Also, organizations can define which contract types that the bid package type can be associated to. Click the Assign contract types icon to add or delete a contract type. You can also click the X by the contract type in the Selected contract types field to delete a contract type.

  

  The All required milestones must be completed toggle has been moved from the Bid packages settings (organization Settings > Contract > Bid packages) to the Bid package type configuration setup. The setting of this field applies to all bid packages.

• Bid package workflow – You can now set mandatory approvals for bid packages based on thresholds. The thresholds are based on the original base value of the budget. Bid package approval workflow can be set at both the organization and project levels. Read more Watch video

  The Bid package approval setup subtab has been added to the Workflow Assignments tab in both the organization and project levels.

  

  Steps in a workflow are defined based on settings and the original base value of the budget. For example, if you have a bid package organization level threshold of 100,000 value and the bid package being started for approval exceeds 100,000, it is required to go through the organization steps.

  Approval steps set at the organization level are assigned users, roles, or approver groups. An approval group is a set of users or roles in steps. For example, you could have a group that flows through your entire approval process or a group that is just the business manager. You can set up multiple groups, and you can assign multiple groups to an approval step. When setting up a threshold, the Project must select specific users based on assigned roles check box is selected by default. When this option is selected, you must edit the threshold at the project level to select specific users within the assigned roles.

  You set up a group on the Group approver setup tab (Settings > Change > Workflow Assignments > Group approver setup). Each group can have one or more steps that represent the approval process.

  There is a new permission for approving and rejecting bid packages. Only users or roles that have that permission are shown when you are setting up workflow steps.

  Approval steps set at the project level can be assigned to roles, users, or groups. Steps set at the project level are performed before the steps set at the organization level.

  Conversion to a contract is not dependent on approval. You can still convert the bid package at any time; however, you cannot publish the purchase order for the contract until the bid package workflow is approved. Bid packages that require approval are not available in a contract for association from the Associate a bid package icon until they are fully approved.

  The Approval status column has been added to the Bid packages register. Ellipses in the column indicate that the workflow has been started. You can hover over the ellipses to view additional information.

  

  The Approval status field has also been added to bid package import and export. The column is ignored in the import template.

  You can also track the Bid package workflow on the project Workflows page (Project > Workflows).

  Notes added when you approve or reject the bid package are shown in the Notes slide-out panel for the bid package. You can also add a message to the Notes section.

  The Action items tab has been added to Bid packages. The tab shows all action items for contracts and bid packages. You can also see the action items for bid packages on the contracts Bid packages page.

• DocuSign enhancements – DocuSign functionality has been added to bid packages, back charges, and payment forms. Also, recipient information can now be updated in the Assigned section of the Send for signature wizard. DocuSign functionality has also changed so that you can no longer remove a file or link for a document with the status of Created, Sent, Completed, or Signed. Read more

  When sending a document for signature, if there are DocuSign tags in the Assigned section you can now edit the recipient information in the first step of the Send for signature wizard. Any changes made in the wizard are saved in the DocuSign section on the header tab of the contract.

  

  When a supporting document has a DocuSign status of Created, Sent, Completed, or Signed, you can no longer edit the file link. The Remove icon also has been removed.

  Also, the Division of responsibilities recipients subsection of the DocuSign section now show in the same order as they are listed in the Division of responsibilities subsection of the Additional details section. Previously, they had been listed in the order they were added in the project settings.

• VCO Line item import – You can now import new line items or update the quantity or price on existing line items. You can import line items only if the contact has been published. You can also export line items. Read more Watch video

  The Import data from template and Export Line items icons were added to the VCO Line items tab. The import data from template icon is disabled if the contract has already been published. You must have the Edit contracts permission to import or view the Import history page.

  

  The import functions in the same way as the line item import. The Line item type and Quantity fields are required. Refer to the Instructions tab on the Import template for complete instructions for importing. Read the instructions thoroughly before importing.

  After importing, you receive an email message listing status, the total line items, the total imported, and number of errors. If the status is pending, you can click the Review data link to see the line items that have completed and those with errors.

  

  You can correct the lines with errors from the Import history grid, select them, and then click Import to continue with the import process. The import is reprocessed, and Contract sends you an email message when the import is completed. The VCO line items tab shows the lines that were imported with the Line item ID New.

  The export function lets you export with data. If there are no line items in the VCO but there are line items for the contract, the export template lists all lines tied to the contract. If you add a line to the VCO and you export with data again, it only pulls the line that you added. The line does not have a line item ID.

• Dynamic contract import – The import template now includes names for custom lists and fields in drop-down lists. Custom lists and fields are shown in the template with the names configured in the organization or project settings.

• Upload a document to InEight Document – You can now upload a document to Document from any of the Supporting documents tabs. This feature eliminates extra steps of having to load the document in Document then link it back in Contract. Read more

  You can now upload a document to the Document module directly from Contract, eliminating extra steps. To upload the document, select it and then click the Upload icon. You are taken to the upload screen in the Documents module of Document. Follow the procedures as you would in Documents module for adding a document. The document you selected in Contract is already attached, but you can add more documents. Click Save and Transmit. The document is now saved in the Document Documents module. After you close the Document window, Contract shows the Edit supporting document dialog box. The file link is replaced with the document link from Document. Click Save. The Supporting documents register refreshes with the file link to the Documents module. The Document source is replaced with InEight Document, and the External document type and status are now populated.

  Only documents added via My Computer are allowed to be uploaded.

• Display vendor proposals from InEight Change – When you upload a document of type Proposal, subtype from Vendor in Change and associate it to a Contract ID, the document is now visible in Contract as read-only on the main Supporting document register and the Contract supporting document tab. Read more

  If a VCO was selected in Change, it is also shown on the VCO supporting document tab. The proposal has an approval status of Not applicable, and Contract Document workflow is not considered. Only the Change workflow for the document is considered. The document is read-only in Contract. New columns for Issue ID, PCO ID, CCO ID have been added to the supporting document page for reference.

• Master agreement enhancements – Contract line items can be reassigned to master agreement line items. All information from master agreement line will update other than quantity. Bid package vendor will flow to Master agreement vendor upon association. The Tax information icon has been added to the Total tax column on the Master agreements and Associations registers. Read more

  The tax information includes a break-down of all the taxes that make up the total tax.

  

• Vendor contact information – Columns in the Vendor contact drop-down lists in the Additional details section of the contract header now include the Name and Email fields. Previously the drop-down list showed the ID and Employee name fields.

• Surety document type – The Effective date and Expiration date fields are now required for the Surety document type.

• Generate a contract document from the Contract or VCO register – You can now generate a contract document from the Contract or VCO register without opening the contract or VCO. Read more

  Generate contract document has been added to the Actions menu on the Contracts and Vendor Change Orders registers. To generate a document, select one contract or VCO, and then expand the Actions menu and click Generate contract document.

  

  The Generate contract wizard opens, and you can follow the procedures for generating a contract document.

• Download a purchase order – You can now download a purchase order from the Contract register without opening the contract. The organization-level default purchase order is also attached in contract approval emails. Read more

  The Download purchase order icon has been added to the Contract register. To download a payment form, select one contract, and then click the Download purchase order icon.

  

• Custom lists and custom fields on Contract and Master agreement registers – Columns for Custom list 1 and 2 and Custom field 1-10 have been added to the Contract and Master agreement registers. The fields have also been added to the export. If you have custom labels, they are used in the export and import.

• Template tag updates – A tag for the generated date, <<Generated date>>, has been added to the general tags list. The tag shows the date that the contract was generated. Tags for DocuSign and Invoice tax types and amounts have been added to the collection table tags. Tax type and amount settings are for the first five taxes used in an invoice.

• Contract payment form query update – Approval status is no longer available in the contract payment form query.

• Approval process for multiple supporting documents – Documents with group workflows can now be included in the approval process for multiple documents at the same time. Read more

  The Start Approval dialog box has been updated to show all the workflow steps for each document selected. For workflows with one or more group steps, you must select groups for each group step in each document. After you enter all information, you can click Start to start the approval process.

  

  The Start approval dialog box stays open until all workflows have successfully started.

• Add payment form enhancements – When you add a payment form, the Payment form details page now opens to make adding a form more efficient. Previously the Add payment form dialog box opened first. If you leave the Payment form details page without saving, the details you added are not preserved.

Updated 01-APR-2022

• eSignature via DocuSign – You can now send contracts directly to DocuSign for electronic signatures. Read more

  Contract can now send contract and vendor change order documents for eSignatures via DocuSign. You can embed common signees into your project templates or add signees at any time to take your project efficiency to next level.

  Link DocuSign account to the InEight cloud platform

  The DocuSign integration is configured in the eSignature tab of Suite administration > Application integration in InEight Platform. DocuSign accounts can be set up for the organization and for individual projects. Contact your InEight representative if you have questions about getting a DocuSign account.

  Project-level set up

  Recipients can be defined at the project level and then are available for use in every contract. The DocuSign setup page has been added to the Contract templates tab in the project settings (Project settings > Contract templates > DocuSign setup). You can enter the names of up to 10 recipients and their companies, titles, and email addresses.

  Recipients can be pulled from the project Assigned contacts list or free text. As you start to type a name, Contract searches the project contact list. You can manually overwrite values.

  

  If you edit the DocuSign setup, the recipients are available for new projects only. You can override the DocuSign recipients in the DocuSign section of the Contract header details.

  Recipient set up

  A DocuSign section has been added to the Contract header details page. You can use this section to view or add common recipients to be used as default signees. This section has subsections for DocuSign, Division of responsibility, and Project contacts. All signees must be added to at least one section.

  

  • DocuSign recipients – Populated from the project DocuSign set up tab (Project settings > Contract > Contract templates >DocuSign setup) or manual entry.

  • Project contacts – Populated with contact information from Project Contacts added in Project details. This section is for reference only. If you want to add or change recipients, you must edit the Project Contacts.

  • Division of responsibility – Populated with user information defined in the Division of responsibilities section of the contract details. The company is populated from the Company legal name in Project details. The title field is always blank. This section is for reference only. If you want to add or change recipients, you must edit them in the Division of responsibility section of the Additional details.

  Contract writer – tag embedding

  DocuSign eSignature tags for recipients have been added to Contract writer General tags, so you can embed signee information to pull into your organization or project templates. DocuSign tags used in a template are read when sending the document for signature.

  When you insert the tags into a template, change the font to white so that the tags do not show when the contract document is generated. Watch video

  Send documents for eSignature

  Documents sent for eSignature must be in Microsoft Word, Microsoft Excel, or PDF format. Any user that has Edit contract permission is able to send documents to DocuSign.

  To send a document for signatures from a contract or VCO supporting document page, select one or more documents with the document source My computer, and then click the Send for signature icon.

  A wizard opens that lets you select signees, add a message, and send for signature.

  

  The Assigned section of the wizard is populated from the DocuSign recipient tags that were embedded into the document. Additional recipients can be added from the Unassigned section. Signing order defaults to the order they were added but can be adjusted by overwriting the number order. You can duplicate a number if you want the recipients to receive or sign the document at the same time. All recipients in the Assigned section have ad-hoc signee tags that can be placed on the document in DocuSign.

  

  The Unassigned section is populated with any recipients that were filled out in the DocuSign section of the contract details. These recipients can be added to the Assigned section.

  When you have all signees in the Assigned section, click Next. You can then enter an email subject and message to the recipients.

  After you click Send, a DocuSign window opens with the documents you chose. If you had any embedded tags, they show on the document. All assigned recipients are available in the upper left drop-down list to drag and place additional signature fields on any of the selected documents.

  

  After you click Send, the documents are routed for signature, and DocuSign sends an email message to each recipient based on the signing order. In Contract, the DocuSign status column on the Supporting documents page is populated with the status of Sent, and a hover over showing the status of the signatures.

  

  When completed, the signed document is loaded as a new supporting document with the same document type and title. The DocuSign status is Signed. All fields can be edited except the file link cannot be removed or changed.Watch video

• VCO ID customization – You can now configure a prefix and starting number for your VCO numbering schemes to ensure consistent numbering. Read more

  At the organization level, you can set a standard prefix and starting number using the ID customization configuration list (Settings > Configurations > ID customization).

  

  The Generate vendor change order IDs sequentially setting indicates whether Contract generates numbers sequentially. The VCO numbers are sequential within a contract. When set to No, you can enter any number as the VCO ID. When set to Yes, you can specify a prefix and a starting number in their respective fields.

  You can enforce the numbering scheme at the project level by ensuring that the Allow projects to edit settings check box is unselected. When unselected, the organization numbering ID is carried to the project level and cannot be changed. When the box is selected, the organization level settings are defaulted at the project level, but the project can override them. You can then use the ID customization list at the project level (Settings > Configurations > ID customization) to configure the prefix and starting number for a project.

  

  After you establish a starting number, and the first VCO is created, you cannot change the starting number at the project level. You can change the prefix.

  You can set the Generate vendor change order IDs sequentially field to No at any time. After the field is set to No, the Vendor change order ID in the VCO goes back to free text.

  If you override the Vendor change order ID, the number does not automatically advance. For example, if the Vendor change order ID is set to VCO#1, and you make a change, the next VCO you create uses VCO#1.

• Vendor change order log – A new register has been added for all VCOs in a project. The log provides visibility to all VCOs for all the contracts in the project for tracking purposes, including those created from InEight Change. Read more

  The register has filtering, column resizing, and information features like other registers in Contract. Data in the columns are linked to any associated issues, PCOs, or CCOs in Change.

  

  You can click on the Information icon to see information about the VCO. The information slide-out panel has links to the line items, associations, back charges, supporting documents, and contract.

  

• Create a VCO via InEight Change upon CCO execution – A project setting in Change lets Change users create VCOs either automatically or manually during CCO execution for vendor pricing items that have not been associated to a VCO. Read more

  The Pricing configuration setting (project Settings > Change > Configurations > Pricing configuration) has a new toggle for Vendor change order configuration. When set to Yes, upon Execution of a CCO, Change creates a VCO for each vendor pricing item that is not already associated to a VCO. When set to No, you must manually associate the vendor pricing item to a vendor change order.

  VCOs that were automatically created have the name Service Account in the Created by column of the Vendor Change order register and the Vendor change orders detail.

  

• VCO supporting documents – You can now associate a Draft change order or Executed change order supporting document to multiple VCOs.

• Configurations for Vendor change order responsible party – You can now configure a vendor change order responsible party drop-down list. Read more

  The Vendor change order responsible party setting is in the Configuration settings at both the organization and project levels.

  At the project level, you can add new responsible parties or activate or deactivate responsible parties.

  

  At both levels you can delete responsible parties only if the party is not in use by the project. Additions or changes made at the organization level are for new projects only.

• Payment form enhancements – You can now add supporting documents to a payment form. You can also generate a payment form using the Contract Writer. New columns have also been added to the line items to accommodate payment forms. Read more

  A Supporting documents tab has been added in a payment form along with the ability to generate a payment form via Contract writer.

  The Generate Payment form action has been added to the Actions menu on the tabs in the payment form. When you generate a payment form, the Contract writer wizard opens. You can then select from payment form templates and generate a payment form document through the Contract writer.

  

  If there are no payment form templates available, or you want to add additional templates, you can click the Settings icon to go directly to the Contract Templates page of the project settings to add or update templates.

  A new document type of Payment form has been added. This document type can only be added in a payment form and will not go to the Contract supporting document register.

  A Payment form ID column has been added to all Supporting documents tabs. After you associate a supporting document to the Payment form Supporting documents tab, the column is populated with the Payment form ID.

  If you remove the document from the payment form, Contract removes the payment form, but the document remains in the Supporting documents register.

  Other changes to the payment form include the addition of the Percent complete and Quantity available columns to the Add line item dialog box. These values show what is available on the payment form that have not been submitted and posted. The quantity does not reflect items that are pending submission.

• Invoice APIM – You can now add invoices to the invoice register through an external API. Refer to the APIM release notes and documentation for more information about the Invoice APIM.

• Vendor contact – You can now assign a vendor contact to a contract. Read more

  The Vendor contact section has been added to the Additional details section of the contract header. The contacts come from the project Assigned contacts associated to the contract vendor. If a vendor is changed or removed from the contract, the contact is removed.

  

  If there are no contacts defined for the vendor, the list is empty, and you cannot add a contact.

  A template tag for the vendor contact has been added to the general tags.

• Purchase order download – You can now quickly download a default purchase order template when you are in a contract. You can supersede the default purchase order template by using the Contract Writer. Read more

  The Download purchase order icon has been added to the Contract Header page. Click the icon to download the default header for the contract type.

  

  Contract provides a standard default purchase order. An organization can override the default with contract-type-specific templates. This is only available at the Organization level; projects do not have the ability to add a purchase order template.

  A new template type, Purchase order has been added to the Contract writer template configuration.

  

  You can also specify the contract types for which the template is the default. When the Set as default field is set to Yes, it becomes the default template when you download purchase orders for the specified contract type.

• Start multiple supporting document workflows – You can now select multiple supporting documents and then start the approval process.

• Invoice register enhancements – The Invoice Status column has been renamed Record status. Contract now generates an error message when you upload a corrupted or encrypted PDF to the Invoice register.

• Payment progress register updates – The Invoice Net amount and Invoice tax amount have been added to the Payment progress register. These fields let you see invoice net and invoice tax information from the ERP system or the proxy ERP.

• Supporting document disassociation – When a Contract ID is disassociated from a supporting document, the VCO ID and Payment Form ID are also automatically disassociated. Previously you had to disassociate the VCO ID and payment form ID manually. The contract must not be executed to disassociate the contract ID from the supporting document.

• Contract type configuration – Contract terms, custom lists, and custom fields have been added to the Contract type configuration setup.

• Goods receipts line item settings – The line items type configuration setup (organization Settings > Configurations > Line item type configuration setup) no longer shows a toggle for Allow edits to goods receipt requirements on line items. The setting is no longer necessary because the Goods receipt setting in line item field grid gives you more functionality. Read more

  You can use the Goods receipt line item field to enable goods receipts and require or lock them for workflows and purchase orders.

  

• Maximum overdelivery field updates – When you change the Maximum overdelivery field in the organization settings to a number lower than the project limit, Contract now updates the Maximum overdelivery field in the project settings. Previously, you had to update the project settings manually. Read more

  Contract updates existing projects only if the new organization setting is less than the project limit. If the organization setting is greater than or equal to the project limit, Contract does not update the project setting.

• Choose sections when copying a line item – When you copy a line item, you can now choose the sections you want to copy. This saves time when creating new line items from existing items because you do not have to enter the information again on the new line item. Read more

  When you copy a line item, the Copy line item dialog box opens to let you select the sections to copy. You can choose to include the Delivery schedule, Equipment details, and Material attributes sections. After you have made your selections, click Copy.

  

• Contract line item – Agreement item ID – Contract line items associated to master agreement line items can now be disassociated. When you disassociate the contract line item from the master agreement line item, the line item goes to the generic MPA 000 line. You can also reassociate the line item to the same or another master agreement line item until the line item is published. After publishing it cannot be associated an remains in the MPA 000 line.

• Bid packages supporting documents – The Notes for the Description slide-out panel has been added to the bid packages supporting documents. The Notes icon has also been updated to be consistent with other pages in Contract. Read more

  The Supporting Document Notes tab of the description shows notes that are specific to the supporting document. You can see notes for the bid package on the Bid Package Notes tab.

  

• Exchange rate currency warning – Contract now shows a warning icon when the selected Contract currency does not have an exchange rate set up in the Project Details.

• Contract template Market assignment – Organization-level templates now default to On in a project when neither the organization template nor the project have a market assigned. If the organization-level template has a market added, it is automatically turned off for all projects that do not have a matching market in the Project details but stays turned on for any project with a matching market. If the project adds a market to the Project details, any organization-level Contract writer templates that were set to Off are automatically set to On.

• New general and collection table tags – General tags have been added to support Vendor contact. Collection table tags have been added to support VCO responsible party and Payment form supporting documents. eSignature tags have been added to support DocuSign.

• VCO configuration – VCO configuration is now done entirely on the VCO Details page. The Add VCO dialog box has been removed. When you click the Add vendor change order icon on the Vendor Change Order Log, the Vendor change order details page opens.

• VCO creation from InEight Change – Change users can now create a VCO from Change. The VCO comes in with a status of Draft. The VCO is automatically associated with the issue, potential change order (PCO), or client change order (CCO) where it was created.

• VCO Change associations update – You can now associate vendor pricing items added at the PCO and CCO levels with a VCO to give you full visibility into the life cycle of the vendor changes. Previously, associations were only available at the issue level. Read more

  The Unassigned Change items field has been added to The Vendor Change Log page. The field shows the sum of any issue, PCO, and CCO pricing items for the vendor contract that have not been associated to a VCO. This total lets you track pricing items in Change that can be added in a VCO.

  

  The Associations section on the Vendor change order Details page has been renamed Associated change items. This section now includes vendor pricing items added at the PCO and CCO levels in Change.

  

  The Add existing issue option has been changed to Add existing change item to include pricing that is added at any level. When you add an existing change item, you now have the option to add pricing items that were added at the PCO and CCO levels.

  

  When you click Add existing change item, the Add Issue dialog box opens. The dialog box contains a grid with columns for Issue ID-Name, PCO ID - Name, CCO ID-Name, Vendor assigned, and Status.

  

  Items in the issue column have pricing that was added at the issue level. If the Issue column is blank, and there is a value in the PCO or CCO column, the pricing items were added at the PCO or CCO level. Adding the issue does not automatically add the PCO and CCO pricing items added at the PCO and CCO levels. If you want to add the pricing items added at the PCO and CCO levels, you must select them.

  When you delete a PCO, all rows associated with the PCO are removed.

• Bid package float update – The float calculations were updated to accurately reflect scheduled float days and durations. The calculations for the remaining float days and Total available float were also updated. The float can now be calculated by Target execution or Needed by date. Read more

  Previously, when you copied scheduled dates to forecasted dates, the completion dates and duration were copied, but float days were not considered. Now when you copy scheduled days, the float days are calculated as the float days from the previous milestone plus the duration days of the current milestone.

  The calculation for remaining float has been updated and gives you the option to calculate based on the difference between Contract target execution date or Project delivery (Needed by) and the date of the last forecasted milestone. You can set the Calculate float based on field to indicate which date is used in the calculation. The Total available float is now calculated as the remaining float plus the sum of uncompleted scheduled milestone float.

  

• Master agreements publishing and close-out enhancements – The name of the Publish MPA button has been changed to reflect the MPA status. The ability to publish or edit master agreements varies depending on whether the agreement has already been published. Read more

  The Publish MPA button has been renamed Publish master agreement and is shown until the first successful publishing of the master agreement.

  After the master agreement has been published successfully, you can update the master agreement. The button becomes Update master agreement and is disabled until changes are saved. After you save changes to the master agreement, the button is enabled, and you can update the published agreement.

  When you change the status of the master agreement to Closed and then save it, the button is now the Closeout Master agreement button. After a master agreement is closed, you can no longer write contracts against it. Any existing contracts associated with the master agreement remain open until they are closed. You cannot add line items from a closed master agreement, even if the contract is already associated to it.

  Closed master agreements have been removed from the Agreement ID drop-down list on the Contract header. Only open master agreements are available for selection in the Contract header.

  You do not have to close out the master agreement entirely. Instead, you can close out individual line items on the master agreement if you have multiple lines. If you close an individual line item on the master agreement, then that line is no longer available for association, but the other lines are. To close a line item, select Closed in the Status field in the Line items details.

  

• Master agreement total tax – The Total tax column has been added to the Associations register. Previously the Associations value in the banner included tax, but the Current value did not. Now, the tax has been removed from the Associations value to be consistent with the Current value. You can total the tax separately. The tax amount is the sum of the Tax amount field in all the line items.

• Master agreements associated contract ERP sync status – The ERP sync status column has been added to the Master agreements Associations tab. This column lets you see whether the associated contract has been synced to the ERP system.

• Deactivate unused custom list selections – You can now deactivate a custom list selection from the organization settings. When you deactivate a list item, you prevent it from being used in the future while maintaining the integrity of the projects that have already used it. Read more

  The Active toggle has been added to the custom list details (Organization settings > Configurations > Custom list).

  

  When the toggle is set to Yes , the item is available for selection in the custom list. When it is set to No, the item no longer is shown for new contracts or line items, but it is maintained where it was previously used. After you change a custom list selection from an active value to an inactive value, the value is no longer available in a drop-down list for your project, and you cannot change the field back to the inactive value.

• Configuration settings for workflow – Contract header and line item fields can be configured based on workflow. Read more

  Configurations have been added to allow Contract header and Line item fields to be set as Require for workflow and Lock after workflow. Settings have been added to the Contract type configuration setup in the organization settings (organization Settings > Configurations > Contract type configuration setup) and the line item type configuration (organization Settings > Configurations > Line item type configuration setup).

  

  When a field is required for workflow, a value must be entered before you can start the approval workflow. Previously, you could require or lock fields for purchase orders only, and users could change values after an item was approved. Now you can set the purchase order and workflow requirements and locks separately as needed by your organization.

• Supporting documents email notifications – Contract now stops automatically sending email notifications for supporting documents 180 days past the expiration date.

• Schedule of values dynamic recalculations – The Unit price field is now automatically recalculated when the Schedule value or Schedule quantity is updated. The Schedule value field is also editable. Previously it was not editable. Read more

  In the Add schedule of value or Edit schedule of value slide-out panel, when you change the Schedule value, the Unit price is automatically updated. If you change the Schedule quantity or the Unit price, the Schedule value is automatically updated.

  

• Payment forms register update – The submitted by and Submitted date columns have been added to the Payment forms register.

• Line item type edit – You can no longer edit the line item type after starting an approval.

• New template tags – Tags for Company legal name and Markets have been added to the general tag list. These fields are in the Platform project details.

• Contract templates – New organization templates now default to Off for Project use. These templates can be manually switched to On in individual projects.

• Master agreements – You can now create master agreements to establish pricing of goods and services for a project. A master agreement is a type of contract, set at the project level, between a general contractor and a supplier to purchase things later. Using a master agreement lets you agree to terms and pricing without having to commit to the full terms of the agreement now. Read more Watch video

  A master agreement lets you set up the terms, conditions, and pricing of an agreement. You do not commit the value until you write an associated contract or purchase order against it. For example, a master agreement could be an agreement to purchase services across for multiple years of a contract. Instead of purchasing all the services now, you can write contracts for the services against the agreement as needed over the duration of the project. All transactions of the contract purchase order are associated to the master agreement for visibility.

  A master agreement is not a standard contract purchase order. Because you receive and pay against all the contracts and purchase orders associated to it, it is not necessary to create a goods receipt against a master agreement.

  Configuration

  As an organization, you can define which contract types should be considered a master agreement. You can add a new contract type or configure an existing contract type to be specific for master agreements.

  

  In the Contract type configuration setup, select the contract type you want to be master agreement, and then set the Is this a master agreement field to Yes. When the field is set to Yes, an additional tab is added in the application register home page for master agreements. You can then specify whether to publish the master agreement to an ERP.

  An additional setting has been added to contract type configuration to allow a contract type to be associated with a master agreement. This setting defaults to No on all existing contract types. Organizations must update their existing contract types to Yes to allow associations to any Master agreement contract types or create new contract types to be associate to master agreements based on their business processes.

  The master agreement tab is only shown in the register home page if there is one contract type that has the Is this a master agreement setting set to Yes.

  Create a master agreement

  To create a master agreement, go to the Master agreements tab, and then click the Add master purchase agreement icon. The Add master purchase agreement dialog box opens.

  

  The dialog box is similar to the Add contract dialog box. The Type drop-down list contains all the contract types that have been configured to be master agreements. The vendor you select for the Vendor field is used as the vendor for all contracts written against the master agreement.

  The tabs are similar to the pages for a contract with some exceptions and updates. There are no tabs for payment forms and payment progress to prevent you from creating duplicate payment forms in the contract and the master agreement. Master agreements have an Associations tab, where you can associate a contract.

  Master agreement line items

  The Line items tab lets you define the line items of the master agreement. These line items can be used when you add line items to an associated contract. You must have at least one line item to publish the master agreement.

  The first line in the line item grid of every master agreement is a default placeholder 0000 line item, where a net price can be manually entered. This line item is used to hold value is not specifically applied to numbered line item. When an associated contract or purchase order has a line item that is not directly from the master agreement line items, the value of the associated line item will show in the 0000 line item progress viewset.

  

  Associations

  The Associations tab lists all contracts that are associated to the master agreement.

  You cannot associate contracts to a master agreement until you publish it. Click the Publish MPA button to publish the agreement. When you publish a master agreement, and the master agreement is configured to be published to the ERP, a master contract is created in the ERP that you write release purchase orders against.

  You can associate a new or existing contract to a master agreement from the Associations tab. To associate a contract, click the Add contract icon, and then select New contract/purchase order or Existing contract/purchase order.

  When you add a new contract, the Add contract dialog box opens. The Type drop-down list includes only those contract types that are allowed to be associated with a master agreement. The Vendor field is disabled and is filled with the vendor name from the master agreement.

  

  After you click Add, the contract Header page opens, and you can then add the contract details as you would with any other contract. On the Header page, the Reference data Agreement ID field is now a link when the contract is associated to a master agreement. If you remove the link, you disassociate the contract from the master agreement.

  To add an existing contract, click the Add contract icon, and then select Existing contract/purchase order. The Add existing dialog box opens with a list of eligible contracts. Eligible contracts must have the same vendor as the master agreement. You can select a contract, and then click Add. The contract is now associated to the master agreement. Any costs associated with the contract are then linked to the master agreement.

  To associate an existing contract, click in the Agreement ID field in the contract, and a list of master agreements from the same vendor are shown for association.

  Master agreement banner

  The master agreement banner shows at the top of all pages in the master agreement to help you track the current value and associations.

  

  The Current value is the amount of the master agreement. This value increases as contracts are associated. The remaining fields come from the contracts associated with the master agreement. For example, as you write associations to the master agreement, the Associations value increases.

  The Remaining to buy field on the Associations and Vendor change order tabs is automatically calculated. The remaining to buy is the difference between the master agreement amount and the total associations current value.

  Contract line items

  When a contract is created from or associated to a master agreement, you can now add a line directly from master agreement or add a new line.

  When you click the Add line item icon and then select From master agreement, a list of line items from the master agreement is shown. You can select one or more line items and then click Add to bring them in from the master agreement.

  

  The line item is added to the contract’s line items. Adding lines from the master agreement, predefines the line item details and creates the association to the master agreement line item. A new column in the Line items grid, Agreement item ID, shows the ID of the master agreement. The line item comes in read-only, and the quantity defaults to 1. To define the value of the line, a quantity must be entered and saved within the data block.

  When you choose to add a new line item (that is you select New line), the line item becomes associated to the master agreement, but because it was not created from an existing line item, it gets associated to the 0000 line item on the master agreement.

  Master agreement totals slide-out panel

  The Master agreement totals slide-out panel lists is similar to the Contract totals slide-out panel. The Received to date, Contract invoices, Submitted to date, Paid to date, Retained to date amounts, and percentages come from the contracts that have been associated to the master agreement and not from the master agreement itself.

  

• Contract type configuration new fields – The Agreement ID, Agreement value, Purchase order ID, Purchase order value, and Harmonized system schedule fields have been added to the Contract type configuration setup. Read more

  You can turn on or off whether the fields are enabled, required for a purchase order, and locked after purchase order. When the Enable indicator field is set to No, it is dimmed on the Contract header page.

  

  Agreement ID, Agreement value, Purchase order ID, Purchase order value configurations will not show on contract types that have been defined as a master agreement.

• Workflow enhancements – You can now copy a workflow from supporting document to supporting document. You can now approve or reject multiple items at one time from the action items tab. A new workflow wizard with options to include message and link supporting documents for email review was also added. Read more

  The multiple select enhancement lets you select multiple items on your Action items tab to approve or reject. If you reject multiple items and enter a note, the note is attached to all items selected.

  The Workflow wizard now has three steps. The first step is the existing workflow step where you see the approval steps. The second step lets you enter and format a customized message for the workflow email notification.

  

  The third step lets you attach supporting documents links for reference. Any supporting document that is associated with the contract or VCO can be added.

  

  The steps to customize the email and to add supporting documents are optional.

  The email notification has been updated to include the links for the supporting documents. The recipient can click a link to download the document.

• Payment form workflow enhancements – The payment form approval setup at the organization level has been updated to let you add multiple approval steps, similar to the steps you configure at the project level. Previously, you could only enter a final approval step at the organization level. Read more

  The Payment form approval setup page now lets you add steps and approver roles for each contract type.

  

• Schedule of values in a copied contract – The schedule of values is now copied when you copy a contract.

• Line Items data block – Custom fields 1-5 and custom lists 1 and 2 have been added to the Line items data block.

• Vendor change order naming conventions – Fields on the Vendor change order details page have been renamed to be consistent with InEight Change. Read more

  The Ball in court field is now in the header bar has been renamed Responsible party. The Issue ID - Name, PCO ID - Name, and CCO ID - Name fields in the Associations section use the custom labels assigned to them in Change, when applicable.

• Partial refresh of contract closeout – You can now refresh a contract closeout checklist. This lets you get the most recent checklist questions without having to recall all the checklists. Read more

  Now you can refresh a checklist in a Contract if any questions have been updated in the project settings. Only checklists that have not been started, not completed, or recalled are refreshed. Previously, after a checklist was started, the Refresh checklist button on the Contract closeout page was dimmed, and you could not restart a refresh.

• Expand multiline text boxes – You can now expand the size of multiline text box for selected fields, so it is easier to enter and read information. Read more

  The expand icon was added to text boxes on the Contract Header and VCO details pages, so you can expand the text area to the size of the whole page.

  

  The expand icon changes to the collapse icon when expanded.

  

  Use the collapse icon to collapse the text box when you are done.

• Contract writer enhancements – You can now use tags in the header and footer of a document template.

• Contract writer tag updates – The list of tags has been updated. Read more

  The following tags have been updated for all templates:

  Old tag	New tag
  <<Contract number>>	<<Project contract number>>
  <<Date project started>>	<<Project contract start date>>
  <<Date project started-words>>	<<Project contract start date-words>>
  <<Original contract completion date>>	<<Project contract completion date>>
  <<Original contract completion date-words>>	<<Project contract completion date-words>>
  <<Original duration>>	<<Project contract duration>>
  <<Original project value>>	<<Project original contract amount>>
  <<Extended/rejected duration>>	<<Contract extension/reductions>>
  <<Revised contract completion days>>	<<Contract revised duration>>
  <<Revised contract completion date>>	<<Contract revised completion date>>
  <<Revised contract completion date-words>>	<<Contract revised completion date-in words>>
  <<Prime contract: Owner: First Name>>	<<Project contact: Owner: First Name>>
  <<Prime contract: Owner: Last Name>>	<<Project contact: Owner: Last Name>>
  <<Prime contract: Owner: Company>>	<<Project contact: Owner: Company>>
  <<Prime contract: Owner: Email>>	<<Project contact: Owner: Email>>
  <<Prime contract: Owner: Contact type>>	<<Project contact: Owner: Contact type>>
  <<Prime contract: Owner: Department>>	<<Project contact: Owner: Department>>
  <<Prime contract: Owner: Position>>	<<Project contact: Owner: Position>>
  <<Prime contract: Owner: Title>>	<<Project contact: Owner: Title>>
  <<Prime contract: Owner: Office number>>	<<Project contact: Owner: Office number>>
  <<Prime contract: Owner: Mobile number>>	<<Project contact: Owner: Mobile number>>
  <<Prime contract: Owner: Fax number>>	<<Project contact: Owner: Fax number>>
  <<Prime contract: Owner: Address 1>>	<<Project contact: Owner: Address 1>>
  <<Prime contract: Owner: Address 2>>	<<Project contact: Owner: Address 2>>
  <<Prime contract: Owner: Country/Region>>	<<Project contact: Owner: Country/Region>>
  <<Prime contract: Owner: City>>	<<Project contact: Owner: City>>
  <<Prime contract: Owner: State>>	<<Project contact: Owner: State>>
  <<Prime contract: Owner: Postal code>>	<<Project contact: Owner: Postal code>>
  <<Prime contract: Designer: First Name>>	<<Project contact: Designer: First Name>>
  <<Prime contract: Designer: Last Name>>	<<Project contact: Designer: Last Name>>
  <<Prime contract: Designer: Company>>	<<Project contact: Designer: Company>>
  <<Prime contract: Designer: Email>>	<<Project contact: Designer: Email>>
  <<Prime contract: Designer: Contact type>>	<<Project contact: Designer: Contact type>>
  <<Prime contract: Designer: Department>>	<<Project contact: Designer: Department>>
  <<Prime contract: Designer: Position>>	<<Project contact: Designer: Position>>
  <<Prime contract: Designer: Title>>	<<Project contact: Designer: Title>>
  <<Prime contract: Designer: Office number>>	<<Project contact: Designer: Office number>>
  <<Prime contract: Designer: Mobile number>>	<<Project contact: Designer: Mobile number>>
  <<Prime contract: Designer: Fax number>>	<<Project contact: Designer: Fax number>>
  <<Prime contract: Designer: Address 1>>	<<Project contact: Designer: Address 1>>
  <<Prime contract: Designer: Address 2>>	<<Project contact: Designer: Address 2>>
  <<Prime contract: Designer: Country/Region>>	<<Project contact: Designer: Country/Region>>
  <<Prime contract: Designer: City>>	<<Project contact: Designer: City>>
  <<Prime contract: Designer: State>>	<<Project contact: Designer: State>>
  <<Prime contract: Designer: Postal code>>	<<Project contact: Designer: Postal code>>
  <<Prime contract: Contact 1: First Name>>	<<Project contact: Contact 1: First Name>>
  <<Prime contract: Contact 1: Last Name>>	<<Project contact: Contact 1: Last Name>>
  <<Prime contract: Contact 1: Company>>	<<Project contact: Contact 1: Company>>
  <<Prime contract: Contact 1: Email>>	<<Project contact: Contact 1: Email>>
  <<Prime contract: Contact 1: Contact type>>	<<Project contact: Contact 1: Contact type>>
  <<Prime contract: Contact 1: Department>>	<<Project contact: Contact 1: Department>>
  <<Prime contract: Contact 1: Position>>	<<Project contact: Contact 1: Position>>
  <<Prime contract: Contact 1: Title>>	<<Project contact: Contact 1: Title>>
  <<Prime contract: Contact 1: Office number>>	<<Project contact: Contact 1: Office number>>
  <<Prime contract: Contact 1: Mobile number>>	<<Project contact: Contact 1: Mobile number>>
  <<Prime contract: Contact 1: Fax number>>	<<Project contact: Contact 1: Fax number>>
  <<Prime contract: Contact 1: Address 1>>	<<Project contact: Contact 1: Address 1>>
  <<Prime contract: Contact 1: Address 2>>	<<Project contact: Contact 1: Address 2>>
  <<Prime contract: Contact 1: Country/Region>>	<<Project contact: Contact 1: Country/Region>>
  <<Prime contract: Contact 1: City>>	<<Project contact: Contact 1: City>>
  <<Prime contract: Contact 1: State>>	<<Project contact: Contact 1: State>>
  <<Prime contract: Contact 1: Postal code>>	<<Project contact: Contact 1: Postal code>>
  <<Prime contract: Contact 2: First Name>>	<<Project contact: Contact 2: First Name>>
  <<Prime contract: Contact 2: Last Name>>	<<Project contact: Contact 2: Last Name>>
  <<Prime contract: Contact 2: Company>>	<<Project contact: Contact 2: Company>>
  <<Prime contract: Contact 2: Email>>	<<Project contact: Contact 2: Email>>
  <<Prime contract: Contact 2: Contact type>>	<<Project contact: Contact 2: Contact type>>
  <<Prime contract: Contact 2: Department>>	<<Project contact: Contact 2: Department>>
  <<Prime contract: Contact 2: Position>>	<<Project contact: Contact 2: Position>>
  <<Prime contract: Contact 2: Title>>	<<Project contact: Contact 2: Title>>
  <<Prime contract: Contact 2: Office number>>	<<Project contact: Contact 2: Office number>>
  <<Prime contract: Contact 2: Mobile number>>	<<Project contact: Contact 2: Mobile number>>
  <<Prime contract: Contact 2: Fax number>>	<<Project contact: Contact 2: Fax number>>
  <<Prime contract: Contact 2: Address 1>>	<<Project contact: Contact 2: Address 1>>
  <<Prime contract: Contact 2: Address 2>>	<<Project contact: Contact 2: Address 2>>
  <<Prime contract: Contact 2: Country/Region>>	<<Project contact: Contact 2: Country/Region>>
  <<Prime contract: Contact 2: City>>	<<Project contact: Contact 2: City>>
  <<Prime contract: Contact 2: State>>	<<Project contact: Contact 2: State>>
  <<Prime contract: Contact 2: Postal code>>	<<Project contact: Contact 2: Postal code>>
  <<Prime contract: Contact 3: First Name>>	<<Project contact: Contact 3: First Name>>
  <<Prime contract: Contact 3: Last Name>>	<<Project contact: Contact 3: Last Name>>
  <<Prime contract: Contact 3: Company>>	<<Project contact: Contact 3: Company>>
  <<Prime contract: Contact 3: Email>>	<<Project contact: Contact 3: Email>>
  <<Prime contract: Contact 3: Contact type>>	<<Project contact: Contact 3: Contact type>>
  <<Prime contract: Contact 3: Department>>	<<Project contact: Contact 3: Department>>
  <<Prime contract: Contact 3: Position>>	<<Project contact: Contact 3: Position>>
  <<Prime contract: Contact 3: Title>>	<<Project contact: Contact 3: Title>>
  <<Prime contract: Contact 3: Office number>>	<<Project contact: Contact 3: Office number>>
  <<Prime contract: Contact 3: Mobile number>>	<<Project contact: Contact 3: Mobile number>>
  <<Prime contract: Contact 3: Fax number>>	<<Project contact: Contact 3: Fax number>>
  <<Prime contract: Contact 3: Address 1>>	<<Project contact: Contact 3: Address 1>>
  <<Prime contract: Contact 3: Address 2>>	<<Project contact: Contact 3: Address 2>>
  <<Prime contract: Contact 3: Country/Region>>	<<Project contact: Contact 3: Country/Region>>
  <<Prime contract: Contact 3: City>>	<<Project contact: Contact 3: City>>
  <<Prime contract: Contact 3: State>>	<<Project contact: Contact 3: State>>
  <<Prime contract: Contact 3: Postal code>>	<<Project contact: Contact 3: Postal code>>
  <<Prime contract: Contact 4: First Name>>	<<Project contact: Contact 4: First Name>>
  <<Prime contract: Contact 4: Last Name>>	<<Project contact: Contact 4: Last Name>>
  <<Prime contract: Contact 4: Company>>	<<Project contact: Contact 4: Company>>
  <<Prime contract: Contact 4: Email>>	<<Project contact: Contact 4: Email>>
  <<Prime contract: Contact 4: Contact type>>	<<Project contact: Contact 4: Contact type>>
  <<Prime contract: Contact 4: Department>>	<<Project contact: Contact 4: Department>>
  <<Prime contract: Contact 4: Position>>	<<Project contact: Contact 4: Position>>
  <<Prime contract: Contact 4: Title>>	<<Project contact: Contact 4: Title>>
  <<Prime contract: Contact 4: Office number>>	<<Project contact: Contact 4: Office number>>
  <<Prime contract: Contact 4: Mobile number>>	<<Project contact: Contact 4: Mobile number>>
  <<Prime contract: Contact 4: Fax number>>	<<Project contact: Contact 4: Fax number>>
  <<Prime contract: Contact 4: Address 1>>	<<Project contact: Contact 4: Address 1>>
  <<Prime contract: Contact 4: Address 2>>	<<Project contact: Contact 4: Address 2>>
  <<Prime contract: Contact 4: Country/Region>>	<<Project contact: Contact 4: Country/Region>>
  <<Prime contract: Contact 4: City>>	<<Project contact: Contact 4: City>>
  <<Prime contract: Contact 4: State>>	<<Project contact: Contact 4: State>>
  <<Prime contract: Contact 4: Postal code>>	<<Project contact: Contact 4: Postal code>>

• Configuration custom list functionality – You can no longer delete a custom list after it has been used in your organization to maintain contract integrity.

• Supporting document validations – Start payment form workflow has been added as an event.

• Back charge to Issue association – Issue association in a back charge now shows all associated change-level pricing items.

• Contract writer – Watermark and edit settings have been moved from the template to organization settings and the market attribute has been added to the template. The generation wizard has been updated to let you specify document details. Read more

  The Contract Templates tab in the organization settings is now divided into subtabs. The Template types subtab contains the templates register. From here, you can add or edit template details. The Market attribute has been added to the template details. This setting lets you assign one or more markets to the template type to provide additional ways to filter templates.

  

  The Template settings subtab lets you set characteristics for templates at the organization level. The Allow users to edit the document during generation setting has moved to the subtab from the template details. You can now enable this setting for all templates rather than having to set it for each template.

  

  The Require watermark stamp on the document generation setting indicates whether users must include one of the defined watermarks when generating a contract document. The Watermark stamp section where you define watermarks has moved from the template details to the organization settings. The transparency settings have been removed, and all watermarks are now semitransparent. The setting for removing the watermark when the document is approved has been removed. Contract now automatically removes the watermark when the document is approved.

  The Output as PDF only setting indicates whether you can only generate a PDF when you create a contract document. When set to Yes, you cannot generate a Microsoft Word or Excel document or make changes to the contract files individually. The changes must be made in Contract. After it is set to Yes, the Generate document as field on the first page of the Generate change template wizard defaults to Download as PDF and cannot be changed.

  The first page of the Generate contract document wizard has been redesigned to give you access to contract template details.

  

  The Generate document as field lets you select whether to generate the document as a merged PDF or as individual documents. When set to individual documents, the Generate document file type as field shows in the details. If the Output as PDF only setting is set to Yes, the Generate document file type as field defaults to Download as PDF and cannot be changed. If the Output as PDF only setting is set to No, you can choose to download as a PDF or as a template file type (that is, Word or Excel).

  You can now specify the name of the document when you save it to the Supporting documents tab. If the Save in supporting documents tab toggle is set to Yes, you can use the new Name of document file field to enter a file name. If you are generating multiple documents, the first one uses the specified name, subsequent documents use the name plus a number. If the field is blank, Contract names the file with the contract ID, template name, and a date-time stamp.

  You also can select a watermark stamp from the Contract template details area. If the Require watermark stamp upon document generation setting is set to Yes, you must select one of the defined watermarks before you can click Next.

• Contract writer conditional tags – You can now insert a collection table tag that generates specific text and additional collection table tags based on a conditional field. Read more

  Conditional tags let you set the language in a contract document collection table tag based on the value specified in a custom field. For example, if the conditional field Line item Custom list 1 is set up with values for line item, lump sum, and cost item, you can set up contract document text for line items, text for lump sums, and text for cost items. Conditional text is available for the following collection table tags:

  • <<Contract: Line item Conditional tag 1>>

  • <<Contract: Line item Conditional tag 2>>

  • <<Schedule of value: Conditional tag 1>>

  • <<Schedule of value: Conditional tag 2>>

  • <<VCO: Conditional tag 1>>

  • <<VCO: Conditional tag 2>>

  • <<Payform: Conditional tag 1>>

  • <<Payform: Conditional tag 2>>

  For each of these you can choose between Line item custom list 1 or 2. The custom list is defined at the organization level with items that are available in a drop-down list. When you set up a template using conditional values, you can add the text that applies to each value (that is, the condition) of the field, including other collection table tags.

  From the Conditional tag setup subtab, you can click the Download conditional collection table tags icon to download the Conditional tag setup spreadsheet. The spreadsheet has instructions for using the conditional tags and lists the collection table tags that can be used in a conditional tags setup. Only the collection tags for the specified document type can be used when creating conditional language in tags. For example, if you are in the contract line items document type, you can only use the collection table tags that are included on the Contract line items page of the spreadsheet.

• Contract writer tag additions – New general tags have been added for custom lists, conditional tags, project information, and project details. Collection tags have been added for VCO issue pricing items and supporting document approval.

• Date in words tags – New tags have been added to let you specify the date in words, such as Wednesday September 1, 2021. Read more

  The following new tags were added:

  • <<Project contract date-words>>

  • <<Prime contract project start date-Words>>

  • <<Original contract completion date-Words>>

  • <<Contract effective date-Words>>

  • <<Vendor change order effective date-Words>>

• Contract type configuration – Schedule of values has been added to the Contract type configuration at the Organization level. Read more

  You can now turn on or turn off the schedule of values by contract type. The Contract type configuration setup page (Organization > Settings > Configurations > Contract type configuration setup) lets you select a contract type and then specify whether to use the schedule of values.

  

  A toggle for Use schedule of values has been added to all contract types. The default value is Yes. If set to No, the Schedule of values tab is not visible.

• Configurations – The ability to configure retention by line item type has been added. Read more

  The Retention allowed toggle has been added to the Line item type configuration setup in the Organization settings. The Retention allowed setting lets you configure retainage on a credit line. This configuration lets you have a negative retention.

  The Default goods receipt as required setting has moved to the line item type configurations to keep the line item type configurations together. The Goods receipt configuration setup was removed from the Configurations menu.

  

  When set to Yes, the retention percentage is copied from the header and can be edited. When set to No, retention is not calculated, regardless of the setting in the header. The Retention percent setting columns for Enable, Require for purchase order, and Lock after purchase order settings are not available.

• Supporting document – Supporting documents have been added to the VCO details and line items functions. A supporting document download link is now attached to supporting document approval email.

• Organization workflow user assignments at the project level – You can now assign a user as required by the Organization level when you edit a threshold at the Project level. This view lets you view the whole organization step at one time. Read more

  When you edit a project-level step, the Edit approval slide-out panel now includes a view of the organization-level steps at the same threshold. The project-level steps are fully editable. If the organization-level steps require editing, you can assign a user. All other fields of the organization steps are read-only.

  

  If the organization-level steps do not require editing, the entire organization-level step is read-only. Organization steps that require editing are marked with a red triangle in the approval details. If there are no project-level steps, you can edit the organization-level steps individually.

• Line items Additional fields – The Custom lists and Custom fields that show in the Additional fields section of the Line items details have been added to the Line item data block.

• VCO issue association – Issue association in a VCO now shows all associated change-level pricing items. Read more

  The Associated issues section of the Vendor change order details has been updated to show pricing items in an issue. If a vendor total from the InEight Change issue has pricing items, they are shown in the new Pricing Item and Contributed value columns.

  

  If there are multiple vendor pricing items in the issue, the issue is shown for each pricing item. The Contributed value column shows the amount of each pricing item. The pricing is read-only. If you delete a pricing item from the Associated issues section, you delete the entire issue.

• Goods receipt – The Delivery number field has been added to the header of the Goods receipt page.

• Norwegian – Contract is now available in the Norwegian (Bokmål) language.

• Common navigation – The common navigation used across all InEight cloud platform applications has been enhanced for ease of use. For more details, refer to InEight Platform release notes.

• Schedule of Values with InEight Plan components – The new Schedule of values tab lets you break down a contract into work items. These scheduled value items can also be tied to components in Plan to track claiming progress. Read more Watch video

  The new Schedule of Values lets you break the contract down by billable work items with their corresponding values to help you verify payments and track component claims in Plan. You define the quantity, unit of measure unit price, value, and associated line item to scheduled lines.

  If the schedule of value has no line item associated, there is no WBS code until you identify the schedule with a line item. Microsoft Excel import and export functionality is also available.

  

  To track these scheduled lines as contract components in Plan, deselect the Hide in plan and progress check box. When the Hide in plan and progress box is unchecked, each schedule item becomes a contract component in Plan. When the box is checked, the components are not created in Plan and are not available for claiming.

  As components are progressed in Plan, you can track them in the Component progress view. The Component progress view shows the quantity and value claimed and the percentage complete of the component. These values are linked to Plan to view claiming, and a date range is provided to view the claims in a specified period. This can help you reconcile monthly vendor statements with components.

• Configurable custom lists – Two custom lists have been added at both the Contract header and line item levels. This lets your organization set a default list that automatically populates all project drop-down lists. Read more

  Contract custom list 1 and Contract custom list 2 are in the Custom fields section on the Contract Header page and Line item custom list 1 and Line item list 2 within the Line item details.

  The drop-down list is configurable from Organization Settings > Configurations > Custom list.

  The display name of the custom list field can be customized using the Custom labels settings at the organization level.

  Custom lists 1 and 2 are also used in the Custom Fields on the Bid packages Overview page. If these values are created in bid packages, the values are carried over when the bid package is converted into a project.

• Contract writer tag enhancement – Tags used in the header or footer of a Microsoft Word template now generate data in a contract document. This helps customize and identify contract documents.

• Collection table tags - Schedule of values – Collection table tags have been added for the contract schedule of values. You can now create a schedule of values collection table in a contract template. You can find the tags by clicking the View available tags icon, and then selecting Collection table tags.

• Workflow enhancements – The look and feel of Workflow email has been updated to the InEight Suite template. During workflow setup, the email address is now shown with the user name when assigning users. Started on and Started by fields have been added to the workflow details page.

• Supporting document workflow enhancements – The ability to start a supporting document workflow from a vendor change order or a back charge has been added. A column for Current approvers has been added to all Supporting document registers, so you can see the person or the role responsible for the current approval step.

• Progress view enhancement – Columns for Good receipt % complete and Invoice received % complete have been added to the viewset. This helps you quickly see the percent complete of the line item.

• Vendor change order and payment form improvements – You can now resize the columns in the vendor change order and payment form line items tabs. The Add line item dialog box has also been adjusted to make it easier to read. A column for last modified by has also been added to the vendor change order and payment form register.

• Contracts register blank ERP sync status filter – You can now filter the ERP sync status column on the Contracts register by a blank value. This lets you quickly see the contracts that have not been integrated with the ERP.

• Project reimport – When a project is reimported into InEight Control, the Contract cost items table is deleted, and the project cost items are replaced. If a contract line item or bid package was associated with a cost item that was deleted from Control, the field is blank, and you must update it manually.

• Group workflow steps at a project level– You can now establish at the project level additional groups of steps to be added as a single step in the primary workflow of contract, vendor change order, or payment workflow. Previously you could only add a group step to a workflow at the contract level. You can also add multiple group steps to a workflow. Read more.

  When you add a contract approval step at the project level, the Assign approvers field on the Add approval slide-out panel now lets you select groups.

  

  When you start an approval, a new dialog box shows with the entire workflow. Any workflow step that contains a group step has a drop-down list for you to select the group.

• Document approval workflow– You can now establish approval workflows by document type at an organization, project, or contract level. This feature lets you have multiple-step approval for individual documents in a contract. Read more.

  You can set up document approval for each document type by contract type. At the organization or project level, go to Settings > Contract > Workflow Assignments > Document approval setup.

  

  At the contract level, you set up document approval workflows on the Document approval page of the Workflow Assignments tab.

  

  At all three levels, you can select a contract type and then select the type of document and the approver roles. At the organization level, approval is always role-based, but you can specify whether projects must select specific users based on assigned roles. At the project and contract levels, you can add steps for roles, users, and groups.

  When you configure steps at the project level, the configuration page shows the steps that have already been configured at the organization level. The steps you set up at the project level are performed before the steps set at the organization level. The contract-level configuration page shows the steps set up at the project and organization levels. Any steps you set up at the contract level are listed first, followed by steps set up at the project level and the organization level.

  At the contract level, all approval steps are listed, regardless of whether the contract has that type of document. For example, if the document approval process has a step for draft contracts, the approval steps for the draft contract are listed even if there are no documents of that type in the contract.

  To start an approval workflow for a supporting document, select a document from the Supporting documents register, and then click Start Approval.

  

  The Start approval dialog box shows all the steps in the approval workflow. If there are group steps, you can select the group for the workflow. The approval process for documents must be started individually.

  

  If you have permission to approve a document, you will see them marked with a blue ellipsis in the Supporting documents register, and they are available from your Action items register. Hover over the ellipsis to see the steps of the current approval and the current approval step.

  You can now recall a document that has already been approved if you have the permission. To recall a document, clickRecall approval in the Edit supporting document dialog box.

  

  You can view document approval workflow progress and history on the Platform Workflows page.

  A new permission, Set back to pending, has been added for recalling a document after it has been approved.

• Configurations– Bid package risk, payment form status, and liquidated damage type is configurable at the organization level. This lets your organization set a default list that automatically populates all project drop-down lists. Read more.

  The new configurations are in organization Settings > Contract > Configurations.

  

  Customizing the bid package risk values gives you the flexibility to manage your risk with values that are tailored to your organization. You can edit very low through very high risk values or add others. The values populate the Risk drop-down list on the bid package Details page.

  You can also customize liquidated damage types. You can now edit the Engineering submittals, Substantial completion, Performance guarantee, and Delivery values or add others. The values populate the LD type filed drop-down list when you add a delivery schedule to a line item. They also populate the Liquidated Damages section of the contract header. The Overall cap liquidated damages type is standard and is not part of the configuration list. Because the types are now custom, all liquidated damage types except the overall cap have been removed from the contract import. Any other liquidated damage types must be added manually.

  The payment form status configuration gives you flexibility in defining the status labels and the order. The statuses populate the Payment form status field on the payment form banner. You can edit the New, In review, Submitted, Submission failed, and Dropped statuses or add new ones. The New status or the value you change it to is always the default status when you create a new payment form. The Dropped status label can be changed and you can change the order, but after it is used, you can no longer edit the payment form. The New and Dropped statuses are marked with a yellow warning symbol on the configuration page. The Submitted and Submission failed statuses are system generated and cannot be changed. These are marked with the blue information symbol.

  

• Liquidated damages caps– The liquidation damages section on the contract header now shows when you have exceeded the liquidated damages allowance for a damages type. Read more.

  The Allowed value column has been added to the delivery schedule. The column shows the amount over the value that you can collect if the line item is past due. A yellow indicator shows when the total is over the cap.

  

  After you have associated the liquidated damage to a back charge, you cannot deselect the check box in the Delivered column or change the actual delivery date.

  Because liquidated damage types are now customizable, all liquidated damages caps, except for the overall damage cap, have been removed from the contract import.

• Invoices tab performance – The Invoices tab performance has been improved so the page loads faster than in previous releases.

• Long description configuration – The line-item long description has been removed from the organization settings configuration list (Settings > Configurations > Line item type configuration setup). You can no longer specify ifthe Long description field is enabled, required for a purchase order, or locked after a purchase order has been created.

• Removal of empty tags in templates– Contract now removes tags that do not have field information from a generated document. Read more.

  The empty tags still show in the review fields to allow users with the applicable permissions to edit tag information. If Contract is not configured to allow users to edit, you must go to the contract to add information or make changes.

• Group workflows– You can now establish additional groups of workflow steps to be added as a step in the primary workflow setup of contract, vendor change order, or payment form workflows. If multiple groups have been assigned in a workflow, the selection of a group is required before starting the workflow item. This provides flexibility in project setup. Read more.

  You can now set up groups as a project administrator when you are configuring workflows. A group is a set of users or roles in steps. For example, you could have a group that flows through your entire approval process or a group that is just the business manager. You can set up multiple groups, and you can assign multiple groups to an approval step, but only one step in an entire workflow can use groups.

  You set up a group on the Group approver setup tab (Project > Settings > Contract > Workflow Assignments > Group approver setup). Each group can have one or more steps that represent the approval process.

  

  To use a group step when setting up a workflow in a contract, select Groupsin the Assigned approvers section. The drop-down list shows a list of all groups.

  

  To start the approval process on your contract, VCO, or payment form, click Save and start approval, and then select the group to use in the workflow. In the example, you would choose the Segment 1 group for the approval process on Segment 1, Segment 2 for the approval process for Segment 2, or Business manager only for an approval that was rejected.

  

• Template watermark stamps– You can now add a watermark to Contract templates when a document is generated and, if applicable, remove it when a document is approved. Read more.

  The watermark stamp is available to use in Microsoft Word templates configured at the organization or project level. You create the watermark in a template on the template Details page in the Document stamp section.

  

  Settings let you specify whether to apply a watermark to the contract template and the watermark text, layout, and opacity. The Remove watermark stamp when document is approved toggle lets you indicate whether to remove the stamp when the document is approved. When the toggle is set to to Yes, Contract automatically removes the watermark upon contract approval. When set to No, the watermark is always on the document, and cannot be removed in neither Contract or Word. When an uploaded document has a watermark, you cannot remove it.

  When you generate a contract document from templates, you can add one or more templates with watermarks. However, if one or more of the documents has a watermark, you cannot combine the templates into a single PDF.

  The Save in supporting documents tab check box in the contract writer now defaults to On (selected). A document must be saved in the Supporting documents tab to be approved, and then the watermark can be removed.

  You now have the option of adding a watermark from the Review templates page regardless of whether one was set up in the template. The Review templates page also lets you update existing watermark text.

  

  You can view the watermark in the preview document.

  

• Generated contract edits– You can now specify whether edits are allowed for contracts generated from templates, giving you more control over the contract document. Read more.

  A new setting in the Details section of the template, Allow users to edit the document during creation, lets you specify if users can edit the document during creation.

  

  When set to No, users cannot update any of the fields, including the watermark, when the contract document is in the review step. This lets you lock a document. If something is incorrect and needs to be changed, you must change it in the contract.

  

• Configuration settings additions– New contract and line item configuration settings have been added for individual fields on the Contract Header and Line Items tabs. Organizations can set these fields as disabled, optional, or required when creating purchase orders based on its ERP requirements or business needs. Read more.

  When you enable a field, the field is available on the Contract Header page or the Line items page. You also can configure whether the field is required for a purchase order or is locked after a purchase order has been created.

  When you disable a field, the field appears shaded on the Contract Header page or Line items page, and you cannot enter information.

  Contract type configuration setup

  Configuration settings for contract types are on the organization Settings > Contract > Configurations > Contract type configuration setup page.

  

  The contract type configuration set up lets you define by content type whether the following fields are enabled:

  • Contract currency. When enabled, the field defaults to the project or vendor currency.

  • Contract terms accordion. This setting indicates whether the fields in the Contract terms section of the contract header are available.

  • Country of origin

  • Delivery address

  • Description

  • Diversity participation. When disabled, the field defaults to Off.

  • Effective date

  • Incoterm location

  • Incoterms. When enabled, the field defaults to the vendor, if applicable, or blank.

  • Invoice plan. If disabled, the field defaults to Off.

  • Payment term. When enabled the Payment term field defaults to the vendor, if applicable, or is blank.

  • Scope of contract

  • Storage location. When enabled, the field defaults to the storage location set in the project settings, if applicable, or is blank.

  • Subtype

  • Vendor

  Line item type configuration setup

  Configuration settings for contract types are on the organization Settings > Contract > Configurations >Line item type configuration setup.

  

  The line item type configuration set up lets you define by line item type whether the following fields are enabled:

  • Line item description. When enabled, the line item description is taken from the material ID, if applicable, or blank.

  • Material ID

  • Product category. When enabled, the product category is taken from the material ID, if applicable, or blank.

  • Long description

  • Country of origin. When enabled, the country of origin is taken from the contract header.

  • Valid from. When enabled, the valid from date defaults to the current date.

  • Valid through

  • Delivery address

  • Account assignment type. When disabled, only WBS is available for this field.

  • Account distribution. When disabled, only single account distribution is enabled (that is, the line item cannot be split between two accounts).

  • WBS category, when enabled, the WBS defaults to consumables.

  • WBS code/Cost center. When enable, the WBS code or cost center defaults to blanks.

  • General ledger account. When enabled, the general ledger account defaults to the value in the mapping table, if applicable, or is blank.

  • Retention percent. When enabled, the retention percent defaults to the value from the contract header.

  • Goods receipt. The default comes from the line item type table but is read only when the field is disabled.

  • Overdelivery tolerance (%). When enabled, the default comes from the project settings for the line item type.

  • Diversity participation

• Master data library additions– General ledger accounts, payment terms, and international commercial terms (incoterms) have been added to InEight Platform master data libraries for easy input and updating. Read more.

  Configuring the general ledger accounts, incoterms, and payment terms in master data libraries makes the data easier to maintain. Previously, you could only add this information through APIs. The master data additions give you the options of entering information manually or importing from a Microsoft Excel spreadsheet. You can also configure the descriptions in languages supported by InEight Platform.

  You can get to the Master data libraries from Favorite projects & organizations > Master data libraries. Select the General ledger accounts, Incoterms, or Payment terms libraries.

  

  Master data includes the following fields:

  • General ledger:

    • General ledger account

    • General ledger description

    • State: Active or inactive. Setting a general ledger account to inactive makes the account unavailable for any new contracts going forward.

  • Incoterms:

    • Incoterms code

    • Incoterms description

  • Payment terms:

    • Code, description

    • Due days:

    • Progress estimate required: Whether a progress estimate is required

    • Billing period required:

    • State (active or inactive). Setting a payment term to inactive makes the payment term unavailable for any new contracts going forward.

    You can use the due days, progress estimate required, and billing period required fields together to set up pay when paid requirements. For example, to set up pay when paid for three days from the receipt of the customer payment, you could set the Due days to 3 and then require a progress estimate for the billing to the client and a billing period.

  If your organization chooses to no longer use a general ledger account, incoterm, or payment term, you can deactivate it by changing the value of the State field to inactive. When you change the state to inactive, the account incoterm or payment term would not be available for any new contracts.

• Diversity participation– You can now enter a percentage of diversity participation that calculates the diversity participation value. Previously, you could only enter values. Read more.

  To accommodate diversity fields, the Additional details section of the Line items detail page has been renamed Additional fields. The Retention section, where the Diversity participation amount field was in previous releases, has been renamed Additional details. The Diversity participation field in the Additional details now contains a line for the percentage and a line for the value. The two lines work together. When you update one, the other updates automatically. For example if the value of the line item is $50,000, and you update the percentage of the diversity participation to 10%, the value of the line item becomes $5000. If you update the value of the line item to $6000, the percentage becomes 12%.

  

  If you make a change to the value of the line item in the vertical form or in the grid, Contract calculates the diversity participation of the percentage.

  When you change the value or percentage of the diversity participation, you get a notification telling you that the diversity participation has changed.

  A tag for the diversity participation percent has been added to the collection table tags for contract line items.

• Approval status hyperlink improvements– Approval status fields have been updated to give more visibility into the approval status. Clicking a link in the Approval status column from a register or page now opens the details of the work flow in a new browser window. Read more.

  The following pages have hyperlinks in the Approval status column:

  • Contract register

  • Invoice register

  • Payment forms register

  • Vendor change order register

  • Contract header page

  • Vendor change order detail page

  • Payment form detail page

     

• Expiration notification enhancement– Contract has been enhanced to send notifications before and after the expiration date of a document. Previously, Contract sent notification of expiring documents only until the expiration date but then stopped. Read more.

  The Expiration notification enabled toggle has been added to the Add supporting document dialog box.

  

  When set to Yes, Contract sends notifications until you edit the document and change the setting to No. The setting is not required, and is set to Yes by default. All users set at the project and organization level to receive notifications receive notifications when the document expires.

  To turn off the notification, select the document and then click the Editicon. You can then set the Expiration notification enabled toggle to No.

  Notification of expired documents has been added to the Other and Certification document types.

  The Expiration notification enabled column has been added to the Supporting Documents register.

  When you close a contract the notification setting is automatically set to Off, so notifications are not sent for expired documents on closed contracts.

• Custom labels for contract custom fields in bid packages– Custom labels for Contract custom fields 1-10 are now available in the Bid packages Custom fields section, so that when the bid package is converted to a contract, the fields are populated correctly. Previously, the custom fields in bid packages were not able to use custom labels.

• Alphanumeric WBS codes– Contract now supports alphanumeric characters, spaces, and hyphens. Previously, only numeric characters were supported.

• Contract configurations– Organization contract type configurations have been moved to the Settings Configurations tab, and additional configurations have been added to provide you more ways to customize your organization’s contract types. Read more.

  You still add a contract type from the Contract Configurations tab in the organization settings (Organization > Settings > Contract > Contracts > Contract configurations). Instead of opening the contract type slide-out panel, you now go to the Contract type configuration setup page (Organization > Settings > Contract > Configurations > Contract type configuration setup). The subtype configuration remains on the contract type slide-out panel.

  The Allow contract overage without a change order field has been renamed to Use change orders for this contract type. When set to Yes, you can now set the unlimited contract overages without a change order. Previously, you would have to set the field to 100% to allow unlimited overages.

  

  The Maximum overdelivery allowed per line item field also allows an unlimited percentage overdelivery per line item.

  The following new configuration fields have been added. When the fields are set to Yes, the corresponding tab or field is shown in the application for that contract type. When they are set to No, the corresponding tab or field is not shown in the application.

  • Use back charges for this contract type
  • Set default retention
  • Use contract closeout for this contract type
  • Track equipment details for line items of this contact type
  • Use liquidated damages for this contract type
  • Use technical field assistance for this contract type
  • Use invoice plan for this contract type

• ERP and proxy ERP configuration– A new organization configuration has been added when setting up the Contract environment. You can now indicate whether your system integrates with an ERP system. If you do not integrate with an ERP, this is called a proxy ERP. This is a one-time setting and cannot be changed after the first contract has been created. Read more.

  ERP integration settings are on the Contract Configurations tab (Organization > Settings >Contract> Contracts > Contract Configurations).

  

  Any formatting you add using the formatting tools is carried over to the contract writer for Microsoft Word documents.

  Considerations for ERP integration

  When ERP integration is set to Yes, you can also indicate whether to integrate the following ERP functions:

  • Tax calculation before publishing a contract
  • Equipment details when publishing a contract
  • Ariba for contracts

  Considerations for proxy ERP

  If you do not have an ERP system to connect to, you can switch the ERP indicator configuration to No, and validations that are only required for an ERP system are removed. When using a proxy ERP, the validations of the successful publishing of purchase orders, vendor change orders, goods receipts, accruals, and payment forms that are required when you integrate with an ERP have been removed. The proxy ERP simulates the successful publishing of these by issuing an auto-response.

  You receive a warning when the contract currency does not match a currency that is maintained in the InEight Platform conversion table for the project. Currency conversions are typically handled by an ERP. But in a proxy ERP, you can use a conversion table in the project details (Project > Project details >Details). The currency is used only in reporting. If you get a notification that the currency is not maintained in project details, contact your project administrator.

  You can only put one invoice on a payment form. With a proxy ERP, if you have multiple invoices, there is no way of knowing the line items that pertain to which invoices.

  The following fields on the Payment Progress tab can be edited:

  • Date cashed
  • Check number
  • Method
  • Paid amount
  • Retention released

• Text editor and formatting– Contract and Vendor change order terms now have text editing to let you format information for template generation. Formatting tools have been added to the Scope of contract field on the Contract Header page and the Scope of contract field and Vendor change order terms fields on the Vendor change order details page. Read more.

  The formatting tools let you add headings, lists, character formatting, and other functions like those in a word processing application.

  

  Any formatting you add using the formatting tools is carried over to the contract writer for Microsoft Word documents.

• Bid package milestones– You can now customize and add milestones at a project level and reorder them at an organization level. This adds more flexibility in defining project milestones. Read more.

  A toggle has been added at the organization level, which lets you activate or deactivate a milestone.

  

  When set to active, a milestone is available for selection at the project level; when set to inactive, the milestone does not show in the default for new projects. Deactivating a milestone is different from deleting a milestone. Previously, you could delete a milestone if it had not been used in any project. This feature still exists, but now you can deactivate milestones that you no longer want to use without removing them from the system. Deactivating a milestone takes it out of use while still maintaining the integrity of projects that had used the milestone.

  Also, at the organization level, you can indicate whether projects can edit or add milestones by selecting the Allow projects to edit add milestones check box. When selected, you and other users can add new milestones or rearrange the order of milestones at the project level.

  You can now change the order of milestones at both the organization and project levels. To move a milestone up or down in the order, select the milestone, and then use the up and down arrows to move it to its new position. Organization-level milestone positions are defaults for new projects. You can now change the positions at the project level.

  Changes at the Organization level take effect with the next new project that starts after you save the configuration and do not affect projects in progress.

  At the project level, you can still require or not require milestones set at the organization level. You can only delete milestones that are not required and have not been used in the project.

  

  If the organization has required a milestone, you cannot turn it off or delete it. Required milestones appear dimmed in the list.

  You can now add custom milestones to add another level of customization to your project. To add a milestone, click the Add milestones icon, and then enter the milestone name and indicate whether it is required.

  You are no longer required to complete the milestones in order. From the bid packages Milestones tab, you can click the Complete flag in the Milestones section in any order.

  

• Contract totals summary– The Invoiced to date field has been renamed Submitted to date to better describe the information in the field, which is the invoices you have posted over the total contract. A new section the Contract totals summary slide-out panel shows the state of all contract invoices in the system to gain visibility into the processing of invoices. Read more.

  The new Contract Invoices section shows the amount and percentage of invoices in the prime contract that have been assigned or submitted and what is remaining. The section is color-coded as follows to give you a visual status of the contract invoices:

  • Orange = Unassigned (not assigned to a payment form)
  • Yellow = Assigned but not submitted, used for payment forms in any status other than submitted or dropped
  • Green = Submitted
  • White = Remaining on contract value (total contract minus submitted invoices)

  

  The Contract invoices hyperlink takes you to the Payment Forms tab if the contract type is configured to use payment forms. If you do not have payment forms configured for the contract type, the Contract invoices hyperlink goes to the Payment Progress tab.

• Unassigned invoices on payment forms– The Unassigned invoices field has been added to the toolbar on the Payment Forms register page to give you visibility into the monetary amount of invoices that still must be added to a payment form. Read more.

  The Unassigned invoices field shows the total amount of invoices from the Invoices register that have been assigned to the contract but, have not yet been added to a payment form within the contact.

  

• Delivery schedule bill of materials– You can now enter additional metadata around materials for reporting purposes. Read more.

  New Tag, Size, Class, Material, Nameplate HP, and Nameplate voltage fields have been added to the delivery item configuration.

  

  You can also view and edit the fields from the third and fourth pages of the Delivery Schedule grid.

  

  The new delivery ID column on the Delivery Schedule grid lets the delivery schedule to be imported more than one time. For example, you can export the delivery schedule, make modifications, and import it again, and the schedule is updated.

• Custom label additions– Ten custom contract and bid package fields have been added to the custom label list to define the use of fields for an organization. A read-only view of organization custom labels has been added at the project level for you to reference against for reporting and contract writer tags. Read more.

  The custom field names show in the Additional details section of the contract header tab.

  

  The read-only view is in Project settings > Contract > Contract Custom Labels.

  

• Payment form export– You can export the information on the Payment form tab to a Microsoft Excel spreadsheet, which gives you another viewing option. Read more.

  Click the Exporticon on the Payment Forms register to download an Excel spreadsheet.

  

  The spreadsheet shows the payment form information at a high level. If your project has many payment forms, exporting to a spreadsheet can help you by making scrolling easier.

• Resized columns retention– You can resize columns on register pages and retain the new size if you leave and come back to the page. Read more.

  The following register pages retain resized columns:

  • Bid packages
  • Contract
  • Supporting document
  • Invoices
  • Accruals/Receipts
  • Back charges
  • Contract > Supporting documents

• Goods receipt configurations– You can now set goods receipts defaults based on line-item types. Previously, the system defaulted to required goods receipts for material and service line items are not required for credit line items. Read more.

  The goods receipt configuration set-up is part of the organization settings (Organization > Contract > Configurations > Goods receipt configuration setup). The settings affect the default value of the Goods receipt field in the Retention section of the Line Item details.

  

  When set to Yes, the default of the Goods receipt field is Required (goods receipts are required for that line type). When set to No, the default is Not required (goods receipts are not required for that line type).

  The Allow edits to goods receipt requirements on line items check box lets you indicate whether changing the default value of the Goods receipt field is allowed. If edits are not allowed (that is, the Allow edits to goods receipt requirements on line items check box is unchecked), and the organization has set the default goods receipt as required, you cannot make changes to the Goods receipt field in a line item. If the organization allows line-item edits, you can make changes to a line item.

• Performance enhancements– Performance updates were made behind the scenes to improve the loading time of the Invoices list page.

• Goods receipts validation in accruals– If you have overdelivery set up, the goods receipt quantity is now validated against the percentage set in the line item. Previously, there was no validation. For example, if the PO quantity is 500, you get a failure when the quantity exceeds 550.

• Contract import hint text– The hint text to the DOR portion of the contract import Microsoft Excel spreadsheet has been updated to indicate that if you want the DOR part of the header to populate, enter the email address of the user. Contract uses the email address as a key to finding the user ID.

• Bid package register owner change amount– The Owner change amount column has been added to the Bid package register.

• Contract publishing required for line items to VCO – You now must publish a contract before you can bring in line items to VCOs or create a new line item from a VCO. The Add line item button is disabled until the line item is published.

• Vendor details from Contract and Action Items pages– When you click a vendor name in the Contracts register or the Action Items register, Contract takes you directly to the vendor record. Previously, the links went to the list of vendors.

• Workflow action items – The new Action items register provides user visibility into workflows currently pending their approval. Any actionable workflow items you have that are waiting for approval are shown in the list. The list is project- and user-specific; when you log in you see only the items assigned to you. Read more.

  You can access the Action items register from the project’s Contracts page of the Contract application. The number of action items assigned to you is shown on the tab.

  

  The register shows all items waiting for your approval. You can approve or reject an item from the Action items register.

• Workflow history – Workflow details now provide visibility into the full history of the workflow, including past recalls or rejections and the name of the person who recalled the item. Read more.

  The Workflow details page now provides visibility into the whole lifecycle with the dates and times of the whole workflow. If the contract had been through workflow a more than once, the most recent record is at the top of the display, followed by the next recent. Previously you could only see the current workflow. Now you can see what happened with a contract each time it went through workflow.

  

• Copy a workflow– When setting up organization and project workflows, you now can copy a workflow from one contract type to another contract type to speed up the setup process when workflows are similar.

• Environment indicator in email subject line– The environment indicator from InEight Platform general settings now appears in brackets in the subject line of notifications and workflow emails. This lets you easily identify the test or production environment that generated the message. Read more.

  The environment indicator is located at the Organization level in Settings > General > Global options. When the Header badge display switch is set to On and the badge display text is included in the subject line. If the text box is empty, square brackets ([ ]) are used instead. If the switch is set to Off, no environment information will be included.

• Document expiration notifications– You can now configure notifications for expiring documents at the project level. Previously, this was available only at the organization level. Configuring notifications at the project level lets the person who works with the vendors to be notified of a document expiration, so they can work on reviewing before anyone at the organization level is notified. Read more.

  You can configure the notification in Project settings > Contracts >Notifications.

  

  You can indicate whether notifications for supporting document expiration is supported, the roles or users to receive the notifications, the days in advance to be notified, and the frequency of reminders.

• Organization level custom labels– Organizations can customize field names in the application to align with their business terminology. Read more.

  The following fields are included in Custom labels to be renamed to suit or define your organizations business needs:

  • Contract terms 1-10

  • Vendor change order terms 1-10

  • Line item custom fields 1-5

  Organization settings has a new tab, Contract Custom Labels (Organization > Settings > Contract >Contract Custom Labels), where you can set custom labels in all languages supported in the InEight Suite. The Enable custom labels toggle switch indicates whether the custom values are shown throughout the application. When the toggle switch is set to On, Contract uses the custom labels throughout the application and in notifications and emails. If you leave a field blank, the default is used. If the toggle switch is set to Off, the default field names are used.

  Contract writer tags continue to display as default names.

• Configurations– The Vendor change order type and Bid package type statuses are now configurable at the organization level. This lets your organization set a default list that automatically populates all project drop-down lists.

• Contract writer language type and localization– Change template language selection has been defined for all languages InEight Platform supports, so that organizations or projects can define in which language the template is generated. General tags are localized to support all languages for the template languages. Read more.

  The language of the template is defined in the Select template language field in the Contract template details.

  Selecting a template language narrows the tags available. For example, if you select Spanish as the template language, you can use only Spanish tags in the template even if the language of your application is English. Upon generation, template and tags are generated in Spanish.

  You cannot use tags in multiple languages in a single template. During template validation, the application only searches the tags of the selected language instead of all languages.

  

  If you have seeded scripts, or anything else for which Contract offers localization, Contract writer pulls the selected language as the seed.

• Inactive Organization templates– Inactive organization templates can now be removed from the project settings list. Previously, the templates were displayed on the project list, but could only be removed from the organization list.
• Payment term days– A Days due column has been added to the customer seed script for payment term. This column is a count of days defined by the customers organization for each payment term. For example, a Net30 payment term would have 30 in the Days due column.

• Invoice aging– A column for invoice days open has been added to the Invoice register and the Payment progress tab within a contract. The field will calculate the number of days the invoice has been open from the invoice date to the paid date. Field text is red if the days open exceed the payment term days.

  Organization payment term seed scripts must be updated for the feature to work

• Vendor change order terms– Change order terms have been added within each vendor change order to define scope, inclusions, and so on. Tags for these fields have also been added to contract writer general tag list. Read more.

  A vendor change order terms section has been added to the Vendor change order details page to further define change order language. The fields are available within contract writer general tags for vendor change order template generation.

• Line item additions– Five custom fields and a field for long description have been added to the line item details. Organizations can use these fields to map to the line item JSON to their ERP system.

• Bid package import improvements– New columns have been added in bid package import and contract import. Read more.

  PO ID, PO value, Custom fields 1-10 can be added to the import and to the export if they are part of the grid. The Contract import template now supports Assigned to, DOR fields 1-10, and agreement ID has been added to the export.

• Add supporting document– Adding a document from InEight Document has been moved to the drop-down list for the Add supporting document button. Currently, you do this from the Add supporting document dialog box. Read more.

  When you click the Add document icon from the Supporting documents register or the Supporting documents tab in Contract, VCO, Back charge, or Bid package, you get the option to add a new document or add one from InEight Document.

  

• Execution status validation– The Create purchase order button is no longer enabled only when contract status is in Executed status. Previously, you could only create a purchase order when the contract status was Executed. Validation has been removed, and the Create purchase order button is available regardless of contract status. If there is an approval, the button is not available until you are fully approved. Validations for supporting documents and workflow settings are still applicable.
• Invoice total field– The Invoice amount field on the Payment progress tab has been renamed Invoice total to be consistent throughout the application.
• Issue association to back charge and VCO– When you create a new issue from a back charge or VCO you will not receive an issue ID until you clickSave. This prevents an issue being created in InEight Change that could be abandoned if not saved in Contract.

• Payment form grid– Retention, Net earned, and Tax columns have been added to the Payment form register. Read more.

  The image below shows the new columns.

  

  A totals bar was added to the bottom of the grid for the Current gross, Retention, Net earned, Back charge amount, Tax, and Net Payable fields.

• Payment progress grid – A totals bar was added to the Payment progress tab grid for Invoice total and Paid amount. Read more.

  The image below shows the new totals.

  

  An export icon has also been added to the grid so you can download a Microsoft Excel spreadsheet of the payment progress grid.

• Contract and VCO statuses configuration at organization level– The Contract and Vendor CO statuses are now configurable at the organization level. This change lets your organization set a default list that automatically populates all project drop-down lists. Read more

  Organization settings for Contract has a new Configurations tab.

  

  The Draft status (or the value you change it to) is always the default status. When the Closed status (or the value you change it to) is used, the contract status becomes uneditable. These are marked with the yellow warning symbol. The Executed status is system generated and cannot be changed. This is marked with the blue information symbol.

  Because Draft and Closed statuses are now customized, there is no longer validation on statuses.

• Contract permissions – Accruals/Receipts permissions now include View, Add, Edit, and Delete functions. Previously anyone could view, add, or delete accruals and receipts without permission validation.

• Contract templates new functions – You can now load a Microsoft Word or a Microsoft Excel template as a contract template. Collection table tags have been added to enhance your template options. When you are in a template, you can preview a template with sample data, so you can check your formatting before using the template. Upon template generation, you can now merge multiple templates into one PDF document. Read more

  A Contract template can now be an Excel document, not just a Word document type. The Downloadicon now gives you a menu that lets you select Word or Excel sample example to review. The Tag list icon also gives you a menu to select general tags list or collection table tags list.

  After you have loaded your template, you can see a preview of a template with sample data by clicking Preview with sample data in the template details.

  Upon template generation, you can now merge multiple templates into one PDF document.

• Contract writer template types Contract writer template types have been defined for contracts, vendor change order, payment form, and other. The Payment form template type allows organizations the ability to define your payment form cover letter rather than use a system-generated letter. The Other template type lets you to add project-specific supplemental and exhibit information. Read more

  The Contract template Details page has been updated to include the Template type field. You can also indicate whether to set a payment form template as a default.

  The Payment form template type has a Use as default toggle switch. The default replaces the system generated document or a previous defaulted payment form document. The default also indicates this is the cover letter that is automatically attached to a payment workflow. Only one payment form can be default selected at a time. An indicator on the register indicates which template is the default.

• Contract writer View available tags– Available tags have been renamed General tags and have been updated to include any new fields or changes. The General tags window has been updated to include the location source and example data to help you see where the tag information comes from. Read more

  The Location source column shows the name of the page from which Contract pulls the information when building the template. You can see an example of how this information might look in the contract in the Example column.

  The sample template has been updated with example data.

  If there are blanks in the template, they are shown as blank in the contract.

• Contract writer collection table tags – New collection tables tags have been added so you can create customizable tables within contract templates specific to contract line items, vendor change orders, and payment forms. Read more

  Collection table tags enable you to enter one tag that "collects" all similar items into a table. For example, if a contract has 20 line items, you could specify the related collection tags one time in a formatted Microsoft Word or Excel table. When you generate the template, Contract writer collects all 20 items into the table. Without collection tags, you could not enter the items into the contract.

  When you add a new template at the organization level, you now specify the template type (that is, Contract, VCO, Payment Form, or Other), so that you can view the appropriate table tags. A template type can have multiple table tag types. For example, the Contract template has table tags for contract line items, contract VCOs, contract payment forms, and so on. Each table can use tags for one table tag-type only. You can include multiple tables in a single template.

  The new Tags section of the Contract Template Details page contains links to general and collection table tags.

  

  After you create your template, you can preview it with sample data, so you can see if it looks the way you want it to look.

• InEight Explore Contract Dashboard quick launch– An option for quick access to the InEight Explore Contract Dashboard has been added to the Actions drop-down field. The Contract Overview dashboard of InEight Explore dashboard opens in a separate window.

• New register data fields– The following data fields have been added to the contract register and import template: Division of responsibility (DOR), custom fields, Assigned to, and Remaining to buy.

• Clear all filters button added to registers– You can use the Clear all filters button to clear any filters you have in place. Read more

  The button was added to the following registers:

  • Contract templates (Organization settings > Contract templates)

  • Project level templates (Project settings > Contract templates > Project level templates)

  • Organization level templates (Project settings > Contract templates > Organization level templates)

  • Contract list page

  • Supporting documents list page

  • Invoices list page

  • Accruals/Receipts list page

  • Bid package list page

  • Email log

• Bid package enhancements– A new column for Bid package ID has been added, and now numbers are sequential within a project. The Bid package overview page has been updated to make DOR, specifications, reporting, and custom field information easier to find. Read more

  The ID numbers on the Bid Package register are now numbered within the project.

  The Bid package overview page now has accordion fields for Division of responsibilities (DOR), Specifications, Reporting, and Custom fields. The custom fields work in the same manner as the DOR fields: when you convert the bid package to a contract, the information in the custom fields populate in the same fields within the contract.

  After a bid package is associated with a contract, the contract does not pick up any new or changed information. It also does not associate the information if you already have a contract established, and you try to bring in the bid package.

  The Actions drop-down menu has been added to all tabs within a bid package.

• Copied bid package upgrades– When you copy a bid package, purchase IDs and purchase order values are included in the copy of the Overview, and you can now indicate whether the supporting document attached to the bid package is also copied.

• Total estimate currency symbol– A currency symbol has been added to the Total estimate field in the bid packages wizard.

• External purchase agreement renamed– The External purchase agreement section in bid packages has been renamed Reference data.

• Vendor optional at contract creation– You can now start a contract without a vendor. The vendor must be assigned before the contract can be published. This helps you get started writing the contract when the final vendor has not been determined, or it has not been entered in the vendor master data. Read more

  This enhancement enables you to start a vendor change order and get a contract number. You still must have a vendor to publish the purchase order.

• Custom fields renamed Contract terms– Custom fields 1-10 in the Contract terms section of the header have been renamed Contract terms 1-10. Contract writer tags have been updated accordingly. The new names align with terms that are used in contracts.

• Custom fields– Ten custom fields have been added to Bid package and Contract header under the Custom field list, giving the user the flexibility to define their own fields. The custom fields have also been added to the Contract register.

• Accordion view changes– On pages with accordion views, you can now expand only one accordion at a time. Opening an accordion closes any open accordion.

• Unpublished line items validation– Unpublished line items no longer are available for change orders or payment forms. Read more

  Previously you could bring new line items into a VCO, payment form, accrual, or receipt, enabling the line items to be edited before they are published. With this enhancement, the unpublished line items no longer show up in the list of existing line items when you add line items to a VCO, payment form, accrual, or receipt. Preventing the use of unpublished line items keeps the line items in sync with the ERP.

• Remaining to buy– The remaining to-buy amount now automatically populates from the bid package unawarded scope after you create a contract.

• VCO details updates– The VCO details tab has been updated to give more visibility to the vendor change order amount and associated issues. Read more

  The updated page is shown below.

  

  The Vendor change order amount field in the Vendor change order details section lets you enter the actual change order amount. As you associate issues, the value in the Vendor change order amount field does not change, and it remains separate from the issues.

  The Associated issues section now has columns for Issue status, Value type, PCO ID – Name, and Client CO ID – Name. The Value type indicates where the value is coming from within the issue.

  The Back charges section has been moved down on the page and theBack charge ID is now a hyperlink.

• Issue display within a VCO– The Issue display now shows Issue status, Value type, Current value, PCO ID, and CCO ID. This provides more visibility of InEight Change issues that are pulled into VCOs.

• Ability to remove an approved supporting document from a VCO– When you remove an approved supporting document from within a VCO, it is still associated to the contract but not to the VCO. If you want to disassociate a VCO from a Contract, you must disassociate it from the Supporting document tab or the Supporting document register.

• VCO and Payments grid improvements– You can now expand the size of a column on the VCO log and Payment forms pages without decreasing the size of other columns.

• Payment form new and in review statuses– After a payment form has been approved, you now can change the status to new or in review. Previously, the only actions available were submit or drop.

• Dropped payment form– You can now change the status of a payment form after it has been dropped. This lets you change the status of payments that have been temporarily parked (and had been in a dropped status) instead of starting over. Read more

  When you drop a payment (that is, select Dropped from the Payment form status drop-down menu), the following fields are not available:

  • Description
  • Work completed from
  • Work completed through

  

  You can still update the Progress estimate number, Progress estimate billing period and Comments fields and change the status.

  You can also now change the status out of Dropped if this change order needs to be revisited.

• Invoices list enhancement– Payment terms have been added to the invoices list so that you can calculate when a payment is overdue.

• APAY label changes– The APAY status fields of the Invoice register and the payment forms Invoice tab have been relabeled to Invoice status to be more descriptive to users who do not use an ERP. The APAY ID fields have been relabeled Record ID.

• Payment form workflow approval email– The link to open a payment form document for review now includes cover letter and invoice attachments.

• Back charge enhancements– You can now link a back charge to an issue and attach supporting documents. A back charge no longer creates a zero-dollar invoice to the ERP. Read more

  Now when you add a back charge you are taken to the Add back charge page instead of a dialog box.

  

  Use the Details tab to define the back charge information. After you have saved the back charge, you can link an existing back charge to a payment form, vendor change order, or issue. You also can split the back charge from this page. After a back charge has been assigned to a payment form or vendor change order, it cannot be assigned again or split.

  When you disassociate a contract from the Supporting document register, the back charge is also disassociated.

• Supporting document enhancements– The effective date and expiration date have been added to the Certification and Other document types. You can no longer replace a manually uploaded document with an integration from InEight Document, you must now create a new document. Read more

  When a document is loaded from My computer, you can no longer change the file type to a document from InEight Document. The InEight Document option shows as unavailable when a document is manually loaded, and you must replace the document with a new one.

  

  In all Supporting documents tabs, the ability to add from the supporting documents list has been added to back charges and VCOs. Selecting From supporting document list, displays a list of all documents that are associated with the contract or not associated with any contract. The supporting document list is the main supporting documents register when you open Contract. Previously you could do this only at the contract level. When you choose a document that has not been associated with a contract, the application associates the VCO or back charge and the contract number with the document.

  If you rearrange columns, the new arrangement is maintained within the supporting document tab. It does not affect other tabs.

• Import enhancement– All imports now automatically generate an email with the import results. The check box on the Import dialog box has been removed. The email contains a link to view the Import History window where you can remove or fix the errors. No records are imported if there is an error in the file.

• General ledger account field– The General ledger account field is no longer automatically overwritten if your mapping table has that field set to a null value. Read more

  In previous releases, if the mapping table had a null value for the general ledger, Contract would replace the value in the General ledger account field with a blank. With this enhancement, Contract no longer overwrites a value with a blank when there is a null value in the mapping table, or if you do not use a mapping table.

• Closeout enhancements– You can now delete closeout sections within a contract if they are not applicable. A notification email message is sent to the contract creator when the checklist is complete. English is the only language supported for any localization settings in email. Read more

  If the closeout section is used in a contract and the status is Not Applicable, Not started, or Recalled, you are able to delete the section. You cannot delete contract closeout sections if they are used in a contract and the status is Started or Complete.

• Equipment number from ERP– The equipment number from the ERP is now shown in the purchase order response. If you enter data into the field in project suite and a number exists in the ERP, the equipment number in Change is overwritten with the information in the PO response. If there is not an equipment number in the ERP, the number in Change is not overwritten.

• Error when the number range is exceeded– When you exceed the configured number of items configured for the contract you now get an error message, so you know why you cannot create that contract type.

• Additional account assignment – Cost center has been added as an additional cost assignment, expanding your assignment options beyond just WBS. Read more.

  Cost center has been added as a new account assignment type to complement the existing WBS type. To accommodate this change, the WBS details section in line items has been renamed Account assignment details and an Account assignment type field has been added to select WBS or Cost center.

  

  New cost center fields and columns have also been added throughout the application where WBS code fields and columns already exist.

• Add supporting document within a VCO – A Supporting Documents tab has been added to the VCO page, so you don’t have to leave the page to add supporting documents. Read more.

  On the new Supporting Documents tab that has been added to each VCO, when you add a new supporting document, the Document type is set by default to Draft change order and the Vendor change order ID is automatically filled with the current VCO ID. Vendor change order ID is also filled if you change Document type to Executed change order.

  

• Add existing supporting documents – You can now pull existing supporting documents into a contract. Previously, you could only create a new supporting document within a contract. Read more.

  On the Supporting Documents tab of a contract, the add button now has two drop-down options to add a New supporting document or From supporting document list. When you add from the supporting document list, a window is shown with a list of existing documents to choose from.

  

• Workflow enhancements – The project Workflows page has been updated to consider new workflow data. This change provides visibility into all workflows for tracking purposes. Read more.

  The project Workflows page has been expanded to include more columns and details for all your workflows. New columns include the associated contract ID, the current and previous approvers, days in the current step, and cumulative days open.

  

  In the details page of a workflow, you can see detailed information about each step, including approvers, status, and duration.

  

• Agreement fields converted with bid package – The Agreement ID and value fields are now retained after converting a bid package to a contract, instead of having to enter these values manually. Read more.

  When you convert a bid package to a contract, the Agreement ID and Agreement value fields in the External purchase agreement section are now retained in the Reference data section of the contract.

  

  

  This connection is not maintained beyond conversion. If you manually change these fields after conversion in either the bid package or contract, the changes are not reflected in both locations.

• Retained to date calculation– In the Contract summary push panel, the Retained to date field calculation has been changed to Actual retained + Remaining new retention value. This new calculation considers what is already paid and new amounts even if the retention rate is changed.
• Vendor currency symbol– Value fields within a contract and list pages now show the vendor currency symbol, which was not previously shown for all values.
• Negative credit line tax value– Credit line tax is now shown as a negative value everywhere it is shown. This value previously showed incorrectly as positive.
• New line item import columns– Columns have been added to line item import for cost center, account assignment category, country of origin, and harmonized system/schedule. Columns for these fields were not previously present for line item import.
• Description character limits– Descriptions for contracts, VCOs, and payment forms have been limited to 100 characters, so they can fit in email subject lines.
• Dutch language localization– Language settings have been added for Dutch, expanding the options for localization.
• Goods receipt/Payment form JSON update– New fields have been added to the JSON.
• Equipment details JSON– Data can now be pulled from Platform instead of from seed data and you can toggle this integration with a new organization-level setting.

• Additional account assignment – Cost center has been added as an additional cost assignment, expanding your assignment options beyond just WBS. Read more.

  Cost center has been added as a new account assignment type to complement the existing WBS type. To accommodate this change, the WBS details section in line items has been renamed Account assignment details and an Account assignment type field has been added to select WBS or Cost center.

  

  New cost center fields and columns have also been added throughout the application where WBS code fields and columns already exist.

• Add supporting document within a VCO – A Supporting Documents tab has been added to the VCO page, so you don’t have to leave the page to add supporting documents. Read more.

  On the new Supporting Documents tab that has been added to each VCO, when you add a new supporting document, the Document type is set by default to Draft change order and the Vendor change order ID is automatically filled with the current VCO ID. Vendor change order ID is also filled if you change Document type to Executed change order.

  

• Add existing supporting documents – You can now pull existing supporting documents into a contract. Previously, you could only create a new supporting document within a contract. Read more.

  On the Supporting Documents tab of a contract, the add button now has two drop-down options to add a New supporting document or From supporting document list. When you add from the supporting document list, a window is shown with a list of existing documents to choose from.

  

• Workflow enhancements – The project Workflows page has been updated to consider new workflow data. This change provides visibility into all workflows for tracking purposes. Read more.

  The project Workflows page has been expanded to include more columns and details for all your workflows. New columns include the associated contract ID, the current and previous approvers, days in the current step, and cumulative days open.

  

  In the details page of a workflow, you can see detailed information about each step, including approvers, status, and duration.

  

• Agreement fields converted with bid package – The Agreement ID and value fields are now retained after converting a bid package to a contract, instead of having to enter these values manually. Read more.

  When you convert a bid package to a contract, the Agreement ID and Agreement value fields in the External purchase agreement section are now retained in the Reference data section of the contract.

  

  

  This connection is not maintained beyond conversion. If you manually change these fields after conversion in either the bid package or contract, the changes are not reflected in both locations.

• Retained to date calculation– In the Contract summary push panel, the Retained to date field calculation has been changed to Actual retained + Remaining new retention value. This new calculation considers what is already paid and new amounts even if the retention rate is changed.
• Vendor currency symbol– Value fields within a contract and list pages now show the vendor currency symbol, which was not previously shown for all values.
• Negative credit line tax value– Credit line tax is now shown as a negative value everywhere it is shown. This value previously showed incorrectly as positive.
• New line item import columns– Columns have been added to line item import for cost center, account assignment category, country of origin, and harmonized system/schedule. Columns for these fields were not previously present for line item import.
• Description character limits– Descriptions for contracts, VCOs, and payment forms have been limited to 100 characters, so they can fit in email subject lines.
• Dutch language localization– Language settings have been added for Dutch, expanding the options for localization.
• Goods receipt/Payment form JSON update– New fields have been added to the JSON.
• Equipment details JSON– Data can now be pulled from Platform instead of from seed data and you can toggle this integration with a new organization-level setting.

• Link InEight Document in Bid package – You can now link bid package documents from InEight Document. This integration allows simpler use of both applications together. Read more.

  You now have the option to link a file from InEight Document to a bid package when adding a supporting document.

  In the Add supporting document window, the SELECT FILE… button is now a drop-down list with a new InEight Document option. Select this new option to open InEight Document and select a file from that application.

  

  If you have not already set up integration with InEight Document, you can select the cogwheel icon next to theInEight Document option to open Application integrations.

• Organization-level workflow thresholds – The organization can now set mandatory approvals for contracts and vendor change orders based on their value. This allows your organization’s thresholds to flow down to project-level settings. Read more.

  In organization Settings for Contract, under the Workflow Assignments tab, the Contract approval setup and Vendor change order approval setup sub-tabs now allow you to set thresholds based on values.

  

  These thresholds are assigned approver roles rather than specific users. When setting up a threshold, the Project must select specific users based on assigned roles checkbox is selected by default. When this option is selected, you must edit the threshold at the project level to select specific users within the assigned roles. A warning message appears telling you that you must make this edit.

  

  This functionality is useful when your organization requires approval by certain roles for some contract amount, but not for all people with that role across the organization. In this case, you can narrow down which individuals with that role can approve at the project level.

  You will not be able to kick off workflow at a Contract level if this warning sign is in project settings.

• Supporting document register – You can add supporting documents to the project before they are associated with a contract. Previously, you could only add supporting documents to a contract. Read more.

  The new Supporting Documents tab gives you one place to store all supporting documents, whether they are assigned to a contract or not.

  You can add new supporting documents and edit, delete or copy existing ones. After you add a document, you can assign it to a contract at any time.

  

• Tax jurisdiction switch – A setting has been added at the organization level to configure on or off to suit your organization’s tax calculation system. Read more.

  Organization-level settings already have an option to notify users or roles to input a tax jurisdiction for delivery addresses. This option can now be toggled on or off, so if your organization does not need to consider tax jurisdictions, you no longer need to assign a user or role.

  This setting is in organization Settings under the Contractstab and the Notifications sub-tab.

  

• Line item navigation – You are now able to quickly move between line item details. Read more.

  You can navigate between line items more easily with a new drop-down menu on the details page for every line item.

  When you open a line item, the header in the top left of the page reading “Line item [ID number] – details” now has an arrow next to it. When you select this arrow, a drop-down list lets you choose between any of the current contract’s line items.

  

• Delivery address at line-item level – You can now change the delivery address at a line-item level. Previously, the address was pulled from the header and applied to all line items. Read more.

  The Delivery address field is in the Line item details section and as a column in the data block. If you have multiple delivery addresses in project settings, the field is a drop-down list.

  

  If a delivery address is updated at a header level, all existing line item delivery addresses will be overwritten.

• Close line items – You can now close a line item without having to close the contract. Read more.

  The toggle to close a line item is located next to Status at the top of the Line item details section. Status is also a column in the data block.

  

  You can close all individual line items without closing the entire contract. If a contract’s status goes from closed to open, all line items will be reopened.

• In-application approval – When it’s your step in an approval process, you can now approve a contract, VCO or payment form in the Contract application. Previously, you could only approve by email. Read more.

  The new Approve button appears in a contract’s header, VCO details or payment form details.

  

  These buttons only appear when it’s your step in the process.

• Bid package milestones– All bid package milestones now appear without having to scroll in a small pane.
• Contract writer date tags– The date tag can now be inserted without a time stamp, removing data that most organizations do not need and consider unnecessary.
• Summation in line item data block– You can now see totals in a line item data block, instead of having to select the sum icon to see contract totals in a separate slide-out window.
• Tax Jurisdiction Code– This field has been updated to accept both alpha and numeric characters that allows more flexibility to work with the software or ERP used to calculate taxes.
• Paid to date calculation adjusted– The Paid to date amount will now include the retention released amount, giving a more useful calculation.
• Line item Account distribution field– The Account distribution field in line items has been changed from a toggle to a drop-down list. Previously, you had to toggle between Single and Split and then select whether to split by Quantity, Percentage or Value in a separate list. Now you can more easily select all four options in one field.
• Multi-line text maintains line breaks– Text boxes that contain multiple lines of text now maintain manual line breaks when you press Enter. This change preserves your intended formatting instead of forcing all text to one line.
• Created by information in Contract totals– The name of the person who created a contract and when it was created has been added to the Contract totals slide-out panel. This slide-out previously lacked this information, which may be useful to know when viewing totals.
• Contract template permissions– There are now permissions at the organization level to view, add, edit and delete contract templates. Previously, these permissions were at the project level only.
• Closeout permission– There is now a permission to complete a closeout checklist. Previously, a user needed permission to edit an entire contract to complete closeout.