{
  "schema": "mcsj-recipe-v1",
  "id": "utility-high-low-report-meter-reading-variance",
  "title": "Utility High/Low Report: Meter Reading Variance",
  "module": "Utility",
  "source": "C:/Solutions/michel/knowledge/foster/mcsj_assets/tip_sheets/high_low_meter_exception_report_v2.json",
  "confidence": "source-compiled",
  "timing_target_seconds": 30,
  "requires_live_mapping": true,
  "short_answer": "Use the Meter Reading Exception Report and select the variance/high-low option. Run it after readings are updated to accounts and before bill calculation so unusual usage swings can be reviewed before bills go out.",
  "steps": [
    {
      "phase": "navigate",
      "action": "Open the exception report",
      "path": "Billing and Collections \u00bb Utility Billing \u00bb Utility Reports",
      "note": "From Utility Reports, choose Meter Reading Exception Report. Menu wording may vary by site/security."
    },
    {
      "phase": "operate",
      "action": "Use the current period",
      "checks": [
        "Enter the reading year/period for the readings just imported or keyed.",
        "Select the correct cycle, service type, and account status.",
        "For monthly billing, this is usually the current read period."
      ]
    },
    {
      "phase": "operate",
      "action": "Pick comparison period",
      "checks": [
        "Most monthly customers compare current usage to the prior period.",
        "Seasonal review may compare to the same period last year.",
        "Use the period that makes the usage comparison meaningful."
      ]
    },
    {
      "phase": "operate",
      "action": "Set variance thresholds",
      "checks": [
        "The screen example uses percentages like -50 and 50.",
        "Start wider, such as -500 and 500, if the list is too noisy.",
        "Tighten the numbers if staff want to catch more accounts."
      ]
    },
    {
      "phase": "operate",
      "action": "Review before billing",
      "checks": [
        "Look for leaks, bad reads, meter issues, seasonal usage, or absence.",
        "High positive usage swings usually need the closest review."
      ]
    }
  ],
  "watch_outs": [
    "Run one exception type at a time when training new users.",
    "Lower current reads may be valid rollover/changeout/reset or a keying error.",
    "If the list is too large, widen the threshold; if too small, tighten it."
  ],
  "completion_contract": [
    "Use live chestervillagenydb only",
    "Verify record/batch ID before write",
    "Capture visible after-proof",
    "For batches, Save alone is incomplete; verify and Update/Post when applicable"
  ]
}