Procore Integration Setup

Integrating Procore Projects to Lentune.

Introduction

Integration Settings in Lentune

Select Procore Settings for Lentune Integration

Purchase Order Setting

Procore Tax Mappings

Introduction

Overview

The integration from Procore to Lentune allows you to import Vendor Codes, Project codes, Cost Codes and Cost Types from Procore to Lentune. 

When invoices are processed in Lentune, the invoice detail can then be sent back to Procore to update financial details for the relevant Projects. Invoices can then be sent on from Procore to your accounting system, e.g. Xero.

Where you have non-project invoices, such as overhead costs, these can be sent directly from Lentune to your accounting system.

Click here to read about Checking Invoices in Lentune for Procure Projects.

More information:

Project codes from Procore will be imported to Lentune depending on the Stage that is currently assigned to the Project in Procore. The Lentune settings determine what Project Stages are set to allow a Project to be imported. When a Procore Project has its Stage updated to an appropriate status, it will then be sent to Lentune.

Procore Vendor codes will be imported to the Lentune DsPayable record when there is a new vendor or changed details for a Procore vendor.

Procore Master Cost codes will be sent from Procore to Lentune. It is preferable that the Cost codes have been set up in Procore with a Cost type as this will avoid the chance that they will be overwritten.

Cost Codes and Cost Types are sent from Procore to Lentune when they are new or have been updated. These codes are then applied via the Project to incoming Supplier (Vendor) invoices.

General Ledger codes can be applied to Cost Types to provide comprehensive financial reporting capability.

Procore Divisions are the header on a grouping of Cost codes. When data is pulled in to Lentune, the Procore Division code becomes part of the Lentune Cost code.

Procore Subjobs are recognised in Lentune as separate Cost Codes. As Lentune does not have a category of subjobs, when subjobs are used in Procore, Lentune relies on the Project from Procore to be created with a budget with Cost codes.

It is suggested that Procore be set up with Cost Types on all Cost Codes, as this will avoid the need to manually allocate Cost Types to Cost Codes and verify Cost Codes while checking invoices in Lentune. For maximum benefit, it is suggested that Budgets be used for Projects in Procore. 

We recommend that the Procore Financials and Budgets are used, as this allows seam-free integration for Cost codes and Cost Types. Cost Codes will then be pulled in to Lentune with the Cost Types already attached. When Budgets have been set up in Procore, the Cost codes will be verified automatically when invoice data is transferred back from Lentune to Procore.

 Return to Top of Page

Integration Settings in Lentune

• Go to Administration > Settings > Integration tab.

In the Batch Interfaces section:

• Select Procore from the dropdown list.
  
  

In the External integration detail section:

• Click Enable Procore setting edit.
• Procore client id: This will be automatically generated.
• Procore client secret: This will be automatically generated.
• Procore callback url: This will be automatically generated.
• Click Connect to Procore.

This takes you to the Procore login, where you can logon with your Procore credentials.

 Return to Top of Page

Select Procore Settings for Lentune Integration

1. Now you can set up the Webhook monitoring settings. These are in the Procore settings section.
   1. Procore project: Update project when project is created or updated in Procore.
   2. Procore company vendor: Update Payable account when company vendor is created or updated in Procore.
   3. Procore standard cost code: Update Master Cost code when standard cost code is created or updated in Procore.
   4. Procore project cost code: Update Cost code when Project or its subjob cost code is created or updated in Procore.
2. In the Project webhook monitoring stages section, you can determine which stages that Projects must be at in order to be transferred to Lentune.
   1. Stages are:
      • • Bidding: Usually not selected.
        • Pre-construction: Usually selected.
        • Course of construction: Usually selected.
        • Warranty: Usually selected.
        • Post-construction: Usually selected.
      
      
      
   2. Create code settings. These settings determine when Cost codes are transferred and checked.
      1. Create cost code and cost type in procore: Create cost code if the cost code does not exist in Procore. This will create the cost code in the Project level and not the subjob.
      2. Check cost type when checking invoice: Cost type is required for cost codes when checking invoices in Lentune.
      3. Fetch cost code linked to cost type only: Cost code used in Procore budget will link to a cost type. By ticking this field, only cost codes used in Procore will be fetched in to Lentune.
3. Tax mappings are set up in the Tax mapping on the top right of the Procore settings section. Refer below for more detail for Tax Mappings.

• Fetch Procore project allows you to immediately fetch new Project data from Procore for your initial set up. To do this, enter the Start date and End date for the Projects to be fetched. These dates then pick up the modified dates for Projects in Procore.

• Click Save and Close to save your changes.

  Return to Top of Page

Purchase Order Setting

To determine whether your Purchase Orders are created in Lentune or Procore, you can select the appropriate setting in the Administration > Settings > Integrations page.

Refer to Procore <-> Lentune Purchase Order Settings to read about this.

  Return to Top of Page

Procore Tax Mappings

The Lentune Tax codes are in the left column. The Procore codes are on the right.

• Select the required Procore tax code to map to each of the required Lentune tax codes.
• Click Save to return to the Settings > Integration screen.

  Return to Top of Page

Last updated: 3 August 2023