Capacity tariff discussions often confuse because teams mix two questions: how much energy was used (kWh) and how much was drawn at once (kW in a given interval). In Belgium, the capacity component is driven by your highest quarter-hour (15‑minute) average demand in the month-so one short spike or a concentrated startup window can set the whole month's charge. If you only look at total consumption or the bottom-line amount, monthly changes can seem random; once you separate usage from peak intensity, the pattern becomes clear.
What typically counts toward monthly peak pressure
- 1. Several high-load systems starting in the same 15‑minute interval (e.g. HVAC, compressors, process lines).
- 2. Predictable morning restart or post-weekend startup when many systems come on together.
- 3. Overlap between production loads and background systems (HVAC, EV charging, hot water, ventilation).
- 4. Late-month or end-of-day catch-up with compressed operating windows pushing demand into fewer intervals.
The driver is concentration in time-often in the first hour of operation-not abnormal total kWh.
What usually does not explain a peak jump on its own
- 1. Stable monthly kWh volume without timing changes.
- 2. One isolated high-use day that is not interval-concentrated.
- 3. Generic invoice amount changes without checking capacity line items separately.
This is why line-item invoice review should be paired with operational timing context.
Operational controls that work without heavy investment
SMEs can usually start with low-friction controls before any hardware change. First, map your top two or three startup windows (e.g. first hour, post-break, end-of-day) where heavy equipment overlaps. Second, define a simple stagger rule: e.g. no more than two major loads in the same 15‑minute window unless operationally required; use 10–20 minute offsets for flexible systems (EV charging, ventilation boost, hot water recovery, non-critical warmup). Third, assign one owner to review interval or peak data weekly so you can adjust before month-end instead of discovering a high peak on the invoice.
Peak risk is often procedural. The goal is better sequencing, not necessarily lower total consumption.
How the capacity line appears on your invoice
Capacity and distribution charges are usually broken out in a separate section or table on the invoice-look for terms like "capactarief", "piek", "puissance souscrite", "distribution" or "netbeheer". The capacity component is often expressed as a €/kW or €/kVA rate applied to your measured peak. If your peak goes up by 10 kW in a month, the extra cost is that delta times the tariff. Seeing the peak (in kW) and the rate on the invoice helps you link "what we did" (operational spike) to "what we paid" (capacity line).
If the stated peak seems wrong-e.g. far above what your site could physically draw-check the billing period and EAN first; then request the 15‑minute interval curve from your DSO and use it as evidence in a dispute.
Building a simple peak forecast for the month
You do not need complex software to get a rough idea of peak risk. Note your highest peak in the last few months and the main risk windows (first hour, post-break, etc.). If nothing has changed in operations, the coming month's peak will likely sit in a similar range unless you have a one-off event (e.g. extra production day, extreme weather). If you have introduced stagger rules, expect the peak to stay stable or drop. If you see a spike in the first half of the month (e.g. from interval data or a mid-month report), act before month-end-adjust schedules or escalate with operations so the second half does not repeat the same spike.
A simple "expected peak range" (e.g. 85–95 kW) written down at the start of the month makes it easier to spot when the invoice arrives with 110 kW and to trigger either an operational review or a dispute with evidence.
Why "same consumption, higher bill" is so common
Because the bill has two main drivers: volume (kWh) and peak (kW). Your energy component tracks volume-so if you use the same kWh, that part of the bill is stable (aside from indexation). The capacity and often part of the distribution component track your peak. So you can have unchanged or even lower total kWh and still see a higher bill if your peak in one 15‑minute interval was higher than in the previous month. Until finance and operations internalise that distinction, "we didn't use more" will feel like a mystery; once they do, it becomes a controllable lever.
Explain this simply to management: "Our bill has a volume part and a peak part. We controlled volume; the increase came from the peak part, which is set by our highest 15‑minute draw. We're now [mapping risk windows / introducing stagger rules / monitoring weekly] so we can control that too."
Regional differences: Fluvius, ORES, Sibelga, Resa
The logic of the capacity tariff (quarter-hour peak) is consistent across Belgian DSOs, but the exact tariff structure, labels on the invoice, and how you access interval data can differ. Fluvius covers Flanders; ORES and Resa cover Wallonia; Sibelga covers Brussels. Each has its own portal and data services. If you have sites in more than one region, keep a short note per DSO: where to find the peak on the invoice, how to request interval data, and whom to contact for meter or registration issues. That avoids confusion when a colleague in another region asks "where do we see the peak?" or "how do we get the curve?"
The same stagger and control principles apply everywhere-only the interface and the exact wording on the invoice change.
Decision rule for finance teams
If month-to-date behavior suggests a new high peak, trigger preventive action immediately and document the expected financial effect. If the final invoice still shows a disproportionate component, open a structured validation and dispute path with interval evidence attached.