Invoice & OSOS

OSOS–invoice reconciliation guide

Period alignment, totals vs profiles, and a practical dispute checklist.

  • Energy Management
  • blog.readMinutes

Invoice reconciliation with OSOS data is the process of independent verification of the invoice issued with the distribution company's meter records. OSOS (Automatic Meter Reading System) offers 15-minute or hourly active consumption, reactive and demand profiles; The invoice is the monetary summary of the same period. When you align two sources, kWh deviation, unit price difference and reactive penalty errors become visible before the invoice payment date.

Why is reconciliation done with OSOS data?

Invoice total amount summarizes history; It does not indicate which day or time the deviation occurred. The OSOS profile details the intra-period consumption distribution, reactive rate trend and demand peaks. As the importance of energy management and monitoring is emphasized in our article, savings claims made without measurement cannot be proven; Reconciliation works on the same logic — the meter data is the source of evidence for the billing claim. Integration and alarm infrastructure on our OSOS consumption monitoring page forms the technical basis of this process.

What data should be prepared before reconciliation?

Three sets of resources are required before reconciliation: (1) electricity bill (PDF or e-invoice) of the relevant period, (2) OSOS consumption export (active kWh, reactive kVArh, demand) of the same period, (3) supply contract or tariff table (unit price reference). PTF and YEKDEM components should also be noted for free consumer subscribers. It is critical that the period start and end dates match exactly on the invoice and OSOS records — a one-day shift can make a difference of thousands of kWh.

Reconciliation steps

  • Step 1 — Period alignment: Match the invoice period dates with the OSOS export range; Note the reading day differences.
  • Step 2 — Active consumption control: Compare OSOS total kWh with the consumption amount on the bill; In case of out-of-tolerance deviation, verify the meter serial number.
  • Step 3 — Unit price verification: Compare the unit price on the invoice with the supply contract or SKTT formula (PTF+YEKDEM)×KBK.
  • Step 4 — Reagent control: Compare OSOS reactive/active ratio to bill limits (9 kW exemption, 33%/20% or 20%/15%).
  • Step 5 — Demand control: Match the OSOS max demand value with the power item on the invoice and the contract power.
  • Step 6 — Variance reporting: Document variances by item; Create evidence package for appeal or correction request.
  • Step 7 — Closing: Archive the approved invoice; Update alarm thresholds for the next period.

How to make active consumption reconciliation?

The total active consumption (kWh) for the period in OSOS export is compared with the “active energy consumption” line on the invoice. Small differences (reading time tolerance) are normal; Deviation of more than one percent should be investigated. For eligible consumer subscribers, supplier and distribution invoices may arrive separately — verify that the consumption amount in both documents comes from the same meter source. Hourly profile analysis also reveals abnormal consumption increase during peak hours.

How to check reagent and demand reconciliation?

In reagent reconciliation, OSOS period total inductive and capacitive kVArh values are matched with the Ri/Rc lines on the invoice. The limits in our Reactive Energy and Reactive Cost guide are applied according to contract power: exemption below 9 kW, 33%/20% below 30 kW, 20%/15% above. In demand reconciliation, the OSOS max kW value is compared with the power excess or demand line on the invoice. If the two items are not controlled together, the reactive penalty and the power overage cost overlap.

15 min typical

OSOS measurement range

Hourly is also possible

≤ 9kW

Reagent exemption

Contract power

15,000 kWh/year

SKTT industry limit

Unit price impact

What to do when deviation is detected?

When an item-based deviation is detected, a written notification is first made to the distribution company or supplier; OSOS export, invoice PDF and calculation table are added. The objection period is limited from the invoice issuance date — early detection is critical. Software-based reconciliation processes create an audit trail; Which item was queried and when is recorded. These steps can be automated in the electricity bill tracking process.

Reconciliation — item-based tolerance and action
pencilTypical toleranceDeviation sourceaction
Active kWhBelow 1% is normalPeriod shift, counterPeriod correction request
unit priceAccording to the contractPTF/YEKDEM updateSupplier objection
Reactive ratebelow the borderCompensation is insufficientoperational response
Max demandContract powerpeak hour peakPower overhaul

What is the multi-site reconciliation difference?

In multi-facility businesses, each subscriber number (installation) requires separate reconciliation; Without a central panel, the Excel-based process does not scale. Subscriber inventory (installation number, contract strength, supplier, OSOS connection status) should be kept up to date. Central consensus shows total portfolio variance and ranking of riskiest facilities; resource allocation is made accordingly.

How to connect unit price reconciliation with OSOS?

Unit price reconciliation is made after OSOS total kWh is verified: the unit price in the invoice for the same kWh is compared with the supply contract or SKTT formula (PTF+YEKDEM)×KBK. OSOS consumption profile provides an hourly breakdown; The consumption rate at peak hours helps narrow down the source of unit price deviation. For eligible consumer subscribers, when supplier and distribution invoices arrive separately, both must be matched with the OSOS record.

What should be the reconciliation frequency?

Monthly reconciliation is the minimum standard; In free consumer and high consumption facilities, OSOS pre-check is recommended before issuing invoices. The reactive limit approach (above 9 kW, 33%/20% or 20%/15%) should be monitored weekly or in real time — monthly reconciliation alone will not prevent reactive penalty. In a multi-site portfolio, the central panel should show the reconciliation status of all subscribers (complete / deviation / disputed) at a glance.

How to archive reconciliation records?

The archive package for each reconciliation cycle should include: invoice PDF/e-invoice, OSOS period export, calculation table (expected vs. invoice values), objection letter and response, if any. This archive serves as evidence in ISO 50001 and EİVER audits. The archive is created automatically in the software-based process; In the manual process, the folder structure (year/month/installation) should be standardized. The audit trail records which item was approved or queried and when.

How is the separation of supplier and distribution invoice managed in reconciliation?

For free consumer subscribers, supplier invoice (active energy, PTF, YEKDEM) and distribution invoice (distribution fee, reactive, power) are issued separately. Reconciliation verifies both documents with the same OSOS consumption record — kWh values ​​must be equal in both invoices. Supplier unit price (PTF+YEKDEM)×KBK; Distribution items are controlled by contract strength and tariff table. Reconciling only one of the two invoices creates an incomplete picture.

Conclusion

Invoice reconciliation with OSOS data is the basic discipline of energy cost management. The seven-step process — period alignment, kWh, unit price, reagent, demand, reporting and closing — should be repeated every month. The manual Excel process works on small portfolios; Software-based reconciliation across ten sites provides both speed and an audit trail. Start your first reconciliation with the checklist in this guide.

Tags

OSOSinvoice reconciliationelectricity billconsumption monitoringreactive punishmentdemand

See the platform live

Request a demo or check pricing and our team will plan a presentation tailored to you.