These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Field Installation PSA
- Features
- Milestone billing
Milestone billing
Track installation deliverables through invoice action and recorded collection.
OverviewSite Milestones Ready To Invoice×
Field Installation PSA · Milestone billing
New
Site Milestones Ready To Invoice
Site milestones
| Milestone code | Site milestone name | Installation engagement | Amount | Due date | Status | |
|---|---|---|---|---|---|---|
| MC-182 | Site Milestone 228 | IE-9506 | 830 | 25 Oct | Approved | |
| MC-651 | Site Milestone 615 | IE-1695 | 140 | 22 Oct | Approved | |
| MC-808 | Site Milestone 936 | IE-4848 | 660 | 04 Oct | Approved | |
| MC-645 | Site Milestone 135 | IE-7830 | 450 | 27 Oct | Approved | |
| MC-901 | Site Milestone 679 | IE-3801 | 770 | 20 Oct | Approved |
6 of 6 records
MC-182Site milestones · SM-93150
ApprovedSite milestone nameSite Milestone 228
Installation engagementIE-9506
Amount830
Due date25 Oct
What you can do
Tie billing to a named deliverable
A site milestone carries a name, due date, amount, deliverable summary, owner and installation engagement. Pending, Submitted, Approved, Invoiced, Paid and Missed statuses show where that milestone stands. The owner prepares the delivery evidence; the Installation Manager reviews the amount and summary before the milestone becomes Approved. Billing readiness, invoiced payment amount and amount outstanding help the Billing Coordinator inspect the position for a specific engagement.
The configured Site Milestone Invoice workflow runs when an approved milestone is taken for billing. It requires an amount and an installation engagement. A valid milestone moves to Invoiced and receives a Site Milestone Invoice operation receipt. If either requirement fails, it remains Approved and receives a Failed receipt. That result is important when a milestone appears ready by status but the billing action has not succeeded.
How the work is organized
- Milestone evidence. The deliverable summary, owner, date and amount let a reviewer identify the promised installation outcome.
- Invoice operation. An Approved milestone is checked for its amount and engagement before moving to Invoiced.
- Collection record. A linked milestone payment records invoice number, amount, due date, paid date, method and collection status.
What to agree during setup
Agree who prepares milestone evidence, who approves it and who invokes the invoice action after approval. Keep the contract or statement of work attached to the relevant engagement, and use the milestone name and amount consistently with it. The billing team should decide how invoice numbers and due dates are assigned and which external system issues the customer document. An operation receipt confirms the in-app action; the customer invoice and accounting result need their own reconciliation.
Define how payment states are updated. A milestone payment can be Scheduled, Invoiced, Received, Overdue or Disputed. The Site Milestone Payment Receipt workflow records a Payment Record operation receipt when a payment is marked Received. The Billing Coordinator should review the amount and payment reference before marking that status. A payment dispute stays visible in the overdue or disputed list for follow-up.
Check the handoff on an actual case
The installation manager sets a commissioning milestone with an amount and due date under the active engagement. The milestone owner records the deliverable summary and submits it. After reviewing the work and commercial amount, the manager approves the milestone. The Billing Coordinator uses the ready to invoice list, invokes the billing action and checks that the milestone is Invoiced with a successful operation receipt.
Suppose a second milestone is approved without an amount. The invoice workflow leaves it Approved and records Failed. The coordinator corrects the amount before another billing attempt. For the first milestone, a linked payment is marked Received when collection is recorded; the payment receipt operation provides an audit trail. The team compares payment amount with the milestone’s outstanding amount before declaring the billing cycle complete.
What your team sees
- Site Milestones Ready To Invoice — Review approved deliverables before the invoice action.
- Site Milestone Payments Overdue Or Disputed — Follow collections that need a decision.
- Site Milestone Billing Exceptions — Find milestones marked Missed for review.
Follow the work through
Follow milestone to collection, then compare the commercial outcome in delivery review.
What it keeps track of
Data model- Site milestones
- Contractual milestones that trigger billing.
- Site milestone payments
- Invoices and receipts raised against milestones.
- Installation engagements
- Billable engagements with contract value, budget and delivery status.
- Operation receipts
- Evidence of executed billing, approval and document operations.
- Record attachments
- Files linked to records across the app.
Who uses it
Permissions- Installation Manager
- Approves the milestone; Billing Coordinator handles invoice and payment records; Field Operations Director reviews delayed collection.
Set up Field Installation PSA your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.