Payment Applications
For Procore Customers in the United States
When your company applies the 'Owners English' or 'Speciality Contractors English' point-of-view dictionary, you'll see different tool names and term changes in the user interface. Learn how to apply the dictionary options.
- To learn the differences: Show/Hide
Subcontractor Invoices
User access to the Project level Payment applications tool depends on the user's access permission to the contracts in the Project level Main Contracts and/or Commitments tool. The tables below highlight which permissions are required for each tool in order to perform specific tasks with the Payment applications tool.
PAYMENT applications
Show/Hide Permissions
Important
Permissions for Payment applications are granted by assigning permissions for the Project level Commitments tool.
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take this action with this permission level AND one or more additional requirements, like granular permissions.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Bulk Edit Subcontractor Payment application Status with the Payment Applications Tool |
  |
||||
|
Bulk Send Subcontractor Payment applications to DocuSign® with the Payment Applications Tool |
|
||||
|
Compile Subcontractor Payment application Backups with the Payment Applications Tool |
|
||||
|
Configure Settings: Payment Applications |
|
||||
|
Create Automatic Billing Periods |
|
||||
|
Create Manual Billing Periods |
|
||||
|
Edit Billing Periods |
|
||||
|
Manage Billing Periods |
|
Main Contracts
Show/Hide Permissions
Important
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take this action with this permission level AND one or more additional requirements, like granular permissions.
What granular permissions are available for the project's Main Contracts tool?
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Create a Main Contract Payment Applications
|
|
||||
|
Create a Record for a Payment Received |
|
||||
|
Delete Main Contract Payment Applications |
|
||||
|
Edit Main Contract Payment Applications |
|
||||
|
Email Main Contract Payment Applications |
|
||||
|
Export Main Contract Payment Applications |
|
||||
|
View a Summary Preview of an Owner Payment application |
|
||||
|
View a Main Contract That is Not Private |
|
|
|
||
|
View a Private Main Contract You were Added To |
|
|
|
|
Commitments
Show/Hide Permissions
Important
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take this action with this permission level AND one or more additional requirements, like granular permissions.
What granular permissions are available for the project's Commitments tool?
PROCORE SUPPORT: INTERNAL NOTES
Some Procore customers choose to grant downstream collaborators a higher level of permissions than documented in this matrix. Although this practice is supported, it is NOT recommended for the reasons stated below:
- 'Standard' level permissions on the project's Commitments tool. Although this permission gives designated payment application contacts the ability to create payment applications with the Commitments tool, it also gives users permission to see ALL purchase orders and subcontracts that are NOT marked 'Private.' Because payment application contacts are not employees of the company account managing the Procore project, it is recommended that users do NOT provide this permission to payment application contacts.
- 'Admin' level permission on the project's Commitments tool. Although this permission gives users the ability to create payment applications, it gives the user full edit access to all of the commitments in the project's Commitments tool. It also gives the user permission to create payment applications before and after the 'Due Date.' Because payment application contacts are not employees of the company account managing the Procore project, it is recommended that users do NOT provide this permission to payment application contacts.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Accept or Decline an 'Invite to Bill' as a Payment Application Contact |
|
|
|
Users must also be the payment application contact on the purchase order or subcontract. | |
|
Add a New Payment to the Payments Issued Tab of a Commitment |
|
||||
|
Add Payment application Contacts to a Purchase Order or Subcontract |
|
||||
|
Add a Subcontractor BOQ to a Commitment |
|
||||
|
Create a Payment Issued |
|
||||
|
Create a Purchase Order |
|
|
|
This action can be performed offline. Tasks performed offline are sync with Procore once a network connection is reestablished. |
|
|
Create a Payment Application on Behalf of a Payment Application Contact |
|
|
|
||
|
Create a New Subcontractor Payment application as a Payment Application Contact |
|
|
Users with 'Read Only' level permissions must also be designated as an payment application contact on the purchase order or subcontract. | ||
|
Create a Subcontractor Payment application for Release of Retention Before, During or After the Current Billing Period |
|
|
|||
|
Create a Subcontractor Payment application for Release of Retention During the Current Billing Period |
|
|
Users with 'Standard' level permissions must also be designated as an payment application contact on the purchase order or subcontract. | ||
|
Create a Subcontractor Bill of Quantities (SBOQ) |
|
|
|
||
|
Create a Payment Received for a Main Contract |
|
||||
|
Delete a Subcontractor Payment application |
|
|
|
||
|
Edit a Commitment's Bill of Quantities |
|
|
|
This item can be viewed or edited offline provided that the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore once a network connection is reestablished. | |
|
Edit a Purchase Order |
|
This item can be viewed or edited offline provided that the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore once a network connection is reestablished. |
|||
|
Enable or Disable a Subcontractor BOQ Tab on a Commitment |
|
||||
|
Enable the Payments Issued Tab on a Commitment |
|
||||
|
Forward a Subcontractor Payment application by Email |
|
|
|||
|
Review a Subcontractor Payment application as a Payment Application Administrator |
|
||||
|
Review Payment Application Line Items as a Payment Application Contact |
|
|
|
Users with 'Read Only' or 'Standard' level permissions must also be designated as an payment application contact on the purchase order or subcontract. | |
|
Revise & Resubmit a Subcontractor Payment application as a Payment Application Contact |
|
|
|
Users with 'Read Only' or 'Standard' level permissions must also be designated as an payment application contact on the purchase order or subcontract. | |
|
Search Commitments |
|
|
|
This item can be viewed or edited offline provided that the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore once a network connection is reestablished. |
|
|
Send an 'Invite to Bill' to a Payment Application Contact |
|
||||
|
Set or Release Retention on a Subcontractor Payment application Before, During or After the Current Billing Period |
|
|
|||
|
Set or Release Retention on a Subcontractor Payment application During the Current Billing Period |
 |
|
|
Users with 'Standard' level permissions must also be designated as an payment application contact on the purchase order or subcontract. | |
|
Submit a New Payment application as a Payment Application Contact |
|
|
|
Users with 'Read Only' or 'Standard' level permissions must also be the payment application contact on the purchase order or subcontract. | |
|
Update a Subcontractor Bill of Quantities as a Payment Application Contact from the Payment Applications Tool |
|
|
|
Users with 'Read Only' and 'Standard' level permissions must also be an payment application contact. |