Skip to main content
Procore

Best Practices for Creating an Owner Payment application Workflow (Beta)

  1. Last updated
  2. Save as PDF
 In Beta
This page details the modernised owner payment application experience.
 In Beta
This page details functionality that is not available in Procore's production environment. Access to the features documented here is limited to specific Procore customers who have signed the required agreement to participate in Procore's Company level Workflows Tool Beta Program. The content on this page is for informational purposes only and all information and content on this page is subject to change without any prior notice. To learn more, see About the Workflows Beta Program.

Owner Payment application + Workflows

When Procore customers enable the Company level Workflows tool, an authorized team member can create a custom workflow template to approve/reject your main contract payment applications. Your company can create any number of Owner Payment application workflow templates. However, only one can be assigned to a project. 

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 Main Contract Payment Applications + Workflows?  How do you create an Owner Payment application Workflow Template? How do you configure the Owner Payment application Workflow Template?

icon-41.svg
An Owner Payment application Workflow always requires a Workflow Manager. Workflows also require assignees to submit responses to the steps. It helps to sketch out your desired workflow and participants before you get started.

Ready to learn more?
See Plan a Custom Workflow Template. You can also review our  Example Owner Payment application Workflow.

icon-15.svg
 Next, Create a Project Permissions Template for Main Contracts and Assign the Project Permissions Template to each participant.

icon-13.svg
Use the Company level Workflows tool to Create a Custom Workflow Template for Main Contract Payment Applications.

You can create multiple templates, but can only assign one (1) to be the default Owner Payment application workflow.

Ready to learn more?
Review the Example Owner Payment application Workflow for recommended steps. You can also review the Self-Serve Workflow User Guide.

icon-14.svg
Next, Configure a Custom Workflow Template on a Project This is where you add your company's Workflow Manager and assignees to the steps in your custom Owner Payment application workflow.
2. Start Using Your Owner Payment application Workflow
How do you start the Owner Payment application workflow? Need to submit an approve/reject response to a workflow? Need to start, restart or return to a previous step in a workflow?

role-accounting.svg

A user first follows the steps in Create Main Contract Payment Applications. When you are ready to start the workflow, see Approve Main Contract Payment Applications.

icon-09.svg

If you are assigned to review an owner payment application, you must submit a response before the due date. See Respond to a Custom Workflow.

icon-34.svg

If you are the designated Workflow Manager for your company's Owner Payment application 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. 

Example Owner Payment application Workflow

This is an example of an Owner Payment application workflow that you can start when you're ready to send your owner payment application through the workflow for approval. You can use this example to create your company's Owner Payment application 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. 

Example

example-owner-invoice-workflow.png

This table shows you the workflow steps and step details for the example workflow.  You can customise 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?
> £50,000
  • Step Name: >£50,000
  • Type: Condition Step
    • When: Amount is Greater Than £50,000.00
  • Then: Exec Approval
  • Otherwise: Approved
 When a payment application amount is greater than £50,000.00 and the Draft is ready to send to the Assignee (Exec) for approval, the user clicks the Start Workflow button. This places the payment application into the Under Review status and sends an email to the Assignee (Exec), Workflow Manager, & Item Creator. 

To learn more about condition steps, see What are the different types of steps in a custom workflow?
Exec Approval
  • Step Name: Exec Approval
  • Type: Response Step
  • Item Status: Under Review
  • Assignee Role: Company Executive
  • Send Emails to Assignees and: Workflow Manager & Item Creator
  • Days to Complete: 5 Calendar Days
  • Responses:
    • If the response is Reject, go to the Rejected step.
    • If the response is Approve, go to the Approved step.
 When the Assignee approves a payment application, the payment application is moved to the Approved step. If the Assignee rejects the payment application, it is moved back to the first step until the reason for rejecting the payment application is resolved and the workflow. Once resolved, the user clicks the Start Workflow button to restart it. 
Approved
  • Step Name: Approved
  • Step Type: End Step (Successful)
  • Item Status: Approved
  • Send Emails to Assignees and: Workflow Manager & Item Creator
 When the Executive approval is received, an 'Approve' response updates the payment application's status to Approved. Emails are sent to the Assignees (Exec), Workflow Manager and Item Creator. 

See Also