REVENUE CONTROL / BROWSER-LOCAL

How the reconciliation ledger is calculated

The engine validates first, then assigns events, resolves every effective price revision, rates exact decimal quantities and rounds once for each governed segment.

The deterministic sequence

  1. Validate unique event and invoice-line keys, non-overlapping invoice periods, types, currencies and timestamps.
  2. Reject gapped or overlapping tiers and conflicting effective price windows.
  3. Assign each event to exactly one [period_start, period_end) interval.
  4. Choose an exact customer price first, otherwise the meter default effective at each event timestamp.
  5. Rate each effective revision, apply its included quantity and minimum, then compare the exact summed minor units.
  6. Emit input hashes, normalized rows, selected pricebook rows and arithmetic trace behind every finding.

Finding classes

late_eventmissing_invoice_lineinvoice_period_unknownextra_invoice_linemissing_usageunbilled_usageunknown_priceambiguous_pricestale_price_idcurrency_mismatchamount_mismatch

An event without an invoice line is blocked because its billing-period allowance and minimum cannot be inferred. Duplicate keys and invalid rows stop before rating; they are input errors, not financial findings.

Limits

A blocked line is never included in an aggregate money claim. MeterProof does not infer a missing contract term, combine currencies or recommend an accounting action.