Back office for ERCOT retailers

You're the REP.
We'll run the back office.

You own the brand, the price and the customer. Conduit takes everything behind them — enrollment, ERCOT transactions, billing, collections and settlements — and runs it as one system instead of four vendors and a spreadsheet.

Book a demo See what we take on

5 capabilities in the core · 4 you switch on · pay for neither until you use them

One record for

the customer
the ESI ID
the enrollment
the meter read
the invoice
the payment

No nightly export between systems. No reconciliation step that exists only because two vendors disagree about the same account.

44: Texas SET 5.0 transaction types modelled
47: MarkeTrak subtypes across all 10 case types
1: double-entry ledger under every bill
2: independent layers enforcing tenant isolation

A look inside

This is the back office we're offering to run.

All 9 screens your team would work in — customers, billing, collections, the market, MarkeTrak, settlements, plans, tax and support. The rail on the left is live: click through it. It is grouped the way the product is, drawn with the product's own type, colour and status vocabulary.

Search⌘K

One customer, whole

The market status is not a field somebody types. It is the transaction chain, read back onto the record — so where an enrollment has got to is never in question.

Sample data

ACC-030118

Enrolling

Service address: Austin, TX 78745
ESI ID: 10443720009988776
Plan: Free Nights · 12 months
Requested start: 18 Mar 2026
TDU: Oncor Electric Delivery
Deposit: Waived — credit check passed

Enrollment

Quoted09 Mar
Switch requested814_0111 Mar
Accepted814_0513 Mar
Initial read867_04due 18 Mar
Active—

Elsewhere on this account

Welcome pack sent13 Mar
EFL delivered with the offer09 Mar
Address normalised to USPS09 Mar
Note from sales08 Mar

Figures here are illustrative. In a demo we load your own — a month of real transactions and a TDSP invoice — and you watch it find things.

See it on your data

The division of labour

Keep the part that makes you money. Hand over the part that costs it.

A retail electricity provider competes on brand, price and service. Nobody has ever won a customer with a better 867 reconciliation. So draw the line there.

You keep

Everything the customer sees

The brand and the offer
What you charge, and to whom
How you acquire customers
The customer relationship
Every margin decision

Conduit never talks to your customers, never sets your prices and never appears on your bill. It is infrastructure, not a partner brand.

We run

Everything behind it

Enrollment and the whole 814 chain
Meter reads, usage and rating
The bill, the ledger and the close
Past-due accounts through to disconnect
Checking every TDSP delivery invoice
ERCOT disputes and inadvertent gains
Tax, tariffs and the audit trail

Not outsourced to a service desk — automated in software you log into, with every decision visible and every figure traceable to the entry that produced it.

Off your desk

9 jobs you stop doing by hand.

Each of these is a capability in the platform. Read them as the work that disappears, because that is what you actually buy.

Core
CRM
Customers & enrollment
You stop keeping a spreadsheet of who was sold what, and re-keying it into a second system to enroll them.
Every prospect, customer, service address and ESI ID in one book of business — from first quote to an active account.
What it does
Core
Texas SET
Market transactions
You stop paying an EDI vendor to hand you files that someone then has to match against accounts by hand.
The full ERCOT document inventory, sent and received, with every chain tracked end to end.
What it does
Opt-in
ERCOT
MarkeTrak
You stop tracking disputes in a shared inbox and hoping somebody remembers the one that ages out this week.
Issue resolution that matches ERCOT's own taxonomy, so a case you open is a case they recognise.
What it does
Core
Financials
Billing & the ledger
You stop closing the month by exporting three systems into a workbook and arguing about which one is right.
A real double-entry general ledger under the bills — every invoice, payment, deposit and adjustment posts to it.
What it does
Opt-in
Dunning
Collections
You stop running the aging report by hand and deciding, account by account, who gets a notice this week.
The path from past due to disconnect, encoded once as policy instead of relived every month.
What it does
Opt-in
Wholesale
Settlements
You stop paying delivery invoices unchecked because nobody has the hours to recompute them line by line.
Check what the wires company charged you. Conduit reprices every TDSP invoice from tariff and meter read.
What it does
Core
Products
Products & pricing
You stop maintaining the rate card in one place, the EFL PDF in another, and hoping the two still agree.
Design a plan, price it per utility, publish its EFL, and renew the customers on it.
What it does
Core
Texas
Tax & tariffs
You stop maintaining tax tables in a spreadsheet and discovering the exemption was wrong at audit.
The Texas bill stack, calculated rather than estimated — and the same engine behind your quotes.
What it does
Opt-in
Collaboration
Support & collaboration
You stop forwarding email threads to explain an account to the next person who picks it up.
Notes, assignments and conversations that live on the record they are about, not in someone's inbox.
What it does

