Managing Exceptions
Filter, investigate, estimate or edit, and resolve flagged reads.
Exceptions are reads that failed a validation rule — a spike, a gap, a suspicious value — and need a human decision before they're finalized. The Exceptions screen is where you review and resolve them.
Filter
The Exceptions screen shows only reads that are still open (closed exceptions are hidden automatically). Narrow the list with:
- Exceptions (rule) filter — pick one or more validation rules, grouped by Billing, Register Reads, or Interval Reads.
- Identified Date — a date range for when the exception was raised.
- Next Bill within — quick presets (3 / 7 / 14 / 30 days) to surface anything that needs resolving before a customer's next bill goes out.
- Meter Group — narrow to a specific meter group.
- Search — by customer or meter.
Use Clear All to reset every filter at once.
Investigate
Exceptions are organized as a tree: Customer → Meter/SDP → Validation Rule. Click a customer to see which of their meters have flagged reads, then click a rule row to open the detail panel on the right — showing every read caught by that rule for that meter together, not one at a time.
Reads are grouped into blocks — one billing window at a time — so you can page through a meter's history block by block (for example, "Block 2 of 5 · Mar 17, 2026 · 3 flagged") rather than scrolling a long list. The reads table shows both register and interval reads, with flagged rows highlighted; a toggle lets you show only failed reads or everything.
Estimate or edit
For each flagged read, you have two ways to resolve the value itself:
- Estimate — click Estimate to preview DPU's system-generated estimate for every flagged read in the group (shown as a green preview, nothing is saved yet). Review it, then Accept to save the estimates, or Cancel to discard the preview.
- Edit — type a corrected value directly into a read's cell. DPU checks it against the rule's expected bounds before saving, and will reject an edit that's clearly out of range.
You can also simply Accept a flagged read as-is, if on inspection it turns out to be correct.
Stage as many of these as you like across the visible reads, then click Save Changes once to commit them together.
Resolve
If a flagged read isn't a real error and doesn't need a value change, use Ignore, which gives you two choices:
- Accept as Valid — keeps the original value and closes the exception.
- Keep Invalid — marks the read invalid and excludes it from billing and reporting, without assigning any final value.
Both ask for confirmation before applying, and both apply to every unresolved read currently in view for that rule group — there's no need to select rows individually.
If there's nothing open, the screen shows "You're all caught up!" instead of an empty table.
