Start here
A water maintenance workflow should keep the fault report, work performed, restoration checks, invoice approval and payment as distinct records. Link them to the same asset and case so a property manager or utility team can explain the work and its cost without treating a completed repair as proof of payment.
Start with an asset-specific fault report
Record the affected pump, tank, pipe or meter rather than only a description such as “water issue.” Add the reported condition, observation time, priority and source evidence. Assign a next handler so a critical report does not remain an unowned note.
A pump running without confirmed flow, a stale sensor and a low storage observation are different situations. Route the report to the responsible operator or maintenance team. Decisions about physical equipment should follow the organization’s operating procedures and local protections.
Separate work completion from restored service
The work record should explain what was inspected, what was changed and what still needs attention. Keep parts, photos and relevant readings linked to the report. A note that a repair is finished should not automatically close a related water outage.
The team responsible for service restoration should record its own checks. This makes it easier to handle a repair that is complete while supply, pressure or another operational condition still needs verification.
Keep invoice approval and payment separate
A linked maintenance invoice is easier to review than an unexplained cost. Check that it refers to the correct work, that the amount and currency are explicit and that the relevant approver can see the supporting record.
| State | What it means | What it does not prove |
|---|---|---|
| Reported fault | An issue has been recorded | That work is authorized or complete |
| Work recorded | The work and observations are documented | That service is restored |
| Draft invoice | A cost is ready for review | That the cost is approved |
| Approved invoice | An authorized review has accepted the invoice | That payment has been made |
| Payment recorded | A payment record is linked to the cost | Provider settlement unless independently confirmed |
A practical invoice review checklist
Approval should answer a specific question: is this the correct invoice for this work, supported by the records the organization requires? It is not a substitute for a payment reference or an accounting decision.
- Match the invoice to the asset, report and work performed.
- Check the amount, currency and description against the supporting record.
- Identify the approver and record the decision.
- Keep approved-but-unpaid costs visible for the next finance step.
- Link the eventual payment reference without overwriting the earlier invoice history.
Example: approved does not mean paid
In the WaterPesa maintenance example, an invoice can remain awaiting approval after the repair is recorded. In a practice review, the sample checks establish that the invoice matches the completed work and the approver has reviewed it.
The resulting state is an approved, unpaid invoice. It should not increase “maintenance paid” merely because the review is complete. This distinction helps the operator explain both the physical work and the outstanding financial action.
What to look for in maintenance software
Look for a traceable relationship between asset, report, work, invoice and payment—not just an editable status badge. Ask whether a reviewer can find the source documents, whether access follows the responsible team and whether corrections retain the original record.
WaterPesa’s public preview uses fictional work and invoice records. It is a way to explore the handoff, not a tax-invoice service or a system that pays suppliers. A live installation needs the organization’s approved financial, access and equipment procedures.
Common questions
Should a completed repair mark the invoice paid?
No. Work completion, invoice approval and payment are separate events. Keep the invoice unpaid until there is an appropriate payment record.
Can the demo switch a real pump or pay a supplier?
No. Public examples do not send equipment commands or make supplier payments.
What should remain linked to a maintenance invoice?
The affected asset, fault report, work record, supporting evidence, approval decision and any subsequent payment reference.
Put it into practice
Explore the workflow
Use fictional records to try the next steps. Live payments, messages and equipment connections depend on your enabled integrations.