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.
- Water Utility Management
- Features
- Operations control
Operations control
Operation receipts, exceptions and reconciliation.
OverviewOperation exceptions×
Water Utility Management · Operations control
New
Operation exceptions
Operation receipts
| Id | Operation key | Action | Parent | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| IDD-610 | OK-847 | ACT-847 | AD-95168 | Pending | 23 Oct | |
| IDD-475 | OK-888 | ACT-417 | AD-53974 | Failed | 05 Oct | |
| IDD-886 | OK-970 | ACT-908 | AD-58560 | Needs review | 13 Oct | |
| IDD-543 | OK-387 | ACT-885 | AD-52580 | Pending | 12 Oct | |
| IDD-634 | OK-986 | ACT-394 | AD-40631 | Failed | 17 Oct |
6 of 6 records
IDD-610Operation receipts · OR-58193
PendingOperation keyOK-847
ActionACT-847
ParentAD-95168
Occurred at23 Oct
Failure reasonCut to length
What you can do
Know that every action really took effect
Every guarded action, such as approving a document, posting a journal, applying cash or cancelling scope, writes an operation receipt. The receipt holds the operation key, the action, the revision expected, the time, and a result: pending, completed, failed or needs review. It also records references to the effects the action was meant to produce and, when something went wrong, the reason.
Receipts are what make retries safe and failures visible. A repeated request with the same operation key returns the earlier result instead of acting twice. A failure is never hidden behind an optimistic total. It waits in the exception queue until someone checks what actually happened.
How the work is organized
The operations analyst works the exception queue; the controller watches it at period end.
- One key, one effect. Each operation key produces its effect once.
- Checked, not assumed. Reconciliation reads what was actually saved, such as a posted balanced journal, applied cash or a recorded decision, before marking a receipt completed.
- Exceptions in one place. Pending, failed and needs-review receipts appear together with their reason.
What to agree during setup
Agree who works the exception queue and how often reconciliation runs, scheduled or on request. Agree what an analyst does with a receipt whose effect is missing: retry, escalate or correct. Prepare examples of a completed posting, a timed-out posting that did complete, a timed-out posting that did not, and a cash application refused for exceeding the balance.
Check the handoff on an actual case
A batch of postings is interrupted by a network fault. Three receipts are left pending. Reconciliation finds that two of the journals were posted and balanced, and marks those receipts completed. The third journal was never saved, so its receipt stays in the queue with the reason. The analyst sends it again under the same operation key, it posts once, and the queue is clear before the period closes.
What your team sees
- Operation exceptions — Pending, failed and needs-review receipts with their reason.
Follow the work through
- Operation reconciliation: From a pending receipt to a verified result.
See reports for exception trends.
What it keeps track of
Data model- Operation receipts
- Idempotent operation receipts with stable operation key and result state.
- Accounting documents
- Water charge, credit, expense and adjustment documents with lifecycle and revision.
- Journal entries
- Balanced journal entries generated from approved documents.
- Cash applications
- Applications of verified cash against posted accounting documents.
Who uses it
Permissions- Operations Analyst
- , Controller.
- The analyst reconciles receipts; the controller checks the queue before closing a period.
Set up Water Utility Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.