Platform architecture

Your systems own the product and the customer. The platform owns everything between a tariff and the meter that requires a supply licence.

   Partner systems              TrueSource                  Industry
   ───────────────              ──────────                  ────────
   product, pricing,      →     one API                →    meter point
   sign-up, servicing,    ←     supply operations      ←    registration,
   customer interfaces          and data                    reads, settlement

Operations the platform runs

These are the capabilities an integration inherits rather than implements:

Operation	What it covers
Supply	Registering meter points and taking them on supply
Settlement	Reconciling consumption against energy bought, per settlement period, ready for half-hourly settlement
Balancing	Managing the difference between contracted and consumed energy
Billing	Bill and statement production, under your brand
Financial settlement	Consumer payment collection, allocation against bills, arrears and recovery, and cash reconciliation
Compliance	Supply licence conditions, industry codes, and statutory consumer communications
Risk and hedging	Forward energy purchasing, position management, and credit cover
Customer operations	The regulated elements of serving a supply customer
Market data flows	The industry messaging a supplier is required to exchange

The integration boundary

The boundary is drawn at the supply licence. Anything a licensed supplier must do sits on the platform side; anything specific to your product sits on yours.

Concretely, you do not implement a billing engine, accede to the industry codes, connect to the smart-meter network, run settlement, or hold regulatory capital.

The ledger

Energy and money are recorded as double-entry transactions in a dual ledger. Consumption and its financial consequences are reconcilable against each other for every settlement period, which is what makes billing auditable end to end.

Contract stability

Interfaces are versioned. A change that would break a consumer of an endpoint or an event is published as a new version alongside the existing one, rather than applied to the published version in place.

Per-market differences in licensing regime and settlement are absorbed behind the API, so entering an additional territory does not require changes to your integration.