Capability index
Everything in the platform.
Grouped by the question it answers rather than by our module names. Every entry is something the software does today. What it does not do is named at the bottom.
Am I being charged correctly?
How validation works- Bill capture
- File and batch import, statement-to-invoice hierarchy, manual entry, and the source document kept attached to what it produced.
- Charge mapping
- Supplier line descriptions mapped to charge types once, with a confidence-scored suggestion queue and per-organisation aliases.
- The six checks
- Identity, period, consumption, rates, arithmetic and credits, run in the order one failure causes the next, so a result is root-caused rather than merely flagged.
- 33 charge types
- Commodity, network, policy and settlement charges priced separately across electricity, gas and water, including the statutory gas conversion chain.
- Published reference data
- Distribution schedules for all fourteen GB networks, transmission, balancing, the levies and half-hourly line loss factors, stored exactly as published.
- Held money
- A line priced from a rate that is not yet final is held rather than failed, and resolved across the settlement reconciliation ladder as later runs publish.
- Credit notes and re-bills
- Paired to the invoices they correct instead of floating loose.
- Validation policy
- Tolerance, and a fail, warn or off action per check, set for the organisation and overridable per site and per meter.
Where is my energy going?
What the analysis shows- Half-hourly consumption
- Compared against the same period last year, last month, another meter, or the rest of the estate.
- Load profiles
- The shape of a day rather than its total, with day-type and in-hours against out-of-hours splits.
- Coverage heatmap
- Presence and gaps down to the individual day, per meter, with a grace period you set per feed.
- Energy intensity
- kWh per square metre, so a library is comparable with a lecture hall and sites rank fairly by efficiency rather than by size.
- Weather normalisation
- Degree-day adjusted, so a cold winter is not mistaken for a failed efficiency programme.
- Vacant energy
- Consumption arriving while a site should be closed, scored against that site's own operating schedule.
- Alerts
- Daily spikes against a same-day-type baseline, overnight baseload creep, missing reads, failed validations and overdue queries.
- League table
- Sites ranked by cost, consumption, unit rate or carbon, at both ends.
Can I answer what I am asked?
What the reports cover- Report library
- Templates, a run wizard, and saved configurations that a colleague can inherit rather than rebuild.
- Scheduled delivery
- By email on a cadence, to people who never sign in, until the end date you set or until somebody stops it.
- Report packs
- Several reports bundled as one document, so a board update is one attachment.
- SECR and ESOS
- Compliance formats built from the same readings that validated the bills, with the working still attached.
- Carbon reporting
- Emissions by commodity and month, with intensity per square metre and the mandatory year-on-year comparison.
- Budgets
- Create or forecast, override per month, approve and lock, then track budget against actual against accrued.
- Accruals
- Unbilled periods priced by the same engine that validates real bills, with run history and export.
- Dashboards
- Multiple named layouts, widgets you drag and resize, an organisation default, and an action-required panel.
Will it work on my estate?
What happens when data is missing- Sites
- Register, bulk import and mass edit, custom fields, cost codes, DEC tracking, operating schedules and per-site tolerance overrides.
- Meters
- The full supply-point record, metering agents, gas attributes, and the rates in force now alongside every rate that ever applied.
- Contracts
- Effective-dated terms and charges, time-of-use bands proved to cover every half hour exactly once, bulk price changes and renewal reminders.
- Consumption ingestion
- Spreadsheets in any shape saved as a per-supplier template, industry flow files, register reads and manual entry, all resumable.
- Readiness and data quality
- Which sites are ready to validate, and for the ones that are not, the exact missing field and the exact charge area it blocks.
- Roles and permissions
- Nine permissions over four base roles, plus custom roles and per-organisation overrides.
- Groups
- Hierarchical estate scoping assigned at invitation, where the group list itself is scoped, not merely the records inside it.
- Audit trail
- Append-only. A re-run adds a record and the previous one survives, so a figure quoted last quarter is still answerable.
- Multi-client
- Membership of several organisations with a switcher and a portfolio view, isolated in the database rather than in application code.
What should we buy next?
How the comparison is built- Three-way comparison
- Fixed, flexible and fully imbalanced, priced against your own half-hourly load shape rather than an annual total.
- Non-commodity included
- The same network and policy build-up on every scenario, so a cheaper headline rate with worse pass-through treatment loses where it should.
- Renewal simulation
- A candidate offer modelled against the site's own last twelve months, line by line, inside the renewal window.
- Supplier and generator data
- Market panes alongside the comparison.
Audit any rate we used
The reference data is open to you, not just to us.
Thirteen read-only tabs inside the product let you look up any published rate the engine applied, with the file it came from and the dates it was in force, including a resolver that explains in words which settlement run won for a given day and why. Most platforms ask you to trust the number. This one lets you check it without opening a ticket.
What is not here
The edges, named.
- Tenant billing and chargebacks
- Scoped in full and deliberately not built. The product re-derives what a supplier's invoice should say, and a system that also raised invoices would be marking its own homework.
- Outbound invoicing
- Not in scope. The platform covers the accounts-payable side: capture, validate, resolve, approve, export and accrue.
- Open self-registration
- Sign-up is invite-only by design, one email to one organisation.
Bring the requirement you think we will fail.
If it is on this page we will show it working on your own data. If it is not, we will say so on the call rather than after the procurement process.