One switch, end to end

A switch is seven documents. You should have to watch none of them.

This is the chain behind a single customer moving to you. Conduit sends and receives all of it, and does the two pieces of work in the middle that decide whether the month was profitable.

814_01
Switch requested
You submit it. Conduit tracks the chain.
814_05
Enrollment accepted
The result lands; the account activates itself.
867_04
Initial meter read
The read sets the real start date.
810_02
Delivery invoiced
The wires company bills you for delivery.
RECALC
Settlement check
Conduit reprices it. Variances open themselves.
INVOICE
Customer billed
Energy, delivery, MGRT, PUC and tax — posted.
820
Remittance sent
You pay what you owe, not what was asked.

↑: you send
↓: the market sends
▪: Conduit does the work

Every code above is a real Texas SET 5.0 document, in the order the market emits it. Conduit models all 44 of them, plus move-in, move-out, cancellation, date change, permit holds and switch holds.

Runs without you

The back office does not wait for someone to open a laptop.

These are scheduled jobs, not screens. They run on their own, and only reach a person when something genuinely needs a decision.

See everything that runs unattended

The bill run

Every cycle

Reads land, usage is rated against the plan, delivery charges and taxes are applied, and the invoice posts to the ledger. Exceptions are queued for a person; the rest just bills.

The dunning sweep

Daily

Every past-due account is measured against your policy. Notices go out on the day they are due, fees apply where you said they should, and anything reaching disconnect becomes a 650.

Settlement recompute

On every 810

The moment a delivery invoice arrives it is repriced against the tariff and the meter read. Where the two disagree, a variance opens itself with the working attached.

Modular by design

Take the core. Add the rest when you need it.

Capabilities are entitlements, not a bundle. A retailer who does not do their own settlements never sees the module and is never billed for it — and can switch it on the month they decide to.

Compose your platform

Core platform — always on

5 capabilities

Customers & enrollment
Market transactions
Billing & the ledger
Products & pricing
Tax & tariffs

Opt in when it earns its place

4 modules

MarkeTrak
Collections
Settlements
Support & collaboration

Underneath

Boring where it counts.

If we are running your back office, the questions stop being about features. These are the four that actually matter.

Event-driven, not overnight: Every change publishes an event in the same transaction that wrote the data. Consumers are idempotent and replayable, so a downstream outage costs you a delay, never a record.
Your data sits behind its own lock: Tenant isolation is enforced twice: application-level filters over row-level security in Postgres. If you would rather not share a database at all, you get your own.
Everything is on the record: Row-level change history with before-and-after values, plus a separate log of operator intent. Both tables revoke update and delete — history cannot be quietly rewritten.
Turn on only what you run: Capabilities are entitlements. A retailer who does not do their own settlements never sees the module, and is never billed for it.

Developer platform

Everything the operator can do, your code can do.

Handing over the back office should not mean losing access to it. Issue a scoped key, call the same endpoints the product calls, and subscribe to the events instead of polling for changes.

Org-scoped API keys with the permissions you choose
Signed webhooks with retries, a dead-letter queue and replay
OpenAPI documents per service, so clients generate themselves
CloudEvents envelopes — the same events the platform runs on

webhook · invoice.issued

delivered

{
  "specversion": "1.0",
  "type": "energy.esi.financials.invoice.issued",
  "source": "/conduit/financials",
  "id": "0195c7a4-8f31-7c2e-9d10-4b5e6f7a8b9c",
  "time": "2026-03-01T14:22:08Z",
  "data": {
    "accountId": "0195c7a4-1c88-7f0a-b3d2-9e1f2a3b4c5d",
    "invoiceNumber": "INV-2026-03-004182",
    "amountDue": "184.62",
    "dueOn": "2026-03-21"
  }
}

See it against your own book.

Bring a month of real transactions and a TDSP invoice. We will run them through Conduit and show you what it finds.

Book a demo Explore the platform

You're the REP.We'll run the back office.

This is the back office we're offering to run.

One customer, whole

ACC-030118

Keep the part that makes you money. Hand over the part that costs it.

Everything the customer sees

Everything behind it

9 jobs you stop doing by hand.

Customers & enrollment

Market transactions

MarkeTrak

Billing & the ledger

Collections

Settlements

Products & pricing

Tax & tariffs

Support & collaboration

A switch is seven documents. You should have to watch none of them.

Switch requested

Enrollment accepted

Initial meter read

Delivery invoiced

Settlement check

Customer billed

Remittance sent