Table of Contents
The Payments Settings page lets payors control how the payment processing features work for Procore Pay. To get there, a Payments Admin clicks the Configure Settings icon in the Payments tool. You'll see two (2) tabs: 'Payment Processing' and 'Payment Requirements.' This guide details sub-pages and controls in the Payments Processing tab.
Payments Admins use these sub-pages and their corresponding controls to manage the payment processing settings for your company's Procore Pay environment.
Before using the Payment Processing tab, it's helpful to understand these considerations as a payor.
For companies using the ERP Integrations tool:
To protect your company's personal and financial information, verification is required. To learn more, see What is a verified bank account in Procore Pay?
For companies using the ERP Integrations tool:
Can I deactivate a default account? No. A default account cannot be deactivated unless you first designate another account as the default. See Set a Default Funding Account as a Payor.
Before you deactivate the funding account, be aware of the following:
The table below details the elements for the Funding Accounts table. Verified funding accounts can receive drawdown requests when creating disbursements.
Element | Type | Description | Learn more... |
---|---|---|---|
Nickname | Field | A Payments Admin enters the account nickname when linking an account. The nickname allows Payment Disbursers to identify an account when creating disbursements. It also protects your financial privacy by eliminating the need to provide disbursers with the full bank account number. | Add Funding Accounts as a Payor |
Verification Status | Field | Shows the current verification status of the account. | Add Funding Accounts as a Payor What are the default verification statuses for bank accounts in Procore Pay? |
Bank ID | Field | A Payments Admin enters a unique Bank ID portion to be part of the unique check number issued to the next invoice payout from this account. A payout is an invoice payment in a disbursement. | Add Funding Accounts as a Payor |
Next Check No. | Field | A Payments Admin enters a unique Next Check No to be part of the unique check number issued to the next invoice payout from this account. A payout is an invoice payment in a disbursement. | Add Funding Accounts as a Payor |
Default | Field | Indicates the account is the default withdrawal account for Procore Pay in the payor environment. | Set a Default Funding Account as a Payor |
Deactivated | Field | Indicates the account has been deactivated. | Deactivate Funding Accounts as a Payor |
Overflow | Menu | Click the vertical ellipsis and choose one of the menu options. The available options in this menu are: Edit, Set as Default Funding Account, and Deactivate. On the Default account, only Edit and Deactivate are available. On a Deactivated account, only Edit is available. | Manage Business Entities as a Payor |
If you are implementing Procore Pay as a payor, your team attends an alignment call and discusses the requirements to add Payment Admins. If Procore Pay is already live, the authorized signer on your company's transaction banking agreement must send a request to your Procore point of contact or Contact Support.
When contacting support:
Complete the Procore Pay Authorized Administrator Form
Upon receipt of a request, an authorized Procore Payments Operations team member provides you with the required Procore Pay Authorized Administrator Form. An authorized signer must complete and sign it. This is usually the owner of your company or an executive to whom the owner has granted signature authority. Once signed, return to the form to Procore Payment Operations.
Add or Remove Payments Admins in the Payor Environment
An authorized Procore Payments Operations team member adds your designated Payments Admin(s) to Procore Pay for you.
To enable Procore Pay on all new Procore projects by default, move the Enable Pay on All New Projects toggle to the right. Existing projects are not affected. Any changes to this setting are logged in the Change History under the Payment Processing tab.
By default, the 'Select at Disbursement' option is enabled on the project row in the Project Controls table. This allows authorized users to select a funding account when creating disbursements to pay subcontractor invoices. See Create Disbursements. Authorized users can also change this setting under Project Controls. To learn how, see Customize the Payment Controls for Your Active Projects.
Any changes to this setting are logged in the Change History under the Payment Processing tab.
Changes are saved automatically. A GREEN success banner confirms the action.
The system saves your changes automatically.
When Procore Pay customers enable the Company level Workflows tool, an authorized team member can create a custom workflow template to approve/reject your disbursements. Your company can create any number of Payments workflow templates. However, only one (1) of those template(s) can be assigned as the default template for Procore Pay.
1. Create and Configure Your Templates |
Who will be your company's Workflow Manager and who must complete the workflow steps? | How do you manage end-user permissions for Procore Pay + Workflows? | How do you create a Payments Workflow Template? | How do you configure the Payments Workflow Template? |
Ready to learn more? |
Ready to learn more? |
Ready to learn more? |
Ready to learn more? |
2. Start Using Your Default Payments Workflow |
How do you start the Payments workflow? | Need to submit an approve/reject response to a workflow? | Need to start, restart, or return to a previous step in a workflow? |
A Payments Admin or a Payments Disburser follows the steps in Create Disbursements. After selecting the funding account, Procore Pay automatically starts the Payments workflow for the disbursement when the Workflow tool is enabled. |
If you are assigned to review a disbursement, submit a response before the due date. To learn more, see Approve or Reject a Disbursement. After submitting an 'Approve' response, an Action Required banner prompts the final reviewer to Authorize the disbursement. Funds are only withdrawn after authorization. See Create Disbursements. |
If you are the designated Workflow Manager for your company's Payments Workflow, learn how to Start a Custom Workflow, Restart a Custom Workflow, or Return a Workflow to a Previous Step. You can also Add Additional Assignees when the existing assignees are unavailable. |
This is an example of a Payments workflow that starts automatically when a disbursement is created. You can use this example to create your company's Payments Workflow or you can create your own custom workflow to suit your specific business needs. For step-by-step instructions, see Create a Custom Workflow Template.
This table shows you the workflow steps and step details for the example workflow. You can customize the steps and details as needed. To learn more, see What are the different types of steps in a custom workflow?
Step Name | Step Details | What does it do? |
---|---|---|
Controller Review |
|
When a disbursement is created, the workflow is placed into the Under Review status and automatically assigned to the Controller. Emails are sent to the Controller, Workflow Manager & Item Creator. The Controller has five (5) days to provide an approve or reject response. |
> $100,000.00 |
|
When a controller approves a disbursement and the aggregate disbursement amount is $100,000.00 or greater, the system requires secondary approval by the CFO. If the disbursement amount is less than $100,000, the system automatically moves the disbursement to the Approved step. To learn more about condition steps, see Optional Condition Steps for the Payments Tool. |
CFO Review |
|
When the aggregate disbursement amount is greater than $100,00.00, the workflow remains in the Under Review status and is automatically assigned to the CFO. Emails are sent to the CFO, Workflow Manager, and Item Creator. The CFO has five (5) days to provide a response. |
Approved |
|
When the Controller or CFO (only if secondary approval was a required condition), an 'Approve' response updates the disbursement's status to Approved. Emails are sent to the Assignees (Controller and CFO), Workflow Manager, and Item Creator. |
Rejected |
|
When the Controller and/or CFO submit a Reject response, the system updates the disbursement's status to 'Rejected.' Emails are sent to the Assignees (Controller and CFO), Workflow Manager, and Item Creator. |
When creating conditional statements for the Payments tool, Workflow Managers have these options:
Payments... Show/Hide
Condition | Definition | Example |
Disbursement Amount | The total amount of the disbursement is greater than the amount set in the workflow. | If the total amount of a disbursement is greater than or equal to $10,000,000.00, route the disbursement to the CFO for approval. |
Highest Invoice Amount | The total amount of any project invoice is greater than the amount set in the workflow. | If the amount on any project invoice is greater than $5,000,000.00, route the disbursement to the CFO for approval. |
Highest Retainage Release | The total amount of retainage release is greater than the amount set in the workflow. | If the amount of retainage released on an invoice payment is greater than $0.00, route the disbursement to the CFO for approval. |
In this tutorial, the details are configured using the example workflow from Best Practices for Creating a Payments Workflow, so you'll need to assign the following roles to perform the steps:
If you have created a custom workflow template, the details you configure will be unique to your environment.
Only a Payments Admin has access to view the Payments tool's Change History. The table on the Change History page logs the actions performed by Payments Admins and Payments Disbursers with the Company level Payments tool. For step-by-step instructions, see View the Payments Tool Change History.
Click here to learn about the table.
The table below describes the default columns on the Change History page.
Column | Description |
---|---|
Date | Shows the date and timestamp of the action. |
Action By | Shows the first and last name of the Procore user as their name appears in the Company Directory. Note: Only a member of Procore's Payments Operations Team can add Payments Admins to your account. This requires an authorized user at your company to complete and sign Procore's Payment Administrator Designation Form. Once added, this entry indicates the user was added by 'Procore Support'. For details, see Add or Remove Payments Admins as a Payor. |
Changed | Provides a brief description of the action. |
From | Shows the value that the action changed from. Note: If the action originated from a setting with a blank or null value, Procore shows the double dash symbol (--). |
To | Shows the To value that the action changed to. Note: If the action resulted in a setting with a blank or null value, Procore shows the double dash symbol (--). |
To learn more about the Payment Processing tab, see: