Pay Points
Flag schedule milestones as pay points, then track each one from completion through confirmation to paid.
A pay point is a schedule milestone that should trigger a payment once the work is done. You flag the milestone on a schedule template, and from then on every lot built from that template tracks the milestone through its own pay-out lifecycle — from the moment the task is created, through completion and confirmation, to when it's finally marked paid.
ℹ️ Where to find them: Pay points live under Financial → Pay points in the sidebar, right next to Work Orders. That's the list your finance team works from to see what's ready to pay.
The pay point lifecycle
Every pay point moves through four states. The state tells you where the milestone is in the pay-out process and who needs to act next.
💡 Every step can be reversed if you make a mistake: un-completing a task sends it back to Pending, Mark not ready sends a confirmed pay point back to Unconfirmed, and Mark unpaid sends a paid one back to Confirmed.
Setting up pay points
Pay points start on your schedule templates, so every lot built from a template inherits the same set of pay points automatically.
Open a schedule template's detail page.
On both the critical-path and subpath tables you'll see a Pay Point column on the far right. Tick the checkbox on any line item that should trigger a payment.
Click Save Changes. The flag is saved on the template.
From then on:
Applying the template to a lot — whether one lot at a time or through the batch scheduler — creates the tasks and marks each flagged one as a Pending pay point.
Duplicating a template carries the pay point flags over to the copy.
⚠️ Flagging a template item as a pay point requires the Schedule Template — update permission, typically held by Builder Admins and Project Managers.
Completing a pay point
Because completing a pay-point task is a money-moving moment, checking it off works a little differently from a normal task.
When you tick the completion checkbox on a pay-point task in the lot task list, a Complete pay point dialog opens instead of completing it right away. You have three choices:
Confirm — completes the task and marks the pay point ready to pay (Confirmed). Only offered to users who can confirm pay points.
Confirm later — completes the task but leaves the pay point Unconfirmed, so it can be confirmed afterwards.
Cancel — closes the dialog without completing the task; nothing changes.
If you un-check a pay-point task that was completed but never confirmed, it drops back to Pending and its completion date is cleared.
Pay points that are already Confirmed or Paid keep their state when you un-check the task — reverse those from the Pay Points list instead (see below).
Confirming from Field View
Completed-but-unconfirmed pay points are easy to lose track of, so Field View surfaces them for you. An Unconfirmed Pay Points section appears on the dashboard whenever pay points are waiting on confirmation (and hides itself when there are none).
Click any row to open the Mark ready to pay dialog and confirm it. Once confirmed, the row drops off the section and the pay point appears as Confirmed in the Pay Points list.
The Pay Points list
The Pay Points list (Financial → Pay points) is where the finance team reviews and pays confirmed pay points. By default it shows only Confirmed pay points, sorted by completion date oldest-first, so the items waiting longest for payment rise to the top.
Columns
Trade Partner — the company to be paid.
Task — the work the pay point is tied to.
Completion Date — when the task was completed.
State — the pay point's lifecycle state.
Filtering, sorting & sharing
Use the search box for a quick free-text filter, or open the Filters panel to filter by State, Trade Partner, or Completion Date. You can also sort by Trade Partner or State.
✅ Every filter and sort is saved in the page's web address, so you can bookmark a view (for example, "everything confirmed for one trade partner") or send the link to a teammate and they'll see exactly the same filtered list.
Row actions
Each row has a split action button whose options depend on the pay point's state and your permissions:
Every action asks you to confirm before it changes anything.
Permissions
Pay points have their own permissions, separate from regular task editing, so you can let field staff complete work without giving them the ability to release payments.