Revenue management

Tariffs, financial billing, payments, debt, settlement, prepayment and STS design.

PRODUCT OVERVIEW

Keep the financial result distinct from the reading.

AetherRevenue is the revenue-operations component of AetherONE. Its approved design takes technical Bill Determinants from MDMS into tariffs, billing, payments, reconciliation, debt and settlement.

Prepayment scope includes accounts and append-only balances, merchants, vending records and STS lifecycle reference metadata. This edition is a synthetic evaluation interface, not a live payment or token service.

Who it is for

Billing analysts and supervisors
Payment allocation and reconciliation teams
Prepayment, merchant and integration teams

Concept revenue chain: usage, tariff bands, bill, receipt and ledger exception. — Concept illustration of the product responsibility. It is not a customer installation or an operational record.

Responsibilities and evaluation scope

Tariffs: Approved design scopeVersioned tariff catalogue, design, golden-case simulation and effective assignment periods.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Billing accounts and cycles: Approved design scopeBilling account list/360, bill-cycle calendar and billing windows.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Bill runs: Approved design scopePopulation, billed amount, quarantined exceptions with reasons and approval trail.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Bills and adjustments: Approved design scopeStep-by-step calculation traces, rebills, credit notes and adjustments with reasons/status.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Payments and allocation: Approved design scopePayment channels, allocated and unallocated payments kept distinct from bills.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Reconciliation: Approved design scopeBank-statement and gateway matching, unmatched items and follow-up hints.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Debt and service actions: Approved design scopeAging buckets, collection cases, and disconnect/reconnect approval references.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Subledger and finance export: Approved design scopeJournals linked to bill runs/payments and export batches acknowledged towards separate AetherFinance.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Prepayment accounts: Approved design scopeAppend-only balance ledger and reconciliation against meter register projections.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Merchants: Approved design scopeMerchants, outlets, terminals, credit, commissions and settlement periods.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
Vending: Approved design scopeSale/payment, delivery, meter confirmation, reconciliation, reissue, reversal and refund workflows.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
STS lifecycle and security context: Approved design scopeToken intent, SGC/KRN/KEN/TID metadata, security-module status projection and key-change campaign view; no token values, keys or module control.; Available in this editionEvaluation interface with synthetic data; no live business operation or persistence.
STS training lab: Approved design scopeFixed public vectors and decoder/lifecycle walkthroughs in a TEST SECURITY DOMAIN.; Available in this editionTraining only; no production token generation, live security module or STS certification.

How the work connects

The original diagrams and interface excerpts below are in English. The surrounding description explains their scope in the page language.

Revenue design: MDMS technical determinants and CIS references through tariffs, bills, payment and reconciliation, with a separate prepayment branch. — Design workflow. The relationships shown are not a claim of running cross-product integration.

Clear responsibility across products

AetherMDMS / AetherCIS: MDMS supplies technical usage/determinants, not a financial bill. CIS owns customer/service identity. Revenue owns financial-context references; their mapping to CIS accounts is a project decision.
AetherFinance / AetherDispatch / AetherHES: Finance receives export batches through a separate boundary; Dispatch owns field work and HES owns device execution. Revenue never reads their private databases.
Versioned contracts: Schema 1.0.0 definitions cover mdms.bill-determinant.ready.v1, revenue.bill.issued.v1, revenue.payment.confirmed.v1 and revenue.sts-token.state-changed.v1. Token changes carry a fingerprint rather than a token. Definitions do not prove live integration.

Utility scenarios

Review a bill run before approval

Set tariff versions and calculation lineage beside quarantined exceptions and the approval trail. Demonstration amounts and populations are examples.

Reconcile payments

Keep a payment, its allocation and its bill as distinct evidence, then investigate unmatched bank or gateway records.

Reconcile a prepaid vend

Compare sale/payment, token-delivery reference, meter confirmation and the append-only account balance; a ledger difference and an offline meter require different follow-up.

Evaluation views · synthetic data

The original diagrams and interface excerpts below are in English. The surrounding description explains their scope in the page language.

Synthetic Revenue bill run, quarantined exceptions and approval trail. — Evaluation interface excerpt with synthetic data. Identifiers, amounts, dates and counts are examples, not customer or performance evidence.

Synthetic prepayment reconciliation and mismatch responsibilities. — Evaluation interface excerpt with synthetic data. Identifiers, amounts, dates and counts are examples, not customer or performance evidence.

Edition and evaluation conditions

Evaluation interface on explicitly selected synthetic records. No connected API, authentication, persistence, posting or real business transaction is provided. Approval, vending, rebill, refund, reissue and campaign controls execute nothing.

No tax-invoice compliance, STS certification, live security module, protocol compatibility, capacity or customer deployment is claimed. Operational use requires tariff rules, payment channels, finance integration, security and approved MDMS/CIS contracts.

Document edition 2026.10 identifies the supplied documents, not a commercial release or a deployed version.

Product documents

Choose a language to download the matching document edition.

AetherRevenue Datasheet · English (PDF)English · PDFDocument edition 2026.10
AetherRevenue Catalogue · English (PDF)English · PDFDocument edition 2026.10

Discuss an evaluation ↗

EXPLORE OTHER LINES

AetherEdge™Smart Metering→

AetherLink™Communication Modules→

AetherNexus™Data Concentrators & Gateways→

AetherSol™Solar Power Electronics→