Check what the wires company charged you.
TDSP delivery invoices are large, frequent and almost never checked, because checking one by hand takes longer than the error is worth. Conduit reprices every line from the tariff and the meter read, and opens a variance where the two disagree.
Off your desk
You stop paying delivery invoices unchecked because nobody has the hours to recompute them line by line.
Without this
What this looks like today.
Delivery charges are one of the biggest lines in a retailer's cost base and the one nobody audits. The invoices arrive, they are plausible, and they are paid — because verifying a single one means pulling the tariff, finding the right rate class, reading the interval data and recomputing perhaps a dozen components.
Do that once and it takes an afternoon. Do it across a book, every month, and it is a team you do not have. So the invoices get paid unchecked, and the errors in them — a demand charge billed against the wrong peak, a nodal fee applied twice, a customer left in the wrong rate class after a change — are found by accident or not at all.
The errors are not usually malice. They are the ordinary error rate of a large automated billing process. Which is precisely why an equally automated check is the right answer to them.
How it works
Settlements, in detail.
Check what the wires company charged you. Conduit reprices every TDSP invoice from tariff and meter read.
Repriced from tariff and meter read
When an 810_02 arrives it is recomputed line by line against the published TDU tariff for that utility and rate class, using the meter data on the same chain. Not sampled, not spot-checked — every invoice, every line.
Variances open themselves
Where the billed figure and the computed figure disagree beyond tolerance, a variance opens automatically and is tracked as work. Duplicate charges, demand billed above what the interval data supports, and wrong rate classes are the recurring three.
The exposure, quantified before you spend the hours
Each variance carries what it is worth. That is the number that decides whether something is worth disputing, and it is the number a manual process never has in time to be useful.
The working is kept
Every recomputation is retained with the tariff section it turned on and the meter data it used. A dispute goes out with its evidence already assembled, rather than someone rebuilding the argument from scratch weeks after the recompute.
At a glance
- Delivery invoices recomputed line by line against the published tariff
- Variances opened and tracked automatically — duplicate charges, wrong demand, wrong rate class
- The exposure quantified, so you know what is worth disputing before you spend the hours
- Every recomputation kept, so a dispute has its working shown
Connected
What this leans on.
Nothing here is a separate product with an integration between it and the rest. These are the capabilities this one shares a record and a ledger with.
Questions
The ones we actually get.
Which charges are actually checked?
Every line on the delivery invoice that the tariff can be evaluated against — metering and customer charges, per-kWh distribution, demand, transmission cost recovery and the various riders and fees. The recurring findings are duplicated charges, demand billed above what the interval data supports, and customers left in the wrong rate class.
What happens when a variance is found?
It opens as tracked work with the computed figure, the billed figure, what it is worth, and the tariff section and meter data behind the computation. You decide what to dispute; the evidence is already assembled either way.
Does Conduit file the dispute with the TDSP for us?
Conduit produces the recomputation and the evidence pack. TODO(esi): confirm before publishing how far the outbound dispute workflow goes today — do not describe automated filing on this page until that is verified.
Is settlements part of the core platform?
No, it is an opt-in module. It tends to become worth switching on at the point where checking delivery invoices by hand has visibly stopped happening.
The rest of the platform
One customer record, one ledger, one audit trail.
See it against your own book.
Bring a month of real transactions and a TDSP invoice. Settlements is easier to judge against data you already argue about than against a demo tenant.