Vista

¹ Project level cost codes must be added to the project from the Company level ERP Standard Cost Code List. New cost codes must be created in your ERP system, and cannot be created in Procore. Custom WBS Segments are NOT supported.

² Budget modifications sync with estimate changes in Vista®.

³ Exports the 'Estimated Cost at Completion' values from a Procore budget to Vista®.

⁴ Export of payment records from Procore to Vista® is only available in the US to customers who license Procore Pay at this time. Import of payment records from Vista® is only available for US customers at this time.

⁵ Budgets containing line items with $0 values can be exported from Procore to Vista®.

When a project is exported from Procore to Vista®, the integration takes the data and inserts into the various Forms (SQL tables) within the Vista® database. The data that is inserted for projects, populates to the JC Job Master (JCJM) and JC Job Phases (JCJP) forms.

¹ Export Note: The Viewpoint Job ID is entered manually by an accounting approver when a project is exported from Procore to Vista®. This may, or may not, depending on what the accounting approver has entered, match the Job Number found in Procore under Project > Admin. This is stored as the Viewpoint Job ID (you can view it under Company > ERP Integrations > Jobs > Synced) and is then used on other project related exports (Budgets, Commitments, Commitment CO’s, etc)

² Both Standard and Project specific cost codes (which can be created in Vista® manually under JC Job Phases) are synced up to the Project Cost Code list in Procore. Project specific codes are displayed in blue.

³ To add cost codes to a previously synced ERP project in Procore , click 'Refresh Cost Codes 'in the project level Admin tool or export the budget.

When a Vendor is exported from Procore to Vista®, a new AP Vendor Master record in the Accounts Payable module in Vista®. The vendor setup can be found in AP Vendor Master Form.

¹ Export note: The ERP Vendor ID is entered manually by an accounting approver when a company is exported from Procore to Vista®. This is stored as the ERP Vendor ID (you can view it under Company > ERP Integrations > Vendors > Synced, or under Company > Directory) and is then used on other vendor related exports (Commitments, Commitment CO’s).

² During implementation, you can select whether to sync the payment address or the purchasing address of vendors in Vista®. The selected address will be used during the import of Vista® vendors into the Procore directory.

A Budget Modification will create a JC Change Order in Vista®.

¹ Typically Budget Modifications are used to move money from one budget line item to another, usually with a zero sum effect.

A Forecasting export will create a JC Cost Projection in Vista®.

You can also manually add a Batch Date within the Procore export screen, which will export to the Batch Month in Vista® for this transaction.

When a Commitment is exported from Procore to Vista®, the integration takes the data and inputs into the various Forms (Tables) within SQL. The data that is inserted for Commitments populates to the SL Subcontract Entry (SLHD & SLIT) or PO Purchase Order Entry (POHD & POIT) forms.

If the Customer does not have the Purchase Order Module within Vista®, all Commitments within Procore will be exported into the Subcontract Ledger module within Vista®.

The Vista® Commitment ID can be defaults from Procore Commitment, or manually by an accounting approver when a commitment is exported from Procore to Vista®. This is stored as the Vista ID (you can view it under Company > ERP Integrations > Commitments > Synced) and is then used on other commitment related exports (Commitment CO’s).

¹ When a Commitment is created in Procore you must select a type, Purchase Order or Subcontract. This is used as the commitment type for Vista®.

² The ERP Vendor ID associated with the Contract Company is used on the import file for Vista®. You cannot export a commitment for a Contract Company that does not have an ERP Vendor ID.

³ Typically Units, Unit Cost and Unit Descriptions are only used on Purchase Orders.

⁴ The field is titled Contract Amount when working in a Subcontract, and it is titled Subtotal when working in a Purchase Order.

When a Commitment Change Order is exported from Procore to Vista®, the integration takes the data and inputs into the various Forms (Tables) within SQL. The data that is inserted for Commitments Change Crders, populates to the SL Subcontract Entry (SLCD) or PO Purchase Order Entry (POCD) forms.

If the Customer does not have the Purchase Order Module within Vista®, all commitment change orders within Procore will be exported into the Subcontract Ledger module within Vista®.

¹ In Vista®, this populates to the Next Sub CO # (has to be completed in order).

² Typically Units, Unit Cost and Unit Descriptions are only used on Purchase Orders.

³ The field is titled Contract Amount when working in a Subcontract, and it is titled Subtotal when working in a Purchase Order.

⁴ Only when a New line item is selected when entering the SOV on the CCO.

If this feature is enabled, all posted cost transaction details are imported into the Direct Cost tool for each project. This provides transaction detail for the costs displayed in Procore, and if the budget view is configured properly the values of those transactions can be viewed into the Direct Costs or JTD Cost columns for a budget line item.

The fields for each Direct Cost entry imported into Procore are populated from the transactions in Vista® according to the table below:

¹ Auto Count is typically 1 (one).

¹ Contract item numbering in Procore is sequential-numeric. When imported, the number or alphanumeric value assigned to an item in Vista® is replaced with the appropriate sequential number on the contract in Procore.

¹ If the option to create a new line item on the prime contract was selected during the entry of the PCO in Procore, the accounting approver will be prompted to assign the new Contract item ID number at the time of export. The Contract item Code entered is used to create the new item on the Contract in the Contracts application during this process. This item will be created with no original contract amount, the only value it will have is the approved change amount of the PCCO.

Export from Procore only. When an invoice is exported from Procore to Vista®, it is automatically posted in the Accounts Payable (AP) module.

¹ The description for an invoice that will be created in Vista® can be entered into the Description field by an accounting approver on the Ready to Export screen in the ERP Integrations tool under Subcontractor Invoices. If no description is entered at the time of export the Description field will be blank on the invoice created in Vista®.

² This is filled automatically based on the Billing Date of the Invoice in Procore, but can be overridden at the time of export on the Ready to Export screen in the ERP Integrations tool under Subcontractor Invoices.

³ Invoices that were created in Procore and sent to Vista® as AP Unapproved invoices are not supported for payment syncing at this time.