Purpose
Payable requirements are the documents Construction Financials collects from general contractors, subcontractors, and vendors when a pay application or expense is created. Organizations can now define their own custom payable requirement types beyond the default set.
Key Features
Custom Payable Requirement Types: Create organization-level requirement types for any document a lender or owner requires, such as HUD forms, change order logs, or stored materials backup.
Payable Requirements Grid in Project Settings: Choose which requirements apply to a project, when they're due, and which costs they apply to, all in one grid.
Project Settings Template Support: Pre-configure payable requirements in a template so new projects start with the right requirements.
Target Users
Organization Admins — define custom requirement types.
Construction Financials users — configure which requirements apply to each project.
Trade partners, subcontractors, and vendors — upload the documents that satisfy each requirement on a pay application.
Owners and lenders using both Construction Financials and CLA+ — see payable documentation count toward draws.
How It Works
1. Create Custom Requirement Types
Navigate to Organization Settings > Field Configurations > Payable Requirements.
Select the edit (pencil) icon on Payable Requirements to open a side drawer. The grid lists the default payable requirements first, followed by any custom requirements. Add a new row for each custom requirement:
Column | Details |
|---|---|
Requirement Name | The name of the requirement as it will appear in Project Settings and on payables. Required. |
Draw Rule | Optional. Select the CLA+ Draw Rule this requirement should satisfy. Free text is allowed, but a warning icon appears because the text must exactly match the name of a custom Draw Rule to work. |
Custom requirements are fulfilled by file upload and don't include an eSign template or generated document. Custom requirements that haven't been used can be archived.
2. Configure Requirements for a Project
In Project Settings, the Payable Requirements section is a grid showing the requirements active for that project. Add a row and select any default or custom requirement from the dropdown, then set:
Column | Details |
|---|---|
Requirement Name | The default or custom requirement being applied. |
Timing Required | When the document is due: With Invoice Submission, In Exchange for Payment, or On Demand. |
Required for Committed Costs | Checkbox — applies the requirement to committed costs. |
Required for Uncommitted Costs | Checkbox — applies the requirement to uncommitted costs. |
Notarized Required | Checkbox — the document must be notarized. |
Select Save to apply the configuration. The same requirement can be added to a project more than once.
3. Use Project Settings Templates
The Payable Requirements section of a Project Settings Template supports custom requirements too. Projects created from the template start with those requirements already configured.
4. Fulfill and Review Payable Requirements
Once payable requirements are configured for a project, they appear on each pay application for the trade partner to fulfill.
Uploading documents (trade partner)
Open the pay application and select the Requirements tab. Requirements are grouped by when they're due, under headers such as With Invoice Submission.
Each row shows the Requirement Name, Status, Updated At, and Updated By. Custom requirements start at Not started.
Select the action menu on a custom requirement row to open the Upload [requirement name] window, then drag and drop the file or browse to it.
The requirement's status changes to Pending once the file is uploaded. Default requirements fulfilled by eSign show Signed.
Select Submit Pay App when all requirements are complete. Built packages the required documents with the submission.
Reviewing documents
Open the pay application's Requirements tab. Each uploaded document can be previewed, downloaded, or voided from the row's action icons.
Select Approve to accept the document.
Select Request Revisions to send it back. Enter instructions in Instruct your contractor how to revise this [requirement name], then select Request. The requirement's status changes to Revisions Requested.
Note:
When revisions are requested, the trade partner sees a banner reading "Revisions requested on one or more requirements. Review the comments on each row below," with the reviewer's instructions shown on the affected row.
Requirement status also rolls up to the commitment's Receivables and Pay Applications grids, under a Vendor Requirements column group with a status icon per requirement.
Benefits
Track every document a lender or owner requires in Built, instead of uploading extras as generic supporting documents and tracking the list elsewhere.
Collect documents once, at the payable stage, and have them count toward the draw.
Consistent setup across projects through Project Settings Templates.
A single review loop for custom documents, with revision requests and comments kept on the requirement itself.
Best Practices
Build requirements into Project Settings Templates to avoid reconfiguring them on every new project.
Give custom requirement types names your trade partners will recognize, since the name is what appears on the pay application and in the upload window.
When requesting revisions, state the reason specifically — the text is the only instruction the trade partner receives.