Compare invoices with measured consumption

What Vega compares

Vega has a dedicated reconciliation workflow that compares billed consumption with the component’s stored active energy consumed measurements for the invoice’s complete billing period.

It reports:

• billed and measured kWh,
• the signed difference in kWh and percent,
• measurement completeness,
• the threshold used for the verdict, and
• warnings that prevent a reliable verdict.

For invoice-to-measurement reconciliation, the default comparison threshold is 5% and the default required measurement completeness is 95%. Historical invoice comparison is a separate calculation and uses a default 20% threshold. A threshold is a review rule, not proof that the supplier or meter is correct.

Prepare the invoice and measurements

1. Upload the original invoice.
2. Open its component in Inventory > Components > Invoices.
3. Expand the invoice and verify the supplier, invoice number, supply point, meter, currency, and billing dates against the source file.
4. Open the same component’s Measurements tab.
5. Confirm that consumption data covers every complete day in the billing period.
6. Check for missing or overlapping intervals and confirm the site’s time zone.
7. Use the broader data-readiness checklist if anything is uncertain.

Invoice periods can include several supply points and do not necessarily match a calendar month. Vega evaluates each physical invoice point over its own full period.

Run the reconciliation in Chat

1. Start a new chat or continue the conversation where the invoice was uploaded.
2. Insert the exact site and component reference.
3. Identify the invoice by invoice number, supplier, or exact billing period.
4. Explicitly ask Vega to compare billed consumption with measured consumption.
5. Ask it to show coverage and warnings, not only the percentage difference.

For example:

For @Main Warehouse / Grid Meter, reconcile the Energa invoice number 12345 with measured consumption for its complete billing period. Show billed kWh, measured kWh, difference in kWh and percent, measurement completeness, threshold, and any warnings.

This explicit wording matters: Vega uses the dedicated reconciliation only when you ask for an invoice-to-measurement comparison.

Interpret the status

• Within threshold means the absolute difference did not exceed the selected threshold and coverage was sufficient.
• Deviation means the absolute difference exceeded the threshold.
• Insufficient measurement coverage means Vega withheld a verdict because too much of the billing period is missing.
• Overlapping measurement intervals means values may be double-counted, so Vega withheld a verdict.
• Component, billing period, invoice consumption, measurement, or time zone unavailable means a required input could not be resolved.
• Zero measurement baseline means a percentage verdict could not be calculated.

These statuses apply to invoice-to-measurement reconciliation. In a historical invoice comparison, Normal means the value is within the default 20% threshold of the median of comparable earlier invoices, while Deviation means its absolute percentage difference exceeds that threshold. Historical comparison can instead report Insufficient history, Metric unavailable, or Zero baseline when it cannot produce either verdict.

A non-verdict status is not evidence that the invoice agrees with the meter. Correct the underlying data or scope and run the comparison again.

Investigate a difference

Ask follow-up questions in a controlled order:

1. “Show the exact billing dates and component used.”
2. “List measurement completeness and any overlapping intervals.”
3. “Break measured consumption down by day for the same period.”
4. “Identify the dates contributing most to the difference.”
5. “List possible explanations separately from observed facts.”

Common checks include estimated readings, billing corrections, losses, meter replacement, import/export direction, daylight-saving boundaries, missing intervals, and different start or end-day conventions.

If your date filter overlaps only part of an invoice, Vega includes the complete invoice without prorating it and reports that warning. Narrow the request by invoice number or use the invoice’s exact period; do not assume a partial invoice amount was calculated.

Compare an invoice with its history

You can also ask whether the latest invoice is unusual compared with prior comparable invoices:

Compare the latest invoice for @Main Warehouse / Grid Meter with prior comparable invoices. Show the historical median, number of baseline invoices, percentage difference, and status for consumption, total cost, cost per kWh, and consumption per billing day.

Vega compares like-for-like invoices by component set, supplier, currency, and billing cadence. By default, it labels a metric Normal when it is within 20% of the historical median and Deviation when the absolute difference exceeds 20%. At least three available baseline values are required for a historical verdict. Insufficient history, Metric unavailable, or Zero baseline means Vega could not classify the metric as normal or a deviation.

Record the conclusion

Finish with a compact, reviewable summary:

Summarize the invoice identity, component, complete period, billed and measured kWh, coverage, difference, status, warnings, and the next manual check. Separate facts from possible explanations.

Open the source invoice and verify Vega’s answer before disputing a bill or making a financial adjustment